Custom Domains for Membership Sites

Why custom domains matter for membership and community platforms

Members are paying to belong to the creator's community, not yours. members.acme.com signals "this is theirs." It also makes the creator's email open rates higher and gives them control if they ever switch platforms (which makes them less likely to actually switch).

What your users get

• Community lives at the creator's domain
• Email and login flows match the creator's brand
• No "powered by" subdomain visible to members

How it works in 3 steps

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