Skip to main content
Comparison

Logfire vs Arize AX

Both provide AI observability but differ in scope. Arize AX monitors your AI layer, while Logfire covers your entire application in one trace: LLM calls, database queries, APIs, and frontend. When agents fail in production, you see the complete picture, not just what happened inside the model. Arize offers two products: Phoenix, an open source tool for LLM tracing and evaluation, and Arize AX, a commercial SaaS platform for ML and AI monitoring. This page compares Logfire against Arize AX.

Feature comparison

Quick comparison

Logfire and Arize AX compared feature by feature
Feature Logfire Arize AX
Observability scope Full-stack (AI + databases, APIs, infra) AI/LLM tracing + ML model monitoring
Strength Application tracing + AI Drift detection, model performance, agent evaluation
Non-AI tracing Full support OTel-compatible but no first-class support for web frameworks or databases
Language support Python, JS/TS, Rust + any OTel language Python-focused
Pricing Personal: 10M records free; Team: $49/month + $2/M over 10M $50 + span and payload usage (AX Pro)
Data retention 30 days default; 90 days (Growth); custom on Enterprise 30 days on AX Pro; custom on Enterprise
Query interface Standard SQL (PostgreSQL) Proprietary DSL (Python expression syntax)
Human annotations Annotations on production runs Annotations on production runs
MCP server Query production traces from your editor or AI agent Instrumentation guidance and docs; production trace querying not available
Cost savings

Pricing comparison

Monthly list price for equivalent workloads in Arize AX and Logfire
Workload Arize AX Logfire Difference
1 user, 5M spans/mo ~$4,055 $0 (Personal) ~$4,055/mo
5 users, 50M spans/mo ~$40,730 ~$129 ~316x
20 users, 500M spans/mo ~$407,480 ~$1,229 ~332x
See the exact pricing math and sources 12 published inputs · 2 official sources · checked August 19, 2026

Calculation scope

Arize AX Pro span and payload pricing compared with the cheapest applicable public Logfire plan for each listed user and record volume.

Basis: USD; public monthly list price. Prices checked .

Published inputs

Logfire Personal base
$0/month Pydantic Logfire source
Logfire Team base
$49/month Pydantic Logfire source
Logfire Growth base
$249/month Pydantic Logfire source
Logfire included telemetry
10,000,000 records/month Pydantic Logfire source
Logfire additional telemetry
$2 per 1,000,000 records Pydantic Logfire source
Logfire Team included seats
5 seats Pydantic Logfire source
Logfire Growth seats
Unlimited Pydantic Logfire source
Arize AX Pro base
$50/month Arize AX source
Arize AX Pro included spans
50,000 spans/month Arize AX source
Arize AX Pro additional spans
$0.0008 per span ($800 per 1,000,000) Arize AX source
Arize AX Pro included payload
10 GB/month Arize AX source
Arize AX Pro additional payload
$3/GB Arize AX source

Assumptions

Average span payload
5 KB This matches Logfire's published average span allowance and makes the cross-vendor payload model explicit. Pydantic Logfire source
Payload conversion
1 GB = 1,000,000,000 bytes Vendor pricing is expressed in decimal gigabytes.
Arize included payload
10 GB This is the allowance currently published on the AX Pro pricing card. Arize AX source

Calculations

1 user, 5M spans per month

The Arize payload model uses 5M × 5 KB = 25 GB per month.

Logfire
$0
  1. Personal plan 5M records are within the 10M Personal allowance $0
Arize AX
$4,055
  1. AX Pro base $50 $50
  2. Additional spans (5M − 50K included) × $0.0008 $3,960
  3. Additional payload max(25 GB − 10 GB included, 0) × $3/GB $45

5 users, 50M spans per month

The Arize payload model uses 50M × 5 KB = 250 GB per month.

Logfire
$129
  1. Team base $49 $49
  2. Additional records (50M − 10M included) ÷ 1M × $2 $80
Arize AX
$40,730
  1. AX Pro base $50 $50
  2. Additional spans (50M − 50K included) × $0.0008 $39,960
  3. Additional payload max(250 GB − 10 GB included, 0) × $3/GB $720

20 users, 500M spans per month

The Arize payload model uses 500M × 5 KB = 2,500 GB per month.

Logfire
$1,229
  1. Growth base $249 $249
  2. Additional records (500M − 10M included) ÷ 1M × $2 $980
Arize AX
$407,480
  1. AX Pro base $50 $50
  2. Additional spans (500M − 50K included) × $0.0008 $399,960
  3. Additional payload max(2,500 GB − 10 GB included, 0) × $3/GB $7,470

Source ledger

  1. Pydantic Logfire — Pricing and plans for Pydantic Logfire Official vendor source · checked https://pydantic.dev/pricing
    “Covers 10 million logs, spans, and metrics every month.”

    The official calculator shows 20 million records and no extra seats totaling $69/month on Team.

  2. Arize AX — Arize AI pricing Official vendor source · checked https://arize.com/pricing
    “$.0008 per additional span”

    AX Pro lists 50,000 spans and 10 GB included, then $0.0008 per additional span and $3 per additional GB.

What this calculation does not include

  • Actual Arize payload charges depend on the average encoded span size. At a smaller payload, Arize costs less than these scenarios; at a larger payload, it costs more.
  • The 500-million-record Logfire scenario uses Growth because its unlimited seats make it cheaper than Team for 20 users.
  • Taxes, negotiated discounts, and model-provider charges are excluded.
Key differences

Why teams choose Logfire

One trace, complete context

When something breaks in production, you need to know whether it was the model, the data, or the infrastructure. Arize AX shows you the AI layer. Logfire shows you the whole thing: the user request, the database query, the LLM call, the API response. One trace, complete context. Arize AX can receive OTel spans from non-AI services, but has no first-class support for web frameworks or databases.

Simpler pricing, better retention

Logfire's Team plan starts at $49 a month and includes 10 million records; additional records cost $2 per million, with no payload surcharge. You can afford to ingest everything, which means when something fails in production, the trace is complete and easier to debug and recover.

Standard SQL, no proprietary query language

Logfire uses standard (PostgreSQL) SQL throughout. Your team already knows it. AI coding assistants write excellent SQL, which means you can ask questions about your production traces without leaving your editor. Logfire also ships an MCP server. Point your coding agent at your Logfire data and it can answer arbitrary questions about production behavior directly, something no proprietary query language makes easy.

Decision guide

Which should you choose?

Choose Logfire if

  • You need to trace your entire app, not only AI calls
  • You have services in multiple languages
  • You want the simplest possible setup (3 lines of code)
  • You prefer one tool for both AI and application monitoring
  • You want to query traces with SQL or via an MCP server

Choose Arize AX if

  • Your team thinks in ML metrics, not application traces
  • You need specialised model drift detection
  • You're already invested in Arize's broader ML platform
FAQ

Common questions

What's the difference between Logfire and Arize AX?

Arize AX comes from the ML monitoring world, excelling at model drift detection, performance metrics, and agent evaluation. Logfire comes from the application observability world, excelling at distributed tracing across your entire stack, databases, APIs, infrastructure monitoring, and real-time debugging, alongside AI. The biggest practical difference is scope. Logfire sees your whole application. Arize AX focuses on the model and AI layer.

Is Arize Phoenix open source?

Yes. Arize Phoenix is open source and self-hostable with no feature gates. This comparison page is against Arize AX, Arize's commercial SaaS platform, which is what most teams reach for when they need a production-ready hosted solution with managed retention, alerting, and enterprise features. If you're evaluating Phoenix OSS specifically, the comparison looks different. Phoenix is free and self-hosted, but you manage your own infrastructure, retention, and scaling, which can become expensive.

Does the Dynatrace acquisition change this comparison?

Dynatrace agreed to acquire Arize in August 2026, aiming to combine Arize's AI evaluation and observability capabilities with Dynatrace's application and infrastructure tracing. The deal is expected to close later in 2026. Pydantic Logfire combines full-stack and AI observability in one product from the start, and hasn't been acquired or merged into another platform. The feature and pricing comparisons on this page reflect Arize AX as it stands today, independent of Dynatrace.

How does developer experience compare?

With Logfire, three lines gets you started: import logfire, logfire.configure(), logfire.instrument_openai(). From there, instrumenting FastAPI, SQLAlchemy, HTTPX, and most common libraries is one more line each. Arize AX is optimised for ML engineers working in the model layer. For general application tracing (web frameworks, databases, background workers) there are no first-class integrations, so you're working with raw OTel setup.

Does Logfire support drift detection?

Logfire focuses on application observability and real-time AI tracing. For specialised ML model monitoring features like drift detection and model performance metrics, Arize AX is better suited. You can use both tools together.

Can I use both Logfire and Arize AX?

Yes. Use Logfire for full-stack application observability, real-time debugging, and querying your traces via SQL or MCP. Use Arize AX for specialised ML monitoring like drift detection and model performance metrics. Both are built on OpenTelemetry, so they integrate cleanly.

Does Logfire support distributed tracing?

Yes. Logfire's OpenTelemetry implementation stitches distributed spans into traces automatically, with no special configuration needed. Spans from different services connect into a single trace out of the box.

Ready to switch from Arize AX?

Get started with 10 million free spans, logs, and metrics per month. No credit card required.