cnames.dev / for / landing page builders

Custom domains for landing page builders

Publish customer landing pages on their own domains with automatic SSL and edge routing — one API call per domain.

The problem

Conversion-focused customers want their landing pages on their own domain for trust and tracking, with HTTPS from the first visit. For a landing-page builder, that means issuing and renewing a certificate per customer domain and routing it to the right page — repeatedly, reliably.

How it plugs in

Preview on an instant subdomain, publish on the customer's domain. Both are the same origin and the same API; the certificate is automatic.

await fetch("https://api.cnames.dev/v1/domains", {
  method: "POST",
  headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
  body: JSON.stringify({ domain: "promo.customer.com", origin_id: "org_pages" }),
});

Why it fits

Sits in front of your existing hosting — no migration.
Automatic SSL, issued on first request and auto-renewed.
Wildcard previews plus per-customer live domains.
Embeddable Connect widget so customers self-serve the DNS step.

Add it this afternoon. Register your first customer domain with one API call — free for 25 domains. Start free · Docs · More use cases

Frequently asked questions

How fast can a customer publish on their domain?

As soon as DNS resolves to the edge, the certificate issues on the first request — typically minutes after they set the record. The Connect widget polls and shows live status.

Can I preview pages on a subdomain first?

Yes. Serve previews on an instant wildcard subdomain (*.preview.yourapp.com), then attach the customer's domain for the live version.

Does it work in front of my existing hosting?

Yes. cnames.dev proxies to whatever origin already serves your pages — no need to move hosting.