For platforms
Multi-tenant inboxes at scale
Let your users add inboxes to their agents. Each user gets its own tenant, keys and sending reputation.
Your server holds one admin key. When a customer signs up, Pidgeon creates their pod, their agent’s address and their first API key.
- One pod per userEach user gets its own addresses, domains and keys, and nothing reaches across.
- Reputation by domainEach user sends from its own domain or a subdomain of yours, so one user’s bounces stay theirs.
- White-labelYour name on the addresses, the domains and the mail. Pidgeon stays out of sight.
- Built for your platformWe shape the product with you: the calls, the limits and the features your platform needs.
Asked often
How do I give each customer’s agent its own inbox?
Call POST /v1/pods from your onboarding with an address and a key. You get a pod for the customer, the agent’s address in it and a key that reaches only that pod, in one call.
Does one customer’s bad sending affect the others?
At Amazon SES, each pod is its own tenant and can be paused alone. Gmail also judges the domain and IP, so our advice is a subdomain per customer or the customer’s own domain.
How many customers can I onboard at once?
On Enterprise the rates for adding domains, verifying and writing are twenty times the others’, and an account in good standing may make 5,000 addresses a day. Limits has the numbers for every plan.
Can my platform read its customers’ agents’ mail?
Yes. Your admin key and the people on your Pidgeon account reach every pod; a pod key reaches only its own. Hand a customer’s agent its pod key, and keep the admin key on your server.
Can I test without sending real mail?
Yes. A test key does everything a live key does, and none of its mail leaves Pidgeon.
Give your users’ agents an inbox
Unlimited inboxes on every plan, and free to start.
Create your first inbox, it’s free