Client-ready secure email

Email workspace without handing the server your inbox.

SkyeMail gives each 0S client a real email lane, a sovereign-key onboarding card, Citadel Database delivery monitoring, encrypted inbox storage, and a clean workspace they can use before the rest of the operating system gets noisy.

Watch The Proof Run Security Tech Stack Pricing Changelog Enter Suite Open SkyeMail
Encrypted Inbox Citadel Database + Sovereign Keys
Client reply receivedSealed into the sovereign workspace
Proposal sentSkyeNet delivered and logged
Sovereign key card issuedSetup link and recovery policy ready
FS27 session activeWorkspace access gated through SkyeGate

What the client gets

A private email room connected to the 0S.

The client can send, receive, reply, monitor delivery, set up sovereign keys, and carry the workspace identity into the larger MetrAIyux platform.

Security posture Message bodies are sealed through the SkyeMail sovereign lane and stored as encrypted sovereign payloads once the client sovereign key is active.

Trust surface

See the email lane working before a client buys in.

Two-way mail proofA sends to B, B receives it, B replies, and A receives the answer back inside SkyeMail.
Workspace handoffEach client gets an email identity, sovereign-key onboarding card, delivery monitoring, and a protected login path.

How it works

Provision, key, send, receive, prove.

1. 0S creates the workspaceThe SaaS worker provisions the client workspace, asks SkyeMail for an email identity, and stores the mailbox receipt.
2. SkyeMail issues a key cardThe card includes the mailbox, setup URL, recovery policy, and sovereign-key security model without exposing private keys.
3. SkyeMail routes the emailOutbound messages and inbound webhooks move through the SkyeMail production mail lane and land in SkyeMail monitoring.
4. Sovereign keys lock the inboxThe public key receives encrypted mail. The private key stays wrapped by the client passphrase.
5. Delivery events stay visibleSent, delivered, failed, bounced, and received events become proof records without exposing inbox content.
6. The client can replyThe proof surface shows a two-party exchange: A sends to B, B receives, B replies, A receives.