Skip to content
nofeb

Product / Security and isolation

Tenant isolation built into storage

Mail is some of the most sensitive data a business has, and agents read all of it. Isolation between customers is built into how nofeb stores and routes mail, not added as an access check on top.

Isolation built into storage

Every stored message, parsed view and metadata value is encrypted with keys derived for its tenant alone. Deleting a tenant's key material makes everything it stored unreadable, which is how deletion is made final rather than eventual. Exports and uploaded hook modules are sealed the same way.

Mail is routed by the envelope recipient given during delivery, not the To: header a sender can write freely, and redelivery of the same message is idempotent.

Organization, pods and inboxes An organization contains pods, one per end customer, created idempotently from your own customer id. Each pod contains inboxes and may own custom domains. API keys, webhook subscriptions and hooks are bound to the organization, one pod or one inbox, and a key cannot create a key wider than itself. Organization: your product org-wide key and webhook: everything below scope: "org" pod: acme external_ref: cus_1042 scope: "pod" pod key, pod webhook, the customer's own domain support@acme.example inbox key: this inbox only · own autonomy tier scope: "inbox" billing@acme.example inbox key: this inbox only · own autonomy tier scope: "inbox" pod: globex external_ref: cus_2210 scope: "pod" pod key, pod webhook, the customer's own domain quotes@globex.example inbox key: this inbox only · own autonomy tier scope: "inbox" agent-7@agents… inbox key: this inbox only · own autonomy tier scope: "inbox"
One organization holds a pod per end customer and any number of inboxes in each. Keys, webhooks and hooks attach at the organization, a pod or one inbox, and never reach past where they attach.

Keys that match the boundary

An API key is bound to the organization, one pod or one inbox, and holds only the scopes it is given. A key cannot mint a wider key, and a webhook must name its scope, so an integration built for one customer cannot read or be told about another's mail. OAuth tokens issued to MCP clients and the webmail resolve to the same kind of bounded principal, never wider than what the approving person allowed.

An agent does not need a stored key at all. It can present the identity its platform already issues (Microsoft Entra ID or Entra Agent ID, a Google service account, an Amazon EKS service-account token, a GitHub Actions OIDC token or any OIDC issuer) and exchange it for a nofeb token that lasts minutes, carries no refresh token and holds only the scopes both its binding and the agent allow, confined to a pod or one inbox if you say so. Bindings match an exact subject plus claim conditions, such as one repository and branch, and deleting one ends its sessions at once.

Who did what

An append-only audit log records every change made through the API, MCP or the console, and every hold, denial and approval the server makes on its own, naming the agent key, the person (including the console user behind a console action) or the system. Query it, or export it as JSON Lines for your own retention.

Agents can be registered with a human sponsor and the keys they act through, and their mail is signed so a recipient can verify which agent sent it.

Every identity exchange is audited with the issuer, subject, agent and scopes, or the reason it was refused, and mail sent through a federated session carries the external identity in its signed claims.

Single sign-on and provisioning

People sign in to the console and the webmail through your identity provider, with OIDC (Google Workspace, Microsoft Entra ID, Okta or any issuer) or SAML 2.0 with signed assertions. A verified domain routes sign-in to your provider; just-in-time accounts are optional, and requiring SSO ends every other session for your domains at once. SCIM 2.0 creates, updates and removes people and maps groups to roles, and removing someone ends their sessions and disconnects the apps they approved. Included on the plans marked SSO on the pricing page.

Retention and a way out

Retention policies expire mail on your schedule, and legal holds stop any deletion in their scope. Any inbox can be exported as mbox or EML with its metadata, and any message downloaded byte-exact.

What we do not offer

  • Self-hosting of the engine. nofeb is a hosted service; your mail stays portable through export and raw MIME download. Not offered

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Per-tenant encryption with crypto-shredding Stored mail and metadata are sealed with keys derived per tenant; deleting a tenant's key material makes its data unreadable. 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
Inbound routed by envelope recipient Mail is delivered to the inbox named in the SMTP envelope, not the To: header, whichever way it arrives, and redelivery is idempotent. 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
Append-only audit log Every change made through the API, MCP or the console, and every hold, denial, rejection and approval the server makes on its own, recorded with the actor, key, operation, target, outcome and request id. Query it with filters and cursors, or export it as JSON Lines. 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
Agent identity and signed mail Register each agent with a name, a human sponsor and the keys it acts through. Its mail carries an agent header and a signature over the sender, recipients, subject and body that anyone can check against your organization's published keys or nofeb's verification call. Revoking an agent stops its keys from sending and marks its mail as revoked. Shipped
Agent identity federation (no stored API key) An agent signs in with the identity its cloud or CI platform already gives it: Microsoft Entra ID or Entra Agent ID (v2.0 tokens), Google service accounts, Amazon EKS service-account tokens (IRSA), GitHub Actions OIDC tokens, or any OIDC issuer. Your organization trusts the issuer and binds an exact subject, plus optional claim conditions such as the repository and branch, to a registered agent with a scope ceiling and an optional pod or inbox restriction. The agent exchanges its token (OAuth 2.0 token exchange, RFC 8693) for a short-lived nofeb access token with no refresh token, usable on the API, MCP, JMAP and the realtime stream. No secret is stored: keys come from the issuer's published signing keys, and each external token is accepted once. Deleting the binding or issuer, or revoking the agent, ends its sessions at once; every exchange is audited, a dry run explains why a token would or would not be accepted, and mail the agent sends carries the external identity in its signed agent claims. Shipped
Retention policies and legal holds Delete messages older than a number of days, or move them to Trash or Archive, per organization, pod, inbox or folder, keeping flagged mail by default, with a dry run that shows what a policy would do. A legal hold blocks every deletion in its scope, including expiry and inbox deletion. Shipped
Full export A whole inbox, a folder, a thread or a search as mbox or a zip of EML files, with every message's folders, keywords, metadata and decisions as JSON, built in the background and downloaded through signed links. Shipped
Byte-exact raw messages Download any stored message exactly as it was received. Shipped
Self-hosting The engine is offered as a hosted service only. Not offered