Deploy and Host calert on Railway

calert forwards Prometheus Alertmanager webhook alerts to Google Chat (and similar providers). It is a single lightweight Go binary with TOML or environment-based configuration.

About Hosting calert

This template deploys ghcr.io/mr-karan/calert:v2.4.0 on port 6000. Provider settings use CALERT_ environment variables (app.address → CALERT_APP__ADDRESS). A demo provider ships with dry_run=true so the service starts without a real Google Chat webhook; replace the endpoint and set dry_run=false when you are ready. Point Alertmanager's webhook receiver at your Railway public URL.

Common Use Cases

Route Alertmanager firing/resolved alerts into Google Chat spaces
Dry-run template and threading experiments before production cutover
Lightweight chat notifications without a heavy alerting stack

Dependencies for calert Hosting

Public domain — Alertmanager must reach the / webhook endpoint on port 6000
Google Chat webhook URL — required once you leave dry-run mode

Deployment Dependencies

calert repository
Public image — ghcr.io/mr-karan/calert:v2.4.0
Sample config

Implementation Details

At deploy time, set:

CALERT_PROVIDERS__DEMO__ENDPOINT — Google Chat webhook URL
CALERT_PROVIDERS__DEMO__DRY_RUN — false to send real messages (default true for safe first boot)

Why Deploy calert 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 calert 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.