public beta

Mailbox infrastructure,
not just delivery.

Postbox is a headless, API-first email platform. Send, receive, store, read — every mailbox capability your app needs, behind one SDK. No SMTP relay stitching. No IMAP servers to babysit.

send + receive + storeEU data residencydeliverability via Amazon SES
~/projects/acmesend-first-message.ts
TS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

The four verbs
of email, on tap.

Most "email APIs" only solve one direction. Postbox is the full backend — send, receive, store, read — composable as a single primitive.

Send

Outbound through Amazon SES with per-domain DKIM, SPF, and DMARC handled. Per-mailbox sender rules and rate limits enforced before anything leaves the queue.

POST /messages/send

Receive

Inbound MX runs spam scoring, parses MIME, resolves threading, and fires a webhook the moment a message is stored in the right folder.

event: message.received

Store

Mailbox storage with attachments, threads, folders, and read state. Fully queryable per user, per mailbox, with retention you control.

GET /mailboxes/:id/messages

Read

Paginated reads and mailbox-scoped tokens, so an end user's client can read exactly one inbox — and nothing else — without touching your backend.

POST /tokens

One pipe in,
one pipe out.

Postbox sits between the public mail network and your application. DNS, SMTP, spam filtering, and storage live on our side; your code talks REST and webhooks.

Internet

Public mail network

  • SMTP / MX
  • SPF / DKIM / DMARC
  • Reputation feedback loops
Postbox

Mailbox runtime

  • Amazon SES outbound
  • Spam-scored inbound
  • MIME parser + thread index
  • Per-mailbox sender rules
  • Encrypted message store
Your app

SDK + webhooks

  • REST: /messages, /mailboxes
  • Webhooks: received, sent, bounced
  • Node + browser SDKs
DNS verification✓ automated
Spam scoringrspamd
Storageencrypted at rest
Multi-tenantday one

Every mailbox event,
as a webhook.

Subscribe once, 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.

message.received
message.sent
message.bounced
domain.dns.verified
POSThttps://api.acme.com/postbox/hook live
just nowmessage.receivedalex@northwind.ioinbox
6s agomessage.sentsupport@acme.comqueued
10s agomessage.receivedbilling@stripe.cominbox
14s agomessage.sentnoreply@acme.comdelivered
18s agomessage.bouncedold@deadhost.invalid5.1.1
22s agomessage.receivedkara@studentmail.eduinbox

Hit the API,
see the wire.

Same call, three runtimes. The response on the right is the shape you get back from POST /messages/send.

requestsend.ts
import Postbox from '@postbox/sdk'; const pb = new Postbox({ apiKey: process.env.PB_KEY }); const { id } = await pb.mailboxes.create('acme.com', { address: 'support', }); await pb.messages.send(id, { to: 'jess@northwind.io', subject: 'Welcome to Acme', html: '<p>Glad you’re here.</p>', });
response200 OK
messageIdmsg_8fq2k1px…
threadIdthr_acme_supp…
fromsupport@acme.com
tojess@northwind.io
statusqueued
dkimsigned by SES (rsa-2048)
webhookmessage.sent → /hook

Who's plumbing
real mailboxes.

If your users expect to read and reply — not just receive a receipt — you need full mailbox semantics. That's what Postbox is for.

SIS / Education

Student email at the institution level

Issue students a real @school.edu mailbox in one API call. Postbox handles DNS and retention policy; you keep the roster logic.

provisioningone API call
Hotel PMS

Per-stay guest comms, two-way

Spin up a per-reservation mailbox. Inbound replies route to the right front-desk queue. Auto-archive on checkout.

lifecyclecreate → archive
CRM / Helpdesk

Support inbox without the SaaS tax

Own the help@ mailbox. Threading, assignment, and SLA logic stay in your product. Postbox is the pipe and the store.

threadsyours to query
Community

Real reply-by-email, no parsing hacks

Every notification gets a unique reply address. Inbound mail comes back parsed and keyed to the thread it belongs to.

threadingserver-side
HR / People ops

Onboarding mailboxes from day -1

Provision an email address before laptop day. Tear down on offboarding with one DELETE, archive intact.

teardownone DELETE
Vertical SaaS

Email as a product feature

Multi-tenant from day one. Your end customers get their own domain, their own DKIM, their own reputation — through your brand.

isolationper tenant

Start free,
pay as you grow.

Every tier includes a monthly email allowance (send + receive combined). Go past it and you pay a simple metered rate — or upgrade.

Freetry it out
$0/mo
  • 3 mailboxes · 1 domain
  • 3,000 emails / mo
  • 5 GB storage
  • Hard cap — never bills
start free
Starterside projects
$20/mo
  • 10 mailboxes · 3 domains
  • 50,000 emails / mo
  • 25 GB storage
  • $1.00 per extra 1k emails
start
Growthreal production
$99/mo
  • 100 mailboxes · 25 domains
  • 500,000 emails / mo
  • 250 GB storage
  • Dedicated sender reputation
  • $0.80 per extra 1k emails
start
Scalefor platforms
$499/mo
  • 1,000 mailboxes · unlimited domains
  • 5M emails / mo
  • 2 TB storage
  • Dedicated reputation + IP
  • $0.50 per extra 1k emails
start
Enterprisenegotiated per-deal
Talkto us
  • Custom volume + limits
  • Dedicated IP pool
  • Custom retention
  • Annual contracts
contact
How usage countsno surprises
  • Every send + every received message counts as one email
  • Overage bills at your tier's metered rate — nothing else
  • Free tier hard-stops at its cap; it never bills
  • Storage measured per GB-month
see it in the dashboard