Put your app on your own domain

What you need first

You need a domain you already own. We do not sell them.

• A domain bought from a registrar, in your name.
• The login for wherever that domain's DNS is managed.
• Your app published, or ready to publish.

01 · Add the domain in your project

Open the domain screen in your project and type the address exactly as you want visitors to see it. You get two values back: a CNAME target and a TXT verification token. Up to 20 domains per project.

02 · Add both records at your registrar

The CNAME points your address at us. The TXT record proves the domain is yours — it goes on a verification host underneath your domain, not on the root. Both must be right; one alone is not enough.

03 · Wait for the check

DNS changes spread at their own pace, usually minutes but sometimes hours. The domain is rechecked every six hours until both records are seen. The screen shows which of the two is still missing.

04 · Let the certificate be issued

The HTTPS certificate is only requested once the domain is confirmed as yours. This ordering matters: issuing a certificate for a domain nobody has proved they own is how other people's addresses get hijacked.

05 · Open it in a browser

Type your address without any prefix. You should see your app with a padlock. Try it on a phone connected to mobile data too — that uses a different DNS resolver and catches records that only look right from your desk.

If you get stuck

It still shows the old site. Old DNS answers are cached, by your computer and by everything between you and us. Wait, then try in a private window or from a phone on mobile data.

The check says the TXT record is missing. Most registrars add your domain to whatever you type in the host field. If you paste the whole verification host you can end up with it written twice. Check the record as it is actually stored.

Can I use a subdomain instead? Yes, and it is often easier. A subdomain leaves your main site untouched, which matters if you already have one running.