Roadmap
What is coming, and what is not
No dates. A roadmap with dates on it is a set of promises, and this one is a set of intentions — worth publishing so that asking about something is not a surprise.
Before 1.0
Everything the product does today is built and tested. What is left before 1.0 is mostly proof: design-partner installs on real domains, a deliverability gate met from a live host, and a purchase run end to end. The admin panel was redesigned in 0.14.0; the one piece of new work left is a redesigned webmail.
Design-partner installs
Three real installs carrying real mail, which is the only test that has not been run.
The deliverability gate
Mail from a live host scored against the usual tests, from an IP with its own reputation.
Purchase, end to end
A licence bought through this site, issued, activated and transferred.
A redesigned webmail
A full-size composer, resizable panes, a conversation view, inbox categories, fuller filters and a usable phone view. The redesigned admin panel shipped in 0.14.0.
After 1.0
Intended for the 1.x line. Nothing here has a date, and the order will change with what customers actually need.
Provider tier
Sub-accounts, per-tenant quotas and branding, delegated admin — for hosting providers reselling mail. The schema already carries it.
The rest of transactional email
Sending from your applications shipped in 0.5.0: a scoped API token, one HTTP call, a status you can read back, and @maildock/sdk. A sending console, webhooks (for your applications, and so a blocklisting reaches your systems), templates, a suppression list and inbound parsing follow; marketing campaigns last, on sending streams of their own.
Server-side AI triage
Delivery-time categorisation, priority inbox and natural-language rules layered on the existing spam engine.
Native .deb packaging
Debian and Ubuntu with systemd, as an alternative to Docker Compose.
PST and mbox import
The migration formats no live connector can reach.
More deliverability
Feedback loops, Google Postmaster and Microsoft SNDS ingestion, DMARC policy progression, per-destination throttling.
Later, or maybe not
Ideas with real dependencies or real doubt. They are listed so that asking about them is not a surprise — not because they are planned.
Calendar and contacts UI
Neither the protocols nor a client exists today. Serving calendars and contacts means running another service beside the mail stack, which is why this sits here rather than in a dated group.
JMAP and mobile apps
New surfaces, each a project rather than a feature.
DANE and BIMI
DANE needs DNSSEC on your zone; BIMI needs DMARC at quarantine or reject and a purchased certificate.
What shipped, when
Every release, with what changed in it.