Opening your workspace…
Opening your workspace…
Your domain email, in one place.
Private beta · Your domain, connected.

A quick self-check before you connect.
Verify your domain, create an address, then complete mail connection with the service owner. Read and reply in your browser. Accepted sends appear in Sent; unconfirmed attempts stay in Outbox.
Setup guide ↗Inbox, Sent, Outbox, plain-text replies and received attachment downloads. IMAP, outgoing attachments and Gmail synchronization are not available.
The original message and request key stay recoverable. Check the saved status in Outbox; checking never sends another copy. Provider acceptance does not prove recipient delivery.
Up to 2 MiB per received message, 20 received attachments, 5,000 stored messages and 512 MiB storage per workspace. Sending is limited to 100 attempts in 24 hours.
This is an invite-only beta. Use the workspace ID and password from your invitation. Public signup is not available. Domain verification and service connection are required before mail can work.
Service scope and billing →Read and send mail from your own domain.
Invited users sign in with the workspace ID and password from their invitation. The service owner can leave the ID blank. No mailbox or paid subscription is created.
Your domain email, in one place.
Login and service-owner setup may still be needed.
Add your domain, verify ownership with a DNS record, then create an address. The service owner completes mail receiving and sending configuration.
Changes apply to future conversations. Existing conversations keep their product.
Choose a message to read it here.
One next step. A clear view of your setup.
DNS checks show records, provider acceptance shows a submission. Neither proves inbox delivery.
The Chrome extension offers an independent compose popup. Native Gmail reply and send are not intercepted.
Extension setup ↗Connect your domains and inspect the records behind your email.
The domain must already use Cloudflare DNS. This form does not change DNS records. If DKIM is not ready, add the domain now and update its selector after provider verification.
Run a live DNS check after adding or changing records.
Observed DNS records only. Confirm domain verification in your sending provider.
Use the right address for each project, without another inbox.
Create an address on one of your configured domains. Routing is a separate, explicit action.
Create routing to the saved, verified Gmail destination.
A real message through your own provider. Start with an inbox you can check.
The last 50 requests. Provider acceptance is not confirmed delivery.
Refresh to read the request ledger.
Connect your domain. Manage your mail here.
Open Inbox, choose Connect an address, then add and verify your domain.
The service owner activates receiving and sending after verification. Use your invitation channel to arrange activation.
Your existing accounts do the work. This workspace connects the pieces.
Use a destination address already verified in Cloudflare Email Routing.
Saving this address does not verify it. Verify your destination in Cloudflare ↗
Enable routing for the domain and verify your Gmail destination. Use the MX records Cloudflare provides, and review SPF before changing existing records.
Cloudflare Email Routing documentation ↗This pilot uses a bring-your-own SMTP2GO account through its HTTPS API. Generic SMTP and other providers are not yet supported. Verify your domain, then configure SMTP2GO_API_KEY as a Worker secret. Never enter provider secrets in this browser.
Send a message to an identity from another inbox. Confirm it arrives in Gmail. Then send a reply and inspect the recipient's From address and authentication headers.
The Chrome extension has a persistent independent composer. On Gmail, explicitly enable the separate domain-reply button, expand one message’s recipient details, and review its proposed context. It does not intercept Gmail Reply or Send; Sent and thread synchronization are not implemented.
Install and configure the extension ↗Google says Gmail will stop sending as third-party addresses on the web and mobile apps in January 2027, with restrictions on adding these addresses rolling out in 2026. This pilot sends independently through SMTP2GO and does not use Gmail's native SMTP Send mail as.
Google's announcement about third-party Send mail as ↗Configuration reported by this Worker. External delivery still needs a real test.
Provider keys and Cloudflare tokens are configured through Worker secrets. This browser cannot read or change them. Configuration instructions ↗
Manage workspace access and provider configuration.
ownerInvitations grant access only and do not indicate payment or subscription. Public signup is unavailable.
Invite-only beta. No checkout is configured.
Recurring subscription. Your sending provider and domain costs are separate. Review the final total in Stripe Checkout.
Service scope and billing →These belong only to your workspace and are encrypted server-side. Secret fields remain empty; saved keys are never returned.
Rotating creates a new token once and immediately invalidates the old token. Revoking returns no replacement.
A new generated password invalidates all sessions. Revoking sessions signs out every workspace browser.
Creates an isolated workspace with its own settings, sending ledger and provider credentials. Login secrets are shown once.
The service owner must configure TENANT_KEK before invitations can be created. An invitation is not a purchase or subscription.
Inspect access and domain setup. Passwords and provider secrets are not readable.
Refresh to load invited workspaces.