Custom Domains for White-Label SaaS

Why custom domains matter for white-label SaaS platforms

When you're white-label, every customer touchpoint that says "yourapp.com" leaks your brand into theirs. The fix is letting them point app.acme.com at your origin and serving the entire experience from THEIR domain. That's what Domainee does in one API call.

What your users get

• Their portal lives at their own domain, not yours
• Automatic SSL, no manual cert work
• DNS verification handled by us, status pushed over webhooks

How it works in 3 steps

1. Your user types their hostname (app.acme.com) into your UI.
2. your white-label SaaS POSTs to the Domainee API to register it and gets back the CNAME the user needs to add at their DNS provider.
3. We monitor DNS, issue the cert via Let's Encrypt, and webhook back when it's live. Usually about 60 seconds.

The code

curl -X POST https://api.domainee.dev/v1/domains \
  -H "Authorization: Bearer $DOMAINEE_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "hostname": "app.acme.com",
    "originUrl": "https://app.your-saas.com",
    "mode": "proxy",
    "redirectWww": true,
    "metadata": { "workspaceId": "your-internal-id" }
  }'

The response includes a dnsRecords array (usually one CNAME). Show that to your user, tell them to paste it at their DNS provider, and we'll handle the rest.

For the full walkthrough, see How to let users connect a custom domain to your SaaS.

This is the exact setup Common Ninja, Embeddable, and Vidocu use internally. Same edge, same API, same cert pipeline.

Pricing

Your first 50 customer hostnames and 100 GB of bandwidth every month are free. After that: $0.20 per domain (graduated to $0.10 at scale), $0.05/GB above 400 GB. No monthly minimum, no contract, no sales call.