Their domains. Your product.
Organize each customer's verified domains, SMTP credentials, and receiving inboxes in a tenant namespace.
Email infrastructure for the platforms people rely on.
For SaaS platforms managing email on behalf of their customers. Build on PostShiba, move from your current provider, or plan a custom deployment with us.
Every customer.
One place to operate.
Give each customer their own sending identity. Keep the controls you need to run email across your whole platform.
Try suspending or resuming the platform, a tenant, or a sending domain in this example. Turning off a tenant pauses sending for that tenant's domains. Turning off the platform pauses every tenant.
PostShibaYour platform
Active
Acme
acme
Active
mail.acme.com
Active
billing.acme.com
Suspended
notify.acme.com
Active
Globex
globex
Active
mail.globex.io
Active
alerts.globex.io
Active
receipts.globex.io
Active
Pause one customer
Suspend a customer's sending and inbox routing while you investigate. Keep the rest of your customers running.
Stop unwanted sends
Carry over each customer's suppression list and manage it alongside their other email resources.
Follow the message.
Find the answer.
Answer your customer's next email question with the delivery history, provider response, and customer context in front of you.
Message activityExample event
Event detailJSON
1
{
2
"event": "delivered",
3
"tenant_id": "customer-a",
4
"response": "250 OK",
5
"attempt": 2,
6
"unique_args": {
7
"order_id": "order_123"
8
}
9
}
Connect delivery events to your product.
Connect it to your customer
Trace a message back to the customer and activity in your product, from an order receipt to a support reply.
Trust the events you receive
Signed delivery and inbound webhooks let your application verify where an event came from before acting on it.
Pick up where you left off
Automatic retries help with temporary webhook failures. Review failed events and replay them from the dashboard.
Grow your platform.
Know what comes with it.
Monthly.
Capacity you can budget for
A fixed monthly plan for each sending environment, with clear hourly and rolling 24-hour outbound limits.
No overages.
A bill you can understand
No per-email overage charges. When an outbound limit is reached, API sends must be retried; SMTP mail waits in the queue for capacity.
Every domain.
Room for your customers
No per-domain or per-tenant fees. Adding customers doesn't add capacity: outbound uses the sending environment's limits, and inbound has a separate team allowance.
A deployment plan.
A team on your side.
Moving providers or exploring your own cloud? Work with the people operating PostShiba and Bento to plan what comes next.
We know how it feels to be locked out.
Account suspension is a last resort. When an issue can be contained to a domain, we focus the response there and work with you on recovery.
How we approach email operationsRequest your platform invitation.
Drop your work email. We're gauging who joins private beta. Any size is welcome.
Prefer to explore? Read the docs →