How to connect a custom domain to an AI-built app | Ample

The short version

First deploy the app and keep its deployment ID. Add the custom domain to that deployment, create one of the DNS records Ample returns, then verify the domain. Verification activates routing and provisions TLS after the required DNS record is visible.

WHO THIS IS FOR

Before you start

This guide is for builders who already have a live Ample app and want it to use their own domain.

STEP BY STEP

How to do it

1. 1

Find the live deployment ID

Use the deployment_id returned by the successful deploy. A domain attaches to a specific deployment.

2. 2

Add the domain

The response includes accepted DNS records and the target host or address for your domain.

ample domain add <deployment_id> app.example.com

3. 3

Create the DNS record

At your DNS provider, create one record from accepted_records. Subdomains normally use CNAME. Apex domains receive an accepted A record because DNS does not permit a standard CNAME at the apex.

4. 4

Verify and activate

After DNS has propagated, ask Ample to verify the record and activate the route.

ample domain verify app.example.com

5. 5

Test HTTPS

Open the custom domain over HTTPS and test a real app path. Keep the generated Ample URL as a useful diagnostic route.

FIT CHECK

What this supports

Good fit

• Subdomains through accepted CNAME records
• Apex domains through accepted A records
• TLS provisioning after verification
• Custom routes to public web deployments

Know the limits

• The app must have a live deployment before the domain can be attached
• DNS propagation time is controlled by your DNS provider and prior TTL
• Only records returned in accepted_records should be used

TROUBLESHOOTING

Common failure modes

Verification says the record is missing

Compare the DNS record with accepted_records, wait for propagation, and verify again.

The apex domain was configured as a CNAME

Use the accepted A record returned for the apex domain.

The domain reaches an old release

Confirm the domain is attached to the intended live deployment and inspect the domain list for that deployment.