Embedded setup flow
Drop the web component into your app so customers can bind a hostname without leaving your product.
Embed a setup flow, create domains through API or dashboard, and keep DNS, SSL, webhook, and monitoring states visible from day one.
docs -> customers.customdomainkit.test_acme-challenge.docs TXT pendingdomain.status_changed queuedEverything a SaaS team needs to expose customer-domain setup without making DNS support a side project.
Drop the web component into your app so customers can bind a hostname without leaving your product.
Create applications, issue setup sessions, inspect domains, and rotate secrets from one control plane.
Keep hostname ownership, certificate validation, and live CNAME checks separate instead of guessing from one status.
Notify your SaaS when domain state changes, then keep checking for DNS drift after launch.
Keep your SaaS responsible for the product experience while CustomDomainKit handles the domain control plane.
Use the dashboard or API to create a customer hostname and receive the setup session payload.
The embedded component gives the customer the CNAME and validation records they need to add.
CustomDomainKit checks Cloudflare for SaaS, live DNS, SSL, and webhook delivery until the domain is active.
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.
Plans map to domain volume so teams can validate the integration before scaling customer onboarding.
3 domains for local validation and trial integrations.
50 domains for early SaaS teams shipping customer domains.
300 domains for growing products with real operational needs.
2000 domains with room for larger customer bases.