Email was built for people. We build it for devices too.
Most mail products assume one person behind one mailbox. That breaks when a hundred devices each need to receive a verification code. Mailcycle is programmable, privacy-first email for one person or a whole fleet.
Why we built it
Teams running device fleets (QA labs, kiosk networks, field hardware, test farms) keep hitting the same problem: shared mailboxes with tangled plus-addressing, a spreadsheet of credentials, a catch-all inbox with forty thousand messages and no way to tell which device a code was meant for.
In Mailcycle a device owns its address. Pairing is a handshake, and revocation is per device.
One private address stays simple. The individual who wants one and the operator provisioning a thousand get the same account, the same encryption and the same API. Only the plan differs.
What we believe
- The best way to protect data is not to have it
- Design so you don't have to trust us
- Knowing an identifier is not authorization
- Refuse clearly; never truncate silently
- Mobile and web are the same product
- If the console can do it, the API can do it
- Label planned features as planned
- Say what we can still see
- State what each privacy choice costs
Reachable by email.
Every address below is the same inbox, and a person reads it.
Sales
Volume pricing, dedicated domains, procurement and security questionnaires.
hello@mailcycle.emailSupport
Anything about a live account, a device that will not pair, or mail that has not arrived.
hello@mailcycle.email