Deploy listmonk v6 Newsletter and Mailing List Manager
Self-hosted newsletters and mailing lists: campaigns, templates, analytics.
Just deployed
listmonk
Just deployed
Deploy and Host listmonk with Railway
listmonk is a self-hosted newsletter and mailing list manager: subscribers, lists, campaigns, templates, transactional mail and analytics in one Go binary on PostgreSQL. This community template runs listmonk v6 with Postgres 18 on Railway, creates the super admin for you and keeps media uploads on a volume.
About Hosting listmonk
listmonk needs one web service and a PostgreSQL database. The listmonk service serves the admin UI, the REST API and the public subscription, archive and unsubscribe pages from one port. On every start it waits for Postgres, installs the schema on the first run (with the super admin from the template variables, so the "create first user" page is never open to visitors), runs pending upgrades, then starts. Media you upload for campaigns lives on a Railway volume. listmonk itself sends mail through SMTP servers you add in Settings; on Railway, outbound SMTP is only available on the Pro plan.
Common Use Cases
- Company or product newsletters with double opt-in lists and public archive pages
- Transactional e-mail templates triggered from your app through the REST API
- Migrating off a hosted newsletter tool to keep subscriber data in your own Postgres
- Segmenting large subscriber bases with SQL queries and custom attributes
Dependencies for listmonk Hosting
- PostgreSQL (included, Postgres 18 with a volume)
- An SMTP provider for sending (SES, Postmark, Mailgun, SendGrid, your own server)
- Railway Pro plan for outbound SMTP, or a messenger webhook (see below)
Deployment Dependencies
- listmonk: https://listmonk.app
- Source and releases: https://github.com/knadh/listmonk
- Installation docs: https://listmonk.app/docs/installation/
- SMTP and messengers: https://listmonk.app/docs/messengers/
- Railway outbound networking (SMTP): https://docs.railway.com/networking/outbound-networking
Implementation Details
| Service | Image / source | Purpose | Public | Volume |
|---|---|---|---|---|
| listmonk | listmonk/listmonk:v6.2.0 (digest-pinned) + start script | Admin UI, API, public pages, campaign sending | yes | /listmonk/uploads |
| Postgres | postgres-ssl:18 | Subscribers, campaigns, settings | no | /var/lib/postgresql/data |
First login
- Open the listmonk service's public URL and go to
/admin. - Log in as
LISTMONK_ADMIN_USER(defaultadmin) withLISTMONK_ADMIN_PASSWORDfrom the listmonk service's Variables tab. - In Settings > SMTP, replace the placeholder
smtp.yoursite.comserver with your provider and use "Test connection". - In Settings > Media, the upload path
uploadsalready points at the volume.
E-mail on Railway. listmonk sends through SMTP only. Railway allows outbound SMTP on the Pro plan; on Trial and Hobby the SMTP test fails with a timeout. Options there: upgrade to Pro, or add an HTTP "messenger" (Settings > Messengers) that posts each message to a relay you run that uses your provider's HTTP API.
Public root URL. On the first install the start script writes ROOT_URL (your Railway domain) into listmonk's settings, which listmonk uses for unsubscribe, archive and tracking links. After you add a custom domain, change it in Settings > General > Root URL.
Admin password reset. Set LISTMONK_ADMIN_PASSWORD to a new 8-72 character value and RESET_ADMIN_PASSWORD=true on the listmonk service, redeploy, log in, then set RESET_ADMIN_PASSWORD=false. A password that is too short or too long never fails the deploy: a new install then gets a random password nobody knows and the log explains this reset.
Scaling. One listmonk instance handles large lists; raise its sending concurrency and rate in Settings > Performance and give the service more CPU. Keep one replica (the uploads volume and the campaign runner are single-instance). Postgres grows with subscribers and campaign views/clicks.
Versions and upgrades. The image is pinned by tag and digest in services/listmonk/Dockerfile. To upgrade, change the tag and digest in your fork and redeploy; the start script runs listmonk --upgrade before the app starts. Back up Postgres first.
Licence. listmonk is AGPL-3.0. If you modify listmonk and offer it to others over a network, you must offer them your modified source. This template is a community template and is not affiliated with the listmonk project.
Why Deploy listmonk on Railway?
Railway runs listmonk and its database privately connected, with a volume for media, generated credentials and HTTPS on a public domain, so you go from template to a logged-in admin in a few minutes and pay only for what the two services use.
Template Content
