Pure-EPL mail server. SMTP / IMAP / POP3, DKIM signing, outbound relay observability, granular shared-mailbox ACLs. Inbound mail becomes rows AI workers can act on. Self-hosted; your mail spool lives on your disk.
Gmail, Outlook, Fastmail — every hosted mail service turns your customer conversation into a black box. Support tickets get typed out twice (once in Gmail, once in the CRM). AI can't read your inbox without a plugin marketplace. And you don't own the server.
Inbound messages drop as rows on the Mail partition — same substrate as Tables, Code, Files. AI workers with per-type tokens can read the inbox, classify, respond, and open rows in other apps. The relay signs everything with DKIM. Your mail server, your data.
SMTP / IMAP / POP3 built in EPL. Runs on Hetzner or Vultr with a fresh MX record; ready in one config edit.
Real domain authority — the crypto keys live in your admin console, not with a relay vendor. Bounce your reputation in-house.
Route inbound mail to an AI worker with a Mail-scoped token. It classifies, drafts replies, and can insert rows into Tables — CRM, tickets, leads.
Granular per-user access on shared boxes (support@, sales@). Read-only, reply, delegate — configurable at the row level.
Every message queued, bounced, deferred, or delivered is a row. Search by domain, code, or window. Debug a deliverability regression in minutes.
A mail thread can link to a Tables Customer, a Code Issue, a Files attachment. One graph — the AI can hop across boundaries without a plugin.
Self-host · full mail stack · community support
Cloud · AI classifies + drafts + links rows
Own the server · own the keys
SLA · migration · custom SLAs
The same binary. The same substrate. Move between them with a data export.
We host Mail with an AI reader baked in. Your inbox becomes structured rows without a relay in between.
Docker one-liner. Full mail stack including DKIM signing and AI reader (BYOK).
Mail as a partition type. AI as a first-class reader. Your keys, your spool, your rows.