What gets in the way?
- Per-inbox pricing punishes exactly the growth you want.
- A webhook or key that crosses a tenant boundary sends one customer's mail to another.
- Every customer domain is a support ticket about DNS records typed into the wrong box.
- Customer-specific mail logic ends up as a fleet of HTTPS services that each have to stay up.
How does nofeb handle it?
Pods as tenants
A pod per customer, created idempotently from your own external_ref. Inboxes, domains, keys, webhooks and hooks attach to it.
Boundaries the server enforces
Keys are bound to the organization, a pod or one inbox and cannot mint wider keys; webhooks must name a scope; a pod-bound credential on the WebSocket stream sees only that pod's events.
Policy per customer
Recipient and sender lists, send caps and rules can be set at the organization, the pod or the inbox, so a trial customer and an enterprise customer get different limits.
Your code inside the pipeline
Upload a WebAssembly module for the inbound.resolve, inbound.pre_deliver or outbound.pre_send stage. It answers like an HTTPS hook, runs sandboxed with fuel, memory and time limits, fetches only URLs you allow, and keeps its last ten versions for rollback.
Customer domains without tickets
nofeb detects the customer's DNS host, publishes the records with a token used once where it can, gives host-specific instructions elsewhere, and names the mistake when a record is wrong. Inbound arrives on nofeb's MX or through Cloudflare Email Routing, Postmark, Mailgun or SendGrid.
Sign-in for your customers and your team
Customers' MCP clients connect with OAuth sign-in and approved scopes rather than pasted keys; your team signs in to the console through SSO with SCIM provisioning, on plans that include SSO.
What does the code look like?
const pod = await nf.pods.create({ name: "Acme", external_ref: "cus_1042" }); // idempotent on external_ref
const inbox = await nf.inboxes.create({ pod_id: pod.id, local_part: "support" });
const key = await nf.keys.create({ pod_id: pod.id, scopes: ["inbox:read", "message:read", "message:send"] });
await nf.webhooks.create({ url, scope: "pod", pod_id: pod.id, events: ["message.received"] }); Where does nofeb stop?
- 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
Frequently asked questions
How do I give each customer its own agent inbox?
Create a pod per customer (idempotent on your external_ref), then inboxes inside it. Give that customer's workers a pod-scoped key.
How do I stop one tenant's bounces from hurting the others?
nofeb suppresses hard bounces and complaints automatically, and each organization can send with its own isolated reputation.
How do I let customers use their own domain?
Create the domain in their pod. nofeb publishes the records through Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi with a one-time token, or returns instructions written for their DNS host, and checks each record live.
Do WebAssembly hooks replace HTTPS hooks?
They sit beside them. Both run at the same stages and answer with the same JSON, and their effects merge; a WebAssembly hook saves a network round trip and a service to operate. The interface is published and versioned, and a failing module follows the hook's fail-open or fail-closed setting.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Pods | Sub-tenants inside one organization: one per end customer, created idempotently from your own customer id. | 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| Managed sending with per-tenant reputation isolation | nofeb sends on your behalf from your verified domain, and each organization can send with its own isolated reputation, so one sender's behaviour cannot damage another's. | Shipped |
| Unlimited inboxes | Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. | 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 |