Sentry is open-source and self-hostable for free — but infrastructure costs real money. Here's an honest cost comparison with AWS estimates, operational trade-offs, and the break-even point.
Sentry self-hosted uses Docker Compose. Here are representative AWS costs for three volume levels:
Tight on resources — minimal redundancy
Production-grade, moderate redundancy
High availability, multi-AZ
| Aspect | Sentry Cloud | Self-Hosted |
|---|---|---|
| Software cost | $0–$80+/mo (plan) | Free (open-source) |
| Infrastructure cost | Included | $140–$1,500+/mo |
| Maintenance burden | None | 2–4 hrs/month + upgrades |
| New features | Immediate | Manual upgrade required |
| Uptime SLA | 99.9% (Enterprise) | Your responsibility |
| Data sovereignty | US/EU (Enterprise) | Full control |
| HIPAA compliance | Enterprise BAA | You're responsible |
| Scaling | Automatic | Manual, requires capacity planning |
| Break-even point | < 250K errors/mo | > 500K errors/mo |
| Best for | Teams under 50 devs | Large teams with DevOps |
The infrastructure cost isn't the full picture. Self-hosted Sentry requires ongoing engineering time: monthly upgrades (Sentry releases every 2-4 weeks), database vacuuming, Kafka consumer lag monitoring, disk space management, and incident response when things break. At a conservative 3 hours/month and $100/hr engineering cost, that's $300/month of hidden cost on top of infrastructure. Add that to your break-even calculation.
Sentry's self-hosted version is free in terms of software licensing — it's open-source. However, you still pay for the infrastructure to run it. A minimal self-hosted Sentry deployment on AWS (suitable for ~100K events/month) requires at least 4 virtual machines (2 CPU, 8GB RAM each), an RDS PostgreSQL instance, and S3 storage, costing roughly $200-$400/month. A production-grade deployment for 1M+ events/month can cost $800-$2,000+/month in AWS infrastructure.
Sentry provides an official Docker Compose-based self-hosted installer (github.com/getsentry/self-hosted). Initial installation is straightforward for teams familiar with Docker and Linux. However, ongoing maintenance includes: upgrading to new Sentry versions (released monthly), managing PostgreSQL database health, tuning Kafka and Redis, and handling disk space for event storage. Budget 2-4 hours/month of engineering time for a well-running self-hosted instance, more during major version upgrades.
Self-hosting typically becomes cost-effective when your Sentry Cloud bill exceeds $500-$800/month — which usually means 250K-500K+ errors/month sustained. At those volumes, self-hosted infrastructure (typically $300-$600/month) is cheaper than cloud event pricing. The break-even depends heavily on your team's operational capability and engineering hourly cost. Factor in 2-4 hours/month of DevOps time at your engineering rate.