OpenClaw

What is OpenClaw?

OpenClaw is the agent engine that runs under Clawga. It is an open-source runtime you (or we) spin up on your own cloud container — a little private computer that can reason, browse the web, run code, touch files, schedule work, and talk to other apps on your behalf.

Unlike a managed chatbot, OpenClaw gives you the whole box: the gateway, the workspace, the config, your SOUL.md and AGENTS.md, your long-running sessions, and the sockets that reach into Telegram, Slack, Discord, and more.

How Clawga uses it

When you upgrade to Clawga Pro, we auto-provision a private OpenClaw container for you in the cloud. Spins up in about ten seconds. Runs in its own VM with a persistent disk mounted at /data. Scales down to zero between sessions so you only pay for what you use.

Your Clawga app connects over a secure WebSocket gateway. Everything you see in chat — streaming tokens, tool calls, lifecycle events — flows through that socket in real time.

Architecture

Three pieces make up a running OpenClaw deployment:

• Wrapper server — boots, serves the /setup wizard, handles health checks, proxies the gateway.
• Gateway — the agent runtime itself. Handles chat, tools, sessions, and channel connectors.
• Persistent volume — /data holds your workspace: SOUL.md, AGENTS.md, long-term memory, task outputs, uploaded files.

Bring Your Own Keys (BYOK)

OpenClaw supports any major LLM provider: Anthropic, OpenAI, Google Gemini, Groq, OpenRouter, Moonshot, MiniMax. Plug your key into the Me tab of Clawga and the agent uses your credits for inference. Keys live as environment secrets on your container — never in your chat logs, never in our database.

Channels

Your OpenClaw can accept messages from Telegram, Discord, Slack, WhatsApp, Line, Signal, Twitch, Nostr and more. Each channel has its own config block; when you enable one the gateway spawns a connector that listens for mentions, DMs, or thread activity and replies in-place.

Self-hosting

Prefer to run it yourself? Deploy OpenClaw to your own cloud — one command, interactive prompts, takes a few minutes. Then point Clawga at your gateway URL and token from the Advanced tab. The app does not care who runs the runtime, as long as it speaks the OpenClaw WebSocket protocol.

Ownership

Everything inside your container is yours. SOUL.md, AGENTS.md, memory files, chat history, task outputs — all sit on your /data volume. Ask the agent for a tarball and it hands over the whole workspace. Cancel Clawga and the bytes still belong to you.