The problem
Per-inbox pricing punishes exactly the growth you want, and a webhook bug that crosses tenant boundaries sends one customer's mail to another's endpoint.
How it runs on nofeb
- Create a pod per customer from your own customer id; the call is idempotent, so a retry does not duplicate it. Create as many inboxes inside it as the customer needs; paid plans have no inbox limit.
- Issue keys bound to the pod, so your per-customer workers cannot reach any other customer, and subscribe webhooks scoped to the pod. Scope is required, so a subscription cannot silently widen to your whole organization.
- Your app's live views connect to the WebSocket stream with a pod-bound credential; it carries only that pod's events, resumes from a cursor, and closes a slow client without holding back the rest.
- Set policy per pod: recipient and sender lists, send caps and rules, beside your organization's defaults, so each customer's plan or risk level gets its own limits.
- Let each customer use their own domain: create it in their pod, then publish the records through their DNS host's API with a token they hand over for that one call, or show them instructions written for their host.
- Receive their mail on nofeb's MX, or keep the provider they already use: Cloudflare Email Routing, Postmark, Mailgun and SendGrid can all pass mail on. An inbound.resolve hook creates an inbox on the fly when mail arrives for an address a customer has not set up yet.
- Run your per-customer logic inside the pipeline as a WebAssembly hook instead of an HTTPS callout: the same stages and answers, sandboxed with fuel and memory limits, fetching only the URLs you allow, with versions you can roll back.
- When your customers connect their own MCP clients, they sign in with OAuth and approve scopes, and optionally one inbox, instead of copying an API key into a config file.
- Your own team signs in to the console through your identity provider, with SCIM provisioning and deprovisioning, on plans that include SSO.
Where nofeb stops
- Sending through your own Amazon SES account: the API accepts the role and sends through it, and verification against live customer accounts is still in progress. Beta
Status of everything this relies on
| Capability | What it does | Status |
|---|---|---|
| Pods | Sub-tenants inside one organization: one per end customer, created idempotently from your own customer id. | Shipped |
| Unlimited inboxes | Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. | Shipped |
| Scoped API keys | Keys bound to the organization, one pod or one inbox, holding only the scopes they are given. A key cannot mint a key wider than itself. | Shipped |
| Signed webhooks with required scope | Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. | Shipped |
| Durable event feed | A pull feed of every event, oldest first after a cursor, for consumers that cannot receive webhooks. | Shipped |
| Realtime stream | A WebSocket stream of the same events as webhooks and the feed, in order, resumable from a cursor with no gap and no duplicates, and filtered by inbox, pod or event type within the credential's own reach. | Shipped |
| Typed metadata on messages, threads and inboxes | Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. | Shipped |
| Custom domains | Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. | Shipped |
| DNS setup made easy | nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. | Shipped |
| Inbound mail server that checks mail at the door | nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. | Shipped |
| Inbound from the provider you already use | Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. | Shipped |
| HTTPS hooks in the pipeline | Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. | Shipped |
| WebAssembly hooks | The same pipeline stages as HTTPS hooks, run as a WebAssembly module you upload, built against a published, versioned interface. Modules run sandboxed with fuel, memory and time limits, can fetch only the URLs you allow, read and set metadata on what they decide about, and keep their last ten versions for rollback. | Shipped |
| Recipient and sender allowlists and blocklists | Lists of addresses, domains or wildcards per organization, pod or inbox: who an agent may write to, and whose mail it reads. A blocked recipient is refused on every autonomy tier, a blocked sender's mail is rejected or quarantined, and you choose whether a send outside the allowlist is held for approval or refused. A check call predicts what a send or an inbound message would meet before it happens. | Shipped |
| Per-agent rate and recipient caps | Limits per inbox and per API key on sends per hour and per day, distinct recipients per day, recipients per message and new recipients per day, checked and charged in one step so concurrent sends cannot overshoot. A usage call shows the budget left, and you choose whether an exhausted cap holds a send for approval or refuses it. | Shipped |
| Rules and Sieve | Declarative rules over sender, recipients, subject, body, headers, attachments, size, the security verdict, metadata and decisions, that label, move, flag, set metadata, quarantine, forward, auto-reply or reject. Test rules against a stored message with a per-rule trace, and import or export Sieve, with anything that cannot be mapped reported line by line. | Shipped |
| MCP sign-in with OAuth | MCP clients connect by signing in instead of pasting a key: OAuth 2.1 with discovery, dynamic client registration, client ID metadata documents, PKCE, tokens bound to the MCP server, refresh-token rotation and immediate revocation. A person approves the scopes, and optionally one inbox, in the console, and can disconnect the app at any time. API keys keep working beside it. | Shipped |
| SSO and SCIM | Single sign-on to the console and the webmail with OIDC (Google Workspace, Microsoft Entra ID, Okta or any issuer) or SAML 2.0, verified domains that route sign-in to your identity provider, optional just-in-time accounts and an enforce switch, and SCIM 2.0 provisioning with group-to-role mapping. Deprovisioning ends the person's sessions and disconnects their apps. Included on plans whose row says SSO. | Shipped |
| Bring your own Amazon SES account | Send through your own Amazon SES account by granting nofeb an IAM role; the API accepts the role and sends through it, and verification against live customer accounts is still in progress. | Beta |