Pricing for Sentry
How pricing changes as you scale: upgrade triggers, cost cliffs, and plan structure (not a live price list).
Freshness & verification
Pricing behavior (not a price list)
These points describe when users typically pay more and what usage patterns trigger upgrades.
Actions that trigger upgrades
- Error volume exceeds 5K events/month free tier — Team plan at $26/month covers 50K events
- Team needs session replay to debug frontend issues — available on Team plan and above
- Organization requires SSO and advanced access controls — Business plan at $80/month
What gets expensive first
- Event quota is shared across all projects — one noisy service can consume quota intended for critical applications
- Performance monitoring transaction quota is separate from error quota — both need monitoring to avoid overages
- Data retention is 90 days on Team plan — historical analysis beyond 90 days requires Business plan or data export
Plans and variants (structural only)
Grouped by type to show structure, not to rank or recommend SKUs.
- Verify current pricing on the official website.
Compare pricing trade-offs head-to-head
Use these comparisons when you are down to two finalists and need a clearer trade-off view.
Next step: constraints + what breaks first
Pricing tells you the cost cliffs; constraints tell you what forces a redesign.
Sources & verification
Pricing and behavioral information comes from public documentation and structured research. When information is incomplete or volatile, we prefer to say so rather than guess.
Something outdated or wrong? Pricing, features, and product scope change. If you spot an error or have a source that updates this page, send us a correction. We prioritize vendor-verified updates and linkable sources.