OpenClaw

OpenClaw is a self-hosted AI assistant and gateway for developers, power users, and teams. A single Gateway process runs on the user’s machine or server and connects supported chat channels such as WhatsApp, Telegram, Discord, Slack, Signal, iMessage, and WebChat to an AI agent. The project is model-agnostic: users can bring a hosted provider, a subscription-backed model, or a local model, and can route different agents to different providers. OpenClaw keeps its workspace and session state on the user’s infrastructure, offers a browser Control UI and device nodes, and supports tools, skills, memory, plugins, cron jobs, hooks, and webhooks. It is software to operate yourself, not a hosted SaaS with a vendor-managed free tier.

✨ Key Features

• Self-hosted Gateway — Run the always-on control plane on a Mac, Linux machine, Windows/WSL2 environment, VPS, or other supported host.
• Multi-channel messaging — Connect WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Google Chat, Microsoft Teams, WebChat, and additional channel plugins from one Gateway.
• Model-agnostic providers — Bring hosted or local models from providers such as Anthropic, OpenAI, Google, OpenRouter, and others, with per-agent routing and failover.
• Local-only option — Use local model services when the workflow must keep data on the user’s own device or network.
• Agent sessions and memory — Maintain stateful sessions, workspaces, context, and memory across conversations and channels.
• Multi-agent routing — Isolate agents by channel, sender, workspace, account, or task, with separate defaults and access boundaries.
• Tool use and coding workflows — Give agents access to configured tools and coding-agent capabilities so they can work on tasks rather than only answer questions.
• Skills system — Load repeatable procedures on demand and build reusable skills for personal or team workflows.
• Automation — Schedule work with cron jobs, hooks, and webhooks, and connect event-driven tasks to the Gateway.
• Control UI and dashboard — Use the browser dashboard for chat, configuration, sessions, nodes, and Gateway operations.
• Mobile and device nodes — Pair iOS and Android nodes for camera, screen, voice, and device-action workflows where configured.
• Media and plugin extensibility — Send and receive images, audio, and documents; build or install channel, provider, and tool plugins through the plugin SDK and ClawHub ecosystem.

💳 Pricing

• OpenClaw software — Free and open source; the official site says there is no subscription, hosted tier, or token fee for OpenClaw itself.
• Model provider costs — Hosted model API or subscription costs are separate and depend on the provider, model, input/output usage, and account terms.
• Local models — Local inference can avoid hosted model API charges but still requires suitable hardware, electricity, storage, and maintenance.
• Hosting and operations — Running a VPS, cloud server, desktop, or other always-on host creates infrastructure costs that OpenClaw does not include.
• Plugins and skills — Review each third-party plugin or ClawHub skill’s trust, permissions, license, and any separate service charges before installing it.

The project’s “no subscription” statement does not mean the complete deployment is cost-free. Confirm provider billing, model data-retention settings, network exposure, hardware requirements, channel terms, and any hosted infrastructure costs. OpenClaw’s independent foundation stewardship and no-telemetry-by-default claims should be checked against the current documentation and the exact build/configuration in use.

⚖️ Alternatives Compared

🎯 Use Cases

• Personal messaging assistant: Reach an assistant from WhatsApp, Telegram, Discord, Slack, or another connected channel.
• Inbox and calendar workflows: Use configured tools or skills to organize messages, manage calendars, and perform approved actions.
• Coding from chat: Send development tasks to an agent that can use repository tools and maintain a stateful session.
• Team gateway: Run a shared Gateway for trusted teammates with named sessions, routing, and role boundaries.
• Local/private automation: Use local models and a local Gateway for workflows that should not pass through a hosted SaaS.
• Scheduled operations: Run recurring reports, maintenance, reminders, or data tasks with cron and event hooks.
• Device-assisted workflows: Pair mobile nodes for voice, camera, screen, and other device actions when permissions are granted.
• Custom integrations: Build channel, provider, or tool plugins and connect internal systems through the SDK, MCP, webhooks, or RPC surfaces.
• Media-aware assistance: Send images, audio, or documents to a configured agent for analysis or workflow handling.

OpenClaw can act on external systems, so treat it as an automation control plane rather than a passive chatbot. Start with allowlists, mention rules, least-privilege credentials, isolated gateways for mutually adversarial users, and a review step for high-impact actions. Audit installed skills and plugins, protect the Gateway from public exposure, and verify model-provider retention and outbound network behavior before using private or regulated data.