Getting Started
Connect a custom domain
Point your own domain at your application and get automatic TLS.
Audience
Builders
Time
15 min + DNS propagation
Requires
Access to your DNS
After provisioning and routing are ready, connect your own domain using the DNS values shown by the console. Wait for domain verification and certificate readiness before inviting customers. A saved hostname is not proof that HTTPS is ready.
Add the domain
- In the app's settings, open Domains and add the hostname you want (for example
app.yourcompany.com). - The console shows you a DNS record to create at your DNS provider — copy it exactly.
- Create the record, then return and click Verify. Verification usually completes within minutes, but DNS changes can take up to 24–48 hours to propagate depending on your provider.
Common problems
| Symptom | Likely cause | Fix |
|---|---|---|
| Verification never completes | Record created at the wrong host, or a conflicting existing record | Check for typos in the host name; remove any old A/CNAME records on the same host |
| Certificate warning in the browser | DNS still propagating | Wait for propagation to finish; certificates issue automatically once verification passes |
| Domain works but shows another site | DNS points somewhere else (old hosting) | Confirm the record target matches what the console shows exactly |
Each customer-facing app can carry multiple hostnames, so staging and production addresses can coexist on one app.
Capability review: 2026-10-22. See current features and setup requirements, the generated API Map and first-class module inventory.
Did this page answer your question?Tell us what’s missing