Compare
DoDomain vs Domainee
Buyers compare these two on the same search — custom domains for SaaS — but they do different halves of the job. Domainee is a proxy with a generous free tier: your customer points a CNAME at it, and it terminates TLS with a Let's Encrypt certificate and forwards to your app. DoDomain is the step before that: getting the record created in the customer's own DNS provider, proving it is live, and watching it afterwards. This page says which half each one does and when you want Domainee instead.
Facts about Domainee checked on against domainee.dev — check their site for current figures. DoDomain's numbers come from its live plan definitions.
Who does which half
| DoDomain | Domainee | |
|---|---|---|
| Gets the customer's DNS record created | Yes — Cloudflare OAuth one-click, signed Domain Connect apply where the provider has enabled it, guided per-provider steps with a live status per record everywhere else | No — the customer adds a CNAME at their registrar (per domainee.dev, retrieved 2026-09-02) |
| Proves the record is live | Yes — read at the domain's authoritative nameservers before success is declared | "Webhooks tell you when DNS lands" (per domainee.dev, retrieved 2026-09-02) |
| Terminates TLS on the customer's hostname | Never — traffic goes straight to your host | Yes — Let's Encrypt certificates, issued and renewed automatically (per domainee.dev, retrieved 2026-09-02) |
| Buys domains for customers | No | Yes — a Buy-a-Domain API alongside the Connect API (per domainee.dev, retrieved 2026-09-02) |
| Drift monitoring | Every 10 min → hourly → 6 h by connection age, 3 confirmed checks before a break, failing records named; free on every plan | "DNS health checks + drift webhook" (per domainee.dev, retrieved 2026-09-02); cadence not published |
| Free tier | $0 forever — 50 verified connections per month, no card | 50 domains and 100 GB bandwidth free forever, no card (per domainee.dev, retrieved 2026-09-02) |
| Metered by | Verified connections per month — a connection counts once, on first verification | Domains served ($0.20/domain/mo, down to $0.10 at 10,000+) plus bandwidth (400 GB included on paid, then $0.05/GB) (per domainee.dev, retrieved 2026-09-02) |
The meters tell the story: Domainee charges for hostnames it serves and bytes it moves, because it is in the request path. DoDomain charges for onboarding events that succeeded, because it is not.
The DNS step is the one nobody else touches
A proxy's instructions page ends with "add this CNAME at your registrar". That sentence is where self-serve onboarding stalls: the customer edits the wrong zone, leaves the orange-cloud proxy on, types the target into the host field, or gives up and opens a ticket. DoDomain replaces the sentence with a path — a scoped OAuth approval on Cloudflare's own page, a signed Domain Connect apply where the provider has enabled our registry-merged templates, or the provider's exact dashboard link with its quirks explained and a live status per record — and then reads the authoritative nameservers before it tells your server anything.
To pair them, pass the CNAME target Domainee gives you to POST /api/v1/sessions and hand your customer the returned connectUrl or the @dodomain/connect widget. The signed connection.verified webhook is your cue that Domainee can issue the certificate.
Where Domainee still wins
Honest flip side. If you want a vendor to serve HTTPS on your customers' domains so you never touch certificates, Domainee does that and DoDomain never will. Its free tier — 50 domains and 100 GB forever — covers a small product entirely, its Buy-a-Domain API lets customers who own nothing yet buy a domain inside your flow, and it advertises a larger MCP tool set (per domainee.dev, retrieved 2026-09-02). If those are the constraints, Domainee is the better fit, possibly with DoDomain in front of it for the DNS step.
Where DoDomain earns its place is the DNS half: writing the record where it can, guiding it precisely where it cannot, proving it at the source, and monitoring it for free afterwards — with no proxy in your request path and no bandwidth line on the invoice.
Frequently asked questions
What does Domainee cost?
As published on domainee.dev (retrieved 2026-09-02): 50 domains and 100 GB of bandwidth are free forever with no credit card; after that domains are $0.20 per domain per month with graduated discounts down to $0.10 at 10,000+ domains, and paid subscriptions include 400 GB of bandwidth, then $0.05 per GB. Check domainee.dev for current figures.
Is DoDomain an alternative to Domainee?
Partly. Domainee is a proxy: your customer points a CNAME at Domainee, Domainee issues the Let's Encrypt certificate, terminates TLS and forwards to your app (per domainee.dev). DoDomain is the DNS layer: it gets that CNAME (or A/TXT/MX record) created inside the customer's own DNS provider — one-click on Cloudflare, a signed Domain Connect apply where the provider supports it, guided records elsewhere — verifies it at the authoritative nameservers, and monitors it afterwards. If what you need is someone to serve HTTPS on customer hostnames, Domainee does that and DoDomain does not. If what stalls your onboarding is the customer's DNS step, DoDomain does that and Domainee leaves it to the customer.
Does Domainee write the DNS record for my customer?
Not as published: for its Connect API, the customer adds a CNAME record at their registrar (per domainee.dev). DoDomain's whole job is that step — writing the record through the customer's own provider where it can, guiding it with the exact values and a live per-record status where it cannot, and proving the result before your server is told.
Both mention drift monitoring — how do they compare?
Domainee lists "DNS health checks + drift webhook" (per domainee.dev, retrieved 2026-09-02); its cadence is not published. DoDomain re-checks every verified connection at the authoritative nameservers every 10 minutes for its first day, hourly for a week, then every 6 hours, confirms a suspected drift on three consecutive checks, names the failing records in a signed connection.failed webhook, and re-emits connection.verified on recovery — free on every plan, Free included, with no monitored-domains cap.
Can I use DoDomain in front of Domainee?
Yes — that is the natural pairing, the same way DoDomain sits in front of Cloudflare for SaaS or Approximated. Register the domain with Domainee, take the CNAME target it gives you, pass that record to POST /api/v1/sessions, and hand your customer the connectUrl or the @dodomain/connect widget. When the signed connection.verified webhook arrives, the CNAME is live at the customer's authoritative nameservers and Domainee can issue the certificate.
What about AI agents and MCP?
Both ship a remote MCP server. Domainee advertises "an MCP server with 11 tools" (per domainee.dev, retrieved 2026-09-02). DoDomain's MCP server at app.dodomain.io/api/mcp exposes seven tools over OAuth 2.1 with scoped consent — check a domain's provider, list apps and connections, create and verify connect sessions, re-verify a connection — and every tool calls the same /api/v1 endpoints your integration uses, so limits and permissions apply identically. Count the tools you would actually call, not the headline number.