Free
$0
For individual developers and quick testing.
- Real-time email receiving
- Password-protected inboxes
- 40 MB storage per mailbox
- 1-hour email retention
- 100 ops / month
- Local history, 5 entries
- Custom domains
- Webhooks
- Reset mailbox passwords
Email infrastructure built for receiving.
·········Custom premium domains, the API, mailbox password reset and more practical features.
Get PremiumLoved by 1000+ members
Upgrade to Pro for custom domains, webhooks, and 200× more API capacity.
$0
For individual developers and quick testing.
$5/ month
For teams, CI/CD pipelines, and production integrations.
| Feature | Free | Pro |
|---|---|---|
| Email retention | 1 hour | 7 days |
| Mailbox history | Local · 5 entries | Cloud · 500 · cross-device |
| Storage per mailbox | 40 MB | 50 MB |
| ops / month | 100 | 10,000 – 1,000,000 |
| API tokens | Yes | Yes |
| API rate limit | 1 req/s | 10 req/s |
| Custom domains | -- | Up to 100 |
| Webhooks | -- | 1 |
| Reset created mailbox passwords | -- | Yes |
| Pro-exclusive email domains | -- | Yes |
Free keeps each message for 1 hour, Pro keeps each message for 7 days — deleted automatically when time is up.
An account remains active when it is accessed at least once every 3 months. Accounts inactive for 3 consecutive months are deleted. Active Pro subscriptions are exempt from this inactivity rule.
Every mailbox has a password, generated the moment the account is created — only someone holding the password can open it. And the mailbox is receive-only: it can receive mail, never send it.
No. The server stores only a derived key, so the password cannot be recovered — this mechanism protects user privacy. Passwords should be stored securely. Pro users can reset a mailbox password from the console.
Mailboxes created by a user are saved in History and can be opened there without entering the password again. Free stores History only on the current device; Pro syncs it to the cloud for access across devices.