Custom domains

Custom domains let a published project use your own domain instead of only a managed publish URL.

Use custom domains when the project is ready to be shared with users, customers, or a client audience.

What custom domains are for

Use a custom domain for:

• A company website.
• A product landing page.
• A client campaign.
• A public MVP.
• A published team tool behind the right access controls.

Before connecting a domain

Confirm:

• The project is ready to publish.
• You control the domain's DNS settings.
• The domain is not already used by another project.
• The project owner or admin approves the connection.
• You understand any plan limits around custom domains.

Typical setup flow

The product may ask you to:

1. Add a domain to the project.
2. Create DNS records at your domain provider.
3. Verify the domain.
4. Wait for DNS propagation.
5. Confirm the published project loads correctly.

The exact records are shown in the product UI when the feature is available.

Common issues

• DNS changes can take time.
• Records may be added to the wrong domain.
• Another service may already use the same host.
• The project may not be published yet.

Safety checklist

• Test the managed publish URL first.
• Verify DNS records carefully.
• Confirm HTTPS works.
• Test the domain on desktop and mobile.
• Keep old DNS settings until you understand the impact.

FAQ

Can I use any domain?

You need control of the domain or subdomain DNS settings. Some reserved or already-used domains may not be available.

How long does verification take?

DNS propagation can be fast or slow depending on your provider. Follow the product verification status.

Do I need to publish first?

Yes. A domain should point to a project that has a valid published output.

Next steps

• Publish first: Publish your project
• Review project access: Project access
• Contact support if stuck: Support policy