Private development · Sign-ups closed

Roadmap

Three lists: what runs today, what is next, and what has not been started. Nothing moves between them because we announced it. It moves when it works.

Shipping today

Your own domainLive

  • Receiving. Mail arrives on a domain you control, through Cloudflare Email Routing in your own Cloudflare account.
  • The client. Folders, threaded conversations, search with from:, to:, subject:, in:, is:unread, is:starred, has:attachment, before: and after:, rich-text compose, drafts, reply and forward, inbound attachments, per-mailbox settings.
  • Access control. Workspaces; owner, admin, operator and viewer roles; per-mailbox grants; invitation-only membership; revocation that takes effect on a live session.
  • The agent. One per mailbox. Reads, searches, triages and drafts, and stops at a server-rendered approval card before any move, send, delete or mark-as-read.
  • Inbound safety. Prompt-injection scanning that gates automatic drafting, failing closed. What that does and does not cover.
  • MCP. 14 scope-gated tools over OAuth 2.1 with PKCE, with owner- and admin-managed clients. The eight read and draft tools work; the six that change something refuse on every mailbox until MCP has a confirmation round-trip.

How the agent is contained today

What we are working on next

Sending in productionPlanned — not built yetGmailPlanned — not built yetOutlookPlanned — not built yetZohoPlanned — not built yetIMAPPlanned — not built yet

Verified sending

The outbound pipeline exists: the message is persisted before any job is published, delivery runs as a durable background job with bounded retries and a dead-letter queue, and provider message IDs are recorded. What it has not had is a live provider on the other end. Until sending is exercised end to end against a real provider — including bounces, rejections and the ugly cases — we will keep calling it unverified, and it is the thing blocking everything else.

Connecting the accounts you already have

Gmail, Outlook, Zoho and generic IMAP. None of these is built. This is the largest single piece of work on the list and the reason the current product only speaks to a domain you route yourself. When one of them lands it will land as one provider at a time, and this page will say which.

Not started

Named here so that nobody has to guess whether they are quietly in progress. They are not.

  • Mobile applications, on any platform. Planned, not built yet.
  • A browser extension. Planned, not built yet.
  • Integrations with anything outside mail, calendar included. Planned, not built yet.
  • Automation rules and filters that run without a person. Planned, not built yet.
  • Pricing, plans and billing. Not built yet.
  • Any certification or external audit. Not started.

About dates

There are none, and we are not going to invent any. We do not promise quarters, we do not promise a beta window, and we will not commit to an order — the two items under “next” can swap, and something in “not started” can jump ahead if it turns out to be the thing blocking real use.

The one commitment: this page will not describe anything as working before it has been tested end to end, and the waitlist gets one email when sign-ups open.

Join the waitlist

Sign-ups are closed. Leave an address and we will write once, when they open.

We store the address you type, plus a hashed form of your IP address so the form can be rate-limited. One email when sign-ups open, and nothing after that. We do not share the list, and there is no analytics or third-party script on this site.