Custom Domains for Online Store Builders

Why custom domains matter for e-commerce platforms

Shoppers trust shop.acme.com more than acme.yourplatform.com, and SEO rewards the merchant's own domain. Most builders cap custom domains behind a paid plan because the infrastructure is painful. Domainee removes the infrastructure, so you can include it on every plan if you want.

What your users get

• Stores live at the merchant's own domain
• TLS auto-issued and renewed forever
• One CNAME for the merchant to add, no second SSL record

How it works in 3 steps

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