Riven Mail
LiveReal mailboxes, provisioned at signup. Every Riven account gets mail and comms together, on infrastructure the platform controls end to end.
Riven Mail is a first-class mail service, not a notification sender. When an account is created, mail and [comms](/docs/commerce/riven-comms) are provisioned together at signup — the user has an addressable mailbox before they have written a line of code.
Provisioning at signup#
- The account is created through Riven Auth.
- A mailbox is allocated and its credentials are sealed into Riven Keymaster — they are never shown in a response body.
- Comms channels are attached to the same identity, so mail and messaging share one address book.
- The mailbox appears in the account’s surfaces immediately; no separate onboarding step.
Because provisioning happens inline with signup, a failed mailbox allocation fails the signup rather than silently leaving an account without mail. There is no “mail pending” state to reconcile later.
What it runs#
- Transport — SMTP submission and delivery with SPF, DKIM, and DMARC aligned per sending domain.
- Storage — IMAP-accessible mailboxes with server-side search.
- Routing — inbound rules that hand messages to Commerce as orders or quotes, or to a support queue.
- Reputation — bounce and complaint handling fed back into Riven Telemetry so deliverability is observable, not guessed at.
AI on the inbox#
Triage, summarisation, and draft replies run through the gateway with the same key and quota as any other workload. Drafts land in the drafts folder — nothing is sent without an explicit human send.
| Workflow | Model behaviour | Human step |
|---|---|---|
| Triage | Classifies and labels inbound mail | Optional review of low-confidence labels |
| Summarise thread | Produces a thread digest on demand | None — read-only |
| Draft reply | Writes a draft with cited context | Required — the user sends |
| Extract order | Proposes line items into Commerce | Required — the operator confirms |
Sovereignty#
Mail is self-hosted on the same Docker Swarm cluster as the rest of the platform, fronted by Traefik and deployed with Dokploy. Message bodies are not sent to a third-party mail provider, and model calls that touch mail content prefer the on-prem fleet.