HTTPS custom tracking domains for email platforms
Branded click and open links need a certificate for every customer's tracking hostname. Here is how to provide one without sending each customer to a CDN.
Read articleFrom the Approximated team
We build and operate the custom-domain edge for SaaS teams. These articles share how to connect customer DNS, automate HTTPS, protect tenant traffic, and keep domains healthy as your product grows.
Last reviewed · Subscribe via Atom
Branded click and open links need a certificate for every customer's tracking hostname. Here is how to provide one without sending each customer to a CDN.
Read articleTLS
Caddy can issue a certificate for a customer's domain on the first request. Here is what it takes to run that in production, and when it is enough.
Read articleSSL
Most limits never bite. A few do, during bulk onboarding, broken customer DNS and renewal waves. This post covers which ones, and how to plan around them.
Read articleSecurity
Combine safe hostname claims and removal with WAF, DDoS protection, Edge Verify, and ongoing domain monitoring.
Read articleProduct design
Replace a vague pending badge with five observable checks and specific customer-facing actions.
Read articleDNS
A plain CNAME can't live at the root. Compare an A record, a provider alias, and a redirect with their HTTPS trade-offs.
Read articleComparison
Compare Approximated, Cloudflare for SaaS, and Entri Power on production tooling, protection, support, deployment paths, and costs.
Read articleGuide
Build the full domain lifecycle with DNS, HTTPS, tenant routing, edge protection, monitoring, and a path to self-hosting.
Read article