Make it real
Your own domain — and the certificate that follows
Your app already answers on your-app.erawan.app. This is how it gets the domain you own: the records to create, what happens on its own afterwards, and what to delete the day you stop.
Rather not set it up yourself? Erawan does it for free on Hobby and above.
Before you start
Your own domain needs the Hobby plan or above, and a domain you have already bought, from any registrar. While you set it up, the app keeps answering on your-app.erawan.app, so the site is never down.
1. Tell your AI which domain
Type this in the chat with the AI you connected to Erawan, with your own domain in it.
From a terminal, run this instead.
Either way you get the records for exactly that name, which is why this step comes before you change anything at your registrar. You also get a link to a page in the console with the values already filled in. If someone else looks after the domain, send them that link.
2. Create the records it gives you
A subdomain such as shop.example.com is one record.
Type | Name | Value |
|---|---|---|
CNAME | shop | ingress.erawan.cloud |
A bare domain such as example.com is two records. You get both, and www is attached at the same time.
Type | Name | Value |
|---|---|---|
A | @ | the IP address it printed |
CNAME | www | ingress.erawan.cloud |
Do not skip the second one. A bare domain cannot be a CNAME, which is a rule of DNS itself, so it has to point at an IP address while www can point at a name. Create only the first and the site works, but anyone who types www out of habit gets nowhere, and nothing warns you. You find out when somebody tells you.
3. If you use Cloudflare, turn the proxy off
Click the orange cloud on that record so it turns grey. With the proxy on, the name points at Cloudflare instead of Erawan and the HTTPS certificate cannot be issued. Erawan recognises this case and tells you to turn the proxy off.
4. Wait, and HTTPS follows
Nothing else to do. Erawan keeps checking the name, and once the records point here it asks for the certificate. To see where it is, ask your AI whether the domain is ready, or run this.
The status starts at pending_dns, becomes issuing while the certificate is issued, and live once the domain works.
A DNS change can take up to an hour to be seen everywhere. Check as often as you like in the meantime: Erawan looks at DNS first every time and does not ask for a new certificate on each check. Once the name is visible, the certificate follows within a few minutes.
5. If the app has a sign-in, add the new domain's return address
An app that uses Erawan's sign-in needs a return address on the new domain in its list, or people who sign in there cannot get in. Ask your AI to add a callback for the new domain, or run this with the path your app uses.
More in Add a sign-in for your users.
6. Optional: send the old address to the new one
The erawan.app address keeps working and stays yours. If you want everyone to end up on your domain, run this.
It is off by default: until you choose, both addresses are equally good. If the domain ever has a problem, turn it off and the erawan.app address serves again at once.
7. When you stop
Once the domain is detached, the app is still at its erawan.app address. The DNS records you delete yourself, at your registrar. Erawan cannot delete them for you, but it tells you which ones. Leave them in place and anyone who opens the domain gets a full-page certificate warning instead of your site.
Follow Erawan for new lessons and news.