Welcome to SaaS Brew, a daily newsletter where we share useful SaaS tools and workflows for founders, builders, and small business owners.
Each edition highlights one product, explains what it does, why it matters, and who it is for. No hype. Just tools worth trying.
Today's brew looks at a problem that slows down nearly every SaaS team eventually:
You need to let your users connect their own custom domains. Sounds straightforward. But then you're staring down cert provisioning, DNS verification, edge routing, wildcard handling, and the fun of debugging why propagation worked for one user and silently failed for another. You wire something together, it holds, and then six months later a cert expires and support tickets start rolling in.
Some teams reach for a patchwork of services. A cert manager here, a reverse proxy there, a registrar integration if you also want to sell domains. Each piece needs maintenance. Each piece is another thing that can break. The "quick feature" becomes a multi-week infrastructure project, and it is still not done.
You need custom domain support that just works, without owning the infrastructure forever.
That is where Domainee fits in.
Domainee handles the entire domain layer for your SaaS in a single API integration. Connecting a domain is one CNAME away: you call one endpoint, return the CNAME record to your user, and receive a signed webhook the moment DNS propagates. SSL certificates are issued via Let's Encrypt on the first request and renewed automatically. No cert monitoring. No renewal jobs. Just verified, secured domains. Built for SaaS teams shipping fast, Domainee removes the infrastructure burden without removing your control over the experience.
Who it is for
SaaS founders who want to offer custom domains without a two-week infrastructure detour
Platform builders letting customers white-label or branded-ify their workspace
Developer tools and no-code platforms where users expect to bring their own domain
Indie hackers who need the same domain infrastructure big teams have, without the ops overhead
Product teams who also want to sell domains directly inside their app and keep the margin
Common use cases
Connecting a user's existing domain to their workspace with a single CNAME and automatic SSL
Selling a brand-new domain to a user at checkout and routing it to their account automatically
Letting users manage DNS, nameservers, and renewals from inside your product instead of a registrar dashboard
Using the MCP server to let an AI agent like Claude or Cursor provision and verify domains through the same API
Replacing a fragile in-house cert and routing setup with a single, maintained API that handles the full lifecycle
What it does
It provisions SSL certificates via Let's Encrypt on first request and renews them automatically for the domain's lifetime
It sends a signed HMAC webhook the moment DNS propagates, so your system knows exactly when a domain is verified
It handles domain search, purchase, and registration through one API call, with the end user as the legal owner
It exposes every endpoint as an MCP tool so AI agents can list, create, and verify domains with the same Bearer key
It charges wholesale plus a flat dollar per domain registration, letting you set your own markup and keep the difference
Why it stands out
It follows Stripe-style conventions with Bearer auth, idempotency keys, and predictable JSON, so integration feels familiar
It ships a free tier with the first 50 domains and 100 GB bandwidth included, no credit card required
It was built in production across three real products for over a year before launching publicly, so the rough edges are already gone
It collapses what is typically four or five infrastructure pieces into one API with fully published, usage-based pricing
Quick take: If you have been putting off custom domain support because the infrastructure work feels bigger than the feature, Domainee could ship it for you the same day.
More tomorrow in SaaS Brew ☕