I did not want email to be a random paid mailbox sitting outside the company system. SkyeMail exists because communication is operational evidence. If a customer signs up, replies, asks for help, gets routed to a workspace, or needs a proof trail, that should live with the 0S instead of being trapped in a separate app I cannot observe.
Email / inbox · 📧 pain first
SkyeMail
Business email usually stops at an inbox, while the actual work lives in replies, routing, proof, aliases, drafts, and account recovery.
Founder note
Why Gray built this lane.
What it does
The practical operating layer.
Hosted mailbox lane
This is not a brochure bullet. In the 0S, SkyeMail has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Inbox import and reply routing
This is not a brochure bullet. In the 0S, SkyeMail has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Alias/contact/thread metadata
This is not a brochure bullet. In the 0S, SkyeMail has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Citadel/FS27 backup receipts
This is not a brochure bullet. In the 0S, SkyeMail has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Competitor stack
How it stacks up without lying.
The comparison is category-level on purpose. Specialist tools are not bad; they are often excellent at the narrow job. The 0S argument is ownership, proof, shared auth, payment activation, and cross-lane context.
| Google Workspace / Microsoft 365 | Great general office suites. SkyeMail is stronger when email must connect to 0S proof, aliases, customer workspaces, and owner-visible receipts. |
|---|---|
| Resend / Postmark | Excellent developer email APIs. SkyeMail turns send/receive into a business inbox product lane. |
| Zoho Mail | Useful hosted mailbox infrastructure. SkyeMail wraps provider mail in the 0S operating context. |
Truth ledger
What we can say out loud.
✅ Runs as part of the 0S operating model, not as a loose side project.
✅ Uses the shared FS27/SkyGate/Free99 gate posture when mounted into the 0S.
✅ Needs proof receipts, owner visibility, and cost boundaries before it is sold as unlimited.
✅ Can be positioned strongly without pretending third-party primitives do not exist behind the scenes.
✅ Advertise free business email only with clear caps and provider-backed proof.
✅ Do not claim a magical mailbox if provider sync or DNS is not ready for a domain.
✅ The value is not just inbox UI; it is inbox plus 0S routing.
Proof and receipts
What backs the page.
🧾 Provider-backed inbox proof
SkyeMail is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 Worker-hosted live proof page
SkyeMail is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 Outbound send lane
SkyeMail is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 Scheduled sync posture
SkyeMail is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.