cnames.dev / for / course and community platforms
Custom domains for course & community platforms
Let creators host their course or community on a custom domain with automatic SSL and per-tenant isolation.
The problem
Paid courses and membership communities are brand-sensitive: creators want their space on their own domain, and members expect HTTPS and a professional feel. Delivering that per creator means certificates, routing, and isolation so creators never interfere with each other.
How it plugs in
Map each creator's space to an origin and register their domain with one API call. Per-tenant isolation keeps each creator's certificate lifecycle independent.
await fetch("https://api.cnames.dev/v1/domains", {
method: "POST",
headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
body: JSON.stringify({ domain: "learn.creator.com", origin_id: "org_creator_42" }),
});Why it fits
- Per-tenant isolation — creators can't affect each other's domains or issuance.
- Wildcards for creators who want multiple community subdomains.
- Automatic SSL and renewal, so a lapsed cert never embarrasses a paid community.
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
Why do creators want a custom domain for a course or community?
It builds trust and keeps the experience on their brand rather than a shared platform subdomain — important for paid courses and membership communities.
Can I isolate one creator from another?
Yes. Per-tenant isolation means each creator has their own origin mapping, quotas, and certificate lifecycle; one creator's activity can't affect another's issuance.
What about a creator with many community subdomains?
Use a wildcard zone so a creator can spin up *.community.creator.com under a single certificate.