Self-Hosted Support
We strive to provide a great self-hosted experience for folks willing to try Sentry that way. The self-hosted repository is geared towards low traffic loads (less than ~1 million submitted Sentry events per month). We believe keeping this setup simple is important to show how various components fit together. Folks needing larger setups can expand from here based on their specific needs and environments.
Note
Please see our troubleshooting section before posting on the forum or filing an issue.
The self-hosted project maintains only the Docker Compose deployment. Sentry does not publish Kubernetes manifests or Helm charts for self-hosted installations and does not provide support for those deployment methods.
A community-maintained Helm chart is available, but it is not affiliated with Sentry and falls outside the self-hosted project's support scope. Direct questions and bug reports about that chart to its issue tracker.
Our principles for the support of self-hosted Sentry are:
- We DO NOT provide dedicated support for self-hosted.
- DO file an issue for questions about your setup.
- DO file an issue for missing docs, bugs during upgrades or installation.
- DO file an issue for functionality problems such as broken auth, features not working, etc.
- DO submit PRs directly for simple fixes.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").