OpenClaw Enterprise Edition: What It Actually Is

The short answer

“OpenClaw Enterprise Edition” refers to OpenClaw Enterprise (OCE), a separate project from the OpenClaw agent itself. The repository describes it as “the open source, vendor neutral platform for managing agents” — in its own words, Kubernetes for agents. It adds the organizational layer that a single self-hosted OpenClaw does not have: multi-tenancy, identity and roles, audit events, and hard boundaries between trusted and untrusted workloads.

Unaffiliated repositories with similar names appeared quickly after the announcement. The official one is under the openclaw GitHub organization; check the owner before you clone anything.

Why it exists

Plenty of companies banned agentic tools like OpenClaw outright, because a persistent agent with shell access, credentials and network reach is hard to govern one laptop at a time. OCE is the project's answer: put agents behind a control plane where an organization can decide who may run what, keep an audit trail, and sandbox untrusted work — without cutting the agent down to something less useful. The announcement lists sandboxing, LLM-based reviews and fine-grained permissions as the security model.

What is in the repository

The README splits OCE into a handful of components:

• OpenClaw Control Plane (OCC) — an HTTP API, browser console, worker and drivers for deploying and managing agents (apps/controller/).
• Contracts — the resource models and driver interfaces (packages/contracts/).
• OCC core — resource lifecycle and the work queue (packages/occ/).
• IAM — identities, roles and resource authorization (packages/iam/).
• Audit — audit events and handling of sensitive values (packages/audit/).

The development setup expects Docker or Podman, k3d, kubectl, Helm, Go, Node.js 24+ and pnpm. That list is a fair signal of the audience: a platform team that already runs Kubernetes, not an individual who wants a Telegram bot. Start from the repository's own getting-started guide, which changes faster than any third-party write-up can track:

git clone https://github.com/openclaw/openclaw-enterprise.git
cd openclaw-enterprise
# then follow README.md -> Local Setup or Kubernetes Setup

What it is not

• Not a license key or paid tier. There is no “Enterprise SKU” of OpenClaw that unlocks features in the app you already run. Pages quoting an OpenClaw enterprise price are quoting a third-party host's plan.
• Not a hosted service. OCE runs on your infrastructure. Nobody operates it for you as part of the project.
• Not finished. Version 1.0 is still under way. The project itself describes the current stage as internal pilots.
• Not a drop-in upgrade. No migration path for an existing ~/.openclaw workspace has been published.

The Hermes Agent side: Business and Enterprise

Hermes Agent took a different route. Rather than an open-source control plane, Nous Research packaged team offerings around its own portal in mid-September 2026:

Hermes Agent itself remains open source and self-hostable without either offering — see running Hermes on Kubernetes and Hermes with Docker. The shared skill library is the Hermes-specific idea: skills one person's agent writes become available to colleagues, which builds on Hermes' habit of creating skills from its own work.

Where managed hosting fits

OpenClaw Launch is not an enterprise edition of either framework, and it would be misleading to present it as one. We do not offer SSO, SAML, an audit console or contractual SLAs. What we do is run OpenClaw or Hermes Agent for you, with each agent in its own isolated container, so a person or a small team can have a working agent without building a platform first.

• Both frameworks, same plans. OpenClaw and Hermes cost the same. Lite is $6/month with one instance; Pro is $20/month with up to three. See pricing.
• Bring your own key. Use the included AI credits or your own provider key — see Hermes BYOK.
• Work channels. Connect Slack or Microsoft Teams alongside Telegram and Discord.

A reasonable way to split it: if your security team needs central identity, per-tenant isolation and audit across hundreds of agents, evaluate OCE or Hermes Enterprise. If you need a few agents doing real work this week, managed hosting is the shorter path — and nothing stops you moving to OCE once it reaches 1.0.

Before you pilot OCE

• Read the OpenClaw security guide first; OCE adds controls, it does not remove the need to understand the agent's reach.
• Clone only from the official openclaw organization.
• Pin a commit. Pre-1.0 means the APIs and resource models can change.
• Keep pilots off production credentials until your own review signs off on the sandbox profile.

OpenClaw Enterprise FAQ

Related guides

• OpenClaw security guide
• Hermes Agent on Kubernetes
• OpenClaw with Docker
• Managed vs self-hosted agents
• Hermes vs OpenClaw
• Managed Hermes hosting