Your customers should never touch DNS.
One embed for you, one button for them. We write the records and issue HTTPS.
Serving on the edge. Your customer never opened a DNS panel.
Your customers fail at the finish line.
A CNAME and a registrar login is where setup dies.
The usual path
With CustomDomain™
Try it on a domain you own.
Type a domain. We read its real DNS, find the provider, and show the flow your customer would see.
Reads public DNS only. Nothing is written to your DNS.
Five steps. One API call starts them.
- 01
Detect the provider
We read public DNS and pick the right path.
- 02
Write the records
OAuth, a scoped token or a guided step.
- 03
Verify ownership
Proven before go live, watched until it resolves.
- 04
Serve on the edge
The certificate is ready before the first request.
- 05
Watch every hour
Drift and renewals handled before you notice.
- Provider detectedcloudflare
- Records writtenA · CNAME · TXT
- Ownership verified_acme
- Certificate issuedHTTPS
- Watching for driftevery hour
Everything a custom domain feature needs.
Provider detection
We find the host and choose the safest path.
Automatic DNS records
A, CNAME, TXT, MX, SPF and DKIM, right the first time.
Automatic SSL
Issued before the first request, renewed ahead of expiry.
Optional edge
Serve from our edge, or hand DNS back to your stack.
Drift monitoring
Hourly checks. We fix and flag changes.
Built for developers
REST API, SDKs, widget, MCP server and webhooks.
Built for how your customers show up.
One API call. Or one line of embed.
Start from your backend, drop in the widget, or let an agent do it over MCP.
# kick off a connection from your server curl https://api.customdomain.ai/v1/connections \ -H "Authorization: Bearer $KEY" \ -d '{"domain":"everjust.co"}' # ← we detect, authorize, write & verify { "id": "con_8kQ2f7", "domain": "everjust.co", "provider": "cloudflare", "method": "oauth", "status": "live", "https": true }
Every provider your customers already use.
Not listed? Your customer gets the exact records and we watch until they resolve. All providers →
Straight answers.
What if a provider can’t be automated?
We fall back to a scoped token or a guided step with the exact records, and watch until they resolve.
What about apex domains, www and wildcards?
All three are written and served, as one connection or many. Apex vs CNAME
Are you in my request path?
Only if you want us to be. Use our edge, or verify and hand DNS back to your own stack.
Can AI agents connect domains?
Yes. The MCP server searches and connects domains with the same verification as any human path. MCP server
Give every customer a real domain.
From $10 a month. 14 day free trial.
DNS notes for SaaS builders.
Two emails a month.