When to self-host
Self-hosting is a good fit when you:- Must keep event data within your own network or a specific region
- Have compliance requirements that prevent sending data to a third-party SaaS
- Want to customize Sentry’s configuration or run it behind an internal firewall
The managed cloud service at sentry.io has a free tier and requires no infrastructure to maintain. If you don’t have a specific reason to self-host, the cloud service is the faster way to get started.
How it works
The self-hosted distribution uses Docker Compose to orchestrate all of Sentry’s required services:- Sentry web — the Django application and API server
- Sentry worker — Celery background task workers
- Sentry cron — scheduled task processor
- PostgreSQL — primary relational database
- Redis — caching, rate limiting, and queuing
- ClickHouse (via Snuba) — event storage and querying
- Relay — event ingestion and filtering proxy
- Symbolicator — debug symbol processing for native and mobile crashes
sentry.conf.py file and environment variables. The configuration file extends Sentry’s defaults and supports overriding any Django setting.
Single-organization mode
Self-hosted installations default to single-organization mode:False if you want to host multiple organizations on a single instance.