What is OpenClaw?
OpenClaw is a personal AI assistant that actually does things. It runs locally on your hardware, connects to 14+ messaging platforms, and extends through a growing Skills ecosystem.
14+ Platforms
WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Teams, and more.
AI Skills
ClawHub ecosystem with 50+ integrations. Browser automation, voice, Canvas.
Privacy-First
Self-hosted, local-first. Your data never leaves your infrastructure.
Gateway Runtime
Node.js gateway on port 18789. WebSocket-based, single-instance, PVC-backed.
Pincer Ops gives OpenClaw a
production-grade Kubernetes home.
GitOps deployment, encrypted secrets, automated backups,
and zero-trust networking. One command to deploy it all.
Sync wave orchestration
Infrastructure deploys before workloads via ArgoCD sync waves.
One kubectl apply reconstructs everything.
ArgoCD
Self-managing GitOps controller. App of Apps pattern.
MetalLB
L2 LoadBalancer IP allocation for bare-metal.
Envoy Gateway
Gateway API ingress. DaemonSet + hostPort routing.
Sealed Secrets
Encrypted secrets in Git. Cluster-side decryption.
cert-manager
TLS certificate automation. Self-signed issuer.
OpenClaw
AI Gateway. StatefulSet, single replica, PVC-backed.
ArgoCD
-10Self-managing GitOps controller. App of Apps pattern.
MetalLB
-5L2 LoadBalancer IP allocation for bare-metal.
Envoy Gateway
-4Gateway API ingress. DaemonSet + hostPort routing.
Sealed Secrets
-3Encrypted secrets in Git. Cluster-side decryption.
cert-manager
-2TLS certificate automation. Self-signed issuer.
OpenClaw
+10AI Gateway. StatefulSet, single replica, PVC-backed.
Three commands. Full stack.
Bootstrap
Single command creates a KIND cluster, installs ArgoCD, and deploys the entire stack. Fully idempotent, run it again and nothing changes.
Sync
ArgoCD watches main branch and auto-syncs. Drift is detected and self-healed. All state is declarative.
- ▸ Sync wave ordering (-10 to +10)
- ▸ ServerSideApply for CRD-heavy apps
Operate
Production-grade operational primitives. NetworkPolicies, daily backups, pre-commit hooks.
Why each tool exists
Every component in the cluster serves a specific purpose. Remove one and something breaks.
Watches the Git repo and auto-syncs to the cluster. App of Apps pattern, one root Application that discovers everything. Self-heals drift automatically.
Allocates virtual IPs for LoadBalancer Services via L2 ARP announcements. Cloud providers handle this automatically, KIND has no cloud, so MetalLB fills the gap.
Implements the Gateway API. Runs as a DaemonSet with hostPort on the control-plane node. Routes localhost:80 traffic through an HTTPRoute to OpenClaw.
Encrypts Kubernetes Secrets with a public key so they can be committed safely. Only the in-cluster controller has the private key. Daily key backup to ~/.pincer/.
Automates certificate issuance and renewal. Self-signed ClusterIssuer for dev environments. Infrastructure-ready for HTTPS when you need it.
AI assistant gateway. Single-instance StatefulSet, PVC-backed. Connects to 14+ messaging platforms. The application everything else exists to serve.
The OpenClaw universe
▸ Configures ArgoCD to sync from your fork (or skip for a quick try)
▸ Creates KIND cluster + deploys full stack (~3 min)
▸ All apps should show Synced / Healthy
▸ Configure your AI agent runtime via the web UI
Cloning without forking? make up still works — bootstrap falls back to local apply when ArgoCD can't reach the remote.