Signed for at the door
Every inbound webhook is signature-verified against your own secret — or the operator secret on the shared path — before a single byte is stored. Unsigned traffic is rejected and recorded, never quietly accepted.
Hosted mailboxes, your domain
A real inbox at name@yourbusiness — without running a mail server.
Mailhaven receives, verifies and archives every message sent to your domain, then hands it to you threaded and readable. Connect your own Resend account in about three minutes, or move to a paid plan and let us provision the DNS for you.
Two paths · bring-your-own Resend or done-for-you DNS · signed inbound · durable fetch with retry
Connection register
studio.example
3
of 4 published
- MX@
inbound-smtp.resend.com
- SPF@
v=spf1 include:amazonses.com ~all
- DKIMresend._domainkey
CNAME → issued per domain
- DMARC_dmarc
v=DMARC1; p=none; adkim=r
POST /webhook/inbound/<account-slug> · svix-signature verified · dedupe on message-id
The record set Mailhaven publishes for a connected domain, and the endpoint that receives its mail.
The register, live
Counted from this deployment’s database on every request
- 3
- Domains verified
- 27
- Messages archived
- 9
- Signed deliveries · 24h
- 9
- Attachments in store
What you are actually getting
Mail handled like cargo with provenance.
Every message that reaches your domain is signed for at the door, logged, fetched and filed. When something is still in progress, the ledger says so instead of spinning.
Nothing lost in transit
Metadata is persisted the moment mail arrives. The body and attachments are collected by a durable background job with exponential backoff, so a provider hiccup delays a message instead of losing it.
Threads that actually hold
Message-ID, In-Reply-To and References are read on the way in and written on the way out, so your replies group correctly in the recipient’s client as well as in your own mailbox.
Read without being tracked
Mail renders inside a sandboxed frame with remote images blocked until you ask for them. Attachments are reachable only through signed links that expire in minutes.
The machinery stays visible
DNS propagation, webhook deliveries, fetch attempts and raw Message-IDs are printed in monospace like a shipping manifest. Pending states say pending, with the time of the last check.
Sealed credentials, strict tenancy
Provider keys are encrypted at rest with a per-record salt, and every query is scoped to a single account. There are no shared views and no cross-tenant joins anywhere in the product.
From registrar to inbox
Four steps, and the ledger records every one.
Both onboarding paths end in the same place: a verified domain, a signed inbound endpoint and a mailbox that keeps a complete record of what arrived and what left.
Read the full routing walk-through- 01
Choose your path
Bring your own Resend account and keep full control of the sending reputation, or move to a paid plan and have Mailhaven provision the sending domain under the operator account.
- 02
Verify for real
We call Resend with your key, confirm the domain’s verification status and run a live test send. Each result you see is the provider’s own response — there are no synthetic green ticks in this product.
- 03
Point the mail at us
Inbound arrives on a signed webhook unique to your account. Deliveries are deduplicated by provider id and Message-ID, threaded, spam-scored and filed before the body is fetched in the background.
- 04
Work the ledger
Read, reply, forward and search from a two-pane mailbox that reads like a register — with every delivery, fetch attempt and send recorded against your account.
“Every state this product shows you is a state it actually observed. If a domain is pending, it is pending. If a fetch failed, the message is still here and the retry is queued. That is the whole promise.”
Plans
Priced per mailbox, not per surprise.
Start on your own Resend account at no cost. Move up when you would rather we handled the DNS, the sending domain and the reputation.
Starter
Bring your own Resend account and run one professional address.
Free
- Addresses
- 1
- Storage
- 1.0 GB
- Sends/day
- 100
- 1 mailbox address
- 1 GB attachment storage
- 100 sends per day
- Bring-your-own Resend key
- Per-tenant signed inbound webhook
Most connected
Pro
We provision the DNS and run the sending domain for you.
$24per month
- Addresses
- 5
- Storage
- 10 GB
- Sends/day
- 1,000
- 5 mailbox addresses
- 10 GB attachment storage
- 1,000 sends per day
- Done-for-you MX, SPF, DKIM and DMARC
- Shared platform sending domain
- Priority postmaster support
Harbour
For studios and agencies running mail for several brands.
$79per month
- Addresses
- 25
- Storage
- 50 GB
- Sends/day
- 5,000
- 25 mailbox addresses
- 50 GB attachment storage
- 5,000 sends per day
- Both connection paths on one account
- Retained raw delivery archive
- Named postmaster contact
Address counts, storage and send limits are enforced on the server on every request — not as a UI hint. Shared platform-domain sending runs on tighter hourly caps because that reputation is shared.
Questions the postmaster gets asked
Straight answers about how the mail moves.
- Do I need my own Resend account?
- On the Starter plan, yes — you supply a Resend API key, a webhook signing secret and a verified domain, and you keep full control of your sending reputation. On paid plans you can instead let Mailhaven provision the sending domain for you under the operator account.
- What happens if the same webhook arrives twice?
- Nothing visible. Deliveries are deduplicated on the provider message id and the Message-ID header, both scoped to your account, so a retried delivery updates the record it already created instead of producing a duplicate in your inbox. The second delivery is still logged so you can see it happened.
- Can Mailhaven staff read my mail?
- The operator console shows connection health, delivery outcomes and job state — never message bodies or attachments. Message content is only ever queried with your account id bound to the request, and provider credentials are encrypted at rest.
- How long does DNS take on the done-for-you path?
- Usually minutes, occasionally up to 48 hours. Each record is checked individually against public resolvers and reported as pending with the time of the last look-up until it appears. Slow propagation never shows up as a failure.
- What happens to a message that is scored as spam?
- It is filed in the Spam folder with the reasons it scored, and it stays there until you move it. Mailhaven never deletes mail automatically, and one click returns a message to the inbox.
- Can I move from my own account to the platform domain later?
- Yes. The connection type is per account and can be switched once you are on a paid plan and your identity check is approved. Existing mail, threads and attachments stay exactly where they are.
Open the register on your own domain.
Connect a Resend key and a verified domain, and mail starts arriving in minutes — signed for, threaded and archived.