Sentry pricing (2026): what a small team actually pays

Sentry's Developer plan is free for one user with 5,000 errors a month. Team is $26 a month billed yearly ($29 monthly), Business $80 ($89), both with unlimited users and the same included volume. The bill grows with errors, spans, replays and Seer at $40 per contributor. For 1 to 10 developers, Team plus a pay-as-you-go budget covers most apps.

Every number below is from Sentry's own pricing page and billing docs, checked on October 29, 2026, and cited inline.¹,² Prices are US dollars before tax. Fixter is our product; it appears once, at the end, where it is a real alternative.

The four plans at a glance

Sentry sells four plans. The three paid ones share the same included monthly volume; what changes between Team and Business is the price, the overage rates, the lookback and a few admin features.¹

List prices on October 29, 2026. Developer is free with no expiry. Business also lists advanced quota management and SAML and SCIM support, the latter priced on request; Enterprise is custom volume and custom pricing.

Two things stand out for a small team. First, the paid plans do not charge per seat: the jump from one user to many is the $26, not a multiplier. Second, 50,000 errors a month is the only volume that grows between Developer and Team. Spans, replays, logs and monitors are identical on every plan, so a team that needs more of those is buying them as extras whichever plan it picks.¹

What the included volume means in practice

Sentry bills by data category, and each category has its own quota.³ Here is what the included numbers mean for an app with real users.

• Errors. One error is one captured exception event, not one issue. Sentry groups repeats into issues, but every repeat counts against the quota, including repeats of an issue you resolved or ignored. Only issues set to delete and discard stop counting.³ A single bad deploy that throws on every request can use the whole 50,000 in an afternoon.
• Spans. Tracing is billed in spans, and a request that touches a database, a cache and two outbound calls is five or more spans. Five million a month is roughly a million such requests. Sampling, set in the SDK, is how you stay under it; sampled-out spans are not counted.²,³
• Session replays. 50 a month is a sample, not a feature. If you turn replay on for every session on a site with any traffic, you are on pay as you go within the first day.¹
• Logs. 5 GB a month is included on every plan, with more at $0.50 per GB on pay as you go only. Logs are counted individually and never grouped.²,³
• Monitors. One uptime monitor and one cron monitor. A second endpoint or a second scheduled job costs $1.00 or $0.78 a month, again on pay as you go only.²
• Profiling. Not included on any plan. Continuous profiling is $0.0315 per profile hour and UI profiling $0.25, pay as you go only.²

The rule that matters most: once you have used the included volume, any reserved volume and your pay-as-you-go budget, Sentry drops the data and does not charge for it. Sentry's own docs say you then lose monitoring for the rest of the billing cycle.² On the free plan there is no pay as you go at all, so a free project that hits 5,000 errors goes dark until next month.¹

Where the price jumps

Above the included volume you pay per unit, either as reserved volume you prepay at a discount (unused volume expires each month) or from a pay-as-you-go budget that all categories share.² These are the rates a small team actually hits, from Sentry's billing docs, which note the per-unit prices are rounded.²

Per-unit rates from Sentry's billing docs on October 29, 2026; the dollar totals in the first row are our multiplication. Error and span rates fall at higher volumes.

The jumps, in the order a growing team usually meets them:

1. The second user. Developer is limited to one user, so the first colleague takes you from $0 to $26 a month. Everything else on Developer carries over, and Team adds API access, integrations and up to 90 days of lookback.¹
2. A noisy release. 100,000 extra errors in a month cost about $29 on Team pay as you go and about $87 on Business. Spike protection, which you enable per project, drops events above a baseline-derived threshold so they are not billed.³ It protects the bill, not the data.
3. Seer. This is the largest jump for a team. $40 per active contributor per month, where a contributor is anyone with two or more pull requests to a Seer-enabled repository; for GitHub the docs count all repository members except bots.² Six developers is $240 a month, nine times the Team plan itself. Seer is billed on its own and does not draw from the pay-as-you-go budget.
4. Replays on by default. At $3.75 per 1,000, 10,000 replayed sessions is about $37 a month. Sample them.
5. Business instead of Team. The plan is $54 more a month, and its overage rates for errors and spans are two to three times Team's. The same 100,000 extra errors cost $29 on Team and $87 on Business. Business buys unlimited dashboards, 1,000 metric monitors instead of 20, advanced quota management, SAML and SCIM support (priced separately) and sampled retention beyond 90 days.¹,² If you need none of those, the cheaper plan with a bigger budget is the better buy.

Three worked bills for a 1 to 10 developer team

These are list prices multiplied out from the tables above, billed yearly, pay as you go rather than reserved. Your own numbers will differ; the shape will not.

One founder, one app, under 5,000 errors a month

Developer plan, $0. Errors, tracing, 5 GB of logs, one uptime monitor, email alerts and MCP access, so a coding agent can read your issues. The limits that bite are the single user and the lack of any budget: a bad week of errors ends monitoring until the month resets.¹,²

Four developers, 30,000 errors, 4 million spans, three uptime monitors

Team at $26, plus two extra uptime monitors at $1.00 each. About $28 a month, or $31 billed monthly. Everything stays inside the included volume. Add Seer for four contributors and it becomes $188.

Six developers, 150,000 errors, 20 million spans, 500 replays, five uptime monitors

Team at $26. Errors: 50,000 at $0.0003625 ($18.13) plus 50,000 at $0.0002188 ($10.94). Spans: 15 million extra at $2.00 per million ($30). Replays: 450 extra at $3.75 per 1,000 ($1.69). Monitors: four extra ($4). About $91 a month. With Seer for six contributors, about $331. The same usage on Business is about $233 before Seer: $80 for the plan, $86.88 for the errors, $60 for the spans, $5.69 for replays and monitors. With Seer for ten people on Business, about $633.

The pattern: for a team under ten people, the plan is the small part. Seer is the line that decides whether Sentry costs you $30 or $300 a month, and error volume is the line that moves month to month.

When a cheaper setup is enough

• Solo and under 5,000 errors: stay on Developer. It is free for good and includes tracing and logs. Set the SDK sample rate low enough that one bad deploy cannot use the whole quota.
• A team whose main need is errors: Team, yearly, with a $20 to $50 budget. Spend notifications and a maximum spend threshold are on Team and above; set both on day one.¹ Skip Business unless you need 1,000 metric monitors, unlimited dashboards or SAML.
• You already code with Claude Code or Cursor: think twice about Seer. Sentry's MCP server is on every plan, including Developer, so your coding agent can open the issue, read the stack trace and breadcrumbs and work on the fix itself.¹ Seer does more, it runs the root cause analysis on its own and opens the pull request, but $40 per contributor buys a lot of agent time. Try the MCP route first; here is what the Sentry MCP server can do.
• Backend services only: turn replays off and sample spans. Replays are a front end feature; a backend team paying for them is paying for nothing. Keep tracing sampled at a rate that fits in 5 million spans.
• Several tools adding up: compare the whole bill, not the plan. Sentry covers errors well and uptime barely, so most teams run a second tool for uptime and a third for logs. Our error tracking for small teams comparison lists the free tiers and prices of the main options.

Where Fixter is the cheaper setup

Fixter (fixter.dev) is our product, so weigh this with that in mind. Fixter finds and fixes the issues in your app in production, from your coding agent: errors, failing infrastructure, slow requests and downtime. It finds the root cause and fixes it: in your agent over MCP, or as a pull request ready for your review. Nothing to learn, built for small teams.

On price, the shape is different rather than every number being lower. There is one meter, the gigabytes of logs, traces and metrics you send over OpenTelemetry, and it is never per seat or per contributor. The Free plan carries 10 GB a month with no card and no expiry. Paid starts at €20 a month: Growth is €50 for 300 GB and Scale €150 for 1 TB, and above that pay as you go per gigabyte. Issue tracking and unlimited users are on every plan. AI investigations, the part that in Sentry is Seer, are included in the paid tiers (15 a month on Growth, 40 on Scale) rather than billed per person.⁴ Setup is one prompt in your coding agent, "Read fixter.dev/llms.txt and set up Fixter."

Where Sentry is still the better buy: you want the deepest error grouping and the widest set of SDKs, you need session replay, or your team already lives in it. Fixter is a younger product and there is no self-hosted option. For the full picture of what else is out there, see Sentry alternatives.

Frequently asked questions

Is Sentry free?

Yes. Sentry's Developer plan is free with no time limit: one user, 5,000 errors, 5 million spans, 50 session replays, 5 GB of logs, one uptime monitor and one cron monitor a month, with a 30 day lookback and alerts by email. Seer, Sentry's AI debugging agent, is not available on it.

How much does Sentry cost for a small team?

Team is $26 a month billed yearly or $29 billed monthly, with unlimited users and 50,000 errors included. Most 1 to 10 developer teams land between $26 and about $100 a month before Seer. Seer adds $40 per active contributor per month, which for a team of six is $240 on top.

Does Sentry charge per user?

Not on Team or Business, which both have unlimited users. The free Developer plan is limited to one user, so the second person on the project is what moves you to Team. Seer is priced per active contributor, at $40 a month each.

What happens when I go over my Sentry quota?

Data sent after your included volume, reserved volume and pay-as-you-go budget are used up is dropped, and you are not charged for it. That also means no monitoring for the rest of the billing month, so Sentry advises setting a budget that matches your usage.

How much does Seer cost?

$40 per active contributor per month on Team and Business, billed separately from your pay-as-you-go budget. An active contributor is a user with two or more pull requests to a Seer-enabled repository in the month. The older $20 a month plus $25 of credits pricing stopped being offered in January 2026.

How do I keep a Sentry bill predictable?

Prepay reserved volume at a discount, set a pay-as-you-go cap, turn on spend notifications and a maximum spend threshold (Team and above), and enable spike protection per project so a bad deploy drops events instead of running up the bill.