Sentry's plan prices are easy to read. The bill is not, because Sentry meters volume: the number of events your application sends, in several categories, each with its own price. If you searched "sentry pricing", this post explains how error volume becomes dollars, with the arithmetic for three volumes, so you can estimate your own number before you commit. If you want to skip to the answer for your volume, our Sentry pricing calculator does the lookup for you.
Everything about Sentry below is from Sentry's own pricing page and billing documentation, read October 4, 2026. Sentry notes that the per-event prices in its docs are rounded.
What do Sentry's plans include?
Sentry sells four plans: Developer, Team, Business and Enterprise. The table shows what each includes for errors.
| Plan | Price | Included errors | Users | Retention |
|---|---|---|---|---|
| Developer | $0 | 5,000 | 1 | 30 days |
| Team | $26/month billed annually, $29 billed monthly | 50,000 | Unlimited | Up to 90 days lookback |
| Business | $80/month billed annually, $89 billed monthly | 50,000 | Unlimited | Up to 90 days lookback plus sampled retention |
| Enterprise | Custom | Custom | Custom | Custom |
The paid plans also include 5 GB of logs, 5 GB of metrics, 5 million spans and 50 session replays a month. Beyond errors, Sentry meters logs, metrics, spans, replays, profiles, cron monitors, uptime monitors and attachments as separate categories. This post covers only errors. If you turn on tracing, replay or uptime alerts, each adds its own line. The page lists, for example, $0.50 per GB of additional logs or metrics and $1.00 per additional uptime alert.
How do events become a bill?
Events become a bill through reserved volume and a pay-as-you-go budget. Sentry's billing documentation describes two ways to buy volume beyond what a plan includes:
- Reserved volume: an amount you pay for in advance, at a discount, monthly or annually. Unused reserved volume expires at the end of each billing month.
- Pay-as-you-go (PAYG) budget: a spending cap you set, shared across all categories on a first-come, first-served basis, that covers anything over your reserved volume.
Past both, the docs say: "Any data sent after you've run through your reserved volume and PAYG budget will be dropped and you won't be charged for it."
The drop rule protects the invoice. It also costs you monitoring for the rest of the billing cycle, so the budget has to match your real peak, not your average.
The per-event prices for errors, from Sentry's docs, are tiered by volume:
| Error volume in the month | Team reserved | Team PAYG |
|---|---|---|
| Over 50k to 100k | $0.00029 | $0.0003625 |
| Over 100k to 500k | $0.000175 | $0.0002188 |
| Over 500k to 10M | $0.00015 | $0.0001875 |
The arithmetic
The docs label each row by a volume bracket but do not say in words whether a rate applies to every event or only to the events inside the bracket. The examples below assume the second reading: each rate applies to the events that fall inside its bracket. If Sentry bills it the other way, your number will differ, and the calculator or Sentry's own estimator is the place to confirm. All three use the Team plan paid monthly ($29) with PAYG pricing.
100,000 errors in a month. 50,000 are included. The other 50,000 fall in the first bracket: 50,000 x $0.0003625 = $18.125. Total: $29 + $18.13 = about $47.13. With reserved volume at $0.00029 instead, the extra 50,000 costs $14.50 and the total is $43.50.
250,000 errors. 50,000 included. Next 50,000 at $0.0003625 = $18.125. Remaining 150,000 at $0.0002188 = $32.82. Overage is $50.945, so the total is $29 + $50.945 = about $79.95.
540,000 errors, because a release shipped a bug. Say your normal month is 40,000 errors and a bad deploy emits 500,000 more. 50,000 are included. Next 50,000 at $0.0003625 = $18.125. The next 400,000 at $0.0002188 = $87.52. The final 40,000 sit in the third bracket at $0.0001875 = $7.50. Overage is $113.145, so the total is $29 + $113.145 = about $142.15, against a $29 month the month before.
The third example is why the setting that matters is not the plan but the budget. A PAYG budget of, say, $50 would have capped that month at $79 and dropped the rest, which is the trade: a bounded bill and a gap in data. Sentry also documents tools that keep a noisy day out of the quota in the first place.
What counts toward Sentry's quota?
Sentry's quota documentation sets the rules:
- Events dropped by inbound filters do not count toward quota, and neither do events dropped by spike protection or by a project's rate limit. Events that pass the filters do count.
- Issues themselves do not count; the errors that make them up do. A new error on an issue you already resolved counts again.
- Ignored issues still count unless you delete and discard future events, which is a Business and Enterprise feature, as is per-project rate limiting.
So the cheapest errors are the ones you filter before they reach the quota. Typical candidates are known browser extension noise, health-check failures you have already triaged, and one chatty issue that emits thousands of duplicates. Sentry's event stream guide lists the tools for this.
The same volumes, priced flat
RealUptime Errors prices by plan, not by bracket:
| Plan | Price | Events a month | Retention |
|---|---|---|---|
| Free | $0 | 10,000 | 14 days |
| Pro | $23.99/month ($239.90/year) | 100,000 | 90 days |
| Business | $58.99/month ($589.90/year) | 750,000 | 180 days |
For the three examples above, 100,000 events fits Pro at $23.99. The 250,000 and 540,000 examples both fit Business at $58.99.
Overage is optional and off by default. If you turn it on, events past your plan cost $0.50 per 1,000, capped by a budget you set. With it off, an account behaves as a hard quota.
The comparison is not like for like. Sentry's Team plan includes allowances for spans, session replays, logs and metrics as well as errors, and Business adds features such as the rate limits above. RealUptime Errors is error tracking only: grouping, releases, alerts and PII scrubbing, with JavaScript/Node and Python SDKs.
When is Sentry the right choice?
Sentry is the right choice when you need performance tracing and session replay in the same tool, or a broader surface than error tracking. It also fits when your team already runs Sentry with workflows built around it. The price is the price of that breadth.
If what you want is error counts, grouping and alerts and a bill you can predict, the flat side is worth a look. The Sentry vs RealUptime comparison goes through the rest. Our earlier posts on Sentry's free tier limits and Rollbar's pricing cover the neighboring questions.
To try it on your own event volume, start RealUptime Errors free: 10,000 events a month, no card. The pricing page lists every plan.
Sources
- Sentry pricing, read October 4, 2026: plans, included volume, metered categories, annual and monthly prices.
- Sentry pricing documentation, read October 4, 2026: reserved volume, PAYG, dropped data, per-event error rates.
- Sentry quota documentation, quotas and the event stream guide, read October 4, 2026: what counts toward quota.
- RealUptime plans, read October 4, 2026.