A test inbox per staging environment
A staging inbox is a receive-only address used for the accounts a team creates on a non-production environment. Keeping one per environment stops staging, UAT and dev mail from mixing and gives the team one place to look.
Last updated September 18, 2026
Who this is for
1Teams with several long-lived pre-production environments
2Developers seeding staging with realistic accounts
3QA who need to know which environment sent an email
In short
Create a project per environment (Staging, UAT, Dev) and an inbox per test account inside it. Every member sees every message, the verification code is extracted, and nothing lands in a real mailbox. Teardown scripts can create and delete inboxes through the API.
The common problem
Staging and production emails look identical in a real inbox.
Seeded accounts use "+" aliases that sites strip or de-duplicate.
Nobody remembers which mailbox the UAT admin account was registered to.
How Inflovy helps
Projects mirror environments; inboxes carry a label and a description.
Receive-only addresses on inbound.inflovy.com, never a real person.
API-created inboxes for seed scripts; search across the project later.
Shared Gmail versus environment projects.
| Need | Shared Gmail | Inflovy |
|---|---|---|
| Separation | Filters and labels, if someone maintains them. | One project per environment. |
| Seeding | Hand-made "+" aliases. | POST /v1/inboxes from the seed script. |
| Access | A shared password. | Workspace membership with roles. |
Questions people ask before switching.
Short answers. Inflovy is a receive-only test inbox for developers and QA teams; it does not replace your mailbox or send anything.
How many inboxes can a project hold?
Limits are per workspace: 10 inboxes on Free, 100 on Pro, 500 on Team. Projects are unlimited on paid plans.
Can I archive an environment?
Yes. Archiving a project disables its inboxes without deleting the messages; restore it later and the inboxes reactivate.
Related guides
Nearby workflows and comparisons, so you can evaluate the right one without guessing.
One project per environment. Start with staging.
Create the project, add the first inbox, and stop mixing staging mail with real mail.