Domainee
Sign inGet started
White-Label

Custom domains your users
experience as yours.

Domainee never appears in the URL, the SSL certificate, the WHOIS, or your customer-facing UI. Your tenants see their own domain serving your app — full stop. The custom-domain layer invisible to everyone except your engineering team.

Start freeRead the deep dive

50 white-labeled customer hostnames free, forever.

0
Domainee mentions in your URLs
0
Domainee mentions in your certs
Your name
in WHOIS on Buy-a-Domain
50
customer domains free, forever

Trusted by teams building the future of SaaS

  • Common Ninja
  • Embeddable
  • Vidocu
  • Brackets Ninja

White-label, every layer

Cert chain that mentions only your customerhostname only

The TLS cert is issued for shop.acme.com. Subject CN = shop.acme.com. Issuer = Let's Encrypt. Domainee appears nowhere in the chain — and that's how every browser, every API client, every WHOIS-style cert checker sees it.

WHOIS lists your customer, not uslegal registrant

On the Buy-a-Domain flow, we register the domain at the upstream registrar with your customer as the legal registrant. Their name, their contact info, their renewal rights. Domainee is invisible in every public record.

Your dashboard, your support flowbranded UI

Domainee's admin tools exist to power your support team — they're not a customer-facing surface. End-users never see a Domainee logo, link, or status badge.

Why white-label is the default, not a feature: we built Domainee for SaaS companies whose value prop is beingthe brand. The whole point of giving your users a custom domain is so they feel like the SaaS is yours, not a reseller of someone else's API. Our infrastructure disappears.

The full audit

Where Domainee shows up, and where it doesn't.

An honest accounting of every surface a curious customer might inspect — and where our name appears (almost nowhere).

The URL barshop.acme.comHIDDEN
The TLS cert subjectCN = shop.acme.comHIDDEN
TLS cert issuerLet's EncryptHIDDEN
WHOIS (Buy-a-Domain flow)Your customer's legal nameHIDDEN
WHOIS (Connect flow — BYO domain)Whoever the customer registered withHIDDEN
HTTP response headersNo Domainee identifierHIDDEN
Routing across regionsMulti-Region edge, latency-routed per user(Same cert, same content from every region)HIDDEN
Customer's DNS panel (CNAME target)edge.domainee.dev(One-time setup; not visible to end-users)VISIBLE
Your support dashboardVisible to your staff only(Internal tool — your team's view)VISIBLE

CNAME aliasing on Enterprise can rebrand even the DNS setup (your customers CNAME to edge.yoursaas.com instead). Talk to us about setup.

The customer-facing flow, end to end

What your customer sees, in order. Domainee never appears.

What your customer pastes

One CNAME at their registrar

customer DNS panel
# What your customer sees in GoDaddy / Cloudflare / wherever
TYPE   NAME             VALUE
─────  ───────────────  ──────────────────────
CNAME  shop             edge.domainee.dev
                        (or edge.yoursaas.com
                         on white-label CNAME)
What end-users see in the browser

shop.acme.com, your app, your cert

end-user view
URL bar:        https://shop.acme.com/cart
TLS subject:    shop.acme.com
TLS issuer:     Let's Encrypt
HTTP headers:   server: cloudflare
                x-acme-store-version: 12.3
                (your headers, your server name)
Page content:   your SaaS, your branding
Domainee:       appears nowhere

Who ships white-label custom domains

Teams whose customers should never feel they're using a middleman.

White-label SaaS resellers

Your platform IS the brand for your customer. Every URL, every cert, every record reads as yours — no third-party logos, no 'powered by' trail.

Agencies running multiple client SaaS

Each client gets their own Domainee workspace. Their customers' domains run through a CNAME that has no relationship to the agency or to us.

Enterprise platforms with compliance

Your customers expect to see only your name in their security audit, their cert chain, and their incident-response runbooks. Domainee is engineered to disappear from those reports.

Vertical SaaS in regulated industries

Healthcare, financial services, government. Your customers' inspectors check WHOIS, cert chains, and DNS — none of which reveal that there's infrastructure underneath you.

What you skip

The white-label plumbing you don't maintain

  • A cert-issuance flow that omits any third-party identifier from the chain.
  • A WHOIS-pass-through where your customer is the legal registrant.
  • An edge that strips your provider's response headers and replaces them with yours.
  • A CNAME aliasing layer for fully-branded DNS instructions (edge.yoursaas.com).
  • A support tooling story that doesn't expose your underlying API to your customers.
  • A reseller billing model so agencies running 100 client SaaS pay one consolidated bill.

Read the full pattern in the white-label SaaS use case.

FAQ

Frequently asked

What does 'white-label' mean for a Custom Domains API?
Your customers never know Domainee exists. The cert is for their hostname, the URL never says 'domainee.dev', the WHOIS lists your customer as the legal registrant (on Buy-a-Domain flows), and the only Domainee string anywhere in the flow is the CNAME target in their DNS provider — invisible to end-users.
Will my customers see the Domainee CNAME at any point?
Only inside their own DNS panel, when they set up the record. They paste 'edge.domainee.dev' as the CNAME value once. After that, no end-user ever sees it. The HTTP requests are served from their domain, the cert is for their domain, even your support dashboard shows the customer's hostname rather than ours.
Can I rebrand the CNAME target as my own?
Yes, on Enterprise plans. We support CNAME aliasing — set up edge.yoursaas.com as a CNAME to edge.domainee.dev, instruct your customers to CNAME to edge.yoursaas.com. The hop is invisible at the protocol level. Reach out via /contact to set this up.
What about the SSL certificate? Does it say Domainee anywhere?
No. The cert is issued for the customer's hostname (shop.acme.com), signed by Let's Encrypt, with no Domainee identifier. Open the cert details in any browser and the only names you'll see are your customer's domain and Let's Encrypt's chain.
What about Buy-a-Domain? Is Domainee in the WHOIS?
No. We register the domain at the upstream registrar with your customer as the legal registrant — their name, their contact info. If they ever leave your platform, they can transfer the domain out. Domainee never appears in WHOIS at any point.
What does my dashboard show when I look up a customer's domain?
Our admin dashboard shows your hostnames and your tenants — not 'domains routed through Domainee.' The data model is yours. The dashboard exists to power your support team, not to remind them they're using a third-party API.
Can I let my customers' end-users buy domains too — fully white-labeled?
Yes. Combine the Buy-a-Domain API + white-label CNAME aliasing + your branded support page and the entire user-facing flow looks like you ran the registrar. Your customer pays you, you pay us wholesale + $1.
What pricing tier do I need for white-label?
The basic white-label experience (no Domainee in the URL, no Domainee in the cert, no Domainee in WHOIS) is on every tier including free. CNAME aliasing (edge.yoursaas.com) and other premium white-label touches are on Enterprise — drop us a note via /contact.

Still have questions? Ask our team →

Ship a white-label experience your users never see through.

Mint an API key, register your first hostname, watch the cert issue with your customer's name on it and nothing else. 50 free, forever.

Get startedRead the deep dive