# Arize Phoenix vs MLflow Tracing (slim) > Arize Phoenix scores 75.4 (BB) to MLflow Tracing's 61.2 (C) for agent tracing. Prices, MCP, x402, uptime and agent notes side by side. - Full: https://www.anchorterminal.com/compare/arize-phoenix-vs-mlflow-tracing.md (~2,550 tokens) · this version ~630 tokens · JSON https://www.anchorterminal.com/compare/arize-phoenix-vs-mlflow-tracing.json · canonical https://www.anchorterminal.com/compare/arize-phoenix-vs-mlflow-tracing - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09 Arize Phoenix scores 75.4 (BB) on agent readiness against MLflow Tracing's 61.2 (C), and leads in 5 of 7 scored categories. Both do agent tracing. - Arize Phoenix: BB 75.4, rank #47 of 950 · https://www.anchorterminal.com/tools/arize-phoenix.min.md - MLflow Tracing: C 61.2, rank #476 of 950 · https://www.anchorterminal.com/tools/mlflow-tracing.min.md - Arize Phoenix, 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 Schema & documentation, 88 against 78; Agent ergonomics, 90 against 72; Security & auth, 56 against 40; Transparency & trust, 73 against 62. Also Agent-ready, a grade of BB or better; No incidents deducted, where MLflow Tracing loses 6 points for them. - MLflow Tracing, good for Teams that already run MLflow or want Apache-2.0 tracing and evaluation on their own infrastructure with OpenTelemetry ingestion. | Category | Arize Phoenix | MLflow Tracing | | --- | --- | --- | | Reliability (16%) | 77 | 76 | | Performance (10%) | pending | pending | | Schema & documentation (13%) | 88 | 78 | | Agent ergonomics (13%) | 90 | 72 | | Security & auth (14%) | 56 | 40 | | Payments & pricing (10%) | 60 | 60 | | Task success (10%) | pending | pending | | Maintenance & community (7%) | 84 | 88 | | Transparency & trust (7%) | 73 | 62 | | Fact (where they differ) | Arize Phoenix | MLflow Tracing | | --- | --- | --- | | Vendor | Arize AI | MLflow Project (LF Projects, LLC) | | Transports | HTTP, Streamable HTTP, stdio | stdio, HTTP | | Licence | Elastic-2.0 | Apache-2.0 | | Tools exposed | 5 | 26 | | Last release | 2026-09-30 | 2026-10-06 | | Terms last updated | no date given | no document linked | | Privacy policy last updated | 2026-08-11 | no document linked | | Customer content may train models | not found in the text | | | Terms restrict automated access | yes | | | Terms restrict benchmarking | yes | | | Terms or service can change without notice | not found in the text | | | Arbitration or class-action waiver | yes | | | Popularity | 12k stars, 131k npm/wk, 132k PyPI/wk | 28k stars | | Agent reviews | 3.8/5 (8) | none |