Skip to main content
Comparison

Logfire vs Langfuse

Logfire brings LLM tracing and evaluation into full-stack observability, with PostgreSQL-compatible SQL across the surrounding application, infrastructure, traces, logs, and metrics.

Feature comparison

Quick comparison

Logfire and Langfuse compared feature by feature
Feature Logfire Langfuse
Observability scope AI and application telemetry across traces, logs, and metrics LLM tracing, prompts, evaluation, and datasets
LLM Tracing Yes Yes
Token/Cost Tracking Yes Yes
Prompt Playground Yes Yes
Human annotations & queues Annotations on production runs + annotation queues Annotations on production runs + annotation queues
Hosted evaluation LLM judges and deterministic evaluators on live traffic Model-based and custom evaluators
Continuous improvement Scheduled proposals and model-swap recommendations Evaluation and prompt workflows
Full-stack workflow Traces, logs, metrics, and infrastructure views Trace-oriented LLM observability
Database/API context Native OTel integrations and service context Can ingest arbitrary OTel spans within traces
Query Interface PostgreSQL-compatible SQL Product UI, metrics API, and public API
MCP server SQL queries over production telemetry from your editor or AI agent Query observations, metrics, scores, datasets, and annotation queues
OpenTelemetry Native across full-stack telemetry Native OTLP trace ingestion
Self-Hosting Enterprise Open Source
Free Tier 10M logs, spans, and metrics 50K units
Python SDK Native OpenTelemetry SDK Native OpenTelemetry SDK
JavaScript SDK Native OpenTelemetry SDK Native OpenTelemetry SDK
Any OTel Language Yes Yes
Try it on your stack

Pressure-test this against your stack

Tell us what you run, what you pay, and what your team needs to keep. We’ll give you a straight answer about where Logfire fits.

Pricing

What the graduated rates cost in practice

Logfire and Langfuse cloud pricing models
Illustrative monthly volume Logfire Langfuse
1M stored units/month $49 Team (30 days) · $249 Growth (up to 90 days) $101/month (90 days, unlimited users)
10M stored units/month $49 Team (30 days) · $249 Growth (up to 90 days) $731/month (90 days, unlimited users)
50M stored units/month $129 Team (30 days) · $329 Growth (up to 90 days) $3,331/month (90 days, unlimited users)
See the exact pricing math and sources 14 published inputs · 3 official sources · checked August 20, 2026

Calculation scope

Langfuse Core's graduated cloud-unit pricing compared with both the lowest applicable 30-day Logfire plan and Logfire Growth for up to 90-day retention at the same stored-object count. The mapping is object-level, not run-level equivalence.

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
Langfuse Hobby allowance
50,000 units/month Langfuse source
Langfuse Core base
$29/month Langfuse source
Langfuse Core retention
90 days Langfuse source
Langfuse Core users
Unlimited Langfuse source
Langfuse Core allowance
100,000 units/month Langfuse source
Langfuse usage from 100,000 to 1,000,000 units
$8 per 100,000 units Langfuse source
Langfuse usage from 1,000,000 to 10,000,000 units
$7 per 100,000 units Langfuse source
Langfuse usage from 10,000,000 to 50,000,000 units
$6.50 per 100,000 units Langfuse source
Langfuse usage above 50,000,000 units
$6 per 100,000 units Langfuse source

Assumptions

Object mapping
1 Langfuse unit = 1 Logfire record A Langfuse unit is one stored trace, observation, or score; this illustration maps each stored object to one telemetry record. Langfuse source Pydantic Logfire source
Langfuse plan
Core with 90-day access and unlimited users Core is the lowest paid cloud plan. Showing both Logfire's lower-cost 30-day plan and Growth prevents the 90-day Langfuse entitlement from disappearing inside a caveat. Langfuse source
Discounts
None The published monthly graduated rates are used without startup, nonprofit, or negotiated credits.

Calculations

1M stored units per month

For this illustration, each Langfuse trace, observation, or score is mapped to one Logfire telemetry record so the two published meters can be calculated from the same object count.

Langfuse
$101
  1. Core base $29 $29
  2. 100K–1M units 900K ÷ 100K × $8 $72
Logfire Team · 30 days
$49
  1. Team base $49 $49
  2. Additional records (1M − 10M included) ÷ 1M × $2 $0
Logfire Growth · up to 90 days
$249
  1. Growth base $249 $249
  2. Additional records (1M − 10M included) ÷ 1M × $2 $0

10M stored units per month

For this illustration, each Langfuse trace, observation, or score is mapped to one Logfire telemetry record so the two published meters can be calculated from the same object count.

Langfuse
$731
  1. Core base $29 $29
  2. 100K–1M units 900K ÷ 100K × $8 $72
  3. 1M–10M units 9M ÷ 100K × $7 $630
Logfire Team · 30 days
$49
  1. Team base $49 $49
  2. Additional records (10M − 10M included) ÷ 1M × $2 $0
Logfire Growth · up to 90 days
$249
  1. Growth base $249 $249
  2. Additional records (10M − 10M included) ÷ 1M × $2 $0

50M stored units per month

For this illustration, each Langfuse trace, observation, or score is mapped to one Logfire telemetry record so the two published meters can be calculated from the same object count.

Langfuse
$3,331
  1. Core base $29 $29
  2. 100K–1M units 900K ÷ 100K × $8 $72
  3. 1M–10M units 9M ÷ 100K × $7 $630
  4. 10M–50M units 40M ÷ 100K × $6.50 $2,600
Logfire Team · 30 days
$129
  1. Team base $49 $49
  2. Additional records (50M − 10M included) ÷ 1M × $2 $80
Logfire Growth · up to 90 days
$329
  1. Growth base $249 $249
  2. Additional records (50M − 10M included) ÷ 1M × $2 $80

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. Langfuse — Langfuse pricing and calculator Official vendor source · checked https://langfuse.com/pricing?calculatorOpen=true
    “100k units / month included, additional: $8/100k units.”

    The official calculator shows a $37 Core total at 200,000 monthly units: $29 base plus $8 usage.

  3. Langfuse — Langfuse billable units Official vendor source · checked https://langfuse.com/docs/administration/billable-units
    “Units are either traces, observations or scores.”

    Langfuse documents the formula as traces plus observations plus scores, including units created by evaluations and annotations.

What this calculation does not include

  • A single agent run usually creates multiple observations and may create multiple scores, so run count alone cannot determine either total.
  • Any trace, observation, or score created by Langfuse features—including evaluations, annotation queues, and experiments—adds to the unit total; the model includes only the stated objects.
  • Langfuse Core includes unlimited users. Logfire seat counts can affect which plan is applicable even when the record total is unchanged.
  • Provider and model charges, taxes, startup and nonprofit credits, and discounts are excluded.
Key differences

Why teams choose Logfire

Full-stack scope

Agent behavior depends on the application around it. Logfire makes model calls, tools, browser RUM and session replay, database queries, APIs, services, logs, metrics, and infrastructure available in the same product, instead of centering the investigation on LLM observations alone.

OpenTelemetry across the whole stack

Logfire applies OpenTelemetry across the entire application, including model and tool calls, databases, APIs, services, logs, metrics, and infrastructure. That keeps instrumentation portable while preserving the context needed to explain production behavior.

SQL query interface

Query telemetry with PostgreSQL-compatible SQL, including joins, aggregations, and ad hoc questions that were not anticipated by a saved dashboard. The same interface is available to coding agents through Logfire's MCP server.

Improve from production evidence

Run hosted LLM judges and deterministic evaluators on sampled production traffic, route low-scoring runs to human review, and turn the resulting evidence into scheduled optimization proposals and model-swap recommendations.

Decision guide

Which should you choose?

Choose Logfire if

  • You want agent traces connected to the surrounding application and infrastructure
  • You want PostgreSQL-compatible SQL and MCP over production telemetry
  • You want hosted evals, human review, and optimization connected to production traces
  • You want one OpenTelemetry-native workflow across languages and frameworks

Choose Langfuse if

  • Your team is already standardized on Langfuse and wants to keep its existing LLM workflow
FAQ

Common questions

What is the main difference between Logfire and Langfuse?

Logfire puts LLM tracing, prompts, evaluation, and optimization inside full-stack observability, so model and tool calls stay connected to browser RUM and session replay, databases, APIs, services, logs, metrics, and infrastructure.

Is Logfire more expensive than Langfuse?

It depends on volume and retention. Logfire includes 10 million records a month; paid plans charge $2 per million additional records. Langfuse Core is $29, includes 100,000 units, 90-day access, and unlimited users, then applies graduated pricing to traces, observations, and scores. The worked rows quote Logfire Team throughout rather than setting a free tier against a paid one, so the smallest workload shows $49 against $101 and Logfire's record pricing stays the lower one as stored-object volume grows. The table keeps the 30-day and 90-day retention options visible rather than treating them as interchangeable.

Can I use Logfire with LangChain?

Yes. Logfire provides auto-instrumentation for LangChain, LlamaIndex, OpenAI, Anthropic, and many other AI frameworks. You can visualize complex chains and retrieval flows automatically.

Can I migrate from Langfuse to Logfire?

Yes. Logfire accepts standard OpenTelemetry traces, so you can send the same telemetry to Logfire while you compare production investigations and move integrations incrementally.

Can I self-host Logfire?

Yes. Logfire is available as a managed cloud service or as an Enterprise self-hosted deployment, and its SDK is open source.

Can Logfire evaluate live traffic?

Yes. Run hosted LLM judges or deterministic evaluators without supplying a model key, sample live production traffic, and route low-scoring runs to a human annotation queue. Scores become telemetry you can query, dashboard, and alert on.

Ready to switch from Langfuse?

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