Your app at your company's address, and emails from your name
Sooner or later someone asks why the expense tool lives at a haechy.app address, and why its emails
come from a sender nobody recognizes. Both can be yours. You tell Claude the address, Claude hands you a few DNS
records to add where your domain is managed, and Haechy takes it from there. Both are on Pro, Team and Business.
Part 1. Open the app at expenses.yourcompany.com
The app keeps its haechy.app address and also answers at yours. People who already have the old link are not locked out.
- Ask Claude. Say what you want, in your words:
Put this on expenses.acme.com.- Add the records Claude gives you. For a subdomain such as
expenses.acme.comit is a CNAME that points at your app'shaechy.appaddress. For a bare domain such asacme.comit is an A record, plus a TXT record at_haechy.acme.comthat shows the domain is yours. - Wait for Haechy to notice. You don't have to come back and press anything. Haechy checks by itself every minute for the first hour, then every 10 minutes for a day, then hourly, and switches the address on when the records are there. A DNS change can take a while to reach everyone; the checks cover that.
- Hurry it along if you like. Ask Claude to "check the domain now" and it checks right away.
- Open it. The certificate (the padlock) is set up for you, and nothing about the sign-in changes: colleagues sign in with an emailed link, with a passkey, or with Google or Microsoft where your plan includes them, just as on the original address.
Use a subdomain if you can. A bare domain works through an A record that points at one server address. If Haechy ever has to relaunch that server with a new address, you would have to update the record. A subdomain with a CNAME never needs touching.
Part 2. Send the app's emails from your own domain
Out of the box an app's emails come from yourapp@haechy.app. A leave request from leave@acme.com looks like it comes from your company, because it does. This part sets that up.
- Ask Claude.
Send the app's email from acme.com.- Add the records Claude shows you. Claude gives you three CNAME records, which let the mail be signed as coming from your domain. Add all three. Claude may also suggest a DMARC record: add it only if your domain doesn't have one yet, and keep an existing one. If your IT person wants bounces to come back through a subdomain of yours, ask Claude for a return-address (MAIL FROM) subdomain, which takes two more records.
- Let it verify. Ask Claude "has acme.com verified yet?" and it tells you.
- Choose the sender. Once verified, tell Claude the sender you want:
Email as expenses@acme.com, and call it Acme Expenses.The app starts sending from that address with that name.
Until the domain is verified, nothing breaks. Mail keeps going out from the default haechy.app address, with a note that your domain isn't verified yet.
What your own sender doesn't change
Email from an app still goes only to people who have access to that app: you, your workspace members, the app's members and anyone who has signed in to it. That holds on every plan, including with your own domain. It is for notifications, approvals and summaries to your team, not for mailing customers or outside lists. The monthly allowance is the same too (sign-in emails don't count against it).
What each plan includes
As of November 2026.
| Item | Free | Pro | Team | Business |
|---|---|---|---|---|
| Own web addresses | 0 | 3 | 20 | 100 |
| Own sending domains per workspace | 0 | 1 | 5 | 20 |
| App emails a month | 300 | 5,000 | 15,000 | 50,000 |
A domain can belong to one workspace at a time.
Not sure which plan you need? See pricing.