Pricing
All plans are billed monthly.
pricing guide
Use this page to decide whether you still need a simple temporary inbox, a steadier account workflow, or a plan built for domains, automation, and collaboration.
If the address must become predictable or reusable, public create is just the start and the next step moves into the account + plan contract. Whether reuse is actually allowed still depends on eligible custom domains and same-team scope boundaries.
A custom domain is a higher-commitment asset. At that point this is no longer just an anonymous mailbox choice but a product/workspace decision.
When mail rules, webhooks, replies, and notifications start to matter, upgrading becomes the reasonable next move.
A custom domain only becomes the right next step when you care about brand, asset ownership, collaboration boundaries, and automation — not just having any inbox that can receive mail.
Once recovery, settings, tokens, webhooks, and mail rules matter, the account becomes the natural next container.
A custom domain is not just cooler branding. It turns the mailbox from a temporary entry point into an asset you can govern, migrate, and keep.
When mailbox events become part of workflow, notifications, team processes, and asset management, that is when deeper plan and workspace contracts make sense.
The flow now includes a setup detail page, retry/polling, diagnostics, and a guided setup lane, so it is no longer only operator-assisted. But it is still not a fully productized start-to-finish public wizard, and it is better to say that clearly than overpromise.
Choose a plan
More features are not automatically better. The right fit depends on whether you are still testing anonymously, using mailboxes steadily, introducing custom domains, or already wiring mailbox events into automation/workspace flows. If the real question is catch-all, reusable locals, or same-team reuse, read that against custom-domain eligibility and team-owned scope boundaries too.
This is about OTPs, throwaway signups, and low-friction testing. Speed matters more than governance.
The mailbox is no longer disposable. You want to recover it, keep it, and reuse it with less friction.
At this point the focus is asset ownership, address governance, and custom-domain contract instead of just mailbox volume.
Once webhooks, replies, priority events, collaboration, and larger throughput matter, the higher tiers start making sense.
For personal testing and light usage
For heavy daily usage and advanced individual needs
For developers, automation, and advanced operations
For high-scale operations and advanced automation
capability matrix
This focuses on the capability lines that most often drive upgrade decisions: retention, custom domains, reusable locals, automation, and workspace/collaboration. When a capability still depends on catch-all management, same-team reuse boundaries, or operator-assisted setup, treat the matrix as a decision aid rather than a promise of a full self-serve loop by itself.
| Feature | Basic | Plus | Pro | Infinity |
|---|---|---|---|---|
| Retention | Mail retention: 30 minutes | Mail retention: 7 days | Mail retention: 30 days | Mail retention: 90 days |
| Custom domain | Not included | Supports 1 custom domain | Supports 5 custom domains | Supports 20 custom domains |
| Reusable local | Not included | Not included | Reuse used local-part on eligible custom domains | Reuse used local-part on eligible custom domains |
| Automation | Not included | Basic support | Webhook notifications | Priority webhook/event processing |