One address, or ten thousand.
Programmable, privacy-first email built for individuals, automation, and large-scale device fleets.
The same product at every point on the curve.
There are no separate editions. Moving from one address to a fleet is a plan change and some extra pairing.
1address
An individual with one private address.
10devices
A developer or a small team, pairing what they already own.
100devices
An operations team running tagged, searchable devices in bulk.
1,000+devices
A fleet operator provisioning email addresses across a whole deployment.
A private email address, simply.
Create an account, create an email address, read your mail. Add a device later if you want one.
- No sign-up form, email address or password. An account is twelve words your device generates. The first unlock on a new device takes about 40 seconds.
- Mail is sealed to a key only your devices hold before it is stored. Remote content is never fetched, so nothing reports back to the sender.
- Retention is a setting: 24 hours, 7 days, 30 or 90 days, after which mail is deleted.
- Read it on your phone, your laptop, or both. The same inbox wherever you are signed in.
You can ignore the rest of this page. Devices, tags and bulk operations appear once you pair something.
Programmable email infrastructure that fits into your application.
Mailcycle's own console is built on the same HTTP API you can call. Mint an address, attach it to a device, read what arrives.
- Create an email address programmatically, and delete it when you are done to free its place on your plan.
- List, rename, tag, disable and revoke devices, and send mail from your own addresses, over the same surface.
- Read mail for one address or across every address a device holds.
- Identifiers are opaque and prefixed, errors carry stable machine-readable codes, timestamps are ISO 8601 UTC.
Message content comes back sealed. Your client decrypts it with a key derived from the recovery phrase. There is no server-side search.
Not built yet
Planned- Long-lived API keys, so a script does not have to run the recovery-phrase handshake
- Webhooks for inbound mail and device lifecycle events
- A hosted event stream, and SDKs over both
Addresses for systems that need to receive something.
Sign-in codes, verification links, delivery receipts, alerts: many automated processes need a real email address. Mailcycle gives each one its own.
- Mint email addresses on demand and delete each one when the process is finished with it, freeing its place on your plan.
- Give a test environment its own addresses without attaching them to anyone's personal mailbox.
- Assign several addresses to one Worker when a single runner handles many flows (Personal and above).
- Keep the whole estate visible in one account, with every address and your plan limit on the same screen.
Devices receive and read mail but cannot send it. Sending is done by the account, over the API, from addresses it owns.
Centrally manage email identities across devices and workflows.
One Operator account holds the devices, the addresses and the assignments between them. "Which device is receiving that?" is answered on one screen.
- Tag devices by team, environment, location or anything else you filter by later (Operator and above).
- Read the mail for any address on the account remotely, without physically holding the device.
- Remove one device without disturbing the rest. Each device has its own credential.
- Plan, address limit and payment in one place, with downgrades checked against the addresses you hold before they apply.
Teams, with several people on one account, are planned.
From one device to thousands.
Provision email addresses across your fleet and manage them from one Operator account. Devices are unlimited on every paid plan; you pay for the addresses you hold.
- Connect devices in seconds with a QR code, or an 8-digit code where there is no camera.
- Devices need no user accounts. A Worker holds a credential, not an identity.
- Search, filter and sort the device list, select many devices, and disable, enable or remove them in one action (Operator and above).
- Distribute addresses however the deployment needs them, and move them between devices by unassigning and reassigning.
Mailcycle is for devices you operate. The acceptable use policy rules out mass-registering accounts on other services.