Sentry Pricing 2026: Error Monitoring Cost

Quick Answer

Sentry pricing 2026 error monitoring cost: Developer free $0 with 5K errors/5M spans/50 replays; Team $26/mo (annual, $29 monthly) with 50K errors/5M spans/50 replays/5GB logs; Business $80/mo (annual, $89 monthly) with SSO + advanced features. Sentry bills across five separately-metered categories — overage, not sticker price, is the real bill.

Last verified: Sep 16, 2026.

At a glance

• Developer: $0/mo, 5K errors, 5M spans, 50 replays, 5GB logs
• Team annual: $26/mo with 50K errors, 5M spans, 50 replays, 5GB logs, 5GB metrics
• Team monthly: $29/mo
• Business annual: $80/mo with SSO + SCIM + anomaly detection
• Business monthly: $89/mo
• Seer AI: $40 per active contributor/mo

Side-by-side pricing comparison

Five separately-metered categories

Sentry bills across five categories that meter independently — and overage, not sticker price, is the real bill.

Errors: $0.15-$0.36 per 1,000 errors above 50K on Team; $0.30-$1.11 per 1,000 on Business.

Tracing spans: $1.60-$2.00 per million spans above 5M on Team; $2.90-$4.00 per million on Business. Spans are the largest line item for traced applications.

Session replays: $1.96-$3.75 per 1,000 replays above 50 (same on both Team and Business plans). Session Replay costs are unpredictable because video replay volume scales with user activity.

Logs and metrics: $0.50 per GB above 5GB on both Team and Business.

Attachments: $0.31 per GB above 1GB on both Team and Business.

Cron monitor: $0.78 each per month above the included 1. Uptime monitor: $1.00 each per month above the included 1. Continuous profiling: $0.0315 per hour.

The base subscription is a rounding error compared to overage. A traced application emitting 50M spans/month pays ~$80-$100 in span overage fees in addition to the $26 base (BudgetForge Sentry analysis, July 2026).

Developer vs Team vs Business vs Enterprise

The four plans map to team size and feature requirements.

Developer (free): $0/month with 5,000 errors, 5M spans, 50 replays, 5GB logs, 1 user. Best for solo developers, side projects, and proof-of-concept evaluation. Limited to a single user with no third-party integrations and only email alerts.

Team ($26/mo annual, $29/mo monthly): 50,000 errors, 5M spans, 50 replays, 5GB logs, 5GB metrics, unlimited users, third-party integrations, basic alerting. Best for small teams with predictable low-to-moderate volume.

Business ($80/mo annual, $89/mo monthly): identical base quotas as Team plus SAML + SCIM support, advanced quota management, unlimited custom dashboards, unlimited metric monitors with anomaly detection, advanced insights. Best for mid-market teams requiring SSO and advanced quota management.

Enterprise (custom): custom pricing with volume discounts, dedicated technical account manager, custom SLAs, advanced security features, and self-hosting options. Best for organizations needing custom contractual terms and dedicated support.

As of January 2026, legacy Seer AI pricing is no longer offered as an add-on. Seer is now available only via direct purchase. Legacy Seer customers continue on legacy terms (Sentry pricing documentation, 2026).

Error pricing ladder

Errors are billed at tiered rates that decrease with volume.

Team plan PAYG error overage rates:

• 50K-100K errors: $0.0003625 per error (~$36 per 100K errors)
• 100K-500K errors: $0.0002188 per error (~$22 per 100K errors)
• 500K-10M errors: $0.0001875 per error (~$19 per 100K errors)
• 10M-20M errors: $0.0001625 per error (~$16 per 100K errors)
• 20M+ errors: $0.0001500 per error (~$15 per 100K errors)

Business plan PAYG error overage rates (2-3x Team):

• 50K-100K errors: $0.0011125 per error (~$111 per 100K errors)
• 100K-500K errors: $0.0006250 per error (~$63 per 100K errors)
• 500K-10M errors: $0.0003750 per error (~$38 per 100K errors)
• 10M-20M errors: $0.0003250 per error (~$33 per 100K errors)
• 20M+ errors: $0.0003000 per error (~$30 per 100K errors)

Reserved capacity is 20% off PAYG rates for predictable monthly volume. For example, errors in the 50K-100K tier cost $0.000290 per error reserved vs $0.000363 PAYG (Sentry pricing documentation, 2026).

Tracing spans: the largest line item

Spans are priced per million and become the dominant line item for traced apps.

A traced app emitting 50M spans/month on the Team plan pays roughly $80-$100 in span overage fees in addition to the $26 base subscription. The same workload on the Business plan pays $160-$200 in span overage fees (BudgetForge Sentry analysis, July 2026).

The per-million-span rate drops with volume. At 500M+ spans/month, the rate is typically $1.60 per million on Team. At 1B+ spans/month, the rate drops further to ~$1.50 per million.

Sentry bills spans regardless of whether they include errors. A trace with 50 spans and no errors still costs 50 events. This is why tracing-heavy workloads can quickly exceed error-heavy workloads in Sentry bills.

Tracing is opt-in via SDK configuration. For workloads where error visibility is sufficient, disabling tracing cuts the bill by 50-70%.

Session Replay and Seer AI

Session Replay and Seer AI are the two largest variable costs beyond base subscriptions.

Session Replay overage: $0.00375 per replay above 50, dropping to $0.00245 per replay above 4.5M. A team running 10,000 replays/month pays roughly $0.00375 x 9,950 = $37/month in replay overage fees. A team running 100,000 replays/month pays $375/month in replay overage fees. Session Replay costs the same on both Team and Business plans.

Seer AI: $40 per active contributor per month, where an active contributor is anyone who makes two or more pull requests to a Seer-enabled repository within a billing cycle. A team with 20 active developers on Seer pays $800/month in Seer fees. Seer AI is the primary AI cost driver for Sentry customers.

As of January 2026, legacy Seer pricing is no longer offered as an add-on. Seer is now available only via direct purchase. Legacy Seer customers continue on legacy terms (Sentry pricing documentation, 2026).

Real-world TCO scenarios

Five common scenarios illustrate how Sentry bills scale.

Solo Developer: $0/month. Stays under 5K errors, no add-ons.

Small team (5-10 devs): Team plan + light overages (~75K errors/mo). $26 + ~$10 overage = $35-$45/month.

Scaling startup (20-50 devs): Team plan + 500K errors + 10K session replays. $26 + $90 errors + $38 replays = $180-$200/month.

Mid-market (50-100 devs): Business plan + Seer AI (10 active contributors) + 500K errors + 10K replays. $80 + $400 Seer + $138 errors + $38 replays = $640-$700/month.

Enterprise (100+ devs): Custom plan with volume discounts, dedicated support. Typically $2,000-$5,000+/month at scale (CheckThat Sentry analysis, June 2026).

Cost-control tactics

Three tactics work together to control Sentry costs.

Tactic 1: enable Spike Protection on all projects. Spike Protection detects abnormal event surges and automatically drops events to prevent quota consumption during spikes. It recalculates thresholds hourly based on the 7-day historical baseline.

Tactic 2: pre-purchase reserved capacity for predictable monthly volume. Reserved capacity is 20% off PAYG rates. Unused reserved volume expires at the end of each billing month, so only pre-purchase what is confidently predictable.

Tactic 3: configure SDK-level sampling rates carefully. Trace sampling in particular can cut span volume dramatically. Some users report sampling controls being less effective than expected, so monitor actual consumption in the Usage Stats dashboard weekly.

The PAYG spending cap is a circuit breaker: when the budget is exhausted, excess data is dropped rather than charged. Setting a conservative PAYG cap prevents runaway bills during traffic surges (Sentry pricing documentation, 2026).

How to choose between Sentry, Datadog, Honeycomb, and LogRocket

The decision hinges on three variables: error focus, session replay needs, and bundle preference.

1. Error focus. Primary need is error monitoring with light tracing: Sentry is the obvious choice. Primary need is full-stack observability: Datadog, New Relic, Dynatrace. Primary need is event-based tracing analytics: Honeycomb.
2. Session replay needs. Need session replay for UX debugging: Sentry or LogRocket. Don't need session replay: any observability platform.
3. Bundle preference. Want one tool for errors, traces, logs, replays, alerts: Sentry. Want one tool for full infra + APM + logs + RUM: Datadog. Want consumption-based simplicity: New Relic. Want cost-effective core observability: Grafana Cloud.

What enterprise buyers should do next

Three actions for organizations evaluating Sentry in 2026.

1. Model the bill on actual error and span volume, not the sticker. Use the Sentry per-tier overage rates and your actual event volume from the past 90 days. The base subscription is a rounding error; the overage is the bill.
2. Pre-purchase reserved capacity for predictable workloads. Reserved capacity is 20% off PAYG rates. If your monthly error volume is predictable within 20%, the savings pay for the procurement effort.
3. Audit Session Replay usage before signing. Session Replay overage can exceed the base subscription cost. If session replay is mission-critical for UX debugging, budget for it explicitly; if it is a nice-to-have, configure conditional recording to limit replay capture to specific user segments.

What to watch next

Three near-term datapoints. First, the Sentry 2027 pricing announcement — Sentry has historically updated pricing in late Q4; watch for changes to base quotas or per-tier rates. Second, the Seer AI usage-based pricing evolution — Seer currently bills per active contributor; if Sentry introduces usage-based pricing, the cost model changes significantly for AI-heavy teams. Third, the Session Replay privacy roadmap — Sentry has been adding privacy controls; new pricing tiers for enterprise privacy features may surface in 2027.