Skip to Content
CUSTOM DOMAIN

Your users should never touch DNS for your product.

Custom Domain detects the provider, writes the records, verifies ownership, and issues HTTPS. Your customers never touch a DNS panel.

Create account Read docs See how it works

25+ DNS providers auto-configured

Connect your domain

Sign in to GoDaddy

Authorize Custom Domain
✓ DNS written, verified, and HTTPS issued, automatically.

See it in action

One click, and a domain goes live

Try it live

Type a domain. Watch us find it.

We detect the DNS host and read its live records, straight from public DNS.

A live lookup. No signup, nothing saved.

POST /v1/connections
# your side, one request curl https://api.customdomain.ai/v1/connections \ -H "Authorization: Bearer sk_live_…" \ -d '{ "hostname": "app.acme.com" }'
201 · response
{ "hostname": "app.acme.com", "provider": "godaddy", "state": "pending_ownership" } # then poll the connection, or listen for webhooks as it goes live

One call. Detection, records, verification, and HTTPS follow automatically. Read docs

The problem

Your customers fail at the finish line.

Your app knows exactly which records it needs. Their DNS host can write them. The only thing standing between the two is your customer, copying values between browser tabs, guessing at record types, hoping they got it right.

Manual DNS is the step where signups stall. It is the one you can remove.

Your product and their DNS host, joined by hand through your customer, the failure point YOUR PRODUCT knows the records YOUR CUSTOMER copies values by hand, the failure point THEIR DNS HOST can write them

0

DNS records your customers should ever touch. They already said yes; do not lose them at a setup screen.

They don’t quit because they don’t want your product. They quit because DNS is genuinely hard, and it’s the one step you handed them. You can’t document your way out of that. You remove the step.

Why custom domains are hard → Custom Domain writes and verifies the records for them.

How it works

Five steps. One API call to start them.

  1. 01

    Detect the provider. We fingerprint your customer's DNS host as they type, and pick the best connect path automatically.

  2. 02

    Write the records. Records go in through provider sign-in, provider-hosted one-click setup, a scoped token, or guided manual with a live check.

    API call · one POST starts everything Drop-in widget · the full flow in a modal Dashboard · connect domains with no code MCP for agents · same gates humans get
  3. 03

    Verify ownership. Proof of ownership comes before go-live, and propagation is watched until records resolve. No check back in 24 hours.

  4. 04

    Serve at the edge. Certificates issue before the first request, renew without touching DNS again, and fail closed. The control plane is never in your request path.

  5. 05

    Watch every hour. Re-checks catch DNS drift, webhooks fire the moment a record breaks and again when it is restored.

How it works, in depth →
example · the records we write
TYPE
NAME
VALUE
TTL
CNAME app.acme.com edge.customdomain.ai 3600 TXT _cd.acme.com cd-verify=… 3600 A acme.com 203.0.113.10 300
pending_ownership → verifying → live

The records, written for them, or handed over exactly, with a live check.

25+ providers auto-configured · one-click setup

Every provider your customers use

Cloudflare
Google Cloud DNS
Azure DNS
GoDaddy
Namecheap
DigitalOcean
Vercel
Netlify
IONOS
Linode
Vultr
Hetzner
Gandi
deSEC
DNSimple
Porkbun
Name.com
Squarespace
OVH
Scaleway
NS1
DNS Made Easy
Hover
Dynadot

Where a provider can’t be automated, the customer gets exact copy-paste records and a one-click check. Logos are the property of their respective owners and shown to describe interoperability.

Moving from another setup →

Objections, answered

Six questions, straight answers.

What if a provider cannot be automated?

Your customer gets the exact records to paste, and a live check watches until they resolve correctly. Guided manual is a real path, not a dead end.

What about apex domains, www, and wildcards?

All three are written and served. Apex, www, and wildcard records are supported, so customers can land on the bare domain or any subdomain.

What happens when a customer's DNS changes later?

Every connected domain is re-checked hourly. If a record drifts, a webhook fires the moment it breaks, and another fires when it is restored.

Are you in my request path?

No. The control plane writes DNS, verifies, and steps out. Your customer's traffic is served at the edge and never waits on our API.

What if a certificate fails to issue?

We fail closed. A broken certificate is never served, and issuance is retried automatically. Renewals at the edge work the same way.

Can AI agents connect domains?

Yes. A hosted MCP server lets agents search, buy, and connect domains, with the same verification gates humans get. Read the MCP docs.

Built for your platform

Wherever your users bring a domain.

Site builders

One click domains for every published site.

E-commerce platforms

Branded storefronts on the merchant’s own domain.

Creator tools

Give every creator a domain of their own.

Agencies and white-label

Connect client domains under your own brand.

AI agents

An MCP server lets agents connect domains.

Starter includes 10 domain connections a year.

Flat tiers with included volume. You always know what a domain costs before you connect it.

See pricing

Give every customer a real domain.

Fully managed. One API call to start. Live in minutes.

Create account Book Demo