Deploy Sentry (Errors Only Mode)

Deploy and Host Sentry (Errors Only Mode) on Railway

Sentry is the industry-standard error tracking platform. This template deploys real self-hosted Sentry — the same stack as getsentry/self-hosted in its errors-only profile — with issues, grouping, metric alerts, and stack-trace symbolication, at the bleeding edge (nightly) or pinned to any upstream release.

About Hosting Sentry (Errors Only Mode)

Self-hosted Sentry is a genuinely heavy, multi-service system: Postgres, Redis, Kafka, ClickHouse, and Memcached feed Sentry's web UI, Relay ingestion gateway, Snuba query engine, Symbolicator, and a fleet of stream consumers. This template runs the complete upstream errors-only profile as 23 cooperating Railway services on the private network, with one public nginx entrypoint carrying upstream's exact routing (your DSNs and UI share one domain). Deployment is one-click — no required inputs: the admin login defaults to admin@example.com with a generated password (both editable on the web service). First boot is zero-touch: secrets are generated per deployment, Relay credentials persist to a volume, object storage lives in a Railway bucket with retention lifecycle, and database migrations plus Kafka topics bootstrap automatically. Expect 10–14 GB resident RAM — this is the genuine article, not a lookalike.

Common Use Cases

• Keep exceptions, stack traces, and user context inside infrastructure you control — for compliance, data residency, or simply avoiding per-event SaaS pricing at volume
• Full-fidelity error monitoring with working metric alerts, issue grouping, and native/JS symbolication for teams already using Sentry SDKs (change nothing but the DSN)
• Track upstream Sentry releases on your own schedule — run nightly to live at master, or pin a release tag and upgrade by changing one variable

Dependencies for Sentry (Errors Only Mode) Hosting

• Sentry's official container images (ghcr.io/getsentry/* — sentry, snuba, relay, symbolicator, taskbroker) at the version you select
• An external SMTP provider if you want email notifications (Railway has no in-platform email; with SMTP unset, email is cleanly disabled)

Deployment Dependencies

• Official self-hosted Sentry guide — the upstream deployment this template mirrors
• getsentry/self-hosted — upstream source of the service topology and configuration
• Template source repository — wrapper Dockerfiles and rendered configuration
• Sentry SDK documentation — point any SDK at a DSN from your deployment's domain

Implementation Details

The version knob is one variable — SENTRY_VERSION on the nginx service, referenced by every other service:

SENTRY_VERSION=nightly   # track upstream master
SENTRY_VERSION=26.7.2    # pin an upstream release

Each service is a thin Dockerfile wrapper: FROM ghcr.io/getsentry/<img>:${SENTRY_VERSION}, plus the upstream configuration fetched at the matching ref and rendered from environment variables at boot — configs always match the images, with no forked files to rot. Changing the variable and redeploying upgrades the whole stack; sentry upgrade and snuba bootstrap run migrations idempotently on start, exactly as upstream recommends. Event payloads, uploads, and profiles live in the template's Railway bucket under separate key prefixes, with retention enforced by a native lifecycle rule tied to SENTRY_EVENT_RETENTION_DAYS.

Why Deploy Sentry (Errors Only Mode) on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Sentry (Errors Only Mode) on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.