cnames.dev / for / agencies
Custom domains for agencies
Host client sites under each client's own domain, with automatic SSL, wildcards, and a dashboard your team can operate.
The problem
Agencies host sites for many clients, each on the client's own domain, and each expecting HTTPS. Managing certificates and routing across dozens of client domains — plus renewals — is recurring operational overhead that doesn't bill.
How it plugs in
Each client site is an origin; each client domain is one API call or a few clicks in the dashboard. Your team manages it without deploys, and certificates renew themselves.
await fetch("https://api.cnames.dev/v1/domains", {
method: "POST",
headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
body: JSON.stringify({ domain: "www.client.com", origin_id: "org_client_acme" }),
});Why it fits
- A dashboard your account team can operate — add domains, check status, fix issues.
- Automatic SSL and renewal across every client domain.
- Wildcards for clients with many subdomains.
- Predictable ~$0.05/domain cost you can fold into retainers.
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
Can I host many client sites under each client's own domain?
Yes. Register each client domain via the API, map it to the origin serving that client's site, and SSL is automatic. Wildcards cover clients with many subdomains.
Can my team manage domains without touching code?
Yes. The dashboard lets your team add domains, see verification and certificate status, and troubleshoot — no deploy required.
Is the per-domain cost workable for an agency?
At ~$0.05/domain on Pro (free for the first 25), hosting dozens of client domains is a small, predictable line item you can roll into retainers.