explaingit

getsentry/self-hosted

9,333ShellAudience · ops devopsComplexity · 3/5LicenseSetup · moderate

TLDR

Run the full Sentry error tracking and performance monitoring platform on your own server using Docker Compose, same features as the cloud version, with your data staying on your own infrastructure.

Mindmap

mindmap
  root((self-hosted Sentry))
    What It Does
      Error tracking
      Performance monitoring
    Setup
      Docker Compose
      Shell scripts
    Audience
      DevOps teams
      Privacy-focused orgs
    Scope
      Full feature parity
      Low-volume use
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Host your own error tracking server to keep crash and performance data private on your own infrastructure

USE CASE 2

Evaluate Sentry's full feature set without sending data to Sentry's cloud or committing to a paid plan

USE CASE 3

Run Sentry for a team with compliance requirements that prevent sending error data to third-party services

Tech stack

DockerDocker ComposeShell

Getting it running

Difficulty · moderate Time to first run · 1h+

Requires Docker and Docker Compose, intended for low-volume deployments and proofs-of-concept, not high-traffic production.

You may use and inspect the code but there are some commercial restrictions under the fair-source license.

In plain English

This repository provides the scripts and configuration needed to run Sentry on your own server instead of using the hosted cloud service. Sentry is an error tracking and performance monitoring platform: when software crashes or throws an exception, Sentry captures the details and organizes them so developers can see exactly what broke, where in the code it broke, and how often it is happening. The self-hosted version packages the full Sentry platform using Docker and Docker Compose. Docker is a system for running applications in isolated containers, and Docker Compose is a tool for starting multiple containers together in a coordinated way. The setup here handles all the components Sentry needs, including its database, message queue, and web interface, so you do not have to piece them together manually. According to the repository description, this setup is intended for low-volume deployments and proofs-of-concept. It is described as feature-complete, meaning the functionality matches the hosted cloud product, but it is packaged for smaller-scale use rather than high-traffic production environments. Teams that want to keep their error data on their own infrastructure for privacy or compliance reasons, or who want to evaluate Sentry before committing to a paid plan, are the likely audience. The README itself is very brief and points to a separate documentation site for full setup instructions. The repository is tagged with the fair-source license, which is a licensing model that allows use and inspection of the code with some commercial restrictions.

Copy-paste prompts

Prompt 1
Walk me through setting up self-hosted Sentry with Docker Compose on a fresh Ubuntu VPS, including a custom domain and SSL.
Prompt 2
How do I upgrade my self-hosted Sentry installation to the latest version without losing existing error and performance data?
Prompt 3
My self-hosted Sentry feels slow. Which Docker Compose services should I scale up and what are the recommended resource minimums?
Prompt 4
Show me how to connect a Python Flask app to my self-hosted Sentry instance using the Sentry SDK.
Open on GitHub → Explain another repo

← getsentry on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.