Deploy Keep

Keep AIOps alert management: UI, API, websocket server and Postgres

Deploy Keep

Just deployed

/var/lib/postgresql/data

Just deployed

Deploy and Host Keep on Railway

Keep is an open-source AIOps and alert management platform. It collects alerts from your monitoring tools (Prometheus, Grafana, Datadog, Sentry, CloudWatch and many more) into one inbox, deduplicates and correlates them into incidents, and runs YAML workflows that enrich alerts, open tickets or notify people automatically.

About Hosting Keep

Keep is not a single container. This template runs the full stack upstream ships, wired over Railway's private network: the Next.js web UI (the public entry point, which proxies API calls under /backend), the FastAPI backend (alert ingestion, workflows, scheduler, database migrations on boot), a Soketi websocket server that pushes new alerts to open browser tabs in real time, and PostgreSQL 17 on a volume. Session secrets, Pusher credentials, the database password and the first admin's password are generated at deploy time, so the deployer isn't asked for anything. Provider credentials are stored in Postgres, so nothing else needs a volume.

Common Use Cases

  • One alert inbox for several monitoring tools, with deduplication and noise reduction
  • Grouping related alerts into incidents and tracking them to resolution
  • Workflow automation: enrich alerts, create Jira or ServiceNow tickets, notify Slack or PagerDuty

Dependencies for Keep Hosting

  • The monitoring tools you want to connect (as providers in the UI, or by sending alerts to Keep's webhook)
  • Optional: an OpenAI API key for AI correlation and summaries

Deployment Dependencies

Implementation Details

Services in this template:

  • Keep: web UI, public. Health check /api/healthcheck.
  • Keep Backend: API, alert and webhook ingestion, workflows. Private network only. Health check /healthcheck.
  • Keep Websocket: Soketi, with its own public domain because browsers connect to it directly. Health check /.
  • Postgres: alerts, incidents, workflows, users and provider credentials, on a volume.

After deploy: open the Keep public URL and sign in as keep with the password in KEEP_DEFAULT_PASSWORD on the Keep Backend service's Variables tab. Then connect providers, or send alerts to the webhook shown in the UI. Optional features go on Keep Backend as variables: OPENAI_API_KEY, or SSO (AUTH_TYPE on both Keep Backend and Keep). If you add a custom domain to Keep, update NEXTAUTH_URL on Keep and KEEP_API_URL on Keep Backend; for one on Keep Websocket, update PUSHER_HOST on Keep.

Updates: the three Keep services build from the template's GitHub repo. When the pinned versions are bumped there, Railway shows an update notice on your project and you choose when to apply it. Read the repo's CHANGELOG first. Keep migrates its database on boot.

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


Template Content

More templates in this category

View Template
Rootprint
Open-source logs and traces with full-text search on object-storage.

Rootprint
1
View Template
Pyroscope profiling
Protected continuous profiling with durable Pyroscope storage.

Anton Orel
1
View Template
SigOnly
Deploy SigNoz with a working demo app & config in one click

zoeyjones
21