close
ZERODROP
DOCSPRICING
connecting...

EMAIL TESTING INFRASTRUCTURE

generating...

Verify signups, password resets and auth flows from code · No signup · No Docker

INBOX

< 1s

email delivery via SSE

30 min

auto-delete TTL

0

Docker containers

parallel inboxes

VERIFY AUTH FLOWS · ANY EMAIL PROVIDER

No MailHog. No Docker. No regex. Just email.otp.

test/auth.spec.ts
1import { ZeroDrop } from 'zerodrop-client'2import { Resend } from 'resend'34const mail = new ZeroDrop()5const inbox = mail.generateInbox()67// Send with Resend8await resend.emails.send({ to: inbox, subject: 'Verify' })910// Catch with ZeroDrop11const email = await mail.waitForLatest(inbox, { timeout: 10000 })1213email.otp        // "123456" — auto-extracted14email.magicLink  // "https://..." — no regex needed
$ npm install zerodrop-clientnpm ↗

GITHUB ACTION · NATIVE CI INTEGRATION

.github/workflows/ci.yml
1- name: Generate test inbox2  id: inbox3  uses: zerodrop-dev/create-inbox@v145- name: Run Playwright tests6  run: npx playwright test7  env:8    TEST_INBOX: ${{ steps.inbox.outputs.inbox }}
No Docker · No SMTP · No configMarketplace ↗

USE CASES

🧑‍💻

E2E Testing

Test email flows in Playwright and Cypress without mocking or Docker.

🤖

AI Agents

Give Cursor, Claude Code and autonomous agents a way to verify real email delivery.

🚀

CI/CD

Run deterministic auth tests on every deployment. No infrastructure required.

AI can build authentication flows. It still can't reliably verify email delivery without infrastructure. ZeroDrop is the missing layer.

Used by developers across Europe, North America and Asia

WORKSPACES — FOUNDING RATE

Custom domain that bypasses disposable email blocklists · Team access · $19/mo · Founder-managed setup

CLAIM FOUNDING SPOT →Already using ZeroDrop in CI? Tell me your use case →

Using Cursor, GitHub Copilot, or Claude Code?

Add the ZeroDrop context file — your AI will write email tests automatically.

GET THE SNIPPET →LLM context →