Services & deployment

You want to own it. We make the deployment happen.

Owned sovereignty means you operate the server. But the first install, the migration off your old stack, the hardening and the handover are real work. That is what we do — a billed engagement that ends with you owning a running, sovereign OxiMail.

Why this exists

The gap between “we want to own it” and “it is running.”

Most organisations that should own their mail do not lack the will — they lack the first kilometre. We close it. We install on your metal or your VMs, migrate your mailboxes, wire identity, harden the host, set up backups and monitoring, and train your team to run it. Then we step back. The data, the keys and the operation are yours. We were the integrator, not the operator. When you want sovereign AI, we also spec and deploy a GPU box that runs the assistant on your own hardware and trains your per-tenant models — no third party, no per-token cloud bill.

What an engagement looks like
  1. Scoping. We map your current stack, your account count, your identity source (LDAP / AD / SWITCHaai), your migration window and your compliance frame.
  2. Pilot deployment. OxiMail on your infrastructure, a test domain and a handful of mailboxes migrated, validated against your real clients (Thunderbird, mobile, webmail).
  3. Production migration. Phased, domain by domain, with a rollback path held throughout. Migration tooling handles Stalwart, Dovecot, Zimbra and generic IMAP sources.
  4. Hardening & handover. Host hardening, backup and monitoring, key custody, and a training session for your team. You receive an operations runbook. You own it from here.
  5. Optional support. A support bundle if you want a safety net — but the goal is your autonomy, not your dependence.
How it is billed

A scoped engagement, not a subscription to us.

Deployment is a one-off professional engagement, priced against your deployment shape — account count, migration complexity, identity integration, compliance requirements. After handover, your only recurring cost is your own infrastructure plus, if you choose it, a software licence for the Pro components and an optional support bundle. We do not become a dependency you cannot leave. That would defeat the entire point.

Who this is for

Public bodies & administrations

A sovereignty mandate but limited internal mail-ops capacity. We deploy; your IT operates.

Hospitals & health networks

Clinical-grade hosting on your own infrastructure, with audit and retention on the roadmap.

Universities & research

Federated identity, large account counts, a strong data-sovereignty position. We handle the cutover.

Enterprises leaving M365

A cost or sovereignty motion off the hyperscaler. We make the migration real.

Start a deployment

Tell us about your environment.

Current stack, account count, identity source, target window and compliance frame. We respond with a scoped deployment plan within a few business days.

What’s driving this?
Anything we should know about your setup or constraints.