Skip to Content

Custom-domain onboarding, on flat, predictable tiers

July 10, 2026 by

Ask a founder what it costs to let customers bring their own domain and you will hear a number that only ever goes up. The closed, per-domain platforms make that math the whole business. You pay a floor of hundreds a month before a single customer has connected anything, and then a metered fee stacks on top of every domain after that. The pricing is designed to grow with your success in the most literal way: the better you do, the more the bill punishes you for it.

That is the per-domain tax. It is easy to miss when you are shopping, because the sticker price looks like a normal SaaS line item. It is hard to ignore two years later, when custom domains are a core feature and the invoice has quietly become one of your largest fixed costs.

What the per-domain tax really covers

Here is the uncomfortable part. Most of what you are paying for is not compute. It is documentation and support. When a platform hands DNS setup back to the customer, someone has to explain how to do it, and someone has to rescue the roughly half of customers who get stuck. The vendor absorbs that cost, prices it into the per-domain fee, and passes it straight to you.

~50%of paying customers stall at the DNS step of a manual setup
25+DNS providers Custom Domain auto-configures for you
$0per-domain fees, with a free tier to start

The tax is not one line. It is a bundle of small charges that hide inside a single monthly number. Once you break it apart, you can see exactly what you are being billed for and why so much of it should not exist at all.

Hidden costWhere it comes fromWith one-click setup
Per-registrar docsEvery DNS provider has a different UI, so support writes and maintains a guide for eachThe provider is detected and its records are written for you, so the guide is unnecessary
Failed onboardingsHalf of customers mistype a record or give up before the domain resolvesThe user never types a value, so the common failure modes cannot occur
Support ticketsWrong MX priority, a missing trailing dot, propagation confusionRecords are applied by template and verified automatically
Per-domain platform feeThe vendor's margin on all of the above, metered on every domainflat-tier pricing at all

Why manual setup is the expensive path

Line the two flows up side by side and the tax becomes obvious. The manual path is not just slower for the customer. It is the thing that generates every downstream cost you end up paying for.

Manual setup
  • Send the customer to find their zone editor
  • Ask them to add records by hand across an unfamiliar UI
  • Wait for propagation, then field the tickets when it breaks
  • Absorb the churn from everyone who quits at this step
One-click setup
  • The customer types their domain
  • We detect the DNS provider automatically
  • They approve one plain-language screen
  • Records are written, ownership verified, HTTPS issued

The right column is the whole point. When customers connect their domain in one click, the per-registrar docs, the failed onboardings, and the ticket queue simply stop being your problem. There is nothing to translate, so there is nothing to break.

What you actually get

Custom Domain does the same job the closed platforms do, without the metered fee sitting on top of it. We auto-configure more than 25 DNS providers, or hand off a signed, provider-hosted one-click flow where that is the cleaner route. We issue and renew certificates automatically at the edge, reverse-proxy traffic to your origin, and fire webhooks the moment anything changes. One REST API, one embeddable widget, one console.

  1. Detect the provider. The customer types a domain and we identify where its DNS lives.
  2. Write the records with consent. They approve one screen and we apply the exact records the service needs.
  3. Verify and secure. We confirm ownership, issue HTTPS, and keep the certificate renewed.

The real saving

You are not just cutting a line item. You are removing the support burden that the per-domain fee was pricing in, and recovering the customers who used to disappear at the DNS step. Start free and see how a one-click connection works.

Custom domains should be a feature you ship, not a tax you pay every month for the privilege of growing. Price it once, pass none of it on, and let the connection just work.

Custom domains, on autopilot

Let your customers connect their own domain in one click, with flat-tier pricing. We detect their DNS provider, write the records, verify ownership, and issue HTTPS, while they just approve one screen.

Get started
Let Your Users Bring Their Own Domain, Automatically