Custom domains

Serve your app from a domain you own — app.yourcompany.com instead of my-app-3f7e2a1c.agentry.live. You add a few DNS records, agentry provisions the HTTPS certificate for you, and the custom domain rides on top of your existing deployment.

Before you start

• You need a running deployment. Custom domains attach to a live app, not to a sandbox or a saved image. Deploy first; add the domain after.
• You need access to your domain's DNS settings (at your registrar — Namecheap, Cloudflare, GoDaddy, Route 53, etc.).
• Use a subdomain like app.yourcompany.com or www.yourcompany.com. A bare/apex domain (yourcompany.com with nothing in front) can't be pointed at agentry with the standard records below — see Apex domains.

Add the domain

1. Open the deployment in the dashboard.
2. Find the Custom domains panel and enter your hostname, e.g. app.yourcompany.com.
3. agentry shows you a small set of DNS records to create — typically:
   • one CNAME that points your hostname at agentry's edge, and
   • one or two TXT records that prove you own the domain and let us issue the certificate.
4. Copy those records exactly into your DNS provider.
5. Back in the dashboard, the domain sits at pending while it waits for DNS to propagate and the certificate to be issued.

Copy the record names exactly

Some registrars automatically append your domain to record names. If the dashboard asks for a record named _acme-challenge.app and your registrar shows the full name as _acme-challenge.app.yourcompany.com, that's correct — but if it ends up as _acme-challenge.app.yourcompany.com.yourcompany.com, the validation will never pass. When in doubt, check what the full record resolves to.

Wait for active

Once the records are in place, agentry handles the rest automatically:

• It confirms the records, validates ownership, and provisions a TLS certificate for your hostname.
• The domain flips from pending to active.
• Traffic to https://app.yourcompany.com now serves your deployment.

This usually takes a few minutes but can take longer depending on how fast your DNS provider propagates changes. The dashboard polls in the background — you don't need to do anything but wait and refresh.

If it's stuck on pending for a long time, it's almost always a DNS record that doesn't match what the dashboard asked for. Re-check names and values character-for-character.

What you get

• Automatic HTTPS. The certificate is issued and renewed for you. Nothing to install or rotate.
• A stable domain. It keeps working across every redeploy and rollback — the custom domain is attached to the deployment, not to a specific image.
• The original URL still works too. Your *.agentry.live URL keeps serving in parallel.

Apex domains

A bare apex domain (yourcompany.com, no subdomain) generally can't use a CNAME, which is what agentry's setup relies on. Options:

• Use a subdomain (recommended) — app.yourcompany.com or www.yourcompany.com. Simplest, always works.
• Redirect the apex — at your registrar or DNS host, set up a redirect from yourcompany.com to your www subdomain, and attach the custom domain to the www host.

Removing a domain

In the deployment's Custom domains panel, remove the entry. agentry tears down the certificate and routing on its side. You can then delete the DNS records at your registrar. Removing a custom domain never affects the underlying *.agentry.live URL.

Next

• Ship an app — get a deployment running first.
• Images & rollbacks — your domain follows the deployment through every update.
• Authentication — put a login screen on your custom-domain app.