Offer your customers mail, today

A Linux VPS with Docker, a domain, and the ability to set DNS records. One command installs everything — Postfix, Dovecot, Rspamd, Postgres, the control plane and the webmail — as a Docker Compose bundle. The install guide is the whole of it.

You also need a provider that does not block outbound port 25, and a static IP with reverse DNS you control. That is a hosting question rather than a MailDock one, but it is the thing that most often decides whether self-hosted mail works.

Your incoming mail never does. From 0.13.0 a lapsed licence switches off extras in stages, and never touches the mail you receive:

• Days 0–30: everything works. The admin panel shows a countdown, and the server emails its owners.
• From day 30: new domains, mailboxes, AI features, new sending tokens and starting migrations are refused. Everything else keeps working.
• From day 60: the admin panel is read-only. Security actions (suspending a mailbox, resetting a password), the licence page and backups stay open.
• From day 90, and only once the licence period has ended without renewal (or 90 days after setup on a server never licensed): mail to outside addresses is refused. Receiving and reading mail, and delivery between your own mailboxes, carry on; so do forwards, auto-replies and password-reset links.

The 30 days run from the end of the subscription, or from the server’s last check-in with our licence server if it cannot reach us; a licence key installed on another machine is limited at once, until it is transferred. A server that cannot reach us never loses its outgoing mail: that kind of lapse stops at the read-only admin panel. Renewing restores everything as soon as the renewed key reaches the server (at once if you install it), and cancelling expires the licence at the end of the period you paid for; cancelling never revokes one.

Per server, per year. The tier sets a cap on mailboxes and domains — Starter is 10 mailboxes on 1 domain, Enterprise is uncapped — but you are never billed per seat, and adding a mailbox inside your cap costs nothing.

If you outgrow a tier, you change plan in the billing portal and the new limits arrive with the next licence heartbeat.

Yes — there is a connector for each, plus generic IMAP. A migration copies mailboxes, folders and flags, runs a delta sync so the mail that arrived during the copy is not lost, and can be resumed if it is interrupted.

The connectors read the source; nothing is deleted there, so you can run a full copy and still cut over whenever you choose.

Only what a user turns on, using a key you supply — Anthropic, OpenAI, Gemini, xAI, Groq, or a local model through Ollama or vLLM, in which case nothing leaves the machine at all.

AI features are per-user opt-in under a per-domain policy, attachments are excluded unless an administrator allows them (and no feature reads one yet), the call log records metadata rather than content (the admin copilot’s tool log keeps its tools’ arguments), and provider keys are encrypted at rest. There is no MailDock inference service, so there is no MailDock copy of your mail.

MailDock generates the records for every domain you add and shows them ready to paste, then verifies them live and alerts you when one drifts. DKIM keys are created for you; rotating one is a click, and the page tells you how long to keep the old record. ARC and SRS are handled on the way through.

It also ingests DMARC aggregate reports and parses MTA-STS and TLS-RPT, so the reports arrive as a dashboard rather than as XML in a mailbox nobody reads.

No. Instead, a first annual licence carries a 30-day money-back guarantee: if it is not right for you, tell us within 30 days of the charge and we refund it in full, however much you used it (the refund policy has the details).

The documentation is public, so you can read exactly how it installs and what it does before you buy.

Yes, and usually yourself, without contacting anyone. A licence is bound to one server at a time. When that machine changes — a rebuild, a restore onto new hardware, a new hostname — you move it from the new server: Licence → Move this licence to this server in the admin console, or mailctl license transfer. There is nothing to do on the old machine; the key installed on the new one is the proof.

Two cases come to us instead, and we move the licence for you: a key that is lost, and a key installed as it was first issued on a second server after another one had already claimed it. The admin console and mailctl license status say when that has happened — Another server has claimed this licence — and we issue a key for the server you mean to keep. If both should run, each needs its own licence.

That is deliberate: rebuilding a VPS is a normal Tuesday, and a licence that turns a rebuild into a support ticket is a licence that punishes good practice.

MailDock is a small commercial product, sold as an annual per-server licence. The honest answer to the second half is the licensing design: the software runs on your server, your mail is in Maildir and Postgres on your disk, and the enforcement is deliberately bounded — even an expired licence never stops the mail you receive.

We publish no customer counts, testimonials or logos we do not have. When there are design partners willing to be named, they will appear here and not before.