Sentry's default Team configuration
The official calculator starts with 50,000 errors, 5 GB logs, and 5 million spans, with no pay-as-you-go usage.
Sentry
$26- Team base and included quotas
$26 + $0 additional usage$26
Comparison
Logfire vs Sentry
Whether you are weighing a Sentry alternative or choosing your first error tracking stack: Logfire brings errors, agent runs, and application telemetry into one OpenTelemetry-native workflow with PostgreSQL-compatible SQL, pending spans, and a path from production evidence to evaluation and improvement.
Quick comparison
| Feature | Logfire | Sentry |
|---|---|---|
| Primary Focus | OpenTelemetry-native full-stack and AI observability | Error, performance, and agent monitoring |
| AI/LLM Support | Automatic framework instrumentation and agent traces | Dedicated Agent Monitoring integrations and AI trace views |
| Agent context | Agent spans inside the surrounding application trace | Agent runs, AI spans, and conversations |
| Logging | Structured logs queryable with traces and metrics | Structured logs correlated with traces and issues |
| In-flight work | Live View for pending spans | Recorded agent traces and conversation views |
| Query Interface | Full PostgreSQL-compatible SQL over traces, logs, and metrics: joins, subqueries, window functions, plus MCP for agents | Field filters (span.op:http.client) with a fixed aggregate menu (p50-p95, avg, max) in Trace Explorer |
| Cross-signal context | AI, browser, database, API, service, log, metric, and infrastructure telemetry | Frontend, backend, agent spans, errors, and logs |
| Pricing | Personal: 10M records free; Team: $49/month + $2/M over 10M | Developer free; Team $26 + reserved volume or a configured pay-as-you-go budget; data drops at the limit |
How Sentry's separate meters add up
| Illustrative monthly workload | Logfire | Sentry |
|---|---|---|
| Base-plan prices | $49 Team; 10M records; 30 days | $26 Team; independent quotas; up to 90 days |
| 1M errors/month | $49/month; errors are not a separate meter and 1M error records sit inside Team's included 10M | $225.40/month |
| 10M errors/month | $49/month; 10M error records equal Team's included allowance | $1,912.90/month |
See the exact pricing math and sources
Calculation scope
Three reproducible Sentry Team calculations using the public calculator's included quotas and pay-as-you-go rates, with the Logfire total computed for the same workload on the equivalent paid plan. The base-plan row is not presented as an equivalent configuration. The error examples need no cross-meter conversion because Logfire has no separate error meter.
Basis: USD; US annual Team list price. Prices checked .
Published inputs
- Logfire Team base
- $49/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
- Sentry Team, annual
- $26/month Sentry source
- Sentry Team included errors
- 50,000/month Sentry source
- Sentry Team included spans
- 5,000,000/month Sentry source
- Sentry Team included logs
- 5 GB/month Sentry source
- Other Sentry Team included quotas
- 5 GB application metrics, 50 replays, 1 uptime monitor, 1 cron monitor, and 1 GB attachments Sentry source
- Sentry Team retention
- Up to 90 days Sentry source
- Sentry additional logs
- $0.50/GB Sentry source
- Sentry errors from 50,000 to 100,000
- $0.0003625/error Sentry source
- Sentry errors from 100,000 to 500,000
- $0.0002188/error Sentry source
- Sentry errors from 500,000 to 10,000,000
- $0.0001875/error Sentry source
Assumptions
- Billing frequency
- Annual Team Sentry's public calculator defaults to the $26 monthly equivalent for annual Team billing. Sentry source
- Other Sentry meters
- At included quotas Each worked example changes one meter and leaves spans, replays, monitors, profiles, attachments, and add-ons at the default allowance. Sentry source
- Retention
- Sentry Team up to 90 days; Logfire Team 30 days The base prices are shown as plan entry points, not as retention-matched configurations. Sentry source Pydantic Logfire source
- Additional usage
- Public pay-as-you-go rates with a configured budget Sentry also sells discounted reserved capacity. Data is dropped after the reserved quota and optional pay-as-you-go budget are exhausted. Sentry source Sentry source
- Errors in Logfire
- Not a separate meter An exception is recorded on its span, so error volume consumes the ordinary record allowance instead of a dedicated error meter with its own rates. Both worked volumes are quoted on Logfire Team against Sentry Team, so neither side is a free tier: the free Personal plan would cover these error counts but pauses ingestion at its limit, and Sentry's free tier includes 5,000 errors. Pydantic Logfire source Sentry source
- Rounding
- Nearest cent Sentry notes that its calculator estimate may differ because of rounding.
Calculations
1,000,000 errors per month
The first 50,000 errors are included, then each published error tier is applied only to the volume inside that band. Logfire has no error meter, so 1M error records sit inside Team's included 10M and add nothing to the base. Both sides are quoted on their paid team plan; the free Personal plan would also cover this volume, but it pauses ingestion at its limit and leaves no allowance for the traces, logs and metrics this page argues errors belong beside.
Pydantic Logfire
$49- Team base; no separate error meter
$49 + (1M error records within Team's included 10M) × $0$49
Sentry
$225.40- Team base
$26$26 - 50K–100K errors
50,000 × $0.0003625$18.13 - 100K–500K errors
400,000 × $0.0002188$87.52 - 500K–1M errors
500,000 × $0.0001875$93.75
10,000,000 errors per month
Sentry's published tiers applied to the full band widths. In Logfire, 10M error records exactly consume Team's included allowance, with no error-specific rate at any volume. This is the ceiling of the row rather than headroom: any traces, logs or metrics alongside these errors bill at the published per-record overage.
Pydantic Logfire
$49- Team base; no separate error meter
$49 + (10M error records = Team's included 10M) × $0$49
Sentry
$1,912.90- Team base
$26$26 - 50K–100K errors
50,000 × $0.0003625$18.13 - 100K–500K errors
400,000 × $0.0002188$87.52 - 500K–10M errors
9,500,000 × $0.0001875$1,781.25
Source ledger
- Pydantic Logfire — Pricing and plans for Pydantic Logfire 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.
- Sentry — Sentry pricing and calculator https://sentry.io/pricing/
“Any usage above your quota is billed at pay-as-you-go rates.”
The default annual Team calculator shows $26/month with 50,000 errors, 5 GB logs, and 5 million spans included.
- Sentry — Pricing and billing https://docs.sentry.io/pricing/
“Any data sent after you've run through your reserved volume and PAYG budget will be dropped.”
Sentry documents prepaid reserved volume, an optional pay-as-you-go budget, and dropping after both are exhausted.
- Sentry — Manage your event stream https://docs.sentry.io/pricing/quotas/
“When spike protection is triggered, events start getting dropped.”
Sentry documents independent quotas and spike protection that can drop excess events.
What this calculation does not include
- Sentry meters errors, logs, application metrics, spans, replays, monitors, profiles, attachments, and Seer independently; a complete bill is the sum of the meters a team uses.
- The worked usage totals use Sentry's higher pay-as-you-go rates. Prepaid reserved volume can be cheaper, but unused reserved capacity expires each month.
- Pay-as-you-go requires a configured budget. Sentry drops data after reserved volume and that budget are exhausted, and spike protection can drop excess events sooner.
- The 1-million-error total rounds each displayed tier to the nearest cent; Sentry says its calculator remains an estimate.
- Monthly billing, taxes, negotiated terms, and add-ons are excluded.
Why teams choose Logfire
Investigate the system behind the agent
Logfire keeps model calls, tools, browser and backend spans, databases, APIs, logs, metrics, and infrastructure in one investigation. Query the telemetry with PostgreSQL-compatible SQL and MCP, then jump from a browser trace to the exact moment in its session replay.
Connect observation to improvement
Logfire carries production traces into hosted LLM judges, deterministic evaluators, annotation queues, scheduled optimization proposals, and model-swap recommendations. Teams can investigate a run, review the evidence, and apply the next change from the same workflow.
Inspect work before the request finishes
Logfire's pending spans show active model calls and tool executions while an agent run is still in progress. That lets a developer inspect a slow or stuck operation before the request completes, alongside the completed-run analysis available after it finishes.
SQL-powered analytics, not a filter bar
Sentry's Trace Explorer queries spans with field:value filters and a fixed menu of aggregates (p50-p95, avg, max). Logfire gives you the whole SQL language over traces, logs, and metrics: "Show me all FastAPI requests that called our LLM more than 3 times." "Which deploy introduced the slow queries, and what did those requests log?" Joins, subqueries, and window functions are all available, and Logfire's MCP server gives coding agents the same interface, so they can investigate production behavior without a dashboard being predefined for each question.
Which should you choose?
Choose Logfire if
- You want PostgreSQL-compatible SQL and MCP over full-stack telemetry
- You want browser RUM and session replay connected to backend and agent traces
- You want agent traces connected to hosted evals, human review, and optimization
- You want to inspect pending spans while a request is still running
Choose Sentry if
- Your team is already standardized on Sentry and wants to keep its existing observability workflow
Common questions
Is Logfire a good Sentry alternative?
If you are looking for a Sentry alternative that combines error tracking and error monitoring with full traces, logs, metrics, and agent observability, Logfire covers that in one OpenTelemetry-native product with usage-based pricing and a free tier.
Can Logfire replace Sentry?
For teams that want errors, full-stack telemetry, and agent observability in one product, yes. Logfire covers errors, logs, traces, metrics, browser RUM and session replay, and agent monitoring in one OpenTelemetry-native product. If Sentry is already embedded in your workflow, you can run both while you move instrumentation and investigations to Logfire.
Does Logfire track errors?
Yes. Error tracking is built in: Logfire captures exceptions as part of the same trace as model calls, tool calls, database queries, and API requests, with correlated logs and metrics available to the same investigation.
Does Logfire have real-time monitoring?
Yes. Logfire's Live View shows pending spans before a request completes, so you can inspect where an active agent is spending time instead of waiting for the request to finish.
How does AI/LLM support compare?
Logfire connects agent traces to PostgreSQL-compatible SQL, MCP investigation, pending-span Live View, hosted and code-based evaluators, annotation queues, scheduled optimization proposals, model-swap recommendations, and managed agent configuration. The same investigation includes the application and infrastructure around the agent.
How does querying traces compare?
Sentry's Trace Explorer filters spans with field:value syntax such as span.op:http.client and offers a fixed menu of aggregates (p50-p95, avg, max), grouped by span attributes. Logfire exposes traces, logs, and metrics as PostgreSQL-compatible tables, so an investigation can use joins, subqueries, window functions, and arbitrary SQL expressions - for example correlating slow spans with a deploy version and the error logs from the same requests in one query. Coding agents get the same interface through Logfire's MCP server.
What happens when you hit Sentry's quota?
Sentry documents that events sent after your reserved volume and any pay-as-you-go budget are exhausted are dropped, and spike protection can drop excess events sooner. Logfire's paid plans bill records beyond the included 10M at a single published overage rate instead of discarding data at a quota boundary.
Can I run both Logfire and Sentry?
Yes. You can keep an existing Sentry deployment while introducing Logfire for OpenTelemetry-native full-stack and agent observability, then move workflows incrementally.
Ready to switch from Sentry?
Get started with 10 million free spans, logs, and metrics per month. No credit card required.