Use your own domain

Put your app on mydomain.com instead of the address we hand out. One DNS record at your registrar, and HTTPS is set up for you.

Every app gets a free address like spring-launch-8f2a.customer.agenthost.eu. It works, it has HTTPS, and it's fine for a test. For anything you'd send to a client or a customer, use your own.

There are two ways to do that:

One app, one hostname — put a single app on app.mydomain.com. You add one DNS record for it. That's the rest of this guide.
A whole domain, many subdomains — connect mydomain.com once, add a single wildcard record, and then spin up blog.mydomain.com, shop.mydomain.com, docs.mydomain.com… as many as you like, with no further DNS. That's the next section.

Connect a whole domain for subdomains

Best when you'll host several things under one domain and don't want to touch DNS every time.

connect mydomain.com so we can host apps on subdomains of it

Your agent connects the domain and hands you one record to add:

One wildcard covers every subdomain

Type:  CNAME
Name:  *.mydomain.com      (many registrars want just "*")
Value: ingress.agenthost.eu

Add that at your registrar once. From then on, ask for apps by subdomain and they just work:

deploy this at blog.mydomain.com

No new DNS record, and each subdomain gets its own HTTPS certificate automatically. If you don't name a subdomain, agenthost picks one from the app's name.

Connect the domain

connect mydomain.com

Your agent registers it and returns the wildcard record. A domain can only be connected to one agenthost account.

Add the one wildcard record

At your registrar, add the *.mydomain.com record your agent gave you. Some registrars accept a wildcard A record to an IP instead of a CNAME; either works.

Verify it

is mydomain.com pointed at agenthost yet?

Your agent runs a live DNS check and marks the domain verified once the wildcard resolves to us.

Create apps on subdomains

put this online at shop.mydomain.com

No per-app DNS, HTTPS issued automatically. Repeat for as many subdomains as you want.

One wildcard, one destination

The wildcard points every subdomain at agenthost, so keep it reserved for apps you host here. If you already serve something else on a subdomain of this domain, add its record before the wildcard — a specific record wins over *.

Ask for it when the app is created

put this online at app.mydomain.com

Say it up front

An app's address is fixed when it's created — there is no tool for moving an existing app to a new hostname. If your app is already live on an agenthost address and you want your own, your agent deploys it again as a new app on the new address and deletes the old one. Nothing is lost; it's just two steps instead of none.

Add the DNS record

Your agent hands you the exact record to add. It looks like this:

For a subdomain — app.mydomain.com

Type:  CNAME
Name:  app
Value: ingress.agenthost.eu

For a root domain — mydomain.com

Type:  A
Name:  @
Value: 203.0.113.10

You add that at whoever you bought the domain from — Cloudflare, Namecheap, GoDaddy, One.com, your registrar's DNS page. agenthost cannot do this part for you: it's your domain, and only you can change its records.

Open your domain's DNS settings

At your registrar, usually under "DNS", "DNS records" or "Advanced DNS".

Add the record your agent gave you

Many registrars want only the sub-part in the Name field — app, not app.mydomain.com — and add the rest for you. If it complains, try the short form.

Wait for it to take effect

Usually a few minutes; occasionally up to a day. Your agent can check whether it has resolved yet.

HTTPS appears on its own

Once DNS points at us, a certificate is issued automatically and https://app.mydomain.com starts working. You never touch a certificate, and there is nothing to renew.

Root domain or subdomain?

A subdomain (app.mydomain.com, www.mydomain.com) is the easy case: a CNAME survives us changing infrastructure underneath you.

A root domain (mydomain.com, no prefix) can't be a CNAME — that's a DNS rule, not our choice — so it takes an A record pointing at an IP address. Some registrars offer ALIAS or ANAME records that work like a CNAME at the root; if yours does, either is fine.

Check it

is app.mydomain.com live yet?

Your agent can fetch the app and re-read the DNS instructions at any time — the record it needs stays attached to the app, so you can ask again days later without losing it.

Common snags

What you see	Usually means
Browser can't find the site	DNS hasn't propagated yet, or the record has a typo. Wait, then re-check the Name field
It loads someone else's site or a parking page	An old A/CNAME record for the same name is still there — remove it
HTTPS warning, or the padlock is missing	The certificate is issued after DNS resolves; give it a few minutes more
Works with `www`, not without (or vice versa)	Those are two different names. Add a record for each, or a redirect at your registrar
Cloudflare users: a redirect loop	Set SSL/TLS mode to Full (strict), not Flexible

Under the hood

The DNS target is per-server: each host in the fleet has its own IP and ingress hostname, so the record your agent gives you is the one for the machine your app actually landed on. Don't copy a record from another app. get_app re-derives the current instructions for a custom-domain app on every read, so the values stay right even if the app moves.

Certificates are issued and renewed automatically once the hostname resolves to us.

On this page