claworc and openclaw-kubernetes
The Kubernetes helm chart is a deployment mechanism for the orchestrator, making them complements—you would use the helm chart to deploy the orchestrator into a Kubernetes cluster.
About claworc
gluk-w/claworc
Openclaw Orchestrator
Multiplexes SSH connections to manage isolated OpenClaw agent instances, each with a containerized browser, terminal, and persistent storage, proxying all traffic through a single control plane with role-based access control and encrypted API key management. Built-in health monitoring with automatic reconnection, audit logging, and key rotation ensure secure multi-user orchestration across Docker or Kubernetes deployments.
About openclaw-kubernetes
feiskyer/openclaw-kubernetes
Kubernetes helm chart for OpenClaw (former Moltbot/Clawdbot)
Deploys OpenClaw's AI gateway as a StatefulSet with persistent storage and optional LiteLLM proxy for multi-model routing (GitHub Copilot, Anthropic, etc.). Includes a headless Chrome browser running in a virtual framebuffer, accessible via noVNC for real-time automation monitoring. Integrates Tailscale mesh VPN for secure private access and supports pluggable "skills"—structured agent instruction sets for external coding tools like Claude Code and Codex CLI—installable via ConfigMaps or shared PVCs.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work