I did not want email to be a random paid mailbox sitting outside the company system, and I do not want owners stuck in a basic compose box when SkyeDocxMax can help them craft the actual message. 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 / Max-backed compose lane
SkyeMail
Business email usually stops at an inbox, while the actual work lives in replies, routing, proof, aliases, drafts, customer memory, and follow-up context that should be authored through SkyeDocxMax.
Founder note
Why Gray built this lane.
What it does
The practical operating layer.
Hosted mailbox lane
SkyeMail gives the business a hosted mailbox path with shared gate context, capacity-safe activation, and owner-visible proof boundaries.
SkyeDocxMax compose
Serious owner emails should open the Max-backed drafting lane for structure, tone, checklist context, follow-up tasks, and reviewed send work.
Inbox import and reply routing
Inbound and outbound mail can connect to customer workspaces, ConnectLog memory, Relay13 rooms, AE Flow follow-up, and CRM notes.
Alias/contact/thread metadata
Aliases, contacts, threads, and owner notes need metadata that can follow the customer across the 0S instead of staying trapped in email.
Citadel/FS27 backup receipts
SkyeMail work should leave a proof trail through FS27, Citadel, and platform events when access, send, cache, or backup behavior matters.
Gray Brain and Access Kaixu path
Included local assistance can draft first. Optional Access Kaixu upgrades should be metered and approval-backed when the user wants deeper model review.
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 SkyeDocxMax drafting, 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 connected to Max-backed drafting and 0S routing. |
| 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 SkyeMail-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 SkyeDocxMax drafting 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.