Infrastructure · Hybrid · unit: thousands of error events
Sentry pricing teardown: plan plus usage
Short answer
Sentry starts with a one-user Developer plan; paid usage and included amounts depend on data category, with different retention terms.
Pricing mechanics
| Plan or rate | Position in ladder |
|---|---|
| Developer | Entry |
| Team | Paid step |
| Business | Paid step |
| Enterprise | Sales-led; terms by quote |
- What the docs describe
- Developer is a one-user entry plan. Paid usage and included amounts depend on data category, with different retention terms.
- Free or trial fence
- Developer: one user.
- Overage or upgrade rule
- Paid usage above included amounts is billed per data category.
- Cap or spend control (none stated)
- Not stated in the linked pricing documentation.
A feature or configuration fence (what a plan includes) is not the same as an abuse cap. We do not infer private costs, margins or unpublished limits.
Takeaway for founders
When you have several signals, keep each meter and its retention visible on its own line.
Load into simulator
Illustrative remix · amounts and costs are editable.
Fictional tiers inspired by the pattern above. It does not reproduce Sentry's plans, invoices or margins. Fictional variable cost: $0.05 per thousands of error event. Sentry has several data categories; the remix uses error events as the representative meter.
| Tier | Model | Price | Limit | Accounts |
|---|---|---|---|---|
| Sample entry | Flat / seat | $0 (free) | hard cap 5 thousands of error events | 200 |
| Sample growth | Hybrid | $26.00 base, 75 thousands of error events included, then $0.22 each | hard cap 700 thousands of error events | 70 |
| Sample scale | Hybrid | $80.00 base, 350 thousands of error events included, then $0.18 each | hard cap 2,400 thousands of error events | 15 |
Related guide: Hybrid vs. usage-based billing · All teardowns