kedge Documentation
Deploy your own hub
Run kedge on infrastructure you control.
The hosted hub at console.faros.sh is convenient, but everything kedge does is open source — you can run the hub yourself and never touch the SaaS.
Self-hosting takes three decisions:
- Where the hub Pod runs — any Kubernetes cluster will do. Even a single-node k3s on a VPS or NUC is fine. See Helm Deployment.
- How agents reach it from the internet — you need a stable hostname with TLS. The hub itself is one Pod; the question is what’s in front of it (nginx, traefik, a Cloudflare Tunnel, a cloud load balancer…). See Ingress.
- How users authenticate — static token for personal use, OIDC via Dex / Auth0 / Okta for teams. See Security.
There are no usage limits. Connect as many edges as you want; the hub is just a stateless API server plus the kcp data store (a PVC).
Helm Deployment →
Deploy the kedge hub with Helm — local kind, single-node k3s, or full production.
Ingress →
Make your hub reachable from the internet — Cloudflare Tunnel, port forwarding, mesh VPN, or cloud LB.
Cloudflare Tunnel →
Expose your hub via Cloudflare Tunnel — no public IP, free TLS, free DDoS protection.