Deploy listmonk
Self-hosted newsletter and mailing list manager, with Postgres
Just deployed
/listmonk/uploads
Just deployed
/var/lib/postgresql/data
Deploy and Host listmonk on Railway
listmonk is a free, open-source newsletter and mailing list manager. It is a single Go binary with a Postgres database and a web dashboard for managing subscribers and lists, writing and scheduling campaigns, transactional e-mail templates, and campaign analytics. It sends through your own SMTP servers or e-mail providers.
About Hosting listmonk
Hosting listmonk takes the listmonk server, a Postgres database, and storage for uploaded media. The database schema has to be installed on first start and migrated after every upgrade, and a super admin user has to exist before the dashboard is safe to expose. This template builds listmonk v6.2.0 from the official image, pinned by digest, and adds Railway Postgres. On every start it waits for Postgres, runs listmonk's idempotent install and upgrade, creates the super admin from the template variables on first boot, sets the Root URL to your Railway domain, and keeps media uploads on a volume. You still configure SMTP after logging in.
Common Use Cases
- Run a self-hosted newsletter for a blog, product or community without per-subscriber pricing
- Send product announcements and updates to customer lists, with double opt-in and unsubscribe handling
- Send transactional e-mails (password resets, receipts) from your apps through listmonk's API and templates
Dependencies for listmonk Hosting
- Postgres (Railway's Postgres service, included)
- An SMTP server or e-mail provider for sending (Amazon SES, Postmark, Mailgun, your own server)
Deployment Dependencies
- listmonk documentation: https://listmonk.app/docs/
- listmonk installation guide: https://listmonk.app/docs/installation/
- listmonk v6.2.0 release: https://github.com/knadh/listmonk/releases/tag/v6.2.0
- Template source and changelog: https://github.com/aalfath/listmonk-railway-template
Implementation Details
After the deploy finishes, open the listmonk service's public URL and log in as admin (or the user you set in LISTMONK_ADMIN_USER). The password is the generated LISTMONK_ADMIN_PASSWORD variable on the listmonk service. Both are used only on first boot. Change the password later in listmonk under Users.
Then go to Settings → SMTP and add your mail server, and send a test e-mail. The Root URL (Settings → General) is set to the Railway domain on first boot. If you add a custom domain, change it there so links in e-mails use it. Media uploads are stored on the volume at /listmonk/uploads, and S3 storage can be set in Settings → Media.
Updates: the service builds from the GitHub repo above. When a new listmonk version is merged there, Railway offers you the update. Read the changelog and back up Postgres first, because listmonk runs its database migrations on start.
Why Deploy listmonk 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 listmonk 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
