kedge is an open-source control plane from faros.sh that brings distributed Kubernetes clusters, as well as bare-metal servers, VMs, Raspberry Pis, and other machines, into a unified Hub. Its key design is that the Agent initiates an outbound connection to the Hub, making the Hub the only component that needs to be publicly reachable. This removes the need for VPNs, port forwarding, or opening inbound firewall rules, making it especially suitable for managing resources behind NAT, home networks, edge sites, and corporate firewalls.
For Kubernetes use cases, kedge provides native kubectl access. It can proxy to registered clusters through a unified kubeconfig, reducing the hassle of constantly switching between multiple kubeconfig files. For non-Kubernetes hosts, it offers an SSH server mode, allowing you to manage VMs, bare-metal servers, or Raspberry Pis via kedge ssh my-server. Another distinctive feature is MCP: it can expose connected clusters as a single Model Context Protocol server, enabling MCP clients or Agents such as Claude and Cursor to operate cluster environments.
For authentication, kedge supports OIDC and can integrate with Dex, Auth0, Okta, and others. It also supports static tokens, which are suitable for home labs and development environments. The page also mentions per-user kcp workspaces for isolation. The CLI is the main entry point, supporting operations such as registering edges, obtaining kubeconfig, SSH access, and generating MCP URLs.
kedge is licensed under Apache 2.0. The page explicitly states that it is free forever, requires no license key, has no telemetry, no paid features, no usage limits, and supports unlimited edges. It offers a hosted hub at console.faros.sh for quick trials, while also supporting self-hosted Hub deployments. The Hub can be deployed via Helm on your own Kubernetes cluster, or placed behind entry points such as a VPS, Cloudflare Tunnel, or nginx.
Its strengths are a simple and straightforward architecture that addresses common firewall and NAT issues in remote cluster access. It also covers both Kubernetes and regular servers, and its integration with MCP is a relatively novel approach for AI Agent-oriented cluster operations. The documentation structure also appears fairly complete, covering quick start, CLI, SSH, MCP, self-hosting, security, and Provider extensions.
The limitations are that the collected content does not provide details on enterprise support, SLA, hosted Hub regions, privacy, or compliance. Information about the third-party ecosystem is also limited beyond Kubernetes, OIDC, MCP, Helm, and Cloudflare Tunnel. For Windows, only WSL is mentioned; there is no clear indication of a native client.
Access from mainland China cannot be determined from the page alone, so it is marked as unknown. If using the hosted hub, cross-border network stability may be a factor. Self-hosting it in mainland China or on a nearby cloud server would offer more control. Alternatives worth considering include Tailscale, Teleport, Cloudflare Tunnel, Rancher, KubeSphere, and Open Cluster Management.
β This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on faros.sh official site.
faros.sh is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 8.0/10, and a China-accessibility score of China direct-connect friendly. Click "Visit Official Site" to reach faros.sh directly.