Managed HTTPS routing for public services and explicitly authorized private homelab targets. Connected enrollment flows are available for kombify Cloud users.
Three steps for existing API-key users and connected enrollment flows.
Use an existing API key or a signed Cloud/Gateway connected enrollment token to manage routing entries.
Set a public HTTP(S) URL as your proxy target. kombify.me only proxies to publicly reachable upstreams.
Create per-service routes and enable exposure when ready. Each service can get a dedicated host.
Built for homelab operators who want public access without the overhead.
Every user gets unique subdomains under *.kombify.me. One base subdomain for your homelab, per-service subdomains for each app.
All traffic is encrypted with managed TLS certificates on the Cloudflare edge. You never touch a certificate.
Requests to your subdomain are proxied to your target address with full header forwarding. Works with any publicly reachable server.
Service subdomains are off by default. Public targets stay on the SSRF-hardened proxy path; private HTTP targets use the owner-authenticated Durable Object relay and never a direct Worker fetch.
Runs on Cloudflare Workers at 300+ locations worldwide. Subdomain lookups are cached in KV for sub-millisecond routing.
StackKit connected enrollment can auto-register routes through signed Cloud/Gateway provisioning flows.
Predictable, collision-free URLs for every homelab and service.
Routing APIs and verified self-hosted signup are available.