Custom Domains for Form Builders

Why custom domains matter for form builders

Form submission rates are higher when the form lives on the customer's domain. People trust acme.com more than typeform.com/to/xyz. It also keeps GDPR cookie banners and tracking domains consistent with the rest of the site.

What your users get

• Forms hosted at the customer's domain
• Pixels, retargeting, and tracking all on one domain
• Custom domain on every plan if you want it

How it works in 3 steps

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