We’ve been recognized! Openlayer is named a Representative Vendor in the 2026 Gartner® Market Guide for AI Evaluation and Observability Platforms.
As AI adoption scales, we’re proud to provide the unified governance and observability teams need to build trust.
Check out the blog for all the details: https://t.co/0wVslc2kyJ
December updates are live ❄️
New this month:
• Google ADK integration for multi-agent evals
• Openlayer on AWS, Azure & GCP marketplaces
• Expanded SQL + Snowflake testing
• Better monitoring controls + UI improvements
Full changelog ↓
🔗https://t.co/VSm655B7iA
November ’25 Changelog 🚀
Governance features are now available to all Openlayer customers. Define/enforce AI rules, require tests + monitoring, assign owners/risk levels, track evidence.
More updates inside.
Full changelog: https://t.co/rvBcQ5Q5E2
AI innovation means nothing without governance.
Openlayer gives you unified oversight across AI, linking evaluation, observability, and compliance in one view.
Build trust before you ship.🔗 https://t.co/NCQ4yqe9lv
🚀 October Changelog
New in Openlayer:
👥 Track users + sessions alongside traces
🏷️ Add tags to organize tests (agentic systems, safety, EU AI Act & more)
🛡️ Redact PII automatically with new guardrails
⚙️ Plus: Batch LLM calls, Python 3.13, improved docs
Full update → https://t.co/ozy6QER2xM
@_cgustavo@linear@raycast curious what processes others have in place for this, particularly if using conventional commits - anyone at team @linear have some wisdom to share?
We were tired of manually writing git commits for @linear issues. So I built a @raycast extension.
Simply copy the Linear issue ID → hit your hotkey → paste the commit message.
That's it!
Why build it?
We love how you can link Git commits to @linear issues. However, doing this while also following other best practices (like Conventional Commits) made writing commit messages painful.
For example, for a Linear issue with ID 'ENG-123' and title 'Some bug', we'd have to:
1. Type the commit type ('fix')
2. Copy the Linear issue ID from Linear
3. Paste it with 'closes' (or some other magic word) → 'fix(closes ENG-123):'
4. Copy the Linear issue title from Linear
5. Paste it → 'fix(closes ENG-123): Some bug'
6. Lowercase the first letter → 'fix(closes ENG-123): some bug'
We'd bounce between Linear and Terminal 3+ times, copying/pasting/editing until we got it right.
The team was rightfully complaining that the process was annoying. We even considered changing how we name Linear issues to minimize the number of edits.
That's why I built the @raycast extension!
Behind the scenes, the extension fetches the Linear issue with the specified ID using Linear's API and constructs the full commit command. The conventional commit type ('fix', 'chore', 'docs', etc.) is inferred from the Linear issue label.
The extension is private to the @openlayerco org, because it follows our commit message formatting, but hopefully you can build your own version of this!
Jericho Security scaled GenAI phishing simulations with confidence 🚀
With Openlayer they:
🔹 Kept outputs 95%+ compliant
🔹 Cut prompt iteration cycles by 50%
🔹 Saved 6+ months of engineering
Full case study 👉 https://t.co/sDbfepwlKw
August 2025 updates are live:
🎨 New UI + light/dark mode
📊 Direct Snowflake integration
🛡 Prompt injection detection
⚡ Priority levels for tests
dozens more upgrades → changelog (https://t.co/C2lCAgu1kW)
Chicago AI/ML leaders — join us Aug 7 for a private Topgolf night
🍸 Drinks & bites
🧠 10-min talk: “Catching GenAI failures before prod”
🎯 Good swings, better convos
🎟️ Space is limited → [Request Invite] 👇
https://t.co/EymmJUm1uS
From oversight gaps to daily audits. A Fortune 1000 market maker scaled from 1 to 10+ models and chose Openlayer over building in-house.
✅ 12+ months eng time saved
✅ Daily R² visibility
✅ 100% compliance coverage
Read more →
https://t.co/9dfwmi0fKM
Say hello to Emmett Nelson, Openlayer’s newest Account Exec! From AWS to Metaplane to Openlayer, he’s seen it all in AI/ML sales.
Why he joined, how he stays sharp, and his favorite 2025 photo 👇https://t.co/yXBX7xPunZ
📍We’re at the Databricks Data + AI Summit next week, come find us at Lounge F624!
🔥 swag and real talk on making GenAI & ML apps reliable and production-ready.
DM us or email [email protected] to connect.
#DataAISummit
We’re heading to @databricks#DataAISummit (June 9–12)! We’ll be on-site all week connecting with teams building GenAI & ensuring their AI systems are reliable + prod-ready. Booth info drops May 30. Swag? 🔥