Sovereign Email Platform

The Sovereign Email Platform is a self-hosted email service running on an active/active high-availability cluster — incoming and outgoing mail, mailbox storage, modern protocols, machine-learning-based spam filtering with integrated anti-phishing and anti-virus, all under your own control. The vendor in the middle of every business email your organization sends and receives goes away. In active production.

  flowchart LR
    A["Internet (senders)"] --> B((MX records<br/>both nodes equal))
    F[Mail clients] --> G((IMAP endpoint<br/>both nodes equal))
    B --> C[Node A: SMTP + IMAP + filter]
    B --> D[Node B: SMTP + IMAP + filter]
    G --> C
    G --> D
    C <--> E[(Replicated mailbox storage)]
    D <--> E
    C -.->|ML scan| H[Spam · phishing · virus]
    D -.->|ML scan| H

What this is about

For most organizations, email is hosted by Microsoft 365 or Google Workspace. That solved the operational problem of running mail servers — but the price is that every business email your organization sends and receives lives on a third-party vendor’s infrastructure. The vendor can read metadata, the vendor controls the keys, the vendor decides the spam rules, the vendor can terminate your account, and the vendor charges per mailbox per month forever.

Running email yourself used to be famously hard. Spam was relentless; uptime was a worry; certificate management was manual; deliverability against the big providers was a fight. None of that is true any more — if the platform is built and operated with current-decade discipline.

The Sovereign Email Platform is the operational discipline to do that well: an active/active cluster so no single machine outage drops mail, modern ML-based spam filtering that handles current spam without false positives, integrated anti-phishing and anti-virus so the protection equals or exceeds what the big providers offer, and all the modern deliverability signals (DKIM, SPF, DMARC, ARC, MTA-STS, DANE) configured properly out of the box.

Operational features

• 🏛️ Active/active HA cluster. Two nodes accept SMTP and serve IMAP simultaneously. Both ingest the same mailboxes via replicated storage. A node failure is invisible to users; the surviving node carries full load by design.
• 📥 Standards-compliant mail transport. Modern SMTP daemon with full TLS, opportunistic and strict, ARC forwarding, MTA-STS publication, DANE TLSA validation.
• 📧 IMAP / IMAPS / POP3 / JMAP. Every modern mail client works — desktop, mobile, webmail.
• 🤖 ML-based spam filtering. Machine-learning classifier trained continuously on each instance’s actual mail flow. Adapts to the organization’s correspondence patterns. Materially better than rule-only filtering against current spam campaigns.
• 🎣 Anti-phishing. URL reputation, lookalike-domain detection, header-anomaly checks, attachment-type inspection. Integrated into the same filtering pipeline.
• 🦠 Anti-virus. Attachments scanned by integrated antivirus engine at SMTP receive time; quarantine policy configurable.
• 📨 DKIM / SPF / DMARC / ARC. All outbound mail signed. All inbound mail validated. DMARC reports collected and reviewed. Forwarded mail handled correctly via ARC.
• 🔐 Encryption. TLS in transit by default (opportunistic and strict per peer). At-rest encryption on the mailbox storage layer. Optional per-mailbox encryption for the truly sensitive accounts.
• 📱 Mobile push. Native push notifications to mobile clients without going through Apple or Google as a content intermediary (using IMAP IDLE and open push proxies).
• 🌐 Webmail (integrated). Browser-based mail access is provided by the Sovereign Collaboration Platform — no separate webmail app to deploy or maintain.
• 🔍 Server-side search. Indexed across the user’s mailbox, instant.
• 🔗 Identity integration. LDAP / SAML / OIDC against your existing identity provider. Single source of truth for accounts and group memberships.
• 🚪 Aliases and distribution lists. Per-user aliases, shared mailboxes, distribution lists, mailing-list software optional.

Active/active cluster shape

Email is one of the few services where active/active actually pays off rather than complicating the design:

• No DNS failover delay. MX records carry both nodes at equal priority. Senders connect to either.
• No “primary / standby” surprise. Both nodes are equal; no scheduled-failover anxiety; no monthly drill required.
• Capacity headroom by default. Each node is sized for full load, so the cluster has 100 % capacity headroom in normal operation. Patching can be done by draining a node with zero user impact.
• Storage layer. Mailboxes live on replicated storage so both nodes see the same mail. Cluster filesystem or replicated block storage, your choice.
• No split-brain on inbound. SMTP is idempotent at the transport level: a duplicate delivery becomes a duplicate message at worst, which is recoverable. The cluster handles this cleanly.

Typical use cases

• 🏢 Replace Microsoft 365 or Google Workspace mail — get out of per-mailbox-per-month billing for a function that should be a fixed infrastructure cost.
• 📋 Regulated industries — finance, healthcare, defense supply chain — where mail content cannot reside in public clouds.
• ⚖️ Legal and consultancy practices — client correspondence kept on infrastructure under privileged control, not on a vendor that can be subpoenaed.
• 🌍 Cross-border organizations — where a single US-based mail vendor introduces extraterritorial legal exposure (CLOUD Act, Section 702).
• 🔑 Sensitive senior accounts — board members, GC, CFO mailboxes that should not exist on a third-party platform even if the rest of the organization is fine on a public cloud.
• 🛡️ Defense in depth — having a sovereign mail path available is a continuity asset when the public-cloud mailbox becomes unavailable for any reason (vendor outage, compliance dispute, geopolitical event).

Why this is a CEO-level topic

• 💰 Cost. Microsoft 365 and Google Workspace charge €8– €15 per mailbox per month. At 200 staff with shared mailboxes and aliases, that is €25–€40k per year for a function whose marginal infrastructure cost is near zero.
• 🛡️ Content sovereignty. Every business email your team sends — proposals, contracts, board minutes, customer conversations — lives in a third party’s storage. Keeping that flow on your own infrastructure is a strategic decision.
• 📋 Compliance fit. GDPR Art. 28 processor obligations disappear; data-residency rules in regulated sectors are met by definition; subpoena risk to a vendor whose terms give them broad access disappears.
• 🔓 No vendor lockout. Public-cloud mail vendors have terminated business accounts over content disputes, alleged TOS violations, payment glitches, and geopolitical events. Owning the mail path means owning the recovery path.
• 🤝 No metadata exposure. The vendor sees who your organization corresponds with — counterparties, customers, acquisition targets. Owning the platform closes that observation channel.
• ⏱️ Continuity. Public-cloud mail outages are rare but they happen — and when they do, every customer of that vendor is offline simultaneously. A sovereign mail path is not affected.
• 🔗 Integration with the comms stack. Shares identity with the messaging platform, the collaboration platform, and the voice/video platform. Single account; consistent contact directory; one identity provider to manage.
• 🛡️ Modern protection at parity with public clouds. ML-based spam filtering, anti-phishing, and anti-virus integrated into the platform — no compromise on protection quality versus the big providers.

Technology foundation

Built on the mature open-source mail stack with the operational discipline of an active/active cluster around it. Every component is standard, audit-friendly, and free of vendor lock-in.

Reach out and we will scope a deployment for your mailbox count, expected mail volume, and integration requirements with the rest of your communications and identity stack.