← Templates · Monitoring & Analytics
GO
GoAlert
CommunityOn-call scheduling and alert routing — escalation policies, rotations, and notifications for an engineering team.
| Runs | goalert/goalert:v0.35.0 |
|---|---|
| Stack | go |
| Provisioned for it | postgres |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions postgres alongside it automatically — zero-downtime deploys, automatic backups and scaling come from the same platform, on a server you already pay for.
Deploying GoAlert 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
- On-call scheduling, escalation policies, and alert routing for an engineering team
- A self-hosted PagerDuty/Opsgenie alternative wired into your own monitoring stack
- Webhook/email-based alert intake with rotation and ack/close workflows
Good to know
- Postgres is wired up automatically; the release phase runs GoAlert's schema migration before boot
- GoAlert ships with no default admin account — after the first deploy, open a console on this app and run `goalert add-user --user-name=admin --user-email=you@example.com --user-pass='<password>' --user-role=admin` to create your first login
- The experimental system gRPC API and the SMTP email-integration listener aren't enabled by this template