Email, but with boundaries
Set up bye in your own Cloudflare.
Bye runs in your Cloudflare account. Connect it, pick an address, and you're done in a few minutes.
What Bye creates
Access requested: Workers, KV, D1, R2, Queues, Containers and Secrets Store, read access to your accounts and zones, and Workers Routes to attach one custom hostname. No DNS, MX or Email Routing access.
Resume your Bye
This Cloudflare account already has a Bye set up through onboarding. Continue managing it here; the previous browser session loses access.
Choose a Cloudflare account
Where should Bye live?
.
Lowercase letters, digits and hyphens.
Your Bye
Notifications in browsers and the Bye apps. The apps get them through Bye's push service, encrypted so it can't read them. You can change this later.
This Cloudflare account has no active domains yet.
Choosing a domain does not change its mail. Incoming email is a separate step you can do later.
Creating Bye
Details
| Check | Result |
|---|
Resources
Progress log
Review needed
This deployment is not a standard first install, so it needs your review before anything is changed.
Changes
| Action | Resource | Type |
|---|
Blocked
Review carefully
Bye is ready
Next, create your owner account with a passkey.
Connect the Bye apps
The link and code contain only this address. The app checks the server, asks you to confirm, then you sign in there directly.
Recovery and connection
Recovery kit
Holds this instance's generated secrets so you can redeploy without this service. It contains no Cloudflare credentials and can be downloaded only once.
Push notifications
Changing this redeploys Bye after you review the plan. Turning it off stops all notifications; turning it back on restores existing devices.