
Deploy Nightingale
Open-source alerting and monitoring, MySQL + Redis, no default passwords
MySQL
Just deployed
/var/lib/mysql
Nightingale
Just deployed
/app/data
Redis
Just deployed
/data
Deploy and Host Nightingale on Railway
Nightingale (n9e) is an open-source, Apache-2.0 licensed alerting and monitoring platform. It evaluates alert rules against Prometheus, VictoriaMetrics, Elasticsearch, Loki, ClickHouse and SQL data sources, processes and routes alert events to chat, email and on-call tools, and includes dashboards, a built-in time-series database, an AI agent and an MCP server.
About Hosting Nightingale
Nightingale is a single Go server with a web UI that needs a relational database (MySQL, PostgreSQL or SQLite) and Redis. Its upstream Docker setup ships fixed example credentials: the admin is root / root.2020, and the internal service API uses a published default password. This template runs the official v9.3.0 image, pinned by digest, with Railway MySQL and Redis on the private network. A small start script writes the configuration from Railway variables, starts Nightingale on localhost first, and replaces the default admin password with a generated one before the public port opens. Metrics stored in the built-in time-series database live on a volume, so they survive redeploys.
Common Use Cases
- Alerting on metrics, logs and database queries from data sources you already run, with notifications to Slack, email, Telegram, webhooks and other channels
- Lightweight host and service monitoring: install the categraf agent on a machine and send its metrics to the built-in time-series database
- A team alerting hub with business groups, permissions, alert muting and event history in one place
Dependencies for Nightingale Hosting
- MySQL (Railway MySQL, included) for users, alert rules, dashboards and events
- Redis (Railway Redis, included) for login sessions, caches and agent heartbeats
Deployment Dependencies
- Nightingale source and releases: https://github.com/ccfos/nightingale
- Nightingale documentation: https://n9e.github.io/docs
- Official image: https://hub.docker.com/r/flashcatcloud/nightingale
- categraf agent for collecting metrics: https://github.com/flashcatcloud/categraf
- Template repository: https://github.com/aalfath/nightingale-railway-template
Implementation Details
After the deploy finishes, open the public domain and sign in as root with the value of N9E_ADMIN_PASSWORD from the Nightingale service's Variables tab. Change it in the UI afterwards if you like; the variable is only used while the default password is still active.
The built-in time-series database is registered as the embedded-tsdb data source (15 days retention, 3 GiB cap by default). Agents push metrics over HTTPS to the public domain with basic auth: user agent, password N9E_AGENT_PASSWORD. Anonymous queries are turned off.
Optional settings you can add to the Nightingale service: N9E_TSDB_RETENTION (for example 30d), N9E_TSDB_MAX_BYTES (for example 10GiB), N9E_EVALLOG_MAX_GB and N9E_LOG_LEVEL. Notification channels (SMTP, chat webhooks) and SSO are set up in the web UI. Updates to the pinned version reach you as a Railway "update available" notice; the repository's CHANGELOG.md lists what changed.
Why Deploy Nightingale 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 Nightingale 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

