Wisp - Disposable Inboxes - Disposable Inboxes accessed through api
by•
Provision ephemeral @wispemail.com inboxes in milliseconds for Playwright, Cypress, and CI/CD test suites. Capture, inspect, and verify transactional emails with ease.
Replies
Best
Maker
📌
Hey everyone 👋
I built Wisp because I kept hitting the same wall testing my own products: verifying email flows in CI is a pain. Gmail app-password hacks, shared team mailboxes that flake under parallel test runs, or paying for enterprise tools sized for teams way bigger than mine.
So I built the thing I actually wanted — real inbound SMTP (not a third-party wrapper), a Redis pub/sub pipeline that pushes new mail to your browser or test runner in under 5ms, and an OTP/magic-link extractor built into the core, not bolted on as an afterthought.
The API is deliberately boring to use:
POST /inboxes → get an address
your app sends the email
GET /messages or open a WebSocket → get the code
Drop it into Playwright, Cypress, or a plain curl call from any CI runner.
It started as an internal tool to unblock my own test suites, and turned into something I think other teams doing QA automation will find useful too — that's the whole reason I'm putting it out here rather than keeping it to myself.
Would love feedback, especially from anyone who's fought with email testing in CI before — what's been your least-bad workaround so far?
Replies