Maillayer ships as a single Docker image (ghcr.io/mddanishyusuf/maillayer-pro). Pick a host, pull the image, point it at an email provider — that's the whole flow.
Pick an install path
- Railway — the fastest. One click, a managed volume, and an HTTPS URL in two minutes.
- Any VPS — paste one
curlcommand on a Hetzner/DigitalOcean/AWS box. Best price/control trade-off. - Docker Compose — drop the image into Coolify, CapRover, Dokploy, or your own compose stack.
What you'll need
- A Linux host with Docker (or a Railway account).
- An email provider account: SMTP, Amazon SES, SendGrid, or Mailgun.
- (Optional) A domain you control, for SPF / DKIM on your sender address.
The whole flow at a glance
- Install. Pick a path above and run the install command.
- Sign up. Visit your URL — the first account becomes the owner.
- Create a brand. Each brand has its own provider, contacts, campaigns, and integrations. Multi-brand →
- Configure a provider. Brand settings → Provider → paste credentials.
- Send a test. Use the "Send test" button to confirm delivery.
- Build something. Import contacts, draft a campaign, wire up an integration. Done.
The SQLite question
Yes, it scales further than you think. SQLite handles millions of contacts on a $5 VPS as long as you mount the volume on a persistent disk. See Backups for the redundancy story.
Already running?
Skip ahead: