For operators

One server. One program to install. No stack to assemble.

You run mail servers. Here is the technical sheet: what ships, how it fails loud instead of silent, and the migration path from whatever you run today. Below five users, running it for yourself, it is free — the whole suite, not a trimmed edition.

The warmest audience: you already left

Coming from Stalwart? Start here.

If you run Stalwart, you are our closest neighbour: another JMAP-native, Rust-adjacent, single-binary mail server. Here is what carries over, what you gain, and how the move actually happens. The command-line migration tools already exist — oximail migrate --from-dump and --from-jmap — built for exactly this move.

From anywhere else you might be running mail or files today.

What you actually get

A real mail and collaboration server. Not a demo, not a teaser.

Everything below runs in the single binary. The web client and the desktop sync agent come with it.

How it runs

One binary. SQLite. Up to about 2000 accounts.

OxiMail is SQLite-backed and has been validated to around 2000 accounts per instance — far beyond what a five-user deployment needs, and enough for a cooperative, an association or a small institution when you outgrow the free tier. Put it on a Debian host, point your DNS, and you have a full mail and collaboration server in one process, one config, one login. No JVM, no orchestration, no specialist on call to keep a six-service stack standing.

# Debian 13, 2 GB of RAM, a domain and a public IP
# one binary, one config file, one systemd service
# no Postfix, no Dovecot, no web server alongside it

The operator documentation covers the whole path: requirements, ports, first boot, DNS and DKIM, TLS, migration from your current server. Prebuilt packages arrive with the public source release — until then, tell us and we will get you a build.

The licence, plainly

Fair source: free below the line, paid above it, and AGPL for everyone after four years.

See what free includes and what is paid →

The documentation is public today. The source opens with the public release.

The operator and developer documentation is complete and online: requirements, ports, DNS and DKIM, TLS, migration, the JMAP extensions. Read it and judge the design for yourself. The server source is published at the public opening, under the licence described above.