Custom domains for website builders

The problem

A website builder's users expect to publish on their own domain, and they expect it to just work with HTTPS. Multiply that by thousands of sites and you're running a certificate authority integration, a proxy, apex/www handling, redirects, and renewals — infrastructure that has nothing to do with your editor or templates.

How it plugs in

Each published site maps to an origin; each customer domain is one API call. Give sites an instant subdomain under a wildcard zone, then let customers attach their own domain via the embeddable Connect widget (one-click on supported DNS providers, copy-the-records elsewhere).

await fetch("https://api.cnames.dev/v1/domains", {
  method: "POST",
  headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
  body: JSON.stringify({
    domain: "www.customer.com",
    origin_id: "org_sites",
    header_profile_id: "hp_www_to_root", // per-domain www↔root redirect
  }),
});

Dogfooded in production

This isn't theoretical: cnames.dev powers 5,000+ production customer sites at Lindo.ai. Apex handling, wildcard subdomains, www↔root redirects, and automatic renewal are the exact features that platform relies on daily.

Why builders pick cnames.dev

• White-label: served on the customer's domain, your brand behind it.
• Apex + www + redirects handled per domain, as data.
• Wildcards for instant subdomains; custom domains on upgrade.
• A dashboard your support team can use to see and fix domain status.

Frequently asked questions