Use cases
Built for products and for the people running them.
Two audiences shaped this: software that needs mailboxes it can create from code, and agencies running mail across domains that are not their own.
For SaaS
Mail your product owns, not a shared inbox
Create a real mailbox for every customer on your domain, from code, the moment they sign up. Inbound arrives on a signed webhook, outbound goes over the API, and a delivery log says what happened to each message — instead of a shared inbox to poll and a forwarding chain to debug.
- Mailboxes provisioned from your own signup flow, not by hand
- Signed webhooks with a delivery log you can inspect
- Extra addresses included on every plan, so a new role address is not a new bill
The routes it runs on
- POST
/v1/mailboxes - GET
/v1/messages - POST
/v1/messages - POST
/v1/webhook-endpoints
Four of about seventy-five endpoints. A folder or label made through the API is a real IMAP folder, so it shows up in Thunderbird too — there is only ever one of them.
For agencies
Every client on their own domain
Run mail for clients under their own domains from one account. Each domain gets its MX, SPF, DKIM and DMARC written and verified separately, so onboarding a client is a DNS authorisation rather than a support ticket — and on the your-cloud mail plane the whole surface carries your brand instead of ours.
- Several client domains under one login and one invoice
- DNS handled per domain, not once per account
- Hand a domain back by pointing its MX elsewhere
One account, separate domains
acme.com6 mailboxesMXSPFDKIMDMARCnorthwind.studio3 mailboxesMXSPFDKIMDMARCharbourlaw.co11 mailboxesMXSPFDKIMDMARC
From a domain to the first message
- 01
Point the domain
Authorise us at your DNS provider, or take the records and add them by hand.
- 02
Records verified
MX, SPF, DKIM and DMARC written and checked until they resolve.
- 03
Create mailboxes
Any address on that domain, Smart today and per-mailbox later.
- 04
Mail flows
IMAP and SMTP in the client you already have open.
Where Ruber sits
One mail plane, two ways out of it — a mail client, or your own code.
Also
Side projects
A working address on ruber.me while you decide, and your own domain when you have one — the trial carries one from the first day.
Small teams
billing@, support@ and hello@ are included addresses, not extra users — each one delivers to whoever you choose.
Consultants
Mail that survives changing provider, because the address was never ours to begin with — leaving is a DNS change.
Anyone tired of being sold
A different address at every checkout, on a domain you own. Mail to one you never gave out tells you who sold it, and blocking it is one click.
Researchers and writers
Publishing a paper or a policy means publishing an address. A catch-all takes them all, and an address that starts attracting spam can be retired without touching the rest.
Anyone running more than one thing
Store, studio and personal on one account and one bill, each on its own domain with its own records verified separately — not three subscriptions and three passwords.
None of this needs a call first.
30 days with 10 GB and a domain of your own, then a plan if the mailbox count has outgrown it. No card to begin.