← Templates · Monitoring & Analytics
S(
Sentry (self-hosted, core)
Community11 services
Sentry, the open-source error and performance monitoring platform — self-hosted, so your data never leaves your own infrastructure.
Deploy Sentry (self-hosted, core)
| Runs | 11 services |
|---|---|
| Stack | sentry-websentry-workersentry-cronsentry-taskbrokersentry-relaysentry-snubasentry-clickhousesentry-kafkasentry-postgressentry-redissentry-symbolicator |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 11 services in this stack together — sentry-web, sentry-worker, sentry-cron, sentry-taskbroker, sentry-relay, sentry-snuba, sentry-clickhouse, sentry-kafka, sentry-postgres, sentry-redis, sentry-symbolicator — wired to reach each other over the private network, on a server you already pay for.
Deploying Sentry (self-hosted, core) is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Self-hosted error tracking and performance monitoring across your Railyard apps
- Keeping crash and event data on your own infrastructure instead of sentry.io
Good to know
- Known gap: web/worker still read Postgres/Redis/Kafka hosts from a config file the official installer bakes in, not from env vars — that wiring needs Railyard-side config support before this is live-usable
- Sentry's own install recommends 4+ CPU cores and 16GB+ RAM given Kafka, ClickHouse and Snuba all run alongside the app — size the server well above a toy instance