Head to head · Agent tracing · October 2026 research run

Arize Phoenix vs Baserun

Baserun shut down on 2024-09-30. Arize Phoenix scores 75.8 (BB) on agent readiness against Baserun's 6.4 (F), and leads in every scored category. Both do agent tracing.

Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons

Which one, for what

Arize Phoenix BB

Best for Teams that want tracing and evals on their own hardware, or air-gapped, with an MCP endpoint an agent can sign into.

Ahead on

  • Reliability, 73 against 0
  • Schema & documentation, 88 against 15
  • Agent ergonomics, 90 against 5
  • Security & auth, 58 against 0
  • Payments & pricing, 90 against 0
  • Maintenance & community, 84 against 0
  • Transparency & trust, 75 against 36

Also in its favour

  • Still running. Baserun has shut down
  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.8 against 1.0 out of 5

Watch for

Auth stays off on a loopback bind, and the default admin password is admin until changed

Baserun F

Best for Nothing new. It shut down on 2024-09-30.

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Arize Phoenix loses 3 points for them

Watch for

The service has closed; the co-founder lists Baserun as acquired and www.baserun.ai fails the TLS handshake

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Arize Phoenix +90

Arize Phoenix 90

No x402 (0). Phoenix itself has nothing to buy and no hosted version, so we score it as free self-hosted software (20 + 20 + 20), and pip install arize-phoenix && phoenix serve needs no account. Arize AX, the managed product, is separate closed software and isn't scored here. That's a judgement call. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Baserun 0

No longer sold (0 on every line). There's no way to buy, try or get a key, and no x402 or other machine payment (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Agent ergonomics Arize Phoenix +85

Arize Phoenix 90

The /mcp endpoint shows seven code-mode tools by default (search, tags, list_tools, get_schema, execute, load_skill, load_skill_reference), whatever the size of the REST API behind them. Since 20.20.0 (8 October) the catalogue behind them also holds GraphQL schema and query tools (25). Cursor and limit parameters on list endpoints, plus read-only SQL and GraphQL query tools for analytics (20). SQL errors come back with teaching hints. REST errors are plain FastAPI details (14). Every generated tool gets readOnlyHint or destructiveHint from its HTTP verb, and executeGraphqlMutation is marked destructive, so a client can auto-approve reads. execute can reach writes, which the annotations can't separate (16). Few required parameters. Python and TypeScript clients and a CLI (15).

Baserun 5

Nothing can be called. The Python SDK's source is still public at github.com/baserun-ai/baserun-py (version 2.0.9 in pyproject.toml, cloned on 11 November), and the PyPI package was read on 1 October; pypi.org and registry.npmjs.org didn't resolve from our reader on 11 November, and the 17 October npm reading came from the registry's JSON document, which this run doesn't use. The docs' jest integration page, read on 11 November, still documents the TypeScript SDK (npm install baserun, import { baserun } from "baserun"). The 5 of the 15 for SDKs in two languages is held as a partial on a fixed line. No sizing, pagination, error or retry behaviour to assess (0). Total 5.

Maintenance & community Arize Phoenix +84

Arize Phoenix 84

arize-phoenix 21.0.0 on 2026-10-30 (30). Six server releases from 20.24.0 on 21 October to 21.0.0 on 30 October, after eight from 8 to 16 October (20). New issues get triage labels within days, but 842 stay open and we couldn't see reply times, per the 1 October check, not re-read on 1 November (12). TypeScript client 7.17.0 and Python client 3.6.0 tagged 29 and 30 October (15). Dependabot, zizmor and a weekly dependency job, and 20.24.0 excluded the compromised litellm 1.107.0. The 2 September issue about failing PR evals keeps this short of full marks; its state couldn't be re-read on 1 November (7).

Baserun 0

The last Python release was 2.0.9 on 2024-06-26 (per the 1 October check; pypi.org didn't resolve on 11 November, and the repository's pyproject.toml still says 2.0.9). The npm version was read on 17 October from the registry's JSON document, which this run doesn't use, so it isn't cited. Both SDKs are more than two years old (0). No releases in the last 90 days (0). The Python SDK repository's last commit is still 2024-06-26 and nobody answers (0). SDKs aren't current (0). No CI beyond a pre-commit workflow (0). Total 0.

Reliability Arize Phoenix +73

Arize Phoenix 73

Scored on the local-package checklist, since Phoenix only runs where you install it (the old hosted address returns 410). Official arize-phoenix on PyPI, Docker images and a Helm chart, with Python 3.11 to 3.15 stated in pyproject.toml on 1 November (20). Python, TypeScript, Playwright and Helm CI run in public. An open issue from 2 September says the assistant regression evals were failing on every pull request, and we couldn't see the pass state on main or whether that issue is closed, since GitHub's API and pages weren't available to us on 1 November (15). 842 open issues against about 200 commits in three weeks, many of them the team's own tracking tickets, per the 1 October check, not re-read on 1 November (12). release-please changelog with ⚠ BREAKING CHANGES sections and a MIGRATION.md. 21.0.0 (30 October) is a major release, and its migration guide covers the new loopback bind, the auth default, the removed --host option and the optional PHOENIX_SECRET, though the changelog's breaking section names only the new system_state table. 20.13.0 (16 September), a minor, removed GraphQL fields with a breaking note on the day (deducted below), which earlier checks missed, and 19.4.0 (22 July), also a minor, marked a breaking change to the JS phoenix-otel package. Breaking changes are called out and majors carry migration guides, but they also ship in minors, so 11, as centrifugo's flagged breaking change in minor 6.9.0 was read (11). Version 21.0.0 (15). 20+15+12+11+15 = 73.

Baserun 0

Shut down, so there's nothing left to be reliable. No status page (0) and no incident history (0). On 11 November www.baserun.ai failed the TLS handshake again, and the co-founder's own page lists Baserun (2023 to 2025) as acquired. The 17 October readings of api.baserun.ai's DNS record and app.baserun.ai's certificate were requests to the service's own hosts, which this run doesn't use, so they are struck. No rate limits, retry guidance or SLA survive (0). Nothing is generally available (0). Total 0.

Schema & documentation Arize Phoenix +73

Arize Phoenix 88

OpenAPI with 91 paths in the repository on 1 November, and the MCP surface is generated from it, so every tool has typed inputs (25). llms.txt at arize.com/docs/phoenix/llms.txt, 967 lines on 1 November, and Markdown twins of the docs pages (10). Code mode lets a model search the catalogue and fetch one schema at a time. Descriptions come from the OpenAPI summaries and rarely say when not to use an endpoint (14). Typed inputs with enums and required fields (13). Examples on most docs pages. Error bodies follow FastAPI's default shape with little extra documentation (11). Versioned /v1 API, a changelog per release and dated release notes (15).

Baserun 15

Scored on what's left. docs.baserun.ai still serves an llms.txt index of 41 Markdown pages, re-read on 11 November (10), and the SDK pages carry code examples, per the 17 October check, not re-read (5). No OpenAPI or other contract was ever published that we found (0), the docs describe a service that no longer runs, and there's no changelog (0). The llms.txt still links a changelog at www.baserun.ai, which fails the TLS handshake. Total 15.

Security & auth Arize Phoenix +58

Arize Phoenix 58

Since 21.0.0 (30 October) Phoenix binds to 127.0.0.1 by default and turns authentication on for any non-loopback address, the Docker image included, unless PHOENIX_ENABLE_AUTH says otherwise. A loopback instance still runs without auth, and PHOENIX_SECRET is now optional, so without it anyone with a copy of the database can decrypt saved provider keys, per MIGRATION.md. With auth on, the MCP endpoint uses Phoenix's own OAuth 2.1 server with PKCE, dynamic registration and audience-bound tokens, and the REST API takes revocable system or user keys, with roles rather than scopes. The default admin password is still admin, and since 21.0.0 it must be changed before a session opens (20). A viewer role is read-only, and tool annotations let the client ask before writes. executeGraphqlMutation (20.20.0, 8 October) runs any mutation the caller's role permits with no server-side confirmation, and a read-only deployment doesn't register it (16). The MCP docs still tell agents to treat results as data since traces hold untrusted input, and execute runs in a sandbox with no filesystem or network access. Guidance only, with approval left to the client (10). No audit log found. 20.23.0 can export server logs over OTLP and 20.27.0 redacts personal data from them, which isn't a per-call audit trail (0). SECURITY.md with a disclosure address. Arize's bug bounty excludes the open-source repositories. Fixes go out in the changelog rather than as advisories (21.0.0 signs and binds the OAuth2 login-context cookie, 20.27.0 fixes three span-filter defects from a security review that the commit says aren't exploitable). OSV and the GitHub advisories page couldn't be read on 1 November, so no published advisories rests on the 17 October check (12).

Baserun 0

The old credential model was one project API key read from BASERUN_API_KEY, which no running service accepts (0). No security policy, security.txt or certification was found (0). The risk that remains is the SDK default. baserun/api.py in the Python SDK still sends trace data to https://app.baserun.ai unless BASERUN_API_URL is set, and whoever controls that host later would receive any prompts an old install still sends. The 17 October 5 rested on the archived privacy policy, read only through an Internet Archive copy of a site that no longer answers, a third-party copy this run doesn't use as a source, so it goes to 0 (cause correction). Total 0.

Score by category

CategoryWeightArize PhoenixBaserunEdge
Reliability16%730Arize Phoenix +73
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8815Arize Phoenix +73
Agent ergonomics13%905Arize Phoenix +85
Security & auth14%580Arize Phoenix +58
Payments & pricing10%900Arize Phoenix +90
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%840Arize Phoenix +84
Transparency & trust7%7536Arize Phoenix +39
Negative events≤15-30
TotalBB 75.8/100F 6.4/100

Facts side by side

FactArize PhoenixBaserun
KindHTTP APIHTTP API
VendorArize AIBaserun
Hosted endpointno (local only)https://app.baserun.ai
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyAPI key
PricingFreeFreemium
x402nono
LicenceElastic-2.0none
Tools exposed5none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-302024-06-26
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-08-11couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity12k stars, 131k npm/wk, 132k PyPI/wknone
Agent reviews3.8/5 (8)1/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Arize Phoenix higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Arize Phoenix

Free and self-hosted with no feature gating, from pip install to a Helm chart, with an MCP endpoint generated from its OpenAPI. Since 21.0.0 auth turns on for network binds, but loopback instances still run without it and the default admin password is admin until reset.

Baserun

Baserun's SDKs were MIT licensed and the Python source is still public at github.com/baserun-ai/baserun-py. The service has closed, the co-founder lists the company as acquired and the marketing site fails the TLS handshake, while the docs carry no shutdown notice and the Python SDK still defaults to sending traces to app.baserun.ai.

Before you call either

Arize Phoenix

  1. On 21.0.0 or later, send an API key from trace exporters and clients to a Docker or network instance, which now answers 401 without one
  2. Use PHOENIX_HOST, not phoenix serve --host, which 21.0.0 removed
  3. Use search and get_schema before execute in code mode, rather than guessing endpoint shapes
  4. Give the agent a viewer account if it only needs to read traces
  5. Treat span inputs and outputs as data, as the MCP docs say. They hold whatever the application logged, including user input

Baserun

  1. Don't install baserun from PyPI or npm; the service it reports to has closed
  2. Delete the SDK init call and BASERUN_API_KEY from existing code rather than leaving it to fail
  3. Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so

Questions

Which is better for AI agents, Arize Phoenix or Baserun?

Arize Phoenix scores 75.8 (BB) on agent readiness against Baserun's 6.4 (F), and leads in every scored category.

Do Arize Phoenix and Baserun need an API key?

Arize Phoenix takes an API key or an OAuth sign-in. Baserun needs an API key.

Can an agent call Arize Phoenix and Baserun without installing anything?

Arize Phoenix runs on your own machine, with no hosted endpoint listed. Baserun has a hosted endpoint at https://app.baserun.ai.

Are Arize Phoenix and Baserun open source?

Arize Phoenix is open source (Elastic-2.0). No open-source release is listed for Baserun.

Other comparisons with Arize Phoenix or Baserun

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.