OpenClaw

OpenClaw is best understood as a free, MIT-licensed, self-hosted personal AI assistant and multi-channel agent gateway, with active GitHub releases and npm distribution verified in June 2026. It is strongest for developers who want local control, messaging-channel automation, and extensible tools, not for buyers seeking a hosted SaaS plan.

Verified evidence is stronger than the original directory scrape suggested. The public GitHub repository at https://github.com/openclaw/openclaw exists under the openclaw organization and describes OpenClaw as a personal AI assistant that runs on a user's own devices. The README links to the current public website at https://openclaw.ai, documentation at https://docs.openclaw.ai, getting-started guides, security guidance, Docker documentation, onboarding documentation, and channel setup pages. The directory URL field remains https://openclaw.com as required by this record, but the repository itself points users to openclaw.ai as the official website.

Five substantial verified facts support the listing. First, the repository is public and contains the OpenClaw source tree, including docs, packages, extensions, apps, security materials, a Dockerfile, docker-compose.yml, package metadata, and release files. Second, package.json identifies the npm package name as openclaw, the repository as git+https://github.com/openclaw/openclaw.git, the license as MIT, and the CLI binary as openclaw. Third, the LICENSE file is an MIT License with a 2026 OpenClaw Foundation copyright notice, meaning the software code is available without a per-seat software subscription under that license, subject to the license conditions and without warranty. Fourth, the README verifies installation through npm, pnpm, or bun, with Node 24 recommended or Node 22.19+ supported, and recommends running openclaw onboard to configure the gateway, workspace, channels, and skills. Fifth, the GitHub releases page verifies recent release activity: release v2026.6.6 was published on June 12, 2026, with release verification links to npm package publication, registry tarball, integrity hash, release SHA, CI evidence, and publish workflows.

OpenClaw's practical positioning is local-first agent automation. The README says the Gateway is the control plane and lists supported channels including WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, IRC, Microsoft Teams, Matrix, Feishu, LINE, Mattermost, Nextcloud Talk, Nostr, Synology Chat, Tlon, Twitch, Zalo, Zalo Personal, WeChat, QQ, and WebChat. It also highlights multi-agent routing, voice wake and talk mode, Live Canvas, first-class tools such as browser, canvas, nodes, cron, sessions, Discord actions, and Slack actions, plus companion apps for Windows, macOS, iOS, and Android.

Pricing should be read carefully. The software itself is free in the sense that the public repository is MIT-licensed and distributed as an npm package, and no official paid SaaS plan or hosted subscription tier was found in the verified sources reviewed. There is no verified OpenClaw-hosted billing page, seat limit, monthly plan, annual discount, enterprise support package, SLA, or official paid support tier in the evidence. Users may still pay for infrastructure, messaging services, model providers, OAuth subscriptions, cloud hosting, devices, or third-party APIs. The README specifically notes model subscriptions such as OpenAI ChatGPT/Codex OAuth and says many providers and models are supported, so total operating cost depends on the user's chosen providers and deployment.

Security evidence is also more concrete. The README documents default DM pairing behavior for major messaging channels, local allowlist approval, a doctor command for risky DM policies, security documentation, a gateway exposure runbook, and sandboxing guidance. It also warns that tools run on the host for the main session by default and that non-main sessions can run inside sandboxes with Docker as the default backend and SSH or OpenShell alternatives. These are meaningful security controls, but they do not remove the need for a production review because an autonomous agent with messaging access, tool execution, filesystem access, browser access, and provider credentials can create serious operational risk if exposed or misconfigured.

The main differentiation is not just that OpenClaw is free. Its stronger verified differentiators are the combination of local-first operation, broad messaging-channel surface, CLI onboarding, active release train, MIT licensing, npm distribution, multi-agent routing, and explicit security/sandboxing documentation. OpenClaw is most appropriate for technical users willing to operate and secure their own agent gateway. It is less appropriate for nontechnical teams that need a managed vendor contract, hosted admin console, guaranteed support response, audited compliance package, or predictable all-in monthly pricing.