Custom Domains for Auth Providers

Why custom domains matter for auth providers and identity platforms

Login pages are the most brand-sensitive surface in any product. When the URL bar says auth.yourplatform.com during sign-in, users hesitate; when it says auth.acme.com, they don't. For multi-tenant B2B providers, every tenant wants their own login on their own domain — and increasingly, a wildcard so each of THEIR customers can have one too.

What your users get

• Login pages on the customer's domain, not yours
• Wildcard support for multi-tenant B2B (one record, every subdomain)
• TLS issued and renewed forever, including wildcard certs

How it works in 3 steps

1. Your user types their hostname (auth.acme.com) into your UI.
2. your auth platform 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": "auth.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.

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.