An identity and routing layer
OhRelay is priced like a routing layer for domain identities, not like another mailbox suite. You are already paying for your mailbox; this product sits on top of that workflow.
OhRelay pricing tracks the domain addresses you manage and the working inboxes behind them, not how many people happen to touch email inside the company.
Your cost grows with the domain addresses and working inboxes you manage, not simply with employee count.
OhRelay is priced like a routing layer for domain identities, not like another mailbox suite. You are already paying for your mailbox; this product sits on top of that workflow.
Your cost scales with the domain email addresses and working inboxes you manage — not with how many people happen to read the mail.
OhRelay fits into the workflow you already have. Keep using Gmail, Outlook, or Apple Mail while your archive stays in your own account and the routing happens in the background.
For solo founders or side projects managing a few core domain addresses.
For small agencies and studios managing multi-brand client addresses.
For distributed teams running complex address maps across many domains.
Managed addresses and working inboxes are concrete — no translation needed from seat-based mailbox billing.
The domain email addresses you route through OhRelay — things like support@, hello@, billing@, or sales@ on any of your domains. This is the main pricing unit because it reflects how many entry points you are managing.
The real inboxes where mail actually lands and gets handled — your Gmail, Outlook, or any inbox you already use. Each working inbox is a real person on your team. Several managed addresses can point to the same working inbox. Your mail stays in your own account, not in OhRelay.
The domains you have connected to OhRelay. Each domain needs DNS and sending configuration. More domains means more infrastructure under management.
The entry tier is not only for multi-domain customers. It also fits a solo operator or a very small company that still needs several visible role addresses.
Studio and Team exist for address and domain growth, not for turning the product into another seat-based email suite.