Hee vs the alternatives
We built Hee because we hit every gotcha in this table. Here's the honest comparison.
Cloudflare for SaaS
Cloudflare's SaaS feature set is the industry default. It's also locked behind Enterprise for the parts you need the moment you go past "demo that works on the hero section." Custom Origin SNI, wildcard certs, predictable Worker routing on the fallback origin — all Enterprise. If you're shipping a real multi-tenant product with custom domains, you pay five figures a year or build your own edge.
Approximated
Approximated does a lot right. It's also a hosted, closed-source relay priced per-domain at amounts that start adding up at ~200 customers. Hee aims to be the Linux to Approximated's macOS: same ergonomics, lower cost, runs on your own infra when you want.
Rolling your own
Totally viable. Caddy's on_demand_tls + Postgres + one €5 box covers 80% of what Hee does. Run it yourself if the API surface and multi-tenant portal aren't worth €19/mo. We'd rather you self-host than pay Cloudflare Enterprise.
Side-by-side
| Capability | Hee | Cloudflare for SaaS | Approximated |
|---|---|---|---|
| Entry price | €0 (3 domains) | Enterprise contract | $29/mo |
| Custom Origin SNI | Yes | Enterprise only | Yes |
| Worker / middleware at edge | Planned | Paid tier only, and routes break | No |
| Own the edge | Yes (open source) | No | No |
| Multi-tenant API | Yes | Custom Hostnames API | Yes |
| First-request cert issue | ~3 s | Pre-provisioned | ~5-8 s |
| Per-tenant metadata passthrough | Yes | No (route yourself) | Limited |
| Self-hostable | Yes | No | No |
| Public status page | status.hee.la (Upptime) | cloudflarestatus.com | statuspage.io |
Updated 2026-04. If you spot something wrong, email ops@hee.la and we'll fix it same-day.