claworc and k8s4claw

The Openclaw Orchestrator provides the core container orchestration runtime, while the Kubernetes Operator serves as a control plane abstraction layer that deploys and manages OpenClaw instances across Kubernetes clusters—making them complementary components in a larger orchestration stack.

claworc

Emerging

k8s4claw

Experimental

Maintenance 13/25

Adoption 9/25

Maturity 11/25

Community 14/25

Maintenance 13/25

Adoption 2/25

Maturity 9/25

Community 0/25

Stars: 113

Forks: 14

Downloads: —

Commits (30d): 0

Language: Go

License: —

Stars: 2

Forks: —

Downloads: —

Commits (30d): 0

Language: Go

License: Apache-2.0

No Package No Dependents

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 k8s4claw

Prismer-AI/k8s4claw

Kubernetes Operator + Go SDK for managing heterogeneous AI agent runtimes (OpenClaw, NanoClaw, ZeroClaw)

Related comparisons

claworc and alphaclaw claworc and openclaw-kubernetes claworc and openclaw

Scores updated daily from GitHub, PyPI, and npm data. How scores work