E2E email testing is a nightmare. I’m trying to fix the middle ground.

If you write Playwright or Cypress tests, you already know the exact moment the joy leaves your body. Testing the UI is easy. But the second your test runner hits a "Check your email for the login code" screen, everything falls apart. I know the email testing space is already heavily saturated, but if you're just trying to verify an auth flow, developers are still forced into two terrible options: The duct-tape method: Wiring up a shared Gmail account via IMAP, writing brittle polling scripts, and praying that concurrent tests don't steal each other's OTPs. The overkill method: Adopting massive, expensive enterprise email QA platforms that feel like bringing a bazooka to kill a fly. There is a gap for a lightweight tool that just does one thing : provisions an isolated inbox on the fly, hands you the OTP or magic link, and gets out of your way. So, I built PostMX to fill that gap. I am launching the V1 today, and to be completely transparent, I have exactly zero users. But I want to sh