Using your own web address

Not available yet. Your app runs on a platform address, and you can't point your own domain — yourcompany.com — at it today.

What you get instead#

Every app that serves a website gets a working, secure link automatically:

https://your-app-name.<platform-domain>

It's HTTPS already, with a valid certificate that renews itself. There's nothing to buy, configure, or remember to update.

You can choose the first part of that address rather than accepting the generated one, which is worth doing — a readable name is much nicer to share. Ask your developer, or set it yourself on the app's Ports panel. It has to be unique across the platform, so a distinctive name is more likely to be free.

What this means for you#

• Share the platform link. It's a normal link and works everywhere.
• A redirect from your own domain is possible if you already have one — your domain registrar or website host can usually forward visitors to another address. That isn't the same as the app being on your domain, and the platform link will show in the browser bar, but for many uses it's enough.
• Don't put the link in print if you might move later. Anything that's expensive to change is worth pointing at something you control.

If you specifically need your own domain#

Some things genuinely require it — a business site where the address is part of your identity, or anything where the address appears in email.

That last one is worth knowing: you can't send authenticated email from a platform address, because the checks that stop email going to spam rely on DNS records under a domain you own. If your app sends email to customers, it needs to send through an email provider using your own domain. Your developer will know what that means.

If your own web address is essential, tell your developer before they build — it affects where the app should live.

We'll update this page if custom domains become available.