These articles explain how OhRelay works, who it fits, and why the routing model matters for small teams managing multiple domain addresses.
These guides are written to help a buyer understand the problem, the mechanism, and the practical fit without having to reverse-engineer the product from setup details.
Cloudflare's new Email Sending beta is genuinely useful for programmatic email from Workers. But it's not the email problem I live with — managing replies across multiple domains and aliases without losing sender identity. Here's what I actually built to solve that.
Getting multiple addresses into one inbox is the easy part. Keeping replies consistent and scalable is where most setups start to fail.
Cloudflare handles inbound delivery. Workspace is a full mailbox product. The right choice depends on whether your problem is receiving mail or managing it end-to-end.
You can reply from a custom domain in Gmail without Workspace, but the approach that works for one address doesn't scale cleanly to multiple addresses or domains.
Traditional mailbox products bundle public email identity with mailbox seats. Separating those two layers is what makes a small-team setup actually fit.
OhRelay focuses on customer-facing inbound conversations and safe, correct replies — not bulk outbound.
Seat-based pricing often charges small teams for address complexity rather than for the number of people actually doing the work.
A clean multi-domain setup depends on consistent address naming, clear routing ownership, and reliable sender handling on replies.
OhRelay keeps the addresses customers see separate from the inbox where your team actually handles the work.
Many small teams have more outward-facing addresses than real email handlers. The real problem isn't hosting — it's managing those addresses without creating a mess.
Forwarding tells mail where to land. OhRelay also preserves the reply context you need to keep the sender identity consistent.
OhRelay uses Cloudflare for domain-level mail handling and programmable routing logic, with a privacy boundary built around headers — not message content.
OhRelay works best when many customer-facing addresses are handled by a deliberately small team.
OhRelay routes your mail and preserves the right reply identity. Your actual email history stays in the inbox you already control.
A technical walkthrough of the forwarding identity gap: why receiving is easy, why replying is not, and how a relay layer with envelope rewriting closes that gap.
