cnames.dev / for / ai app builders
Custom domains for ai app builders
Give every generated app its own domain — instant subdomains via wildcard, custom domains via one API call, and an MCP server for agent-native flows.
The problem
Vibe-coding platforms, site generators, and agent products spin up user apps constantly — and users immediately want them on a real domain, not a shared path. But most generated apps live on free plans, so the custom-domain layer has to be cheap per domain, instant, and fully automated. Sales-led suites that start at hundreds of dollars a month don't fit a product where 90% of apps may never pay.
How it plugs in
Two moves cover the whole journey. Give every new app an instant subdomain under a wildcard zone, then let users attach their own domain when they upgrade — both through one API.
// 1) Instant subdomain for a new generated app (wildcard zone: *.apps.yourplatform.app)
// No per-app cert needed — the wildcard cert already covers it.
// 2) User brings their own domain:
await fetch("https://api.cnames.dev/v1/domains", {
method: "POST",
headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
body: JSON.stringify({ domain: "myapp.founder.com", origin_id: "org_123" }),
});
// → returns the DNS record to set; SSL issues automatically on first request.Agent-native: the MCP angle
If your product publishes apps from a chat interface, domains can be provisioned by the agent itself. The cnames.dev MCP server exposes add-domain, check-status, and list-domains as tools, so "publish this to myapp.com" becomes a tool call inside the conversation — no context switch to a settings screen.
Pricing at your scale
Free for the first 25 domains, then $49/mo for up to 1,000 (~$0.05/domain). Because most generated apps sit on free tiers, per-domain cost is what matters — and this is priced for it, versus suites that begin in the hundreds per month regardless of how many domains convert.
Why builders pick cnames.dev
- One API call (or one MCP tool call) per domain — no infrastructure to run.
- Wildcard zones for instant per-app subdomains under one cert.
- Per-tenant isolation so one user's bulk activity can't stall issuance for others.
- Transparent, per-domain pricing that survives a free-heavy user base.
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 add custom domains from an AI agent or chat flow?
Yes. The API is a single call to register a domain, and there is an MCP server so an agent (Claude, Cursor, etc.) can provision and check domains as a tool — ideal for products that publish user apps from a chat interface.
How do generated apps each get their own subdomain instantly?
Use a wildcard zone (*.yourplatform.app) for instant per-app subdomains under a single certificate, then let users upgrade to their own custom domain when they are ready — both through the same API.
What does it cost at the scale of a busy AI builder?
Free for the first 25 domains, then $49/mo for up to 1,000 (~$0.05/domain). That is far below sales-led suites that start in the hundreds per month, which matters when most generated apps are on a free plan.
Do I need to run any infrastructure?
No. cnames.dev terminates TLS and proxies to your origin. You call the API; certificates issue and renew automatically.