CLOSED BETA · FOR SIGNUP, OTP AND MAGIC LINKS

Email testing
for SaaS teams.

Give every test its own inbox. Wait for the email, finish the flow with its code or link, and run the same test in production.

Book a demo Read the docs

TEST EVENTS FREE A MONTH: 300
DEVELOPER PLAN: $19
EMAIL DOMAIN ON FREE: 1

acme-qa.devhelmmail.com

ActiveAssigned

Any address @acme-qa.devhelmmail.comLast message 14:06 UTCKept 14 days

Receiving

Newest first · 50 per page

Your Acme verification code

Acme <no-reply@acme.dev> → signup+7f3a@acme-qa.devhelmmail.com

7 Oct 2026 · 14:06:22 UTC

418302

Found in the text and HTML parts, counted once

Hi Ada,

Enter this code to finish signing up to Acme:

418302

This code expires in 10 minutes.

Acme

Links

0

Attachments

0

None on this message

AUTOMATE

Automate tests in minutes.
In the language you test in.

Give each test a fresh address, trigger the email, and wait. One call returns it with the code and links already pulled out, from TypeScript, Python, the CLI or plain HTTP.

·1import { test, expect } from '@playwright/test';

·2import { Devhelm } from '@devhelm/sdk';

·3

·4const devhelm = new Devhelm({ token: process.env.DEVHELM_API_TOKEN! });

·5

·6test('new user verifies their email', async ({ page }) => {

17 const mailbox = await devhelm.email.address({ label: 'signup' });

·8 await page.goto('/signup');

·9 await page.getByLabel('Work email').fill(mailbox.email);

210 await page.getByRole('button', { name: 'Create account' }).click();

·11

312 const message = await mailbox.wait({

313 subjectContains: 'verification code', timeoutMs: 60000,

314 });

·15 const code = message.otp?.[0]?.value ?? '';

·16 await page.getByLabel('Verification code').fill(code);

·17 await expect(page.getByRole('heading', { name: 'Welcome' })).toBeVisible();

·18

·19 await mailbox.clear();

·20});

IN THREE STEPS

1Pick any address

A new, empty inbox on your domain for every run. Nothing to create first.signup-3f9a1c2e@acme-4j4n.devhelmmail.com

2Trigger the email

Your app sends it the way it would to a customer, through your own email provider.“Your Acme verification code”

3Wait for it

Returns as soon as the email lands, or fails with a 408 at your timeout.

200otp[0].value"482913"

408WAIT_TIMEOUT · nothing in 60 s

WORKS WITH

PlaywrightCypressSeleniumVitestJestpytestRSpecGitHub ActionsGitLab CIanything that speaks HTTP

TypeScript and Python SDKsPlus the devhelm CLI and a REST API for anything else.

Clean up in one callClear the inbox in teardown, so runs never mix.

Match the right emailFilter by subject. Older mail never matches.

Your own timeoutUp to 120 s per wait. A 408 means nothing came.

Safe in parallelEvery new address is a separate inbox.

Inject test messagesAdd mail through the API, with no provider.

INSPECT

Inspect every message.
Body, headers, codes and links.

Open any email to see exactly what your users get: the HTML and text body, every header, and the codes and links we pulled out.

acme-qa.devhelmmail.com

ActiveAssigned

Any address @acme-qa.devhelmmail.comLast message 14:06 UTCKept 14 days

Receiving

Newest first · 50 per page

Your Acme verification code

Acme <no-reply@acme.dev> → signup+7f3a@acme-qa.devhelmmail.com

7 Oct 2026 · 14:06:22 UTC

418302

Found in the text and HTML parts, counted once

Hi Ada,

Enter this code to finish signing up to Acme:

418302

This code expires in 10 minutes.

Acme

Links

1

Verify your email

Attachments

0

None on this message

IN EVERY MESSAGE

1Every address, one inbox

All mail to your domain, newest first

2HTML and text body

What your users read, as it was sent

3Codes and links

Pulled out of every message for you

4Headers

From, To, Reply-To and every raw header

5Raw source

The original message, as it arrived

History by plan3 days on Free, 7 on Developer, 30 on Team, 90 on Business, 365 on Enterprise.

Same data in the APIEvery message, header, code and link, for your tests and tools.

Private to your teamOnly your workspace can read your domain’s inboxes.

CAPABILITIES

Test every email you send.
No mail server, no shared inbox.

Everything an email test needs, on an assigned domain that works from your first request.

01INBOXES

Assigned domainAny local-part receives mail immediately. No inbox to create.

TEAM AND UP

Your own domainReceive on a subdomain like test.acme.dev with one MX record.

SAME PLAN

Webhook inboxesCapture the webhooks your flow sends, next to its emails.

02MESSAGES

Codes and links extractedOTP codes and links come out of every message, ready for your test.

Wait with a timeoutBlock until the right email arrives, or get a 408 when it doesn’t.

SOON

Spam scoreSee how spam filters would score each message before customers do.

FLOWS

Cover the flows users depend on.
From signup to team invites.

If a user waits for an email to get in, a test should too. These are the flows teams cover first.

Prove new users can verify their emailSign up with a fresh address, read the code from the email, and land on onboarding.

THE TEST CHECKS THAT

The email arrives within 30 seconds

The code in it is accepted

The new user lands on onboarding

Run it in CI, then every few minutes in production as a browser check.Browser checks →

FromAcme <no-reply@acme.dev>Tosignup-3f9a1c2e@acme-4j4n.devhelmmail.comSubjectYour Acme verification code

acmeEnter this code to finish creating your account:482913The code expires in 10 minutes.

EXTRACTED

otp[0]482913

Received14:02:11

After trigger2.1 s

TSsignup.spec.ts

8 const mailbox = await devhelm.email.address({ label: 'signup' });

9 await page.getByLabel('Work email').fill(mailbox.email);

10 await page.getByRole('button', { name: 'Create account' }).click();

11 const message = await mailbox.wait({ subjectContains: 'verification code' });

12 await page.getByLabel('Verification code').fill(message.otp?.[0]?.value ?? '');

13 await expect(page).toHaveURL(/onboarding/);

PLATFORM

Part of the DevHelm platform.
Test business flows end to end.

Run the same signup test as a browser check every few minutes, with email and webhook inboxes, alerts and AI triage on one account.

01 · BROWSER CHECK

02 · EMAIL INBOX

03 · WEBHOOK INBOX

04 · EVERY 5 MIN

05 · WHEN IT BREAKS

01 · BROWSER CHECK

TSsignup.spec.tsr12

const mailbox = await devhelm.email

.address({ label: 'signup' });

await page.getByLabel('Email')

.fill(mailbox.email);

await page.getByRole('button',

{ name: 'Create account' }).click();

const message = await mailbox.wait({

subjectContains: 'verify' });

const event = await inbox.wait({

http: { pathPrefix: '/hooks/users' } });

expect(event.json().type)

.toBe('user.created');

Playwright@devhelm/sdksecrets: TEST_PASSWORD

02 · EMAIL INBOX

mailbox.wait()2.1 s

acmeEnter this code to verify your email:482913Verify email

subject"Verify your Acme email"

tosignup-3f9a1c2e@acme-4j4n…

otp[0]"482913"

links"Verify email" → acme.dev/verify

03 · WEBHOOK INBOX

POST/hooks/users0.8 s

content-typeapplication/json

x-acme-sig…t=1760541731,v1=9c…

{
  "type": "user.created",
  "id": "usr_9f2k1",
  "plan": "trial"
}

inbox.wait() matched

04 · EVERY 5 MIN

Signup flowFailing

TypeBROWSER

Regionsus-east, eu-west

Sign up1.9 s

Verification email60.0 s

408 WAIT_TIMEOUT

user.created webhookskipped

last 60 minfailing since 13:58

05 · WHEN IT BREAKS

Slack#on-call

● Signup flow: no verification email in 60 s

Status page

Sign-up: degraded

status.acme.dev

AI SREVENDOR

SendGrid is delaying mail since 13:56. Your code is fine.

ON ONE ACCOUNT

Email inboxesWebhook inboxesBrowser and API checks20 alert integrationsStatus pagesVendor status

AI SRE (founding offer)

Browser checks →

BUILD OR BUY

Stop reading the QA Gmail.
Use inboxes built for tests.

A shared mailbox or a public inbox works for one test. It breaks once tests run in parallel, in CI and in production.

DevHelm.ioWorkspace-only reads, built for tests

A shared GmailOne team mailbox, read over IMAP

A public inboxA free disposable address

ADDRESSES

A new address for every test

Any address, instantly

Plus-aliases on one mailbox

Any name, on a public domain

Who can read the mail

Your workspace only

Everyone with the password

Anyone who guesses the address

Your own domain

On Team and up, with one MX record

Only with Google Workspace

Not available

GETTING THE CODE

Waiting for the email

One call, 408 at your timeout

Poll IMAP in a loop

Poll the page in a loop

Reading the code or link

Extracted for you

A regex you maintain

Tests running in parallel

A unique address per run

Tests read each other’s mail

Works, in public

IN PRODUCTION

Scheduled checks and alerts

Browser checks, 20 alert integrations

Build it yourself

Message history

3 to 365 days, by plan

Until someone cleans it up

Often deleted within hours

PRICING

300 test events free.
Paid plans from $19.

Events are emails and webhook requests combined. Add Testing to any monitoring plan, Free included.

Free

$0forever

For trying webhook and email tests.

Includes

3 webhook inboxes
1 email domain
300 events a month
3-day history

Start free

Developer

$19/ month

For one developer’s test suite.

Everything in Free, plus

10 webhook inboxes
3,000 events a month
7-day history

Start Developer

Team

$79/ month

For teams testing flows in CI and production.

Everything in Developer, plus

100 webhook inboxes
3 email domains, including your own
100,000 events a month
30-day history

Start Team

Business$149/ month

Start Business

500 webhook inboxes · 10 email domains
300,000 events a month
90-day history

EnterpriseCustom

Book a demo

Unlimited inboxes, domains and events
365-day history
Hands-on setup with our team

EVERY PLAN

Wait APITypeScript and Python SDKsCLIOTP and links pulled from emailsNo usage charges

No usage charges on Testing. When the included events are used, new ones stop.

Webhook and Email Testing are in beta.

FAQ

Questions,
answered.

What teams ask before they move their email tests to DevHelm.

Still deciding?

We’ll set up your first email test with you on a call, and answer the rest.

Book a demo Read the docs

Your workspace gets its own domain, like acme-4j4n.devhelmmail.com. Any address on it is an inbox, so there is nothing to create first. The SDK’s address helper gives every test run a fresh, empty one.

Email testingfor SaaS teams.

Your Acme verification code

Links

Attachments

Automate tests in minutes.In the language you test in.

Inspect every message.Body, headers, codes and links.

Your Acme verification code

Links

Attachments

Test every email you send.No mail server, no shared inbox.

Cover the flows users depend on.From signup to team invites.

Part of the DevHelm platform.Test business flows end to end.

Stop reading the QA Gmail.Use inboxes built for tests.

300 test events free.Paid plans from $19.

Questions,answered.

Test the emails your users wait for.

Email testing
for SaaS teams.

Automate tests in minutes.
In the language you test in.

Inspect every message.
Body, headers, codes and links.

Test every email you send.
No mail server, no shared inbox.

Cover the flows users depend on.
From signup to team invites.

Part of the DevHelm platform.
Test business flows end to end.

Stop reading the QA Gmail.
Use inboxes built for tests.

300 test events free.
Paid plans from $19.

Questions,
answered.