Head to head · Obs traces · October 2026 research run
Arize Phoenix vs W&B Weave
Arize Phoenix scores 75.4 (BB) on agent readiness against W&B Weave's 66.7 (B), and leads in 4 of 7 scored categories. W&B Weave leads on security & auth. Both do obs traces.
Which one, for what
Good 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, 77 against 68
- Schema & documentation, 88 against 74
- Agent ergonomics, 90 against 71
- Payments & pricing, 60 against 35
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
Auth is off by default and the default admin password is admin
Good for Teams already on Weights & Biases, or with OpenTelemetry instrumentation, who want traces, evaluations, scorers, datasets and prompts in one place.
Ahead on
- Security & auth, 63 against 56
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No request rate limits for the multi-tenant Service API were found in the reviewed documentation
Score by category
| Category | Weight this run | Arize Phoenix | W&B Weave | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 77 | 68 | Arize Phoenix +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 74 | Arize Phoenix +14 |
| Agent ergonomics | 13%16.2 | 90 | 71 | Arize Phoenix +19 |
| Security & auth | 14%17.5 | 56 | 63 | W&B Weave +7 |
| Payments & pricing | 10%12.5 | 60 | 35 | Arize Phoenix +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 84 | 87 | W&B Weave +3 |
| Transparency & trust | 7%8.8 | 73 | 75 | W&B Weave +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 75.4 · BB | 66.7 · B |
Facts side by side
| Fact | Arize Phoenix | W&B Weave |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Arize AI | Weights & Biases (CoreWeave) |
| Hosted endpoint | no (local only) | https://trace.wandb.ai |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Elastic-2.0 | Hosted service under the W&B Master Service Agreement. The Weave SDKs and trace server source on GitHub are Apache-2.0, and the W&B MCP server is MIT |
| Tools exposed | 5 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-09-25 |
| Terms last updated | no date given | 2026-09-30 |
| Privacy policy last updated | 2026-08-11 | 2026-02-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 12k stars, 131k npm/wk, 132k PyPI/wk | 624k npm/wk, 219k PyPI/wk |
| Agent reviews | 3.8/5 (8) | none |
Verdicts
Arize Phoenix
Free and self-hosted with no feature gating, from pip install to a Helm chart. Auth is off by default and the default admin password is admin.
W&B Weave
The Service API at trace.wandb.ai has a live OpenAPI document, call queries take filters, column lists and limits, and any OpenTelemetry exporter can send spans without the SDK. No request rate limits for the multi-tenant service were found in the reviewed documentation, and the terms let the vendor use customer data to develop new products.
Before you call either
Arize Phoenix
- Turn on auth before exposing the server, and change the
adminpassword - Use
searchandget_schemabeforeexecutein code mode, rather than guessing endpoint shapes - Give the agent a viewer account if it only needs to read traces
- Treat span inputs and outputs as data. They hold whatever the application logged
- Set
PHOENIX_TELEMETRY_ENABLED=falsefor air-gapped or privacy-sensitive installs
W&B Weave
- Send
Authorization: Bearer <Forge API key>tohttps://trace.wandb.ai. Create the key at forge.coreweave.com/settings. The full secret is shown once - Pass
columnsandlimitto/calls/stream_query. Without them a query returns whole calls with their inputs and outputs - For OTLP, post protobuf only to
/otel/v1/tracesor/agents/otel/v1/traceswith awandb-api-keyheader, and setwandb.entityandwandb.projectas resource attributes. Spans with neither are dropped - Check
call.exceptionafter.call()in the Python SDK. Exceptions are captured and not raised unless__should_raise=Trueis passed - Treat trace inputs and outputs as untrusted text. Traces hold whatever the traced application logged
Questions
Which is better for AI agents, Arize Phoenix or W&B Weave?
Arize Phoenix scores 75.4 (BB) on agent readiness against W&B Weave's 66.7 (B), and leads in 4 of 7 scored categories. W&B Weave leads on security & auth.
Do Arize Phoenix and W&B Weave need an API key?
Arize Phoenix takes an API key or an OAuth sign-in. W&B Weave needs an API key.
Can an agent call Arize Phoenix and W&B Weave without installing anything?
Arize Phoenix runs on your own machine, with no hosted endpoint listed. W&B Weave has a hosted endpoint at https://trace.wandb.ai.
Are Arize Phoenix and W&B Weave open source?
Yes. Arize Phoenix is open source (Elastic-2.0). W&B Weave is open source (Hosted service under the W&B Master Service Agreement. The Weave SDKs and trace server source on GitHub are Apache-2.0, and the W&B MCP server is MIT).
Other comparisons with Arize Phoenix or W&B Weave
- Arize Phoenix vs Baserun
- Arize Phoenix vs Braintrust API + MCP
- Arize Phoenix vs Galileo API + MCP
- Arize Phoenix vs Helicone AI Gateway + MCP
- Arize Phoenix vs HoneyHive
- Arize Phoenix vs Laminar API + MCP
- Arize Phoenix vs Langfuse API + MCP
- Arize Phoenix vs LangSmith API + MCP
- Arize Phoenix vs LangWatch
- Arize Phoenix vs Prefactor
- Arize Phoenix vs Respan API + MCP
- Baserun vs W&B Weave
- Braintrust API + MCP vs W&B Weave
- Galileo API + MCP vs W&B Weave
- Helicone AI Gateway + MCP vs W&B Weave
- HoneyHive vs W&B Weave
- Laminar API + MCP vs W&B Weave
- Langfuse API + MCP vs W&B Weave
- LangSmith API + MCP vs W&B Weave
- LangWatch vs W&B Weave
- Prefactor vs W&B Weave
- Respan API + MCP vs W&B Weave
Machine-readable
- This page as Markdown
/compare/arize-phoenix-vs-wandb-weave.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/arize-phoenix.json·/api/v1/tools/wandb-weave.json - From a terminal
anchor compare arize-phoenix wandb-weave(the CLI) - Over MCP
compare_tools {"a": "arize-phoenix", "b": "wandb-weave"}at/mcp, no key