AI Observability
Braintrust
Braintrust evaluates and traces AI apps and agents. Dataset experiments and scorers test prompt and model changes, plus code, before release. Production tracing and online scoring, plus Topics, track results afterward. It runs in Braintrust's US or EU cloud, or, on Enterprise, with a data plane in your own cloud.
The 30-Second Take
Pick Braintrust if evals should gate every prompt, model and code change.
A failing production trace becomes a dataset example that code, an LLM judge or a person scores every later change against. Dropbox blocks merges on about 150 judged queries per pull request.
- Best fit
- Product teams shipping LLM features that want evals to gate every prompt and model change.
- Main constraint
- Braintrust charges per gigabyte ingested and per score recorded, and nothing caps the total. BYOC and self-hosting require Enterprise.
- First move
- Instrument one feature on Starter. Build a ten-example dataset from real traces and run it in CI on every pull request.
Why
Watch the keys: in May 2026 an attacker reached a backup holding decrypted provider keys, and 30 customers reported suspicious key use. Connect providers through short-lived credentials and set spend alerts, since nothing caps the bill.
32 practitioners, 73 sources reviewed, Updated Oct 30, 2026How this is measured
- Operating stack
- AI Application Platform
Comparisons
How does Braintrust compare with the alternatives?
Braintrust vs LangSmith
- AI Observability
On Parlance Labs' 100 production traces, Braintrust Loop found the most failures and LangSmith Engine too few to score. Pick Braintrust for evals many people review, US$474 a month at 200,000 traces in GILD's calculation; pick LangSmith to host LangGraph agents too.
Braintrust vs Langfuse
- AI Observability
CREATE SOMETHING retired Braintrust for Langfuse in July 2026. Pick Langfuse to self-host its MIT-licensed core free; at 200,000 traces a month GILD's calculation puts Langfuse Pro at US$369 and Braintrust Pro at US$474. Pick Braintrust for a managed eval product whose data plane runs in your cloud only on Enterprise.
Braintrust vs Arize
- AI Observability
On Parlance Labs' 100 production traces, Braintrust Loop caught the most failures and 91% of Arize Alyx's flags were valid. Pick Arize to self-host free on Phoenix; pick Braintrust for Pro overage rates you can price, US$474 a month at 200,000 traces in GILD's calculation.
Operator Insights
What are teams learning from building on Braintrust and running it in production?
Brian XuEngineer, Agents teamRox
Rox's Agents team, which runs its production agent traces through Braintrust and reviews a weekly pull request of new evals. Rox published the post in partnership with Cognition and Braintrust.
Rox engineering blog, published Read the write-up (opens Rox engineering blog in a new tab)
Observation
Rox has Devin turn about 350 production conversations a week from Braintrust traces into evals. The first sweep covered 67 behaviors, where 142 hand-written evals had covered 34.
- Takeaway
- Build the eval suite from production traces, and read every failing verdict before you trust it, because agent runs vary.
- What happened
- Each week Devin pulls about 350 conversations from Braintrust, labels them, builds evals with synthetic data in per-branch environments and opens a pull request the team reviews (Rox, Oct 14, 2026). Before the first sweep Rox had 142 hand-written evals covering 34 behaviors; the first sweep's suite covered 67 behaviors and 72% of conversations in each of the next two weeks. About 1 in 8 evals passes some runs and fails others with no code change, and in 36 of 40 failing verdicts the team reviewed, the judge applied its criterion correctly. Production bugs now show up as failing evals in that week's pull request.
“Every week, Devin, the coding agent from Cognition, reads real conversations on Rox from our production traces in Braintrust, turns them into evals, and opens a pull request that we review.”
Brian Xu - Public engineering write-up
- Team metrics reported
Deployment details
Rox's Agents team, which runs its production agent traces through Braintrust and reviews a weekly pull request of new evals. Rox published the post in partnership with Cognition and Braintrust.
- Public engineering write-up
- Team metrics reported
- Team
- Rox Agents team
- Duration
- Weekly sweeps, with two weeks measured after the first
- Workload
- Evals for Rox's production agent, written by Devin from Braintrust traces
- Product version
- Braintrust tracing, read by a Devin skill
- Measurement
- 67 behaviors covered against 34; 72% of conversations covered; 36 of 40 failing verdicts applied correctly
createsomethingtodayMaintainer, create-something-monorepoCREATE SOMETHING
CREATE SOMETHING's monorepo of MCP services, Dify agents, evals and telemetry.
GitHub, createsomethingtoday/create-something-monorepo, published Read the write-up (opens GitHub, createsomethingtoday/create-something-monorepo in a new tab)
Observation
CREATE SOMETHING left Braintrust for Langfuse across its evals and telemetry, then reran its eval suites on Langfuse with none failing.
- Takeaway
- Keep scorers and suites in your own repository, so a platform change is a rerun of the same suites on the new backend.
- What happened
- A pull request merged Jul 6, 2026 replaced every active Braintrust eval, telemetry, package, script, environment and workflow surface with Langfuse equivalents, and archived the Braintrust artifacts as internal history. Its validation ran the MCP and Dify eval sets on Langfuse, 9 suites each with 0 failed. The pull request does not say why the team left.
- Public engineering write-up (GitHub pull request)
- Team metrics reported
Deployment details
CREATE SOMETHING's monorepo of MCP services, Dify agents, evals and telemetry.
- Public engineering write-up (GitHub pull request)
- Team metrics reported
- Team
- CREATE SOMETHING maintainers
- Workload
- Evals and telemetry for MCP services and Dify agents
- Product version
- Braintrust evals and SDK telemetry, replaced by Langfuse
- Measurement
- 9 eval suites rerun on Langfuse with 0 failed, for each of two eval sets
Buying and deployment
What a team building on it should verify before production traffic grows.
Sourced from Braintrust documentation
Signals
What is the current evidence saying about Braintrust?
Named teams at Dropbox, Fintool, Rox, Notion and Zapier gate releases on Braintrust experiments, and Parlance Labs found its Loop agent caught the most failures on 100 production traces. Builders report SDK problems, and some left for Langfuse or their own tools. Each finding links to its public sources.
Practitioner sentiment, teams and leaders
+50 Strong positive net
of 34 sources that take a side, each author counted once.
How this figure is madeCurrent sentiment
Positive, mixed and negative sources
The score counts them as 19 positive, 10 mixed and 3 negative votes, one per author.
Team accounts lean positive: of the 34 team and leadership sources that give an opinion, 20 are positive, 11 mixed and 3 negative. Evaluation draws the most praise. Seven of 8 discussing trace-level debugging praise it. All 6 discussing SDK or ingestion reliability report problems. Teams also weigh building their own eval workflow. Platform decisions run 12 to 3 in favor of keeping or choosing Braintrust.
Run a pilot on one production app to measure which failures it surfaces and how long tracing them takes.
Evidence field. All 73 sources, one mark each.
Arrange by
Each mark is one source: positive, mixed, negative, no opinion stated, or documentation (not counted).
| Group | Sources | Positive | Mixed | Negative | No opinion stated and not counted in the score | Documentation, checked and not counted |
|---|---|---|---|---|---|---|
| Positive | 20 | 20 | 0 | 0 | 0 | 0 |
| Mixed | 11 | 0 | 11 | 0 | 0 | 0 |
| Negative | 3 | 0 | 0 | 3 | 0 | 0 |
| Not counted | 7 | 0 | 0 | 0 | 7 | 0 |
| Documentation | 14 | 0 | 0 | 0 | 0 | 14 |
| Outside this group | 18 | 7 | 6 | 4 | 1 | 0 |
| Quarter | Sources |
|---|---|
| Q2 2025 | 7 |
| Q3 2025 | 3 |
| Q4 2025 | 6 |
| Q1 2026 | 11 |
| Q2 2026 | 7 |
| Q3 2026 | 19 |
| Q4 2026 | 6 |
| Documentation, checked | 14 |
By sentiment
14 documentation pages check facts and are not counted; 18 sit outside this group.
Hover a mark for a quick look, click it or press Enter to open its source.Tap a mark to open its source, then step to its neighbors with Previous and Next.
What practitioners praise
Top praise of 3. Each mark is a source on it; filled marks praise it.
Most common concerns
Top concern of 2. Each mark is a source on it; filled marks raise it.
All 73 sources behind these findings
- Braintrust ruled out because self-hosting is Enterprise onlyCollectionPure7752, Reddit user, r/mlops (self-described: An early-stage team replacing Langfuse after letting non-engineers edit prompts), Reddit post, published Oct 22, 2026
- Living Evals: an eval suite that grows from productionBrian Xu, engineer on the Agents team at Rox (self-described: Rox's Agents team, with Devin writing evals from Braintrust production traces each week), Engineering blog post, Rox, published Oct 14, 2026
- Arize, Langfuse and Braintrust all intimidating at firstGanesh Iyer, AI payments builder and creator of the Nura family assistant (self-described: Tried the observability tools for his own agents), Post on X, published Oct 13, 2026
- Plans and limitsBraintrust (Official), Product documentation, checked Oct 12, 2026
- Billing FAQBraintrust (Official), Product documentation, checked Oct 12, 2026
- Monitor usageBraintrust (Official), Product documentation, checked Oct 12, 2026
- Configure data retentionBraintrust (Official), Product documentation, checked Oct 12, 2026
- Deployment optionsBraintrust (Official), Product documentation, checked Oct 12, 2026
- ArchitectureBraintrust (Official), Product documentation, checked Oct 12, 2026
- SecurityBraintrust (Official), Product documentation, checked Oct 12, 2026
- Protect sensitive dataBraintrust (Official), Product documentation, checked Oct 12, 2026
- ExperimentsBraintrust (Official), Product documentation, checked Oct 12, 2026
- Run experiments in CI/CDBraintrust (Official), Product documentation, checked Oct 12, 2026
- Score production tracesBraintrust (Official), Product documentation, checked Oct 12, 2026
- Trace LLM callsBraintrust (Official), Product documentation, checked Oct 12, 2026
- Send OpenTelemetry traces and logsBraintrust (Official), Product documentation, checked Oct 12, 2026
- Use the Braintrust GatewayBraintrust (Official), Product documentation, checked Oct 12, 2026
- feat(observability): Braintrust refuse-to-enable until compliance affirmed (audit C2/H7)mdenner1234, Developer (pull request author) (self-described: Tech Fleet network, member Q&A assistant), GitHub pull request, published Oct 10, 2026
- feat(evals): link Braintrust experiments to their CI run and the PRMatt Rossman (mattrossman), AI tooling at Supabase (self-described: Supabase evals repository, experiments run from GitHub Actions), GitHub pull request, published Oct 8, 2026
- Remove the Braintrust integrationdealvz, Developer (pull request author) (self-described: GoodParty.org omni platform: chat, briefings, PMF runner), GitHub pull request, published Oct 5, 2026
- Used Braintrust and did not enjoy it, built custom evals insteadOmrinachmani, Reddit user, r/LangChain (self-described: A developer running custom offline observability and evals after trying Braintrust), Reddit comment, published Sep 27, 2026
- Question: why does a self-hosted deploy's daemon contact www.braintrust.dev on cold start?LuizNascimentoTR, Developer (issue author) (self-described: Team running a self-hosted Braintrust deployment), GitHub issue, published Sep 25, 2026
- chore(eval-tests): upgrade eval deps, weekly evals, standalone Braintrust CLI CLOUDP-450203Nima Taheri (nima-taheri-mongodb), Contributor to MongoDB's MCP server (self-described: MongoDB MCP server, eval tests in CI), GitHub pull request, published Sep 25, 2026
- Remove Braintrust reporting and implicit judge gateway integrationaviggiano, Developer (issue author) (self-described: Ultrafuzz, Monad developers' fuzzing project), GitHub issue, published Sep 22, 2026
- Braintrust LLM observability: spans for every model call, off by defaultpunitarani, Developer (pull request author) (self-described: Personal research project calling models through OpenRouter), GitHub pull request, published Sep 21, 2026
- AI Evals: Everything You Need to KnowHamel Husain, AI evals consultant and course instructor (self-described: Advising client teams on eval tooling and vendor selection), Personal blog post, hamel.dev, published Sep 18, 2026
- feat: trace simulations to Braintrust instead of the GigaFlow SDKgiga-james, Developer (pull request author) (self-described: GigaFlow, tau2 agent simulations), GitHub pull request, published Sep 17, 2026
- feat(homelab): tail-sample LLM traces into Braintrust and repoint birmelshepherdjerred, Developer (pull request author) (self-described: Homelab services with an OpenTelemetry gateway), GitHub pull request, published Sep 10, 2026
- The same evals score production traffic, not only experimentsCheap-Ad-2360, Reddit user, r/LangChain (self-described: A team scoring production traffic with its release evals), Reddit comment, published Sep 9, 2026
- FunctionCall tool-span instrumentation for Agno leaks the full Agent/Team object (incl. model.api_key) into span metadatapaulosuzart, Developer (issue author) (self-described: Team tracing Agno agents with MCP tools), GitHub issue, published Sep 3, 2026
- Eval::Runner's per-case force_flush adds 10-25s+ per case even when no scorer/classifier uses trace:satanas, Developer (issue author) (self-described: Ruby eval suite), GitHub issue, published Aug 19, 2026
- Our PM runs prompt changes against the dataset without an engineerLow_Dust_9566, Reddit user, r/mlops (self-described: A team whose product manager changes prompts and reviews regressions), Reddit comment, published Aug 19, 2026
- Flue adapter: logging the full conversation-so-far per turn makes background-logger retention O(turns²), OOMs 128 MB Workers isolatesdknecht, Developer (issue author) (self-described: Production agent on Cloudflare Workers Durable Objects), GitHub issue, published Aug 11, 2026
- Migrate ThoughtForm observability to Langfuseadambelton, Developer (pull request author) (self-described: ThoughtForm, a personal app with five runtime prompts), GitHub pull request, published Aug 7, 2026
- The best evals we've written came from production failuresDisastrous_Injury561, Reddit user, r/mlops (self-described: A team that turns odd production traces into regression tests before each model upgrade), Reddit post, published Aug 5, 2026
- Back model benchmark with Braintrust, drop in-house scoringtime-attack, Developer (pull request author) (self-described: GStack model benchmark driving Claude, Codex, and Gemini CLI agents), GitHub pull request, published Jul 21, 2026
- feat(evals): bump braintrust to 3.x; first-party BraintrustSpanProcessor OTEL sinkMiguel (miguelg719), Contributor to Browserbase's Stagehand evals (self-described: Browserbase Stagehand, browser-agent evals), GitHub pull request, published Jul 13, 2026
- Auto-evals: Braintrust Loop, Arize Alyx and LangSmith on the same 100 tracesAntaripa Saha and Hamel Husain, Parlance Labs (self-described: 100 hand-labelled traces from a production apartment-leasing assistant), Independent evaluation, Parlance Labs blog, published Jul 11, 2026
- Retire Braintrust for Langfusecreatesomethingtoday, Developer (pull request author) (self-described: Create Something monorepo: evals, telemetry, prompts, and MCP services), GitHub pull request, published Jul 6, 2026
- How Braintrust uses AI agents, evals, and CI to ship better softwareAnkur Goyal, founder and CEO of Braintrust, on How I AI with Claire Vo (self-described: Braintrust's own engineering team, using coding agents, evals and CI), Podcast episode, How I AI, published Jun 15, 2026
- feat(photo-curation): local eval store + runner (replace Braintrust write path)julianken, Developer (issue author) (self-described: Photo-judge eval for a personal bird-sighting system), GitHub issue, published Jun 12, 2026
- Standalone-api / brainstore v2.1.1 ships starlette < 1.0.1 (CVE-2026-48710)joel-vaz, Developer (issue author) (self-described: Self-hosted data plane on the Helm chart), GitHub issue, published May 28, 2026
- Combine Skills and MCP to Close the Context GapPedro Rodrigues, AI tooling engineer, Supabase (Supabase testing coding agents with its MCP server and Agent Skills), Conference talk with transcript, AI Engineer Europe 2026, published May 15, 2026
- Shipping complex AI applications: Braintrust & TrainlineOussama Hafferssas and Mayank Soni, Engineers at Trainline (self-described: Trainline travel assistant: refunds, train changes, and handover to support), Conference talk (co-presented with Braintrust), AI Engineer Europe 2026 (YouTube), published May 1, 2026
- Replacing 12K LoC with a 200 LoC SkillDavid Gomes, Engineer on coding agents, Cursor (Cursor team replacing its worktree feature with an agent skill), Conference talk with transcript, AI Engineer Europe 2026, published Apr 30, 2026
- feat(observability): replace Arize with Braintrust OTel + exact wire logging via Finch telemetryBlueHotDog, Developer (issue author) (self-described: Frontman, agent platform on Elixir), GitHub issue, published Apr 10, 2026
- setup_adk() does not trace tool calls in nested sub-agentssm-stripe, Developer (issue author) (self-described: Google ADK pipeline with nested sub-agents), GitHub issue, published Mar 24, 2026
- Comment on: Ask HN: How are people doing AI evals these days?mierz00, Hacker News commenter (self-described: Team using an LLM for classification), Hacker News comment, published Mar 17, 2026
- Comment on: Ask HN: How are people doing AI evals these days?mierz00, Hacker News commenter (self-described: Team using an LLM for classification), Hacker News comment, published Mar 11, 2026
- Regular 500 responses from /logs3CodingCanuck, Developer (issue author) (self-described: Team eval pipeline on the TypeScript SDK), GitHub issue, published Feb 27, 2026
- Significant latency regression between TypeScript SDKs v0.4.10 and v1.0.0CodingCanuck, Developer (issue author) (self-described: Team eval pipeline on the TypeScript SDK), GitHub issue, published Feb 19, 2026
- chore(sc-41159): Add Braintrust evaluation cronjob infrastructureyodem, Developer (pull request author) (self-described: Sefaria, AI chatbot in production), GitHub pull request, published Feb 4, 2026
- Lessons from Building AI Agents for Financial ServicesNicolas Bustamante, Founder of Fintool (Fintool, AI agents for financial research and equity analysis), Personal blog post, nicolasbustamante.com, published Jan 24, 2026
- Remote Evals (examples and support)gabe-kent, Developer at a Braintrust customer (issue author) (self-described: Customer organization with a main Rails app), GitHub issue, published Jan 13, 2026
- Comment on: Ask HN: Where are you keeping your LLM logs?barbazoo, Hacker News commenter (self-described: Hacker News thread: Where are you keeping your LLM logs?), Hacker News comment, published Jan 9, 2026
- feat: implement remote Braintrust evals for all HolmesGPT testsaantn, Maintainer (pull request author) (self-described: HolmesGPT, an open-source SRE agent, with about 53 LLM evals), GitHub pull request, published Jan 3, 2026
- LangFuse Telemetry not working, switch to Braintrustfyang0507, Developer (issue author) (self-described: Personal Notion agent, CLI and Next.js app), GitHub issue, published Jan 1, 2026
- Migrate to Braintrust-native eval frameworkNick Sullivan (TechNickAI), Builder at Carmenta Collective (self-described: Carmenta, evals for model routing and file handling), GitHub pull request, published Dec 11, 2025
- Ask HN: What do u use for agent/agentic evals?hhthrowaway1230, Hacker News commenter (self-described: Evaluating agents), Hacker News post, published Nov 25, 2025
- Node.js SDK has broken/bad bundlingai-simple-ai, Developer (issue author) (self-described: Team patching the SDK locally), GitHub issue, published Nov 20, 2025
- BOLT - How Mura wrote an in-house LLM Eval FrameworkJames Mackey, Co-founder of Mura (self-described: Mura, seed-stage startup automating billing for commercial HVAC providers), Engineering blog post, James's Newsletter (Substack), published Oct 21, 2025
- A practical blueprint for evaluating conversational AI at scaleRanjitha Gurunath Kulkarni, Ameya Bhatawdekar, and Gonzalo Garcia, Dropbox Dash engineers (Dropbox Dash, a conversational AI search product), Engineering blog post, Dropbox Tech blog, published Oct 2, 2025
- Selecting The Right AI Evals ToolHamel Husain, AI evals consultant and course instructor (self-described: Three-person panel that watched LangSmith, Braintrust, and Arize Phoenix complete the same eval assignment), Independent evaluation, hamel.dev, published Oct 1, 2025
- Evals your LLM driven Agents (Experiments and Lessons Learned) with BraintrustAIForOver50Plus, Reddit user, r/LLMDevs (self-described: Weekend experiments with an email management agent), Reddit post, published Sep 28, 2025
- If you log a span instance, your API key is included in the logAustin Tackaberry (austintackaberry), Co-founder and CTO at Levenza (self-described: Levenza, logging with the Braintrust TypeScript SDK), GitHub issue, published Sep 7, 2025
- Evals Are Not Unit TestsIdo Pesok, engineer on v0, Vercel (Vercel v0 team running evals in CI and on a daily schedule), Conference talk with transcript, AI Engineer World's Fair 2025, published Aug 6, 2025
- Turning Fails into Features: Zapier's Hard-Won Eval LessonsRafal Wilinski, Tech Lead for Zapier Agents, with Vitor Balocco (Zapier Agents team comparing models on Braintrust experiments), Conference talk with transcript, AI Engineer World's Fair 2025, published Jun 30, 2025
- How to build world-class AI products: Sarah Sachs (AI lead @ Notion) & Carlos Esteban (Braintrust)Sarah Sachs, Engineering lead, AI modeling, at Notion (self-described: Notion AI team: engineers, data specialists, PMs and designers), Conference talk (co-presented with Braintrust), AI Engineer World's Fair 2025 (YouTube), published Jun 27, 2025
- The Web Browser Is All You NeedPaul Klein IV, Founder and CEO, Browserbase (Browserbase, browser infrastructure for AI agents), Conference talk with transcript, AI Engineer World's Fair 2025, published Jun 20, 2025
- Ask HN: What tools are you using for AI evals? Everything feels half-bakedfazlerocks, Hacker News commenter (self-described: Team running LLMs in production for content generation, customer support, and code review assistance), Hacker News post, published Jun 5, 2025
- test(max): Migrate insight deepevals to BraintrustMichael Matloka (Twixes), Engineer at PostHog (self-described: PostHog Max AI, evals for generated insight queries), GitHub pull request, published May 6, 2025
- Review of BraintrustHowie Liu, Product Hunt reviewer, Airtable (self-described: Airtable AI Assistant), Product Hunt review, published Apr 9, 2025
- Unit-testing AI agents in the browserAnirudh Kamath and Sean McGuire, Browserbase Stagehand team (self-described: Stagehand browser-agent SDK, model comparison on its eval suite), Engineering blog post, Browserbase blog, published Apr 9, 2025
Apr 2025 to Oct 2026.
59 sources from practitioners, by month and sentiment.
Where It Fits
Where does Braintrust belong in the stack?
Braintrust is Core across Evaluate and Operate, supports Model and Build, and touches Data.
- Business area
- Product & Engineering
- Function
- Software Development
- Operating stack
- AI Application Platform
- Primary role
- AI Evaluation & Observability
Model
Model APIs: Touches
Model APIs, touches. Braintrust's built-in models serve playgrounds and scorers, plus Topics and Loop, using monthly model credits. Applications access production models through OpenAI, Anthropic, Google, and the other providers Braintrust records.
Model gateway: Supports
Model gateway, supports. Braintrust Gateway exposes providers through one OpenAI-compatible API with caching and logging. Self-hosted data planes can run it. The hosted Gateway has no SLA and is not generally available, so production routing remains with a dedicated gateway.
Build
Orchestration: Touches
Orchestration, touches. Braintrust traces agents built with LangGraph, the Vercel AI SDK, the OpenAI Agents SDK, the Claude Agent SDK, CrewAI, and other frameworks. It has no agent framework of its own.
Tool use: Supports
Tool use, supports. Braintrust records tool calls and hosts tool and scorer functions that models invoke. Coding agents query logs and experiments through its MCP server. The application's framework owns tool execution.
Data
Retrieval: Touches
Retrieval, touches. Braintrust traces and scores retrieval, including whether an answer uses the retrieved context. The application embeds and indexes its documents and stores them elsewhere.
Evaluate
Evaluation: Core
Evaluation, core. Braintrust tests changes through datasets and experiments in code, the UI, or CI. Teams compare runs side by side using code and LLM scorers, plus human review and playgrounds.
Operate
Observability: Core
Observability, core. SDKs in six languages and OpenTelemetry send traces to Brainstore. Teams search logs and score production traffic there. Topics groups the logs, and SQL thresholds trigger alerts.
Cloud deployment: Touches
Cloud deployment, touches. Braintrust versions and serves prompts and runs its own functions. Enterprise data planes can run in your cloud. Braintrust supplies no application hosting or model capacity.
Guardrails: Touches
Guardrails, touches. Braintrust online scoring runs scorers automatically on production logs for quality and safety analysis. It evaluates recorded conversations and does not sit in the request path to block them.
Market mapThe layers Braintrust covers, and who else owns each one.
Evaluation & testing
Observability & tracing
Model gateways & routing
- LiteLLM
- OpenRouter
- Portkey
- Vercel AI Gateway
Tool use & integrations
Model APIs
4 more layers on the full map. Core, Supports and Touches describe coverage. They say nothing about quality.
Models
Which models run in Braintrust?
The current releases GILD tracks that public sources record running in Braintrust. Each model's page charts its public benchmark scores.

