SaaSKevin alternatives in 2026: where $0.15 a domain actually wins
SaaSKevin charges $0.15 per domain per month after 3 free ones, which makes it the only custom-domain provider with a cheaper per-domain rate than Domainee's $0.20. The catch: the free tier is 3 domains against 50, bandwidth is "fair use", and there's no public API. The crossover lands at exactly 191 domains. Here's the math.
Most posts in this series find a hidden cost and build the tables around it: Entri's $249 floor, CoAlias's request caps, SaaS Custom Domains' unpublished bandwidth meter. SaaSKevin is the opposite problem. Their headline rate undercuts ours by a nickel, and I build Domainee, so the honest version of this post has to start by admitting that and then work out exactly where the nickel matters and where it doesn't.
Why people search for a SaaSKevin alternative
Three patterns show up:
- The free tier is 3 domains. That's enough to test the product and connect your first customer or two. It's not enough to run a launch, a staging environment, and your early adopters at the same time. Domain #4 starts the meter.
- There's no public API documented. This is the big one. Custom domains for a SaaS is an API-shaped feature: your onboarding flow calls an endpoint when a customer types in their domain, your dashboard polls verification status, your billing reacts to webhooks. SaaSKevin is driven from their dashboard. At 10 domains that's a mild chore. At 200 it's a part-time job.
- Bandwidth is "fair use". No published GB allowance, no overage rate. It probably never bites a small fleet. But you can't put "probably" in a unit-economics spreadsheet, and if one customer's domain gets popular, you find out what fair use means by email.
Notice what's missing: nobody complains about the price. The price is the part that works.
What SaaSKevin actually charges
The published numbers, checked July 2026:
| Plan | Price | Domains | Bandwidth |
|---|---|---|---|
| Free | $0 | 3 | "Fair use", no published number |
| Pay as you go | $0.15/domain/mo | Billing starts at domain #4 | Same fair-use policy |
That's the whole pricing page, and I mean that as a compliment. No tiers to decode, no sales call, no card required to start. There are no volume discounts as you scale, which matters later in this post. The full side-by-side is at /alternatives/saaskevin.
The crossover math
Domainee's rates: first 50 domains and 100 GB free, then $0.20 per domain per month. SaaSKevin: first 3 free, then $0.15. Cheaper rate, smaller head start. So there's a crossover point, and it's computable: $0.20 × (N − 50) = $0.15 × (N − 3) solves to N = 191.
The bill at each fleet size, per-domain charges only (bandwidth excluded, because SaaSKevin doesn't publish a number to compare against):
| Your domain count | SaaSKevin | Domainee |
|---|---|---|
| 3 | $0 | $0 |
| 10 | $1.05 | $0 |
| 25 | $3.30 | $0 |
| 50 | $7.05 | $0 |
| 100 | $14.55 | $10 |
| 191 | $28.20 | $28.20 |
| 250 | $37.05 | $40 |
| 500 | $74.55 | $90 |
| 1,000 | $149.55 | $190 |
Reading it honestly, in three zones:
Up to 50 domains, Domainee is free and SaaSKevin bills single-digit dollars. The amounts are small either way; the difference is that 50 free domains covers most products all the way through finding product-market fit, with staging environments to spare.
From 50 to 191 domains, Domainee stays cheaper because the 50 free domains keep not costing anything while SaaSKevin's meter has been running since domain #4.
Past 191 domains, SaaSKevin's sticker price is lower. The gap grows by a nickel per additional domain: $15.45/mo at 500 domains, $40.45 at 1,000. That's real money, and I'm not going to pretend the spreadsheet says otherwise.
There's a fourth zone, for completeness: Domainee's volume discounts step down 5% per 1,000 domains (the first 1,000 at $0.20, the next at $0.19, and so on to $0.10 at 10,001+), while SaaSKevin's $0.15 is flat. The curves cross back at roughly 10,800 domains. So the precise claim is: SaaSKevin has the cheaper sticker between 191 and about 10,800 domains, and Domainee is cheaper everywhere else. You can model your own fleet in the custom domain cost calculator.
What the nickel doesn't buy
Here's why I'm comfortable publishing a table where the competitor wins a zone. At 500 domains, the $15.45/mo you'd save comes with three gaps, and each one is worth more than the savings:
No API means manual onboarding. With 500 customer domains, domains come and go weekly. On Domainee that's POST /v1/domains in your onboarding flow and a webhook when verification completes. The customer never waits on you. Without an API, every connect, every DNS check, every removal is someone clicking in a dashboard. One manual onboarding a month eats the savings.
No agent surface. Domainee ships an MCP server, so an AI agent (or your support tooling) can register a hostname, check DNS, and read SSL status programmatically. SaaSKevin has nothing to point an agent at, because there's no API underneath to expose.
No published bandwidth number. Domainee's meter is public: 100 GB free, 400 GB included on usage pricing, $0.05/GB after. Fair use is fine until the month it isn't, and a fleet of 500 domains is exactly the situation where one customer's traffic spike turns a policy into a phone call. I did the page-weight math on what unpublished bandwidth can cost in the SaaS Custom Domains post; the same reasoning applies here.
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 side-by-side:
| SaaSKevin | Domainee | |
|---|---|---|
| Free tier | 3 domains | 50 domains + 100 GB/mo |
| Per-domain rate | $0.15 flat | $0.20, discounts to $0.10 |
| Cheaper sticker | 191 to ~10,800 domains | Everywhere else |
| Bandwidth | "Fair use", unpublished | 100 GB free, $0.05/GB after included |
| REST API | Not documented | Yes |
| 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 is published at /pricing. The developer experience is Stripe-shaped: Bearer keys, idempotency, HMAC-signed webhooks, and the Buy-a-Domain API if you want to sell domains inside your product instead of just connecting them.
Where SaaSKevin is genuinely better
Three honest cases.
If you run a small fleet by hand and like it that way, SaaSKevin's product is simpler because it does less. No API keys to manage, no webhook endpoints to stand up. Connect the domain in the dashboard, SSL happens, done. For an agency managing a dozen client domains with no automation ambitions, that simplicity is a feature.
If your fleet sits solidly in the 191-to-10,800 window, you never need programmatic onboarding, and your traffic profile is boringly low, the sticker is lower and stays lower. The table above is exactly as true when it favors them.
And their pricing story fits in one sentence, which is worth something when you're explaining infrastructure costs to a co-founder. "Three free, then fifteen cents" beats reading anyone's pricing page.
Switching from SaaSKevin
If the API gap or the free tier says move, the migration is deliberately boring:
- Sign up at /sign-up. The free tier needs no card and covers 50 domains, which for most SaaSKevin fleets is the entire fleet.
- Add each hostname via the dashboard or
POST /v1/domains. Domainee returns the CNAME target. - Update the CNAME at the customer's DNS. Hostnames route independently, so move one at a time.
- SSL issues automatically once DNS points at the edge, and monitoring starts on its own.
- Remove the domain from SaaSKevin after cutover.
The quickstart has the copy-paste version. Both products use standard CNAME routing, so there's no lock-in in either direction.
FAQ
Is SaaSKevin cheaper than Domainee? Between 191 and roughly 10,800 domains, yes, on per-domain sticker price: $0.15 flat against $0.20 with volume discounts. Below 191 domains Domainee costs less, and below 50 it's free outright. Past ~10,800, Domainee's graduated discounts win again.
Does SaaSKevin have an API? No public API is documented; the product is driven from their dashboard. Domainee exposes a full REST API plus an MCP server, so both your code and AI agents can manage domains programmatically.
What does SaaSKevin's "fair use" bandwidth actually allow? They don't publish a number, an allowance, or an overage rate, so nobody outside the company knows. Domainee publishes the whole meter: 100 GB free, 400 GB included on usage pricing, $0.05/GB after.
Can I run both providers during a migration? Yes. Each hostname routes via its own CNAME, so you can cut over one domain at a time and leave the rest on SaaSKevin until you're done.
Does Domainee support apex domains and wildcards? Yes, both. Apex domains work via A/ALIAS records, and wildcard subdomains are included without tier gating.
What to do next
If you're under 191 domains, the math is unambiguous: start on the free tier at /sign-up and the bill is $0 until domain #51. If you're past 191, the question isn't the nickel, it's whether you can keep running a domain fleet without an API; if the answer is yes, SaaSKevin is a fine product and you should stay. 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 honest-math treatment of the rest of the market is at /blog/entri-alternative-2026, /blog/coalias-alternatives-2026, /blog/approximated-alternative-2026, and /blog/saas-custom-domains-alternatives-2026.