Projects and teams

A project for every client and app, with its own addresses, keys and people.

Projects keep test accounts apart. Each has its own addresses, settings, API keys, connected agents and reports, and on the Team plan, its own list of people.

Create a free accountOpen the app See the Team plan

Free plan · No credit card · Addresses last up to 30 days

What a project is

Everything for one client or app, kept together.

Its own addresses

Every test address belongs to one project, so Client A’s accounts never mix with Client B’s.

Its own settings

The website you’re testing (one click from the app), environments such as staging and QA, an email prefix like cna- for every new address, and the mail domain new addresses use.

Its own keys and agents

API keys and connected AI agents work in one project only. A key for Client A can’t see Client B.

Its own people

On the Team plan, choose who’s on each project. Organisation admins see them all.

Its own reports

A dashboard of what needs attention and what changed, and a QA report for any date range: what was tested, with which accounts, and every code or link they received.

Archive, then restore

Archiving stops a project’s addresses at once. Restore it from the Projects page within 15 days; after that it’s deleted.

Set one up

Ready in a minute.

Name it
Choose New project and give it a name, such as the client or the app. Projects are unlimited.
Add the details
The website you’re testing and its environments, such as staging and production.
Set the defaults
Under Advanced, an email prefix (cna- makes every new address start with it) and the mail domain: @mailclub.dev or @enable.li.
Start testing
Add addresses by hand, connect your AI agent, or create an API key for your test suite.

Agents and the API

Tests and agents reach exactly one project.

Whether it’s your CI pipeline with an API key or an AI agent signed in through the browser, access is to one project, as the person who set it up.

AI agents sign in to one project

Connecting through the MCP server opens a browser page: you sign in, choose the project the agent may use and allow it. Its first call, get_project, tells it that project’s mail domains, prefix and limits.

API keys belong to one project

Create a key in Project settings for a test suite or CI. It acts as the person who made it, only in that project. It’s shown once; reading saved passwords needs a key made with that permission.

Revoke or disconnect any time

Keys and connected agents are listed together in Project settings → API keys. Revoke one and it stops at once. Each key has its own request limit.

Who can see what

Choose who’s on each project.

Free: private to you
Every address and project is private to the account that made it.
Team: an organisation
One price for the whole organisation, with unlimited seats. Invite people by email; their link works for 7 days.
Owners and admins
See every project, approve invite requests and manage who’s in the organisation.
Members ask
Members can ask an admin to invite someone, rather than inviting directly.
Project leads
Each project has leads, who add people from the organisation, remove them and choose who else leads.
Everyone else looks
People on a project see and use its accounts; only leads and admins change who’s on it.

Reports and records

Show what was tested, and who did what.

Reports

The Dashboard covers the last 7 or 30 days: failed email checks (SPF, DKIM, DMARC, local or http links), refused mail and failed runs; changes such as a new sending provider, a code where there was a link, or links to a different site; and how fast emails arrive. For the QA report, pick a date range and get the project’s addresses, personas, notes and every email’s code or link, to print, save as PDF or download as CSV. Saved passwords are left out unless you tick the box, and addresses that share a password are flagged without revealing it.

Activity log

Who created, changed or deleted what, who opened or copied codes and links, and when passwords were revealed, with how each action came in (the app, the Chrome extension, an agent or an API key) and a filter for it. Kept for 90 days; owners and admins see it.

Runs

Each CI job or agent session as a run, with which emails arrived, how fast, their codes and checks, and any that never came. The GitHub Action posts its report on the pull request.

An account pool

Tag accounts with their state, such as verified or premium, and let tests check one out that no other test has. A held account shows who has it and until when, and anyone on the project can free it.

Debug mode

Keep each new email’s original .eml file, with every header and attachment, until its address expires. Useful when a code wasn’t picked up.

Dev environments

Mark a host such as localhost:3000 as your dev environment, so its links stop being flagged in that project and pass the email checks. Agents and test suites can mark one too.

FAQ

Questions

How many projects can I have?

As many as you like, on every plan.

Can an API key or agent reach my other projects?

No. Each key and each connected agent works in the one project it was made for, and only with what the person who made it can do there.

Do I need the Team plan to share a project?

Yes. On the Free plan everything is private to your account. The Team plan adds an organisation, where you choose who’s on each project.

What happens to a project’s addresses when I archive it?

They stop receiving mail straight away. Restore the project from the Projects page within 15 days to bring it back; after that it’s deleted with its addresses and mail.

More features

Start with one project. Add the rest as you go.

Projects are unlimited on every plan. Bring your team when you’re ready.

Create a free accountOpen the app