Use casesDevelopers
Email hosting for developers: mailboxes, a send API and webhooks on one account
Short answer
Shipmail hosts the mailboxes for your domains and sends your transactional email from the same account. Sign-up and password-reset emails go out through the API from a sending subdomain, and replies land in a real mailbox. Solo costs $4 a month for 2 mailboxes and 3,000 transactional emails, then $0.30 per 1,000, across up to 50 domains. If you need dedicated IPs, use a dedicated sending service.
Send transactional email from your domain and keep the replies
Your app sends from a subdomain such as notify.yourdomain.com. Receiving providers can then tell transactional email apart from the mail you write by hand. The sender needs no extra mailbox and has no fee of its own.[4]
Each sender has a Reply-To mailbox. When a customer answers a receipt, the reply arrives in that mailbox as a normal conversation. Sent copies stay in separate storage, so they do not fill your Sent folder.[4]
Bounces and spam complaints go on a suppression list, and the API refuses later sends to those addresses. A retry with the same Idempotency-Key returns the first message instead of sending twice.Sources[5]Shipmail suppressions documentation[6]Shipmail idempotency documentation
API keys, SDKs and the CLI
Shipmail gives developers scoped API keys, sm_test_ test keys, typed SDKs on npm and PyPI, and the shipmail-cli command line tool. A key can be limited to certain domains and mailboxes.Sources[7]Shipmail API authentication documentation[8]Shipmail sandbox documentation[9]Shipmail TypeScript SDK documentation[10]Shipmail CLI documentation
- Scoped keys. Choose scopes per key and limit a key to certain domains and mailboxes, so one project's key cannot read another project's mail.
- Test keys. Keys that start with sm_test_ run against isolated shadow mailboxes. Pass sandbox_outcome to simulate a delivery, a bounce or a complaint in CI.
- SDKs. The shipmail packages on npm and PyPI are typed clients for the REST API. The Python one has sync and async clients.
- CLI. shipmail-cli covers domains, mailboxes, inbox messages, sending, webhooks and suppressions, which is enough for deploy scripts.
Receive email in your app with webhooks
Subscribe to message.received and your endpoint gets a POST for each new message in the mailboxes you choose. Use it to open a ticket from support@, parse an invoice, or start an onboarding flow.[11]
Delivery events (message.delivered, message.bounced, message.complained) and domain events such as domain.verified use the same webhook. Shipmail signs each request with HMAC-SHA256 and adds a timestamp, so your handler can reject forged and replayed calls.Sources[11]Shipmail webhooks documentation[12]Shipmail webhook signature verification
Let Claude, Cursor or your own agent use a mailbox
The Shipmail MCP server runs hosted at shipmail.to/api/mcp or locally from the shipmail-mcp npm package. Connect it to Claude, ChatGPT or Cursor and the agent can read, draft and send from the mailboxes its key allows.Sources[13]Shipmail MCP server docs[14]Shipmail MCP npm package
The built-in assistant comes with every paid plan, in beta. Ask it which support@ threads still need an answer and it drafts replies into the Drafts folder for you to check.[15]
What it costs across several side projects
You pay for mailboxes, not domains. Every plan allows up to 50 domains in one organization, and the mailbox and transactional allowances are each shared across all of them.[3]
- One project, just you: Solo at $4 a month for 2 mailboxes and 3,000 transactional emails.
- Three projects with one mailbox each: Pro at $9 a month for 4 mailboxes. Aliases cover the other addresses on each domain.
- You plus a co-founder, six mailboxes: Pro plus 2 extra mailboxes at $15 a month.
- A product with a support team: Team at $29 a month for 12 mailboxes, unlimited members and 30,000 transactional emails.
When a dedicated sending service is the better choice
If your app needs dedicated IPs, use a sending service and keep Shipmail for the mailboxes. On a paid plan, transactional email starts at 1,000 recipients a day and rises on its own to 25,000 with clean sending. A person approves more, so plan a launch-day blast around it.Sources[3]Shipmail pricing[16]Shipmail sending policy
If you need IMAP-level access to build your own mail client, connect over IMAP and SMTP directly. The REST API covers mailboxes, messages and sending, not every IMAP extension.[17]
Core pain points
- Two vendors per project. A typical side project runs mailboxes on one host and transactional email on a sending service. That is two dashboards, two sets of DNS records and two bills for each domain.
- Replies to transactional email go nowhere. A noreply@ sender drops the customer who answers a receipt with a question. Routing those replies into a mailbox usually means an inbound parse webhook you write yourself.
- A new domain means a new account. Most hosts tie billing to a domain or a user. Five small projects end up as five subscriptions you forget to cancel.
Getting started
- 1
Add the domain. Shipmail shows the MX, SPF, DKIM and DMARC records and checks them for you. With a supported DNS provider it can publish them itself.
- 2
Create the mailboxes the project needs, such as you@ and support@. Add aliases like hello@ to an existing mailbox instead of buying another one.
- 3
Add a sender on a subdomain such as notify.yourdomain.com and pick the mailbox that receives replies.
- 4
Create an API key under Developer > API keys. Limit it to the project's domain, then install the SDK with npm install shipmail or pip install shipmail.
- 5
Point a webhook at your app for message.received or message.bounced, and verify each request's HMAC-SHA256 signature.
Sources17 sourcesVerified 2026-11-18
- [1]Resend pricing
Resend pricing page: Free $0 for 3,000 emails a month, at most 100 a day, 3 domains; Pro $20 a month for 50,000 emails or $35 for 100,000, 10 domains; Scale from $90 a month for 100,000 emails, 1,000 domains; extra emails at $0.90 per 1,000 on Pro and Scale with pay-as-you-go; Enterprise on quote. Every plan includes 3 inboxes; more cost $1 per inbox a month on paid plans with pay-as-you-go. Add-ons: 100 more domains for $20 a month on Pro and Scale, a dedicated IP for $30 a month on Scale, SSO for $150 a month on Scale. 30-day data retention below Enterprise. Inbound email, SMTP relay, SDKs and React Email on every plan. The page carries no customer testimonials.
resend.com · 2026-11-01
- [2]Amazon SES pricing
Amazon SES charges $0.10 per 1,000 outbound emails a la carte, or $0.16 per 1,000 on its Essentials tier, with no monthly fee. Receiving costs $0.10 per 1,000 emails plus $0.09 per 1,000 incoming 256 KB chunks. A standard dedicated IP is $24.95 a month. New AWS customers get up to $200 in general Free Tier credits; there is no SES-specific free allowance.
aws.amazon.com · 2026-11-16
- [3]Shipmail pricing
Shipmail plan prices, mailbox limits, team access, and send limits.
shipmail.to · 2026-11-16
- [4]Shipmail transactional email documentation
Shipmail transactional email: an app sends from its own sending subdomain of a domain already verified in Shipmail, and replies go to a Shipmail mailbox. Sends count toward the plan's monthly quota, a sender costs nothing extra, Activity shows delivery status, and a retry with the same Idempotency-Key returns the first message. Every email from a sender carries its mailbox's address as Reply-To, so replies arrive in that mailbox's Transactional folder; the sending address itself cannot receive email. On a paid plan, an organization's transactional email starts at a safety limit of 1,000 recipients a day, raised daily to twice the highest clean day of the last 7 days, up to 25,000 automatically; the plan keeps 80% of its daily limit as a floor; a migration review with the last 30 days gets an answer within one business day.
shipmail.to · 2026-11-09
- [5]Shipmail suppressions documentation
Shipmail suppresses an address after a permanent bounce or a spam complaint, accepts manual additions, scopes the list to the organization and rejects a send to a suppressed recipient.
shipmail.to · 2026-10-15
- [6]Shipmail idempotency documentation
Shipmail POST, PATCH and PUT requests accept an Idempotency-Key header; the response is cached for 24 hours.
shipmail.to · 2026-10-10
- [7]Shipmail API authentication documentation
Shipmail API keys have scopes and can be limited to specific domains and mailboxes; live and test keys are separate.
shipmail.to · 2026-10-15
- [8]Shipmail sandbox documentation
Shipmail test keys simulate sends without delivering them and can simulate a delivery, a bounce or a complaint.
shipmail.to · 2026-10-15
- [9]Shipmail TypeScript SDK documentation
The shipmail npm package, a typed client for the Shipmail REST API.
shipmail.to · 2026-10-15
- [10]Shipmail CLI documentation
The official Shipmail CLI for API health checks, domains, mailboxes, inbox messages, sending, webhooks, suppressions and raw API calls.
shipmail.to · 2026-10-15
- [11]Shipmail webhooks documentation
Shipmail webhook events such as message.received, mailbox and domain scoping, signing, retries, and the optional Authorization header sent with each delivery.
shipmail.to · 2026-10-15
- [12]Shipmail webhook signature verification
Every Shipmail webhook delivery is signed with HMAC-SHA256.
shipmail.to · 2026-10-10
- [13]Shipmail MCP server docs
Official Shipmail MCP server tools, resources, prompts, and install steps.
shipmail.to · 2026-11-16
- [14]Shipmail MCP npm package
Published npm package for installing the official Shipmail MCP server.
npmjs.com · 2026-11-16
- [15]Shipmail Assistant documentation
The AI assistant answers what needs a reply, finds conversations, files messages, sets up inbox rules for future mail and drafts replies. Its replies are normal drafts in the Drafts folder, Writing Style drafts from pasted examples, and organization admins can turn AI off for everyone.
shipmail.to · 2026-10-15
- [16]Shipmail sending policy
Limits count recipients, not messages. During the free trial an organization can send to 100 recipients a day across the dashboard, API, SMTP and transactional senders. From the first paid day the daily limit is the monthly quota divided by 30: Solo 20,000 a month (667 a day), Pro 40,000 (1,334), Team 120,000 (4,000), Scale 10,000 per mailbox (334). There is no warm-up for new accounts. On a paid plan, transactional senders have their own safety limit. Sending slows down at 25 failed recipients and 5% over 7 days, and pauses at 50 and 10% or 25 and 20%.
shipmail.to · 2026-11-18
- [17]Shipmail email client connection settings
Shipmail IMAP, SMTP, and JMAP settings: mx1.shipmail.to, IMAP on port 993 with SSL/TLS, SMTP on port 465 with SSL/TLS or 587 with STARTTLS, the full email address as username, and the mailbox password or an app password.
shipmail.to · 2026-10-15
Questions worth answering
Questions developers ask before moving transactional email and mailboxes to Shipmail.
Can I send transactional email from my own domain with Shipmail?
Do I need a separate account for each side project?
Can I test email sending without sending real email?
How do I process inbound email in my app?
Is Shipmail a replacement for Resend, Postmark or SES?
Related
More on Shipmail pricing, comparisons, and how it handles shared inboxes.
Email, newsletters and booking pages on your own domain, in one plan.
Get started for free