Deploy Novu
Self-hosted notification infrastructure: in-app inbox, email, SMS, push
Just deployed
novu-worker
Just deployed
Redis
Just deployed
/data
novu-api
Just deployed
MongoDB
Just deployed
/data/db
novu-dashboard
Just deployed
novu-storage
Bucket
Just deployed
Deploy and Host Novu on Railway
Novu is open-source notification infrastructure. You define a workflow once, with in-app inbox, email, SMS, push and chat steps plus delays and digests, then trigger it from your backend with one API call. Novu handles provider credentials, subscriber preferences, retries and a ready-made in-app inbox.
About Hosting Novu
Self-hosted Novu (Community Edition 3.20.0) runs four services from the official images: the API, a worker that processes the queues and delivers messages, a WebSocket server for the real-time inbox, and the web dashboard. It needs MongoDB for data, Redis for queues and cache, and S3-compatible storage for attachments. This template wires all of it over Railway's private network. It generates the JWT and encryption secrets, keeps MongoDB and Redis on volumes, uses a Railway bucket for attachments and gives the API, WebSocket server and dashboard public URLs with health checks. You fill in nothing at deploy time.
Common Use Cases
- Send product notifications (in-app inbox, email, SMS, push, Slack and other chat) from one API call
- Add a real-time notification inbox to a web app with Novu's React or JavaScript SDK
- Batch frequent events into digests and let users manage their notification preferences
Dependencies for Novu Hosting
- MongoDB (pinned official
mongo:8.0image, on a volume) - Redis (pinned official
redis:8.2image, on a volume) - A Railway bucket (S3-compatible) for attachments
Deployment Dependencies
- Novu source and releases: https://github.com/novuhq/novu (release v3.20.0)
- Self-hosting docs: https://docs.novu.co/community/self-hosting-novu/overview
- Template repo (Dockerfiles, start scripts, changelog): https://github.com/aalfath/novu-railway-template
Implementation Details
After deploy
- Open the novu-dashboard URL and create your account. The first account becomes the owner of the instance.
- Sign-up then closes: further registrations are refused, so nobody else can create an account on your instance. To add teammates, set
ALLOW_OPEN_REGISTRATION=trueon novu-api, redeploy, and remove it afterwards. To disable sign-up entirely, setDISABLE_USER_REGISTRATION=true. - Copy your secret key under API Keys, connect your providers under Integrations, and trigger a workflow. In the SDKs set
backendUrlto the novu-api URL andsocketUrlto the novu-ws URL.
Secrets: JWT_SECRET, STORE_ENCRYPTION_KEY (32 characters, encrypts provider credentials) and NOVU_SECRET_KEY are generated on novu-api. The worker and WebSocket server reference them. Never change STORE_ENCRYPTION_KEY after setup, or stored provider credentials can no longer be read.
Updates: every Novu service builds from the template repo, where each image is pinned by version and digest. When a new Novu version is merged there, Railway shows you an update notice and you choose when to apply it. Read CHANGELOG.md in the repo first, and back up MongoDB before a major upgrade.
Optional settings: self-hosted mode, pool sizes and telemetry defaults live in each service's start.sh as overridable defaults. Set any of them as a service variable to change it.
Why Deploy Novu 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 Novu 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
novu-worker
aalfath/novu-railway-templateRedis
redis:8.2.11novu-api
aalfath/novu-railway-templateMongoDB
mongo:8.0.38novu-dashboard
aalfath/novu-railway-templatenovu-storage
Bucket
