CCustomDomainKitDashboard

Custom domains your SaaS can ship this week.

Embed a setup flow, create domains through API or dashboard, and keep DNS, SSL, webhook, and monitoring states visible from day one.

Built on
Cloudflare for SaaS
Best first fit
Subdomain CNAME onboarding
Runtime
OpenNext on Workers
Domain setupdocs.customer.example.com
Current statusWaiting on customer DNS
Checking
CNAME targetdocs -> customers.customdomainkit.test
Certificate validation_acme-challenge.docs TXT pending
Webhook deliverydomain.status_changed queued

What developers get

Everything a SaaS team needs to expose customer-domain setup without making DNS support a side project.

Embedded setup flow

Drop the web component into your app so customers can bind a hostname without leaving your product.

API and dashboard control

Create applications, issue setup sessions, inspect domains, and rotate secrets from one control plane.

DNS, SSL, and CNAME visibility

Keep hostname ownership, certificate validation, and live CNAME checks separate instead of guessing from one status.

Signed webhooks and monitoring

Notify your SaaS when domain state changes, then keep checking for DNS drift after launch.

A binding workflow your customers can understand

Keep your SaaS responsible for the product experience while CustomDomainKit handles the domain control plane.

  1. 1

    Create the domain

    Use the dashboard or API to create a customer hostname and receive the setup session payload.

  2. 2

    Show exact DNS instructions

    The embedded component gives the customer the CNAME and validation records they need to add.

  3. 3

    Verify and notify

    CustomDomainKit checks Cloudflare for SaaS, live DNS, SSL, and webhook delivery until the domain is active.

Built for honest operations

The homepage promise matches the product boundary: CustomDomainKit guides and verifies DNS setup, but it does not pretend to own the customer's registrar account.

Cloudflare custom hostname lifecycle and SSL activation tracking
Signed webhook delivery for domain status changes
No domain purchasing
No DNS-provider login
Optional trusted proxy mode for origins that cannot accept customer hostnames

Start small, keep the path to production visible

Plans map to domain volume so teams can validate the integration before scaling customer onboarding.

Development

$0/mo

3 domains for local validation and trial integrations.

Starter

$20/mo

50 domains for early SaaS teams shipping customer domains.

Professional

$100/mo

300 domains for growing products with real operational needs.

Enterprise

$500/mo

2000 domains with room for larger customer bases.