Deploy Plunk

Open-source email platform on AWS SES: transactional, campaigns, workflows

Deploy Plunk

Just deployed

/data

/var/lib/postgresql/data

/data

Deploy and Host Plunk on Railway

Plunk is an open-source email platform built on AWS SES. One dashboard covers transactional email through a REST API, marketing campaigns, contacts and segments, and event-driven workflows such as welcome or onboarding sequences. It tracks opens, clicks, bounces and complaints, and is licensed AGPL-3.0.

About Hosting Plunk

Plunk's official image runs its API, background worker and dashboard, and needs PostgreSQL, Redis and AWS SES credentials. Upstream routes each app by host name, so it expects four separate domains. This template serves the dashboard on /, the API on /api and uploaded images on /uploads from one Railway domain, so it answers on the first deploy. It adds Railway Postgres, Redis and a private MinIO bucket on a volume, runs database migrations on every start, creates your admin account and keeps sign-ups closed. You supply an admin email and SES keys.

Common Use Cases

  • Send transactional email (sign-up confirmations, password resets, receipts) from your app through one API call
  • Run newsletters and marketing campaigns to segmented contact lists with open and click tracking
  • Automate drip and onboarding sequences triggered by events your app sends to Plunk

Dependencies for Plunk Hosting

  • An AWS account with SES (an IAM access key, a verified sending domain, and production access for sending to anyone)
  • PostgreSQL, Redis and MinIO, all included in this template

Deployment Dependencies

Implementation Details

What you get:

  • Plunk (public): Plunk v0.18.0, pinned by version and digest, built from the template's GitHub repo. Health check: /api/health.
  • MinIO (private, volume): stores images uploaded in the email editor. Plunk serves them read-only at /uploads.
  • Postgres and Redis (private, volumes).

After deploying:

  1. Open the Plunk domain and log in with ADMIN_EMAIL and the generated ADMIN_PASSWORD (Plunk service, Variables tab).
  2. In AWS, create the SNS topic and the plunk-configuration-set configuration set from Plunk's SES guide. The SNS subscription endpoint is https://YOUR-DOMAIN/api/webhooks/sns.
  3. Add and verify your sending domain in Plunk, then send with your project's secret key to https://YOUR-DOMAIN/api/v1/send.

Optional: set DISABLE_SIGNUPS=false on the Plunk service for a moment to let a teammate register; set PUBLIC_URL=https://YOUR-DOMAIN after adding a custom domain; add GitHub or Google OAuth keys. The landing page, docs site and SMTP relay from the upstream image aren't run.

Updates: the template builds from its GitHub repo, so Railway shows you an update notice when a new Plunk version is merged there. Read the repo's CHANGELOG before applying it. Migrations run automatically on start.

Why Deploy Plunk 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 Plunk 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

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0