listmonk
Self-hosted newsletters and mailing lists - millions of subscribers on a flat plan, sent through any relay you like.
One-click deploy, from $13/mo on a Miget plan.
Newsletter SaaS prices by subscriber count, which means your bill grows precisely when your project succeeds. listmonk decouples that: a single Go binary on Postgres that manages subscribers, double opt-in, campaigns, templates, and analytics - while delivery goes through whatever relay you configure.
That architecture is the honest one for a PaaS: platforms cannot send port-25 mail credibly (nobody can, from shared IPs), so listmonk hands delivery to SES (~$0.10 per 1,000 emails), Resend, Postmark, or Mailgun - configured in the admin UI - and owns everything else.
This template is fully env-driven on a managed Postgres, with listmonk’s idempotent install/upgrade running on every deploy. A 50,000-subscriber list that costs hundreds monthly on hosted platforms runs here for $13 plus relay postage.
Upstream project: listmonk
#what you get
- Subscriber management with double opt-in and custom attributes
- Campaigns, templating, A/B-style experiments, click/open analytics
- Sends via any SMTP relay - SES, Resend, Postmark, Mailgun
- Public subscription pages included
- Managed Postgres auto-provisioned; schema auto-upgrades on deploy
- Go-fast: millions of subscribers on this footprint
#topology
| Service | Role | Public |
|---|---|---|
| listmonk | admin + public pages (:5000) | yes |
| db | Postgres - managed service on Miget, container locally | no |
#miget sizing
// this stack needs
1.5 GiB RAM · 5 GB disk · 2 services
listmonk itself idles near 50 MB; the database carries the list. Campaign throughput is governed by your relay’s rate limits, not this plan.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| listmonk on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| Resend | Pro | ~$20 | 50k emails/mo - works great AS the relay under listmonk too |
| Postmark | Basic | ~$15 | 10k emails/mo, $1.80 per extra 1k |
listmonk is the list/campaign layer, not the pipe: pair it with SES (~$0.10/1k) or any relay above - no per-subscriber pricing anywhere in the stack.
#vs. other PaaS
Estimated monthly cost of running this exact stack (1.5 GiB RAM, 5 GB disk, 2 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$75 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$23 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$20 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$16 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$10 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
listmonk -
Set the required variable:
LISTMONK_ADMIN_PASSWORD, first-run admin bootstrap (with LISTMONK_ADMIN_USER)
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/listmonk
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
What does sending actually cost?
The relay’s rates: Amazon SES is ~$0.10 per 1,000 emails, Resend Pro is $20/month for 50k, Postmark $15/month for 10k. listmonk adds no per-subscriber or per-send fee on top - a 100k-send month through SES costs about $10 in postage plus this $13 plan.
Why not just use the relay’s own campaign tools?
Ownership and limits: your subscriber list, consent records, and engagement data live in your Postgres, exportable as SQL - and switching relays is a settings change, not a migration. Relay-native tools also tier their campaign features by contact count; listmonk does not count.
Does it handle double opt-in and GDPR basics?
Yes - double opt-in flows, per-list consent, unsubscribe links, and full data export/wipe per subscriber are built in. The public subscription pages run on the same domain.
Ship listmonk today
One compose stack, 1.5 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.