Skip to Content

About

We built this four times before. Never again.

We built this feature four times at four different companies and swore, each time, never again, the DNS writer, the certificate renewal job, the support queue full of "my domain doesn't work". So we built it once, properly, and made it the product.

It runs fully managed for you: integrate one API, let your customers type a domain, and watch it come up live with HTTPS across 63 DNS providers. That's the whole promise, and it's the only thing we work on.

That history shows up in the details. One call starts a connection, every state change arrives over a webhook, and the edge fails closed rather than serve someone else's certificate. Boring, in the way infrastructure should be.

CustomDomain™ is a managed service that lets your customers use their own domain with your product. A customer types a domain, and CustomDomain™ detects their DNS provider, writes the records, verifies ownership and issues HTTPS, with an edge that serves the traffic. You connect to it through a REST API and webhooks, an embeddable widget and SDK, or a hosted MCP server.

It serves teams whose users publish under their own name: site builders, e-commerce platforms, creator tools, agencies that resell a platform under their own brand, and AI agents that connect a domain as one step in a longer task.

Every domain goes through three phases: detect the DNS provider and write the records, verify ownership, then go live with HTTPS. How it works walks through each phase, pricing lists the plans, and the documentation covers the API, widget and webhooks.

How we treat your customers' DNS

01We never see registrar passwords, no flow in the product asks for one.

02Provider tokens are used once, then never stored.

03Certificates fail closed, an unapproved hostname gets nothing.

Get started →