CUSTOM DOMAIN
THE CUSTOM-DOMAIN LAYER FOR STOREFRONTS
Stores convert on their own domain.
A shopper who trusts acme.com hesitates at acme.myplatform.com. Your merchant types the domain they already own, and we take the storefront live on it. Apex included, checkout on HTTPS from the first request, no downtime at cutover.
Apex and www on 25+ DNS providers, auto-configured. Your merchants never touch a DNS panel.
The problem, for you
The apex domain is where carts get abandoned.
Merchants sell on trust, and trust lives at the root of their domain: acme.com, not acme.myplatform.com. But the root is exactly where DNS fights back. You cannot point a plain CNAME at the apex, every registrar invented a different workaround, and the ones without a workaround pin an A record to an IP that eventually changes out from under them.
Every apex failure reads to the merchant as “the platform broke my store.”
HTTPS
over the buy button is not optional. One lapsed certificate turns a checkout into a browser security warning, and the sale is gone.
When it half-works, it is worse. A merchant forwards the apex to a subdomain and every checkout takes a redirect that leaks conversions. A migration flips the domain before the cert is ready and the store goes dark in the window that mattered. Each one shows up as churn, chargebacks, and a support queue full of DNS you did not write.
How it works for you
One call takes a store live.
Your merchant pastes the domain they own. You send us the hostname. We detect the provider, write apex and www, verify ownership, and issue HTTPS before a single shopper arrives.
-
01
Detect. We fingerprint the merchant’s registrar as they type, then pick the path: provider sign-in, a provider-hosted one-click setup, a scoped API token, or guided manual with a live check.
-
02
Write. The root resolves without a pinned IP, and www is covered in the same pass. No forgotten half of the domain.
-
03
Verify and issue. A connection proves ownership and gets its certificate before it serves, so checkout is on HTTPS from the first request and the store is never dark.
-
04
Serve and watch. Traffic flips with SEO continuity intact, and drift monitoring pages you, not the merchant’s customers, if a zone edit breaks the store.
What you get
The hard part of custom domains, handled.
Apex domains that actually work
The root resolves on every provider without pinning an IP that will rot, so no merchant is stuck on a subdomain they do not want to sell on.
No cart-killing redirects
The apex serves directly instead of forwarding to a subdomain, so no checkout takes an extra hop that leaks conversions.
Certificates that never lapse
Issued in the TLS handshake and renewed automatically, so an expired-cert warning never appears over a buy button.
One integration, every registrar
25+ DNS providers auto-configured behind a single API, so you stop maintaining per-registrar setup instructions and the support tickets that follow them.
Where your merchants bought their domain
Apex and www, on all of them.
GoDaddy
Namecheap
Squarespace
Cloudflare
Google Domains
IONOS
Porkbun
Name.com
Hover
Gandi
Vercel
DNSimple
Where a provider cannot be automated, the merchant gets exact copy-paste records and a one-click check. Logos are the property of their respective owners and shown to describe interoperability.
Ownership is verified before any storefront goes live. Certificates issue in the TLS handshake and renew themselves, so checkout is never served without HTTPS. Drift is caught hourly, so if a merchant changes their zone, you know before a single shopper hits a broken store.
Questions
The three things builders ask.
Do apex domains really work everywhere?
Yes. The root resolves to our edge on every supported provider without pinning an IP, so there is no address to rot and no apex a merchant cannot use.
Is there downtime when a store cuts over?
No. A connection verifies and gets its certificate before it serves, and the previous setup keeps answering until the replacement is proven. The store stays live throughout.
What about SEO continuity?
Traffic is served at the domain the merchant already ranks on, apex and www both covered, so links and rankings carry over instead of scattering across a subdomain.
Put every store on its own domain.
Bring a real merchant domain to the call. We take it live on the apex, zero downtime.