Why we built SMTPBox
Email powers important product journeys: registration, password resets, invoices, alerts and account changes. Testing those journeys should not require a complicated enterprise platform or the risk of sending unfinished messages to real people.
SMTPBox captures mail from development, staging, preview and automated-test environments. It does not deliver those messages to their intended recipients. Your team gets a realistic email workflow with a deliberately safe outcome.
Made for the way software teams work
Developers
Use familiar SMTP credentials, inspect rendered messages and raw source, and diagnose email problems without changing how your application sends mail.
QA engineers
Keep test messages in shared inboxes, check links and attachments, and make email part of repeatable automated tests.
Growing teams
Separate projects and environments, invite the people who need access and retain test data only for a defined period.
Security-conscious teams
Keep production delivery credentials out of non-production environments and automatically remove old test messages.
Our principles
- Safety by default. A sandbox should prevent accidental delivery, not merely make it less likely.
- Useful before expensive. The free plan should support genuine development work, not just a short demo.
- Clear boundaries. SMTPBox is an email testing service, not a production sender or permanent archive.
- Focused tools. Every feature should help a team capture, understand or test email.
Build with us
Have a workflow SMTPBox could make safer or faster? We would like to hear about it.
Contact SMTPBox →