Self-host Mailpit on a VPS
An email testing tool that catches outbound mail.
A fake SMTP server that traps, stores and displays mail during development, with a web UI.
Why self-host Mailpit?
Mailpit makes testing signup, reset and notification emails safe and inspectable without sending anything real.
How to install Mailpit
- 1
Provision a VPS
Pick a Debian/Ubuntu template and get root SSH in about a minute.
- 2
Install the runtime
Install Single Go binary.
- 3
Deploy the application
Net what you need from the project’s official source and run it.
- 4
Put it behind TLS
Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.
- 5
Add it to your backups
Include the data directory and database in your backup routine before you rely on it.
Practical tips
- Give Mailpit its own database user with rights only on its own schema.
- Reverse-proxy Mailpit and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep Mailpit patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Mailpit need?
- Plan on 256 MB for typical use; add headroom if you expect many concurrent users.
- What stack does Mailpit run on?
- Single Go binary.
- Can I run other things on the same VPS?
- Yes — size the plan so Mailpit plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include MailHog, Mailcatcher, Mailtrap (hosted) — browse all app guides.
About Mailpit
Mailpit is open-source software released under the MIT licence. HostingSwift does not maintain, sell or support Mailpit itself — you install and run it on your own VPS. These are the official links to the project:
- Website: mailpit.axllent.org
- Source code: github.com/axllent/mailpit
Read the project's own documentation before deploying. We credit upstream projects because we genuinely run and recommend them — see our full open-source directory.