Nano
Available in beta
$5 /mo
100 emails / hour 600 emails / day (rolling 24 hours)
We're changing how email is priced.
Choose a fixed monthly plan for each sending environment. Size for your busiest hour and rolling 24 hours, including customer campaigns and traffic spikes. No overages, no surprise fees.
Cloud
Micro
Available in beta
$15 /mo
4k emails / hour 24k emails / day (rolling 24 hours)
Small
Available in beta
$49 /mo
40k emails / hour 240k emails / day (rolling 24 hours)
Medium
Available in beta
$99 /mo
100k emails / hour 600k emails / day (rolling 24 hours)
Large
Available in beta
$299 /mo
200k emails / hour 1.2m emails / day (rolling 24 hours)
XL
Unavailable during beta
$599 /mo
400k emails / hour 2.4m emails / day (rolling 24 hours)
Burst
Unavailable during beta
$1,499 /mo
800k emails / hour 4.8m emails / day (rolling 24 hours)
When the hourly or rolling 24-hour cap is reached, the REST API returns 429 with error
throttled. Your application can retry or requeue messages when capacity is available. If you are sending a high volume of emails, consider spreading your sends over time for better deliverability and pricing.
Boosts
Boost
Available in beta
Variable
A temporary boost to your cluster's capacity for the days where you really need it.
Additional IPs
Additional shared IPs
$15 /mo
Extra shared sending IP
Additional dedicated IPs
$50 /mo
Exclusive sending IP
Enterprise BYOC (Bring Your Own Cloud)
Talk to Sales
Custom
Run capsules in your cloud.
Beyond Cloud
Published plans or IP add-ons do not fit the workload.
Your Cloud
You want sending run in your cloud account.
Something else
Custom requirements that are not on this page.
No overages
Postmark, Resend, and other usage ESPs bill the spike. PostShiba returns 429, emails you, and you retry later. Like a database. You pay for the instance.
A sign-up attack: PostShiba vs. Competitors
Illustrative bills, not list prices
- Competitor Usage Bill $960
-
PostShiba $15/mo Micro
Postmark, Resend, and others
Every extra send is billed. A traffic spike becomes an overage invoice.
PostShiba
REST returns 429 throttled. SMTP waits in queue. Same monthly capacity. No surprise bill.
Before you start
Plan access, capacity, and support before moving your customers' email.
Can I use multiple sending domains?
Yes. Add multiple sending domains to one account without a per-domain charge. Verify each domain before sending. Messages across those domains share your chosen cluster's capacity.
Set up a sending domainWhat limits sending during beta?
Plan capacity is the sending limit during beta. Size your cluster for the busiest hour and the rolling 24 hours.
How do invitations and production approval work?
Start by requesting beta access. After signup, create your first cluster, verify a domain, and test with your team's email addresses. Request production approval from the dashboard and tell us how you plan to use PostShiba.
We review accounts individually before opening sending to external recipients. There is no fixed invitation or approval timeframe during beta, so wait for approval before scheduling your migration.
How production approval works Request Beta AccessIs there a trial, and do I need a card?
Your first cluster includes 7 days free. Add a payment method before creating it. The trial is tied to your first cluster's subscription and runs separately from production approval. The selected monthly plan applies after the trial.
Which plans can I start with?
New clusters can choose Nano (100 / hour · 600 / 24h), Micro (4,000 / hour · 24,000 / 24h), Small (40,000 / hour · 240,000 / 24h), Medium (100,000 / hour · 600,000 / 24h), and Large (200,000 / hour · 1,200,000 / 24h) during beta. Choose for your busiest hour and the rolling 24 hours, including spikes. If your workload needs more, contact us before moving production traffic.
Estimate your capacity planWhat happens during a traffic spike?
Requests over the hourly or 24-hour REST sending cap return 429. SMTP queues. Your app must retain rejected REST messages and retry when capacity is available. Size your plan for peak traffic so urgent mail is not delayed.
Review sending and retry requirementsHow do I get help?
Email jesse@postshiba.com for setup, migration, or sending questions. For a delivery investigation, include the message ID and sending domain. If you need specific support coverage, discuss it with us before migrating.