A good home for your team’s mail.

Shared mailboxes on your own domain. A calmer place to work, together.

Get started See how it works

Claim a domain you control. Receive through Cloudflare. Send with your own Resend key when you want replies.

Inbox

All

Mira Chen

9:14

Deck for Thursday's review

Latest version is attached.

Ivy Park

8:02

Refund for order 8812

Customer asked for a status update.

Owen Diaz

Yesterday

Invoice 44 is past due

Can billing take a look today?

ArchiveReply

Deck for Thursday’s review

Mira Chen

to me

Shared the latest deck in hello@. If anyone on the team wants a pass before Thursday, it is sitting in the same thread.

A company address is not a person, but you keep paying for one.

Three ways the usual options go wrong.

You pay per person for one address

hello@ and support@ are addresses, not people. Seat-priced providers bill you as if they were, then charge again for the shared inbox that makes them useful.

Forwarding loses the thread

Point the address at a personal inbox and it works until you reply. The reply comes from the wrong address, and nobody else can see what was said.

Everyone sees everything

The contractor helping with support should not be reading billing. Most cheap setups have exactly one access level: the shared password.

Three steps, then mail starts arriving.

You keep the keys. Cloudflare delivers inbound mail. Resend sends it back out when you add a key. Sending stays optional.

1
Claim your domain
About a minute
Sign in and enter a domain you own. You become its owner. We give you a TXT record. Publish it and press Check DNS.
DNS record
```
_ghar.yourdomain.com   TXT   ghar-verify=…
```
2
Point Cloudflare at us
About five minutes
All in the Cloudflare dashboard, no command line. Turn on Email Routing, create an Email Worker, paste the script we hand you, and press Deploy. Your ingest secret goes in as a worker secret, never in the code.
Cloudflare dashboard
```
Email → Email Workers → Create
  → Create my own → paste → Deploy

Settings → Variables and Secrets
  → Secret: INGEST_SECRET

Email Routing → Routing rules
  → hello@yourdomain.com → this worker
```
3
Add a Resend key to reply
Optional
Until you do, the mailbox receives only, which is useful on its own. Verify your domain in Resend, paste an API key, and replies go out as the mailbox.
Resend
```
Resend free tier
3,000 emails / month
1 verified domain
```

Step 3 is optional. Skip it and you have a working receive-only inbox, which is all a careers@ or a press@ ever needs. Add the key whenever you want to reply.

Decide who reads what, per mailbox.

Mail belongs to the address, not to a person, so two people can work the same inbox and see the same thread. Everything else is a matter of who you let in.

Domain owner

Whoever claims the domain. Holds the secrets, hands out seats, and can delete it.

Domain admin

Runs one domain for you. Invites people, adds mailboxes, reads everything on that domain and nothing beyond it.

Mailbox member

Sees only the mailboxes you assign. Put someone on support@ without giving them billing@.

studio.example

you@studio.exampleownerevery mailbox

sam@studio.exampleadminevery mailbox

ivy@studio.examplesupport@

owen@studio.examplebilling@, invoices@

Replies go out as the mailbox, never as the person.

What you bring, and what stays free-tier.

Ghar does not sell seats. Receiving uses Cloudflare Email Routing. Sending uses your own Resend key, on their published free-tier limits.

Cloudflare Email Routing

Unlimited addresses, inbound

Their free tier

Resend

3,000 outbound emails a month

Their free tier

Your domain

The one you already own

Already yours

Add mailboxes and teammates without changing any of the above.

Bring a domain you already own.

Get started