Postbox provisions real mailboxes on your domain, and each one can send, receive, store, and read mail through a single API. Storage, inbound routing, and deliverability are handled for you.
A Postbox mailbox is a resource you create and own: it can send, it can receive, and it keeps every message with folders, threads, and read state.
Outbound on managed sending infrastructure, with per-domain DKIM, SPF, and DMARC set up for you. Per-mailbox sender rules and rate limits run before anything leaves the queue.
Inbound MX scores spam, parses MIME, resolves threading, and files the message in the right folder, then fires a webhook the moment it lands.
Every mailbox keeps its messages: attachments, threads, folders, read and starred state, queryable per user, per mailbox, with retention you set.
Mint a short-lived, mailbox-scoped token so an end user's client reads exactly one inbox, and nothing else, without your API key ever touching the browser.
An org holds as many projects as you need: Production, Staging, one per customer. Each carries its own domains, mailboxes, API keys, region, and sender reputation, isolated from every other project in the org.
Postbox sits between the public mail network and your app. DNS, SMTP, spam filtering, storage, and sender reputation live on our side; your code talks REST and webhooks. No warm-up spreadsheets, no IMAP servers to babysit.
The same mailbox, three surfaces: your server, the browser, or raw HTTP. The response on the right is what POST /messages/send returns.
Subscribe once and get a signed, typed payload for every send, receive, bounce, and domain event, delivered at-least-once, with per-endpoint delivery logs you can inspect from the dashboard.
If your users expect to open an inbox, not just receive a receipt, you need full mailbox semantics. That's the job Postbox does.
Issue a real @school.edu mailbox in one API call. Postbox handles DNS and retention; you keep the roster logic.
Spin up a per-reservation mailbox. Inbound replies route to the right front-desk queue. Auto-archive on checkout.
Own the help@ mailbox. Threading, assignment, and SLA logic stay in your product. Postbox is the pipe and the store.
Provision a mailbox per agent: it sends and receives on your domain, and inbound mail arrives as parsed, typed events the agent can act on. No IMAP to poll.
Provision an address before laptop day. Tear it down on offboarding with one DELETE, archive intact.
Your customers point CNAMEs at Postbox-branded names and never see a third party. You set the markup; we run the mail and stay invisible.
Every tier includes a monthly email allowance (send + receive combined). Go past it and you pay a simple metered rate, or move up a tier. No per-seat pricing; projects are free to create.
Search a mailbox by meaning, not keywords. Every result cites the message it came from, so an agent can work from the source.