A sovereign mail backend you operate. Keep your UI, or adopt ours.
You host mail for customers who want their data in your jurisdiction, under a local operator they know — not a hyperscaler tenancy. OxiMail is the backend: one Rust binary, lean enough to run at volume, with full legacy-protocol support. Whether you already have a webmail you want to keep, or want a full suite to resell, OxiMail fits.
Delegated sovereignty. You read at runtime — and that is fine.
When you host OxiMail for a customer, you are the operator. OxiMail decrypts at read for the authenticated user, so technically you can read their mail at runtime — exactly as you can with any mail platform you operate today. What OxiMail changes is the rest: the data stays in your jurisdiction, under your local law, with you as a named, trusted operator instead of a US hyperscaler. That is jurisdictional sovereignty with a trusted local operator — not zero-trust. The zero-trust, "operator is no one" tier exists only when the customer runs their own metal.
The owned-vs-delegated distinction, in full →Keep your own UI, or adopt our Workspace.
You have your own webmail.
Your users interact with your UI. You want a modern, efficient, standards-based mail backend under the hood. Run OxiMail backend-only and connect your existing UI via JMAP or IMAP. Your users never see OxiMail — they see your brand.
You want a full suite to resell.
You host without a fully-developed webmail of your own. Run OxiMail plus the Workspace client under your white-label branding. You sell a complete sovereign collaboration offer; you operate the stack; you own the commercial relationship.
One binary. Less infrastructure.
A standard legacy mail stack running IMAP, SMTP, a webmail, a spam engine, a calendar server and backups typically consumes 10 to 18 GB of RAM on a production host. OxiMail in a similar configuration runs in 2 to 4 GB. The difference comes from the single-binary design — one process, one memory space, no inter-service marshalling, no separate webmail PHP pool, no standalone CalDAV daemon.
Lower RAM means fewer hosts per thousand boxes. Fewer hosts means simpler deployment, simpler backup, simpler monitoring. The operational story changes materially at scale — and at scale is exactly where a hoster’s margin lives.
Evaluation to production.
- Test instance. We spin up an OxiMail instance on your infrastructure; you migrate a handful of test mailboxes and observe protocol behaviour against your existing UI.
- Single-domain trial. One customer domain in production, with you and us monitoring together for two to four weeks. A rollback path is held throughout.
- Production migration. Phased rollout, domain by domain or shard by shard. Migration tooling handles Stalwart, Dovecot and generic IMAP sources.
- Ongoing support. A support bundle tailored to your SLA — see pricing.
Drive: a file-server replacement for your PME customers. A pilot, not a product yet.
If your customer base is small and mid-sized businesses with on-premise Samba, Windows Server or NAS stacks, Drive is your future differentiator — a file-server replacement positioned as the VPN-killer, the ransomware-vector-eliminator, the identity-unifier. It is on the roadmap as a pilot in Q3 2026 on Linux and Windows; it does not ship today, and we do not let you sell it as if it does. The VPN-replacement and file-server arguments all belong to Drive — keep them roadmap until it lands. Lead your customers on the sovereign mail + collaboration suite that is live now.
Distribution groups standard. Managed lists on Pro.
Community ships distribution groups — aliases that fan out to N members, LDAP-syncable, with per-group greylisting behaviour. Pro adds managed mailing lists — moderation queues, archives with search, digest mode, double opt-in, DMARC-friendly ARC signing, bounce auto-unsubscribe, external subscribers under policy. Two names, two scopes, no confusion at billing time.
Volume pricing — talk to us.
The public per-box grid is being reworked, so we are not printing numbers here that we would have to walk back. Hoster pricing is a scoped conversation against your volume, your tier (backend-only or backend + Workspace) and your support SLA. The pricing page carries the current framing.
See pricing →Tell us about your platform.
Volume, current stack, target migration window, any special requirements. We respond with a tailored evaluation plan within two business days.