Support custom domains
for your users in minutes.
Connect your users' custom domains to your product with one simple API. Automatic SSL, automatic renewals, handled for you for life.
50 custom domains and 100 GB bandwidth, free forever.
Trusted by teams building the future of SaaS
How it works
Add custom domains to your product in three steps. No infra to build, no card to start.
01
Get your API key
Sign up and get your API key. 50 domains free, forever.
02
One API call
POST /v1/domains with the hostname and your origin. We return a CNAME.
03
SSL + renewal forever
Customer adds the CNAME. SSL, renewal, and DNS monitoring run forever.
Who builds with Domainee?
If your product touches multi-tenant URLs or your users keep asking when you'll support their domain, you're in the right place.
Engineering teams at scaleups
Between 50 and 5,000 customer hostnames is exactly where building it yourself costs more than buying. We replace 2–4 months of v1 and an ongoing chunk of someone's calendar.
Learn more
Engineering teams at scaleups
Between 50 and 5,000 customer hostnames is exactly where building it yourself costs more than buying. We replace 2–4 months of v1 and an ongoing chunk of someone's calendar.
Learn moreIndie hackers & solo founders
Stop dreading custom-domain requests. Ship the feature on a Tuesday afternoon with no card on file, and revisit billing only when the free tier is no longer enough.
Learn more
Agencies & platform builders
Multiple client SaaS, each with their own custom-domain story. One Domainee workspace per client, one set of API keys, one webhook handler you reuse.
Learn more
Builders shipping with AI
You're writing the app in Cursor or Claude Code anyway. Point your agent at our MCP server and let it provision domains, debug DNS, and walk customers through setup.
Learn more
Two ways your users get a custom domain.
Bring-your-own and buy-in-app, behind the same workspace, the same billing, the same API key. Most SaaS teams start with connect, add buy later when they realize their users would rather not log into a registrar.
Your user already owns a domain.
One API call returns a CNAME. Your customer adds it to their registrar. SSL provisions automatically, renews forever. Webhook fires on every DNS state change.
- Apex + subdomain support
- Let’s Encrypt + auto-renewal
- DNS health checks + drift webhook
- 50 hostnames free, forever
Endpoint
POST /v1/domains
Returns cname status webhook_url
Your customer never needs a registrar account. One CNAME record, then Domainee handles SSL issuance, renewal, and health monitoring for life.
Your user needs to buy a domain.
We register, charge their card through your Stripe account, and connect it to your app. Wholesale pricing, user is the legal registrant.
- 500+ TLDs
- Wholesale + $1 flat fee
- User is the legal registrant
- DNS + renewal endpoints included
Endpoint
POST /v1/domain-purchases
Returns domain registrant invoice_id
Most teams add this after launch, when users ask to buy a domain directly in-app rather than visiting a registrar.
One product.
Two front doors.
Same auth, same workspace, same Bearer token. Wire it into your backend or point your AI agent at it — both paths are first-class.
$ curl https://api.domainee.dev/v1/domains \
-H "Authorization: Bearer sk_live_…" \
-H "Idempotency-Key: order-123" \
-d '{
"hostname": "shop.acme.com",
"originUrl": "https://acme.fly.dev"
}'
// Response
{
"domain": {
"id": "8f09b47c-…",
"status": "pending",
"cname": "shop.acme.domainee.dev"
}
}
POST /v1/domains
Returns a CNAME your customer adds to their registrar. SSL provisions automatically.
- Webhook on DNS live
- Apex + subdomain
- Auto-renewal forever
- 50 hostnames free
Auth, rate limits, billing gates: same on both paths.
Why Domainee
Built differently,
by design.
Why we publish everything: the most expensive thing about buying infrastructure is the call you have to get on first.
A free tier with real headroom
50 domains and 100 GB of bandwidth a month, no card to start. Even after you cross the threshold, the free quota stays. Most teams run their whole pilot and early-paid phase before paying a cent.
MCP-native, not API-only
Same Bearer key drives a REST API and an MCP server. Claude, Cursor, Claude Code, or any MCP-aware agent can list, create, and verify domains in plain English. The only Custom Domains API your AI tooling can drive directly.
Published pricing, all the way up
$0.20/domain/month, graduated to $0.10 at 10,000+ domains. $0.05/GB after 400 GB included with paid. No contact-sales, no fair-use clauses, no enterprise-only tier. The curve is on the pricing page.
What you'd build instead.
Custom domains feel like a weekend feature until you actually ship them. Then it's ACME rate limits, edge TLS termination, SNI routing, DNS health checks, certificate rotation, and a Slack channel called #domains-on-fire.
We did the four months. We're still doing the ongoing care. You get the API.
- 2-4 months for v1
- One engineer on call for cert outages
- ACME rate-limit management forever
- Edge cert store + SNI router
- DNS monitoring + reverification
- Renewal cron that fails at 2am
- Live in an afternoon
- No card to start
- Webhooks tell you when DNS lands
- SSL + renewal handled forever
- MCP server for your AI tooling
- One CNAME for your customer
free
$0.20/domain/month after, with graduated discounts down to $0.10 (50% off) at 10,000+ domains.
See the full pricing breakdownfree
Every month. 400 GB included with any paid subscription, then $0.05/GB. Metered by the edge, billed monthly.
No card to start. Add a payment method only when you cross the free quota.
Frequently asked
The questions we hear most. If yours isn't here, the team answers within one business day.
How fast can I integrate Domainee compared to building it myself?
Building the custom-domain stack in-house is a 2-4 month project. Domainee takes an afternoon. We've already shipped ACME automation, edge TLS termination, SNI routing, DNS health checks, and the renewal cron that fails at 2am.
Do I need to set up Let's Encrypt or any registrar accounts?
No. We handle ACME challenges, certificate issuance, renewals, and all registrar plumbing. You make one API call per customer hostname and we do the rest.
Is Domainee white-label friendly?
Yes. Your customers see their own domain serving your app, with your branding. Domainee never appears in the URL, the SSL cert, or the customer-facing UI.
Will routing customer traffic through Domainee slow down their site?
No. Our Multi-Region edge terminates TLS close to the user — US users hit a US PoP, EU users hit an EU PoP, latency-routed automatically with target-health failover between regions. Most requests are sub-50ms TTFB. Static assets are cached at the edge.
Can AI agents use Domainee to manage custom domains?
Yes. Domainee ships an MCP server with 11 tools. Connect it to Claude Desktop, Cursor, Claude Code, or any MCP-compatible client and your agent can list, create, verify, and debug custom domains in natural language.
Does Domainee support both bring-your-own and buy-a-domain flows?
Yes. The Connect API is for users who already own a domain — one CNAME, SSL handled. The Buy a Domain API is for users who don't — 500+ TLDs, wholesale + $1 flat fee, your end-user is the legal registrant.
What happens when a customer's DNS isn't set up correctly?
We monitor DNS continuously and fire a webhook on every state change. The dashboard surfaces the exact issue ("CNAME points to wrong host," "DNS not resolving," "Cloudflare proxy enabled") so your support team can guide the customer.
Can Domainee handle thousands of customer domains?
Yes. Free tier covers your first 50 hostnames. Per-domain pricing graduates down to $0.10 at 10,000+ domains. No code change at any volume tier, no contact-sales gate.
Still have questions? Ask our team
Ship custom domains today.
Mint an API key, register your first hostname, send your customer a single CNAME. The first 50 are free.