updated Oct 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Oct 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
The full self-hosted edition of Sentry's error tracking and performance monitoring: exceptions, stack traces, releases, alerts, tracing, session replay and profiling, using the same SDKs as the hosted product. The upstream self-hosted repository is a Docker Compose blueprint of about 50 containers (Kafka, ClickHouse, Postgres, Snuba, Relay and more) licensed under the Functional Source License (FSL-1.1-Apache-2.0) — source-available, converting to Apache 2.0 after two years — and it needs 4 CPU cores and 16 GB of RAM at minimum.
Pick the full Sentry stack only when you specifically need Sentry itself: its SDK ecosystem, tracing, session replay and profiling on your own hardware, with data that never leaves your network. It is a heavy install, not a small tool. If you only need exception tracking with the same SDKs, GlitchTip or Bugsink do that in a few hundred MB of RAM instead of 13 GB.
What you need
Any VPS with at least 16384 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Sentry self-hosted — the official repo at release 26.9.0. The project's minimum is 4 CPU cores and 16 GB RAM (plus 16 GB swap on a 16 GB box); install.sh refuses to run below about 14 GB.git clone https://github.com/getsentry/self-hosted.git && cd self-hostedgit checkout 26.9.0# --skip-user-creation: non-interactive; --no-report-self-hosted-issues: do not send install telemetry to Sentry./install.sh --skip-user-creation --no-report-self-hosted-issuesdocker compose up --wait # → http://SERVER_IP:9000# create the first superuser (replace the email); the generated password is printed on the next linePW=$(openssl rand -hex 12); docker compose run --rm web createuser --email you@example.com --password "$PW" --superuser; echo "$PW"# port 9000 is published on all interfaces, no TLS; put a reverse proxy in front. Databases and brokers are not published.
Self-hosted Sentry is a blueprint for a whole platform, so the cost shows up in resources and maintenance:
non-negotiableIt is heavy. Upstream's minimum is 4 CPU cores and 16 GB of RAM (with 16 GB of swap on a 16 GB box), and the installer refuses to run below about 14 GB. In our install check the stack ran about 50 containers and idled around 13.3 GB of RAM on a 16 GB machine, leaving almost no headroom. Plan for a 32 GB server if the box does anything else.
non-negotiableThe licence is the Functional Source License (FSL-1.1-Apache-2.0), not an OSI open-source licence: you can self-host and modify it for your own use, but not run a competing commercial service, and each release converts to Apache 2.0 after two years.
non-negotiableUpstream gives no support guarantee for self-hosted: help comes from the community Discord. Billing, spike protection and Seer and other AI features are not part of it, and mobile symbolication is limited.
non-negotiablePort 9000 is published on all interfaces without TLS. Put a reverse proxy with HTTPS in front before exposing it, and set the system URL prefix in the UI to match.
non-negotiableReleases are monthly and upgrades re-run the installer, which can migrate ClickHouse and Postgres. Pin a release tag as the install here does, back up the Docker volumes first, and read the release notes before bumping.
non-negotiableDisk I/O matters as much as RAM: databases and brokers share one machine, and upstream warns that sustained iowait above 10 percent means the host cannot keep up.