AI Wiki

Explore AI Wiki

Citation and evidence

OpenClaw Enterprise

20 min full readUpdated 37 references

This article's verification

Report a problem with this article

More

Use this article

Raw MarkdownExplore connections

Improve this page

Suggest editRevision historyDiscussion

Browse categories

AI AgentsAI InfrastructureEnterprise AIOpen Source AI

Cite this article

OpenClaw Enterprise (OCE) is an open-source control plane for deploying, governing and auditing persistent AI agents on an organization's own infrastructure. The OpenClaw Foundation announced it on 29 September 2026, describing it as "an open source, vendor neutral platform for managing persistent agents in sensitive environments" and naming Red Hat, NVIDIA and OpenAI as collaborators.[1][2] The project's README calls it "Kubernetes for agents".[3] Its core component, the OpenClaw Control Plane (OCC), adds multi-tenancy, governance and hard security boundaries to deployments of OpenClaw agents, and it can also run agents on OpenAI's Codex harness.[4][14]

According to the Foundation, OCE "originally started at OpenAI and then was donated to the OpenClaw Foundation", where it is now an independent project developed with Red Hat and NVIDIA.[1] The code is published under the MIT License, and the Foundation says OCE "will always be free for any organization to use".[1][27] As of 30 September 2026 the project is pre-1.0: the Foundation says it is suitable for "internal pilot workloads", with a 1.0 release planned for "later this year" and a security reference architecture promised "in the coming weeks".[1]

AttributeDetail
TypeControl plane for persistent AI agents
StewardOpenClaw Foundation[1]
OriginStarted at OpenAI, donated to the OpenClaw Foundation[1]
Collaborators named at launchRed Hat, NVIDIA, OpenAI[1][2]
Announced29 September 2026[1][2]
Repositorygithub.com/openclaw/openclaw-enterprise (created 29 August 2026 per the GitHub API)[23]
Documentationdocs-enterprise.openclaw.org[4]
LicenseMIT (copyright line: "Copyright (c) 2026 OpenAI")[27]
Package version0.1.0 in package.json; no tagged GitHub releases as of 30 September 2026[36][23]
LanguagesJavaScript per GitHub's classification; the occ command-line tool is written in Go[23][3]
Deployment targetsKubernetes (local k3d or an existing cluster); Docker/Podman Compose preview for control-plane development only[3][7]
Status (30 September 2026)Pre-1.0; recommended for internal pilot workloads[1]

Expanded article table

Background

OpenClaw is an open-source personal agent that Peter Steinberger started as a weekend project in Austria; the OpenClaw Foundation was introduced on 8 July 2026 as a 501(c)(3) non-profit meant to keep it "MIT licensed, open, and independent".[22] The Foundation's launch post said it had convened councils on "agent identity, agent profiles, evals, and enterprise deployment", and listed OpenAI, NVIDIA, Microsoft, the University of Michigan, Red Hat, Tencent and Atlassian among its partners.[22]

In the OCE announcement, Kevin Lin wrote that almost a year after OpenClaw's launch "the actual deployment of persistent agents remains limited", because organizations want a stronger common security, safety and governance standard first. He added that, as a result, "the default stance of IT in most organizations is to ban agentic platforms like OpenClaw altogether."[1] The post framed OCE's goal as a question: "how do we safely deploy powerful agents without nerfing their capabilities in enterprise environments?"[1]

Announcement

The OpenClaw account announced the project on X on 29 September 2026, saying that "in collaboration with @RedHat, @nvidia and @OpenAI the OpenClaw Foundation is open sourcing a powerful enterprise control plane for persistent agents", and that OCE "is built to run on your own infrastructure and will always be free for an organization to use."[2] The accompanying blog post, "OpenClaw Enterprise - The Open Agent Platform", was written by Kevin Lin.[1]

Red Hat published a companion post the same day by Joe Fernandes, vice president and general manager of its AI Business Unit, titled "Why Red Hat is building an open foundation for enterprise agents with OpenClaw Enterprise".[19] NVIDIA's @NVIDIAAI account followed early on 30 September (UTC) with a post saying organizations "can use NVIDIA OpenShell as an open source option for governing agents with OpenClaw Enterprise."[21]

Provenance and development

The Foundation's account of the project's origin is that it "originally started at OpenAI and then was donated to the OpenClaw Foundation, where it is now an independent project and has been further developed in collaboration with Red Hat and NVIDIA."[1] Red Hat's post describes Kevin Lin as the person "who leads OpenClaw Enterprise efforts at OpenAI".[19] Lin also wrote the Foundation's July 2026 post introducing extended-stable OpenClaw releases and a feature maturity scorecard, both aimed at users running OpenClaw for critical workloads.[34]

The repository itself records this history:

  • The GitHub API gives the repository's creation time as 29 August 2026.[23] The earliest commit, "Initial OpenClaw Enterprise release", is dated 31 August 2026, is authored under an OpenAI email address, and adds 249 files.[24]
  • The architecture document names Kevin Lin as its author and carries a front-matter creation date of 8 July 2026.[6]
  • The LICENSE file carries the line "Copyright (c) 2026 OpenAI".[27]
  • The repository was private before launch. A commit on 29 September 2026 removed "stale private-repository wording" from the contribution and security guides, noting that "The repository is public".[25]

As of the latest commit on 30 September 2026 (01:49 UTC), the main branch held 1,870 commits.[35] Most were authored under openai.com addresses. Other contributors used redhat.com and nvidia.com addresses, and Foundation engineers Vincent Koc and Dallin Romney also appear.[35][22] OpenClaw creator Peter Steinberger wrote the bundled SSH Compute Driver for plain Linux hosts, committed on 5 September 2026 (US Pacific time; 6 September UTC).[26]

Architecture

Control plane and data plane

OCE separates a control plane from a data plane. The OpenClaw Control Plane (OCC) configures and manages Agent deployments: its API authorizes resource changes, and a separate worker uses Drivers to provision and update workloads asynchronously. The data plane handles Agent conversations and execution. Deploying an Agent is a control-plane operation; processing a message is data-plane work.[5]

The architecture document lists the implemented parts as an HTTP API, a browser console at /console/, a durable worker, PostgreSQL persistence and Kubernetes packaging. PostgreSQL stores platform state, IAM policy, controller work and audit evidence.[6] Rather than making one OpenClaw gateway multi-tenant, "OCC manages multiple single-Agent runtimes": each deployed Agent gets its own gateway and revision history.[6] The repository splits the code into a controller app (API, console, worker and Drivers) and separate packages for resource contracts, lifecycle and persistence, IAM, and audit, plus a Go CLI.[3]

Resources

ResourceRole
InstallationOne deployment of the platform; each deployment owns exactly one.[5][6]
NamespaceGroups and isolates Agents, Configurations and credentials; the logical tenant boundary.[5]
AgentA persistent workload definition with its own identity; creating it does not start a process.[5]
AgentRevisionAn immutable snapshot of an Agent's configuration and execution settings, created on each deploy. Editing an Agent does not change the running revision.[5]
ConfigurationReusable native OpenClaw settings stored in a Namespace.[5]
SecretA sensitive value stored separately from Configuration; OCC returns metadata, not the value.[5]
PresetA reusable Agent template with variables that users fill in from the console.[31]
Principal / ServicePrincipalIdentities for people and for automation; each Agent has its own ServicePrincipal.[5]
Role, AccessBinding, RestrictionA Role defines permissions, an AccessBinding grants a Role within a scope, and a matching Restriction denies access.[5]

Expanded article table

Deploying an Agent follows a fixed sequence: authorize and create the Namespace, have the worker reauthorize and prepare infrastructure, snapshot the admitted inputs into a revision, prepare the runtime and check readiness, then activate the new revision and retire the old one.[6]

Gateways and Harnesses

Each deployed Agent has a gateway, which handles client connections and messages, and a Harness, which executes Agent turns and tools.[5] The documentation lists these combinations:

HarnessExecution modeSupport (30 September 2026)
OpenClawembeddedGateway and Harness run in one workload; available on Kubernetes and SSH. This is the default for new Agents.[14]
CodexdedicatedThe gateway connects to a separate Codex Harness workload; available on Kubernetes.[14]
OpenClawdedicatedExperimental; requires Sandbox provisioning, and stock OpenShell has upstream blockers, so it is "not a supported production path".[14]

Expanded article table

In dedicated execution, the gateway runs in a control-plane runtime namespace with its own identity and private storage, while the Harness stays in a data-plane namespace. Only the model-executing Harness receives the model credential; the dedicated gateway does not.[6][14]

Drivers and Backends

Drivers connect OCE to infrastructure. An Installation operator picks one implementation for each capability, and individual Agents cannot choose their own Drivers.[11] The blog post says OCE is designed so that "core primitives like the harness, model, and sandbox can be swapped out with third party solutions as well as internal implementations."[1] The bundled implementations documented at launch were:

DriverUseLimits at launch
Kubernetes ComputeRuns embedded OpenClaw or dedicated Codex Agents; the recommended starting pointManaged ChatGPT credentials require dedicated Codex[11][10]
Kubernetes SecretStores and delivers OCC SecretsRequired even when SSH Compute is selected[11]
SSH ComputeRuns embedded OpenClaw on operator-managed Linux/systemd hostsNo dedicated Codex or OCC-managed model credentials[11]
Docker/Podman ComputeRuns the local Compose control plane for developmentCannot deploy new Agents under current authentication[11]
OpenShell SandboxDedicated Harness sandboxing through NVIDIA OpenShellProduction Agent deployment unsupported[11][12]
OpenShell Credential GatewayKeeps the dedicated Codex OpenAI API key outside the HarnessOnly the openai source type; no update or rotation[11]

Expanded article table

A separate, experimental Backend abstraction gives related Drivers an authenticated client. The bundled ChatGPT Backend issues ChatGPT service-account credentials for dedicated Codex Agents; it manages accounts and does not route inference.[5][33] The documentation keeps this separate from an Agent's Provider and Model selection.[5]

Channels, plugins and presets

A dedicated Codex Agent can be connected to a Slack workspace through Socket Mode. Slack credentials go to the Agent's gateway rather than the Harness, and embedded OpenClaw is not supported for this because it "cannot isolate channel credentials from the Harness".[32] Plugins are selected per Agent. Embedded OpenClaw supports a bundled Diffs plugin, and dedicated Codex can use selected apps from Codex's curated catalog.[18] The default Namespace ships with two Presets, "Standard Codex" (dedicated Codex) and "Standard OpenClaw" (embedded OpenClaw).[7][31]

Deployment

The Foundation says organizations can "self host OCE today by cloning the repo", using docker-compose for local development and Kubernetes for internal deployment.[1] The repository docs add a caveat: running occ dev up with no profile selected starts "a Compose control-plane preview that cannot deploy Agents". Local Agent deployment requires explicitly selecting a Kubernetes-only profile.[3][7]

Local setup. The quickstart runs OCC, PostgreSQL and Agent workloads in a local Kubernetes cluster created with k3d, on Linux or macOS. It requires Docker Engine (or Podman), k3d, kubectl, Helm, Go, Node.js 24 or later, pnpm, and about 20 GB of free container-engine storage for the first build.[7] Installation needs no model credential. The first-Agent walkthrough then needs an OpenAI API key that can use gpt-6-astra, "the default model", which can be overridden with another model ID.[8] That walkthrough creates an embedded OpenClaw Agent that answers model prompts only, with tools and the native admin UI disabled.[8]

Existing cluster. A production-style install needs Kubernetes 1.35 or later with a network plugin that enforces NetworkPolicies, Envoy Gateway, Gateway API CRDs and cert-manager, external PostgreSQL with separate application and migration roles and verified TLS, and a container registry reachable by the cluster. The Helm chart does not create public Ingress or TLS.[9] A separate guide covers Amazon EKS.[9]

Security model

The blog post calls security "the primary focus of OpenClaw Enterprise" and says OCE "combines hard boundaries between trusted and untrusted workloads with sandboxing, LLM-based reviews, and fine-grained permissions."[1] The published documentation describes these mechanisms as follows.

Trusted and untrusted workloads. The architecture document says operators "must configure disjoint trusted Gateway and untrusted Harness node pools" and that namespace separation alone does not provide node isolation.[6] Embedded OpenClaw "remains one untrusted data-plane workload".[14]

Kubernetes hardening. The Kubernetes Compute Driver requires the restricted Pod Security level on every tenant namespace. Each tenant namespace also gets a ResourceQuota, a LimitRange, and default-deny ingress and egress NetworkPolicies. A gateway "cannot connect to another Agent in the same Namespace".[17] The docs describe a temporary Agent-only TCP/443 internet egress exception, which excludes private ranges and cloud metadata addresses, and say it should be replaced with an approved model egress proxy "before treating destination isolation as complete".[17]

Identity and access. Signing in identifies a caller but does not grant access. OCC checks each action against the caller's current permissions on the exact Installation, Namespace or resource, and a matching Restriction overrides a grant.[15] Each Agent has its own Namespace-scoped ServicePrincipal and "does not inherit its creator's permissions".[5][15] People sign in with administrator-provisioned accounts, optionally through GitHub or Google for enrolled users; public signup and generic OIDC are not supported.[15]

Secrets. OCC returns Secret metadata, never the value. Secret values are kept out of resource responses, revisions and audit records.[5][6] The architecture document notes that model credentials still reach the executing Harness, and that same-cluster Codex transport uses a capability token over ws:// rather than mutually authenticated TLS.[6]

Review of agent actions. Plugin tool policies set when review is required: all_actions, write_actions, none, or a provider default. They also set who reviews, human or auto. For Codex, auto maps to Codex's native auto_review setting, and "Automatic review can deny a call."[18]

Sandboxing. A Sandbox Driver can add network, filesystem and process restrictions to a dedicated Harness. Selecting a Sandbox is optional and "does not add per-tool authorization or guarantee that every command is approved before it runs."[13] The only bundled Sandbox integration is OpenShell (see below).[13]

Audit. OCC records audit events for bootstrap, successful resource changes, authorization denials and lifecycle completions such as activating a revision. Events are stored in PostgreSQL.[16] The audit log is not a record of all reads, prompts or model responses. At launch there was no console view or public API to browse or export audit events, and no configurable retention.[16]

Fail-closed behavior. The design's safeguards chapter says OpenClaw fails closed when a required boundary or dependency fails, such as identity verification, authorization, sandbox support or gateway readiness. If a candidate revision fails before cutover, the previous active revision, workload and route stay unchanged; a failure during or after cutover keeps the previous workload but leaves routing disabled until a route can be verified.[37]

The architecture document lists several parts of the design as not yet implemented: external access-gateway admission, workload-token authentication to OCC, and general credential-free model inference.[6]

NVIDIA OpenShell integration

NVIDIA OpenShell is NVIDIA's open-source sandbox runtime for agents. NVIDIA's launch-day post presented it as "an open source option" for governing agents with OCE.[21] OCE bundles an OpenShell Sandbox Driver and an OpenShell Credential Gateway, but as of 30 September 2026 its documentation describes the integration as "a work in progress" and states that production Agent deployment through it is unsupported.[12][11] The documentation says stock OpenShell v0.1.0, released by NVIDIA on 25 September 2026, "cannot accept the Secret-backed app-server token or projected workload identity a dedicated Agent requires", so the OCE driver rejects the deployment instead of starting a wrongly credentialed Harness.[12][30]

The OCE docs list upstream OpenShell capabilities "being worked on" before production use. These include creating Sandboxes with the per-Agent Kubernetes ServiceAccount, keeping projected ServiceAccount tokens and approved workspace mounts, and carrying bearer authorization through OpenShell's service routing.[12] When OpenShell is selected, it becomes the outer containment boundary; for dedicated Codex the driver sets the inner Codex app-server sandbox to danger-full-access to avoid stacking one sandbox inside another. OpenShell isolates a whole AgentRevision from other workloads but "does not isolate mutually untrusted sessions within one Agent".[12] OpenShell is not required: the quickstart and first-Agent walkthrough explicitly run without a Sandbox Driver.[7][8]

Partners and pilots

OpenAI. The Foundation says OCE is being piloted internally at OpenAI and that "OpenAI is already running OpenClaw agents with full access to codebases and plugins."[1] The post quotes RJ Marsan, a member of OpenAI's technical staff, on an internal agent called Androidclaw: "Our internal enterprise agent Androidclaw has really been well-adopted by our team", and "Alert about a broken build? Androidclaw finds the PR and can quickly fix it." He called its ability to trace a problem, publish a PR and merge it "Kinda game changing."[1] Kevin Lin, quoted by Red Hat, said "Enterprises want the flexibility and innovation of open source with the governance, security, and reliability they expect from enterprise software."[19]

Red Hat. The Foundation lists Red Hat as an internal pilot site. Red Hat says it looks forward to deploying OCE "to orchestrate internal agent deployments" and is putting engineers behind the OpenClaw Foundation, which it sponsors.[1][19] Fernandes described an "open control plane for agents" as an emerging layer of the enterprise AI stack. He compared the effort to Red Hat's history with Linux and with Kubernetes through Red Hat OpenShift, and said Red Hat intends to work with OpenAI, NVIDIA and the community "to help establish open standards".[19] An earlier Red Hat post, on 9 September 2026, said Red Hat joined the Foundation as a sponsor when it was announced in July. It named Red Hat engineer and OpenClaw maintainer Sally O'Malley as the lead of its upstream work.[20]

NVIDIA. The Foundation credits NVIDIA as a development collaborator, and NVIDIA positions OpenShell as an optional governance runtime alongside OCE.[1][21]

License and the "always free" pledge

The code license and the Foundation's pricing pledge are separate things. The repository is released under the MIT License, and third-party components keep their own licenses.[3][27] Separately, the Foundation pledges that OCE "will always be free for any organization to use".[1] Red Hat's post says both OpenClaw and OCE "are fully open source".[19] VentureBeat noted that enterprises would still pay for their own compute, models, storage and operational infrastructure.[28]

Status and roadmap

DateEvent
8 July 2026OpenClaw Foundation introduced; the OCE architecture document carries the same creation date[22][6]
29 August 2026GitHub repository created[23]
31 August 2026First commit, "Initial OpenClaw Enterprise release"[24]
5 September 2026Peter Steinberger's SSH Compute Driver committed[26]
9 September 2026Red Hat describes its OpenClaw Foundation sponsorship[20]
25 September 2026NVIDIA releases OpenShell v0.1.0, the version OCE's OpenShell docs target[30][12]
29 September 2026OCE announced; repository made public[1][2][25]
30 September 2026NVIDIA posts about using OpenShell with OCE[21]
"Coming weeks" (announced 29 Sep 2026)Reference architecture showing how OCE's protections work together[1]
"Later this year" (announced 29 Sep 2026)OCE 1.0 release[1]

Expanded article table

The Foundation describes OCE as something organizations can use "for internal pilot workloads" and says it open-sourced the code early "to build in the open and co-develop with the wider community ahead of the 1.0 release".[1] It adds: "We are early, and there is much more work ahead."[1] At 02:02 UTC on 30 September 2026, the repository had 87 stars, 11 forks and 95 open issues and pull requests, with no tagged releases.[23]

Relationship to OpenClaw, NemoClaw and OpenShell

ProjectStewardWhat it is
OpenClawOpenClaw FoundationThe open-source personal agent that OCE deploys as its embedded Harness and gateway[22][14]
OpenClaw EnterpriseOpenClaw FoundationThe multi-tenant control plane that deploys, governs and audits many OpenClaw or Codex agents[1][5]
NVIDIA NemoClawNVIDIADescribed by the Foundation as a one-command install of OpenClaw with open Nemotron models and the OpenShell secure runtime[22]
NVIDIA OpenShellNVIDIAA sandbox runtime that OCE can use as an optional, currently non-production Sandbox Driver[12][21]

Expanded article table

OCE does not replace OpenClaw. The docs describe OCC as adding multi-tenancy, governance and security boundaries "to OpenClaw agent deployments", and OCE Configurations store native OpenClaw settings.[4][5] VentureBeat described OCE as sitting "above" runtime protections such as OpenShell, "providing the organizational control plane for deploying and governing agents at scale."[28]

Reception

VentureBeat called the project's provenance "particularly notable" and wrote that the hard problem for enterprises "is increasingly not whether an AI model can execute a task, but whether a company can safely let hundreds or thousands of persistent agents touch production systems".[28] It contrasted OCE with the lightweight runtime NanoClaw and the commercial control plane Runlayer. It also compared OCE with the Dots agents and ChatGPT Space that OpenAI announced at DevDay the same day, calling the OpenAI products "more complementary than directly competitive" with OCE.[28] VentureBeat also stressed that "Despite the 'Enterprise' name, OpenClaw is not presenting OCE as finished production infrastructure yet."[28] Crypto Briefing summarized the launch as turning a personal AI tool into something an enterprise IT team could deploy, and noted the lack of paid tiers or hosted services.[29]

See also

References

  1. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13 ^14 ^15 ^16 ^17 ^18 ^19 ^20 ^21 ^22 ^23 ^24 ^25 ^26 ^27Kevin Lin, "OpenClaw Enterprise - The Open Agent Platform", OpenClaw Blog, 29 September 2026. openclaw.ai/...openclaw-enterprise
  2. ^1 ^2 ^3 ^4 ^5OpenClaw (@openclaw), "Today we're announcing OpenClaw Enterprise", X, 29 September 2026. x.com/...2105023990607786313
  3. ^1 ^2 ^3 ^4 ^5 ^6OpenClaw Foundation, "OpenClaw Enterprise" (README), GitHub, accessed 30 September 2026. github.com/...openclaw-enterprise
  4. ^1 ^2 ^3OpenClaw Enterprise documentation, "OpenClaw Enterprise" (overview), accessed 30 September 2026. docs-enterprise.openclaw.org
  5. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13 ^14 ^15 ^16OpenClaw Enterprise documentation, "OpenClaw Enterprise concepts", accessed 30 September 2026. docs-enterprise.openclaw.org/...concepts
  6. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11OpenClaw Enterprise documentation, "OpenClaw Enterprise architecture" (Kevin Lin; last updated 29 September 2026). docs-enterprise.openclaw.org/design
  7. ^1 ^2 ^3 ^4 ^5OpenClaw Enterprise documentation, "Set up OpenClaw Enterprise locally", accessed 30 September 2026. docs-enterprise.openclaw.org/...quickstart
  8. ^1 ^2 ^3OpenClaw Enterprise documentation, "Deploy your first Agent", accessed 30 September 2026. docs-enterprise.openclaw.org/...first-agent
  9. ^1 ^2OpenClaw Enterprise documentation, "Set up OpenClaw Enterprise on Kubernetes", accessed 30 September 2026. docs-enterprise.openclaw.org/...kubernetes-setup
  10. ^OpenClaw Enterprise documentation, "Integrations overview", accessed 30 September 2026. docs-enterprise.openclaw.org/...integrations
  11. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8OpenClaw Enterprise documentation, "Drivers overview", accessed 30 September 2026. docs-enterprise.openclaw.org/...drivers
  12. ^1 ^2 ^3 ^4 ^5 ^6 ^7OpenClaw Enterprise documentation, "OpenShell SandboxDriver", accessed 30 September 2026. docs-enterprise.openclaw.org/...openshell-sandbox
  13. ^1 ^2OpenClaw Enterprise documentation, "Sandbox", accessed 30 September 2026. docs-enterprise.openclaw.org/...sandbox
  14. ^1 ^2 ^3 ^4 ^5 ^6 ^7OpenClaw Enterprise documentation, "Harness execution", accessed 30 September 2026. docs-enterprise.openclaw.org/...harness-execution
  15. ^1 ^2 ^3OpenClaw Enterprise documentation, "IAM overview", accessed 30 September 2026. docs-enterprise.openclaw.org/...iam
  16. ^1 ^2OpenClaw Enterprise documentation, "Audit log", accessed 30 September 2026. docs-enterprise.openclaw.org/...audit-log
  17. ^1 ^2OpenClaw Enterprise documentation, "Kubernetes security controls", accessed 30 September 2026. docs-enterprise.openclaw.org/...security
  18. ^1 ^2OpenClaw Enterprise documentation, "Agent plugins", accessed 30 September 2026. docs-enterprise.openclaw.org/...agent-plugins
  19. ^1 ^2 ^3 ^4 ^5 ^6Joe Fernandes, "Why Red Hat is building an open foundation for enterprise agents with OpenClaw Enterprise", Red Hat Blog, 29 September 2026. redhat.com/...nterprise-agents-openclaw-enterprise
  20. ^1 ^2Stephen Watt, "Red Hat sponsors the OpenClaw Foundation to advance an open future for production AI agents", Red Hat Blog, 9 September 2026. redhat.com/...nce-open-future-production-ai-agents
  21. ^1 ^2 ^3 ^4 ^5NVIDIA AI (@NVIDIAAI), "Congrats to the OpenClaw community on OpenClaw Enterprise!", X, 30 September 2026. x.com/...2105090691806474350
  22. ^1 ^2 ^3 ^4 ^5 ^6Dave Morin and Peter Steinberger, "Introducing the OpenClaw Foundation", OpenClaw Blog, 8 July 2026. openclaw.ai/...introducing-openclaw-foundation
  23. ^1 ^2 ^3 ^4 ^5 ^6GitHub REST API, repository metadata for openclaw/openclaw-enterprise, retrieved 30 September 2026 02:02 UTC. api.github.com/...openclaw-enterprise
  24. ^1 ^2kevinlin-openai, "Initial OpenClaw Enterprise release" (commit 6f7be46), openclaw/openclaw-enterprise, GitHub, 31 August 2026. github.com/...e4679e504623ad16415e144a5034ee06b371
  25. ^1 ^2Nathan DeMoss, "docs: drop stale private-repository wording" (commit f8833f9), openclaw/openclaw-enterprise, GitHub, 29 September 2026. github.com/...3f954109d6b504e150d50eca8d4e71864357
  26. ^1 ^2Peter Steinberger, "feat(compute): add bundled SSH Compute Driver for raw Linux hosts" (commit 5d10ba0), openclaw/openclaw-enterprise, GitHub, 5 September 2026. github.com/...ba01a4516cd18fce03f302e80bfdc106a5e1
  27. ^1 ^2 ^3 ^4openclaw/openclaw-enterprise, "LICENSE" (MIT License), GitHub. github.com/...LICENSE
  28. ^1 ^2 ^3 ^4 ^5"OpenClaw launches free enterprise control plane for persistent AI agents, backed by OpenAI, Red Hat and Nvidia", VentureBeat, 30 September 2026. venturebeat.com/...ed-by-openai-red-hat-and-nvidia
  29. ^Diego Almada Lopez, "OpenClaw launches free enterprise control plane for AI agents", Crypto Briefing, 29 September 2026. cryptobriefing.com/...prise-ai-agent-control-plane
  30. ^1 ^2NVIDIA, "OpenShell v0.1.0" (release), NVIDIA/OpenShell, GitHub, 25 September 2026. github.com/...v0.1.0
  31. ^1 ^2OpenClaw Enterprise documentation, "Presets" reference, accessed 30 September 2026. docs-enterprise.openclaw.org/...presets
  32. ^OpenClaw Enterprise documentation, "Connect an Agent to Slack", accessed 30 September 2026. docs-enterprise.openclaw.org/...slack
  33. ^OpenClaw Enterprise documentation, "Use the ChatGPT Backend (experimental)", accessed 30 September 2026. docs-enterprise.openclaw.org/...chatgpt
  34. ^Kevin Lin, "On the Road to LTS: Extended-Stable Releases and the Maturity Scorecard", OpenClaw Blog, 30 July 2026. openclaw.ai/...le-releases-and-maturity-scorecards
  35. ^1 ^2openclaw/openclaw-enterprise, commit history of the main branch (head ed69e6e, 30 September 2026), GitHub. github.com/...main
  36. ^openclaw/openclaw-enterprise, "package.json", GitHub. github.com/...package.json
  37. ^OpenClaw Enterprise documentation, "Secrets, failure behavior, and platform invariants" (design chapter), accessed 30 September 2026. docs-enterprise.openclaw.org/...safeguards

Improve this article

Add missing citations, update stale details, or suggest a clearer explanation. Every suggestion is reviewed for sourcing before it goes live.

1 revision · v2 · 4,085 words · full history

Fact-checks are independent of edits: a reviewer re-verifies the article against its sources and stamps the date. How we verify

Research and drafting on this wiki are AI-assisted, under named human editorial standards. How AI is used here

Reviewer note: Independent verification V1 (xg13, 30 Sep 2026): ~115 claims checked vs cloned repo, docs site, OpenClaw/Red Hat posts, tweets, press; 0 material, 6 minor fixed

Cite this page: AI Wiki. "OpenClaw Enterprise." aiwiki.ai, updated 30 Sept 2026, fact-checked 30 Sept 2026. CC BY 4.0. https://aiwiki.ai/wiki/openclaw_enterprise

Suggest edit