The best custom-domain experience I've ever had was Lovable's

I was building a little app in Lovable. Nights-and-weekends, not serious yet — the kind of project you don't tell people about until it looks real. And the thing that makes a project look real, the moment it stops being a *.lovable.app URL and starts being yours, is the custom domain.

So I braced myself. If you've ever connected a domain to anything, you know the drill: open the registrar, hunt for the DNS panel, decode whether you need an A record or a CNAME, paste a value that looks like a ransom note, misjudge the TTL, refresh for two days, open a support ticket, and eventually get an SSL warning because the certificate didn't issue. The custom-domain step is where side-projects quietly go to die.

I pasted my domain into Lovable and reached for my registrar login.

I never needed it.

It detected where my domain lived, asked me to authorize, and did the rest. The records appeared. HTTPS came up on its own. The whole thing took less time than it's taking you to read this paragraph. I sat there for a second, a little stunned, and thought: that's it? that's how it's supposed to feel?

Why that tiny moment stuck with me

Because the custom domain isn't a settings row. It's the moment of commitment — the point where a user decides your product is worth putting their own name on. It is, quietly, one of the highest-intent things a customer will ever do inside your app.

And most products treat that sacred moment like a plumbing task. They hand the user a CNAME and a registrar login and call it "custom domain support." That's not support. That's a support ticket with a countdown timer. You took someone at their most committed and handed them the single most brittle, most abandonable step in your entire onboarding.

Lovable understood the opposite: the reward for a user's commitment should be less work, not more. Make the hard part invisible, and the moment that used to lose people becomes the moment that converts them.

The principle I couldn't unsee

Your users should never touch DNS for your product.

Not "we have good docs for DNS." Not "our support team will walk you through the CNAME." Never touch it. They shouldn't know what a CNAME is. They shouldn't meet their registrar. They paste a domain, they click once, and it's live — theirs, on HTTPS, in seconds.

The problem is that building this yourself is genuinely hard. There are 60-plus DNS providers, each with a different API, different auth, different quirks. There's ACME and certificate issuance and renewal you can't afford to get wrong at 2 a.m. There's ownership verification, apex vs. subdomain, CAA records, propagation, drift when a customer changes something upstream. Lovable could afford to solve it because domains are core to what they do. Most teams can't — so they punt, and their users pay for it with a CNAME.

So we built the part everyone punts on

That 30-second experience in Lovable is the entire reason Custom Domain exists. We took the thing that made me sit back in my chair and turned it into a drop-in any platform can add in an afternoon.

Your customer taps one button. We detect their DNS provider, authorize over OAuth where it exists, write the records correctly the first time across 63 providers, verify ownership, issue and auto-renew HTTPS, and serve it at the edge — then watch for drift so it stays live. Add it as a widget, a REST API, or an MCP server your AI agents can call. Zero DNS panels your customer should ever see.

I didn't start this because DNS is interesting. I started it because that one effortless moment made a product feel like magic to me — and I think your customers deserve to feel that about your product, at exactly the moment they've decided to bet on you.