Point staging SMTP and webhook URLs at us. Test without worrying about emailing real customers: we capture the emails and never deliver them. Webhooks stay here unless you configure forwarding or replay a request.
Test without worrying about emailing real customers. Webhooks stay here unless you configure forwarding or replay a request.
HTML, text, headers, attachments. Your staging or test environment uses our SMTP instead of a real mailbox.
Connect your app →{
"type": "payment.succeeded",
"amount": 900,
"currency": "eur"
}
Body, headers, response you choose. Replay a request, or forward it to localhost while you debug.
Setup guide →Preview HTML at desktop and mobile widths. Inspect headers, attachments, links and possible verification codes. Check captured content for common issues and compare two messages.
Inspect content spam scores and matched findings, then recheck after a change. These checks assess message content, not inbox placement.
451Temporary failure550Permanent rejectionSimulate temporary 451 failures or permanent 550 rejections for one inbox. The simulation turns off automatically after 15 minutes.
Use the API to retrieve messages, links and webhook payloads in your tests. Connect your code agent through MCP, or forward webhooks to localhost with the CLI.
The SMTP inbox captures messages for inspection. It never relays them to their recipients.
Every plan includes email catch, webhooks, API access and localhost forwarding. Paid plans buy more room, longer history and more people — not a different product.
The everyday toolkit for a solo developer.
More room and history for growing projects.
Room for more projects and the people building them.
Prices are per workspace, billed monthly. Checkout shows the total before you pay.
AMMO products
