Skip to Content

THE CUSTOM-DOMAIN LAYER FOR CREATOR TOOLS

Put the creator’s name on the door.

Creators upgrade to own their name, not to learn DNS. They type jordan.com inside your product, and their link-in-bio, portfolio, or newsletter is live on it about 30 seconds later. No CNAME to paste, no support thread, no “ask your web person.”

Built for link-in-bio, portfolios, newsletters, and courses. 25+ registrars auto-configured.

See how it works

Your brand · connect domain

Use your own domain

jordan.com
Make it mine
✓ Namecheap detected ✓ Records written · ownership verified Issuing certificate…
The whole flow, in your brand. The creator never sees a DNS panel.
25+ registrars, auto-configured · Ownership verified before go-live · HTTPS issued in the TLS handshake · Upgrade fulfilled by webhook

The problem, for you

Creators quit at the last step.

The person upgrading is a photographer, a coach, a writer. Someone who has never opened a DNS panel and never will. They hit “add a CNAME record pointing to…,” and they stop. The upgrade they already paid for sits unfulfilled.

Manual DNS setup is where the paid upgrade stalls. That is the step this removes.

0

DNS records the creator ever touches. The alternative is a paid upgrade that stalls at “add a CNAME record,” then a refund request a week later.

A creator’s whole reason to pay you is to stop renting a subdomain and own their name. Handing them a CNAME to paste is asking them to do the one thing they paid you to handle. You cannot document your way out of that. You remove the step.

Why custom domains are hard → Coverage: 25+ DNS providers auto-configured.

How it works for you

Type a domain, done. No DNS in sight.

  1. 01

    The creator types their domain, inside your product, under your brand. That is the entire ask on their side. A domain, in a text box.

  2. 02

    We take the DNS off their plate. We detect the registrar, including the budget ones creators actually use, and write the records via provider sign-in, provider-hosted one-click setup, or a guided path.

  3. 03

    Ownership verifies, HTTPS issues. The certificate is issued in the TLS handshake, apex and www covered, so their page looks professional the instant it is live.

  4. 04

    A webhook flips their upgrade flag. The moment the domain is serving, your app marks the upgrade fulfilled automatically. The creator just sees their name go live.

See the full path →
records · jordan.com
TYPE
NAME
VALUE
TTL
CNAME www.jordan.com edge.customdomain.ai 3600 A jordan.com 203.0.113.10 300 TXT _cd.jordan.com cd-verify=… 3600
pending_ownership verifying live

The records the creator would have had to paste, written for them. You get a state change on a webhook, not a support ticket.

Whatever the creator is upgrading

Their name, wherever their work lives.

LINK jordan.com

Link-in-bio

The whole point of the paid tier is the clean URL in their bio. They type it, you serve it, no jordan.yourapp.com in the way.

SITE studio.jordan.com

Portfolios

A photographer’s book has to read as their studio, not your platform. Apex or subdomain, HTTPS-green from the first load.

MAIL news.jordan.com

Newsletters

Subscribe pages and archives on the writer’s own domain build the list under their brand, not a shared one. Deliverability records handled in the same flow.

HOME learn.jordan.com

Courses

A course sold on the creator’s own domain converts better and looks like a real product. Checkout and content stay on your platform, under their name.

Drop-in widget

Skip building the DNS UI.

Drop one line into your upgrade flow and the creator gets the entire connect experience, detection, one-click setup, and live status, in a polished modal in your brand. No DNS screens for you to design, and no records for a creator to get wrong.

embed
// npm i customdomain-js customdomain.open({ app: "3f2c…" })

~90 white-label tokens. Your colors, your copy, 13 locales.

Widget & SDK docs →

The registrars creators actually use

GoDaddy logo GoDaddy
Namecheap logo Namecheap
Squarespace logo Squarespace
Porkbun logo Porkbun
Cloudflare logo Cloudflare
Name.com logo Name.com
Hover logo Hover
Dynadot logo Dynadot
Gandi logo Gandi

25+ registrars auto-configured, including the budget ones where creators buy their names. Where one can’t be automated, the creator gets a one-click check, never a paste-the-CNAME task.

After it is live

Nothing breaks on their site.

Verified before go-live

A creator can only connect a domain they control. Ownership is proven before any page serves under their name.

Certificates that renew themselves

HTTPS renews at the edge without touching their DNS again, and fails closed. Nothing expires on a creator’s site.

Drift caught hourly

A broken connection surfaces to you on a webhook before it embarrasses the creator, not after they email you.

Read our security model →

Questions

The short version.

Do my creators ever see a DNS panel?

No. The creator types a domain and approves, and we write the records. Even the guided fallback is a one-click check, never a paste-the-CNAME task.

Can I keep it fully under my brand?

Yes. The connect flow renders inside your product under your name, with ~90 white-label tokens. The creator’s whole experience is with you.

How do I know a creator’s domain went live?

A webhook fires the moment it is serving. Your app flips the upgrade flag automatically, so the creator just sees their name appear.

What if the creator uses a budget registrar?

Those are the ones we optimized for. 25+ registrars are auto-configured, including the cheap ones creators actually buy names at, so the flow works whether they are on Cloudflare or Porkbun.

Let creators own their name.

Create an account, drop the connect flow into your upgrade, and watch a creator’s domain go live.