SaaS Custom Domains alternatives in 2026: the line item you can't model
SaaS Custom Domains charges a $20/mo minimum that covers up to 100 custom hostnames, $0.20 per domain after that, and volume discounts down to about half price. What it doesn't publish is the bandwidth side: no included allowance, no overage rate. If you're serving customer storefronts through those hostnames, that's the half of the bill you can't forecast before you sign up.
Domainee's numbers are all published: 50 domains and 100 GB of bandwidth free forever, then $0.20 per domain graduating to $0.10, with 400 GB included on usage pricing and $0.05/GB after that.
I build Domainee, so read this the way you'd read any vendor writing about a competitor. Every SaaS Custom Domains figure below comes from their public pricing page, the gaps I point at are gaps in that page rather than accusations, and the section on where they win is written in earnest.
Why people search for a SaaS Custom Domains alternative
Three things send people looking.
The $20/mo floor starts on day one. There's a trial, not a free tier, so a pre-launch product with four test hostnames pays the same $20 as one with ninety. Over a year that's $240 for a feature you haven't validated yet.
Bandwidth isn't priced on the page. Per-domain cost you can model in a spreadsheet. Traffic you can't, and traffic is the meter that moves when a customer's storefront has a good week.
There's no agent surface. REST API, webhooks, analytics, WAF: a solid list, with nothing on top of it for AI tooling. If you want an agent registering hostnames or checking certificate status, you write that layer yourself.
What SaaS Custom Domains publishes
| SaaS Custom Domains | |
|---|---|
| Free tier | Trial only |
| Monthly minimum | $20, covers up to 100 domains |
| Per-domain rate above 100 | $0.20 |
| Volume discounts | Up to 50% at scale |
| Bandwidth included | Not published |
| Bandwidth overage | Not published |
| API + webhooks | Yes |
| WAF / DDoS | Yes |
| MCP / AI agents | No |
The domain column is competitive and, to their credit, stated plainly. The two blank rows are the reason this post exists. The full side-by-side is at /alternatives/saas-custom-domains.
The line item you can't model
Custom domains for SaaS are rarely just DNS and a certificate. The hostname proxies real traffic to your origin, and somebody meters the bytes. So here's the arithmetic worth doing before you pick any provider.
A lean marketing page, with compressed images and no video, runs about 500 KB fully loaded. A typical customer storefront with product photography runs closer to 2 MB. Those two numbers bracket most of the custom-hostname traffic I see.
| Page weight | Views inside 100 GB | Views inside 400 GB | Cost per 10,000 views at $0.05/GB |
|---|---|---|---|
| 500 KB (lean marketing page) | 200,000 | 800,000 | $0.24 |
| 1 MB (content site) | 100,000 | 400,000 | $0.49 |
| 2 MB (storefront with photos) | 50,000 | 200,000 | $0.98 |
| 5 MB (media-heavy, hero video) | 20,000 | 80,000 | $2.44 |
The table says two things.
Bandwidth is cheap when it's priced. At $0.05/GB, ten thousand views of a heavy storefront costs about two dollars and forty cents. Nobody's business model breaks on that. The published free 100 GB covers a couple hundred thousand views of a normal page, which is more than most products serve across all their customer hostnames in year one.
Bandwidth is unknowable when it isn't priced, and that's the actual problem. You can't put a row in your unit-economics sheet for a rate you don't have. You find out what it costs the month after a customer's launch goes well, which is exactly the month you'd rather not be surprised.
If you want to model your own numbers against any provider, the custom domain cost calculator does the domain-plus-bandwidth arithmetic for you.
Meet Domainee
Domainee is a custom domains API for SaaS with a native MCP server — 50 domains and 100 GB free.
Your user brings their domain, you call one endpoint (or click once in the dashboard), and Domainee returns the CNAME target and handles SSL issuance and renewal from then on, with DNS health monitoring and webhooks on every state change. The domain points at whatever HTTPS origin already serves your app.
| SaaS Custom Domains | Domainee | |
|---|---|---|
| Free tier | Trial | 50 domains + 100 GB/mo, forever |
| Monthly minimum | $20 | None |
| Per-domain rate | $0.20, discounts to ~$0.10 | $0.20, graduating to $0.10 |
| Bandwidth included | Not published | 100 GB free; 400 GB on usage pricing |
| Bandwidth overage | Not published | $0.05/GB |
| REST API + webhooks | Yes | Yes, HMAC-signed |
| WAF / DDoS | Yes | Edge protection, no separate tier |
| AI agents | No | MCP server, 11 tools |
| In-app domain sales | No | Buy-a-Domain API, 500+ TLDs, $1 flat fee |
| SSL | Automatic | Let's Encrypt, issued and renewed automatically |
Every number in that column is at /pricing, including the overage rates. The developer experience is Stripe-shaped: Bearer keys, idempotency, signed webhooks, and an MCP server so an AI agent can register a customer hostname from a chat session.
Where SaaS Custom Domains is genuinely better
The bundled WAF and DDoS controls are a real feature, and they're surfaced as a product decision rather than an enterprise upsell. If your customers' storefronts attract abuse (ticketing, drops, anything with scalpers), having per-hostname rules in the same dashboard as the hostname itself is worth something.
Their per-domain analytics are also more detailed than ours. We report health, status, and certificate lifecycle; they report traffic shape per hostname. If you resell that view to your own customers, that's a feature you'd otherwise build.
And to be fair on price: above the $20 floor the per-domain rates are close enough that nobody should migrate a large fleet over the domain line alone. Migrate for the free tier on secondary environments, the published bandwidth rate, or the agent tooling.
Switching from SaaS Custom Domains
The migration is deliberately boring, because both products route with standard CNAMEs:
- Sign up at /sign-up. The free tier needs no card and covers 50 domains.
- Add each hostname via the dashboard or
POST /v1/domains. Domainee returns the CNAME target. - Update the CNAME at the customer's DNS. One line, and you can move hostnames one at a time.
- SSL issues automatically once DNS points at the edge, and certificate renewal runs from then on without prompting the customer.
- Remove the hostname from the old provider after the cutover.
The quickstart has the copy-paste version. Nothing about either product locks the hostname in, which is the nice thing about a market built on CNAMEs.
FAQ
How much does SaaS Custom Domains cost? A $20/mo minimum that covers up to 100 custom hostnames, then $0.20 per domain per month, with volume discounts of up to about 50% at scale. There's a trial rather than a free tier, and the bandwidth allowance and overage rate aren't published.
Does Domainee charge a monthly minimum? No. The first 50 domains and 100 GB of bandwidth a month are free permanently, with no card required. You only pay once you cross one of those two lines, and both meters are published.
How much bandwidth does a custom domain actually use? It depends on page weight. A 500 KB marketing page fits about 200,000 views inside 100 GB; a 2 MB storefront fits about 50,000. At $0.05/GB, ten thousand views of that heavier page costs roughly one dollar.
Can I run both providers during a migration? Yes. Each hostname routes independently through its own CNAME, so you can cut over one customer at a time and leave the rest where they are until you're done.
Does Domainee support apex domains and wildcards? Both. Apex domains work through A/ALIAS records and wildcard subdomains are included without tier gating.
What to do next
If the unpriced bandwidth meter is what sent you looking, the fix is a provider that publishes the rate, whoever you end up choosing. Ours is at /pricing, and the free tier covers 50 domains and 100 GB with no card. If you're still comparing the whole field, the roundup is at /blog/best-custom-domain-apis, the provider list is at /alternatives, and the same treatment of the two closest-priced competitors is at /blog/approximated-alternative-2026 and /blog/coalias-alternatives-2026.