Service type
OpenClaw service
OpenClaw gateway service for running agent workflows and connecting configured model and messaging integrations.
Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.
On Wodby
How OpenClaw runs on Wodby
wodby/openclaw image, which starts the OpenClaw gateway on port 18789.Generated configuration
On every start the container renders the template /etc/gotpl/openclaw.json.tmpl to ~/.openclaw/openclaw.json (OPENCLAW_CONFIG_PATH), from its environment variables. The result is rewritten on each start: never edit it. The template itself is the config file "OpenClaw config" of the service; edit it there to change anything the variables below do not cover.
What switches features on
| Variable on the service | Effect in the generated configuration |
|---|---|
OPENAI_API_KEY | adds the agents openai and openai-code |
ANTHROPIC_API_KEY | adds the agent claude |
GEMINI_API_KEY or GOOGLE_API_KEY | adds the agent gemini |
TELEGRAM_BOT_TOKEN | enables the Telegram channel |
DISCORD_BOT_TOKEN | enables the Discord channel |
The first provider present, in the order above, is the default agent. Models and workspaces of the agents have their own optional variables: OPENCLAW_OPENAI_MODEL, OPENCLAW_OPENAI_CODE_MODEL, OPENCLAW_CLAUDE_MODEL, OPENCLAW_GEMINI_MODEL, OPENCLAW_AGENTS_WORKSPACE and OPENCLAW_<AGENT>_WORKSPACE. Without a provider key the configuration has no agent list.
Access
- Port 18789 is the service's main HTTP endpoint and is not marked private, because Application Access serves only routable HTTP endpoints. The OpenClaw stack requires Private network access for the entire app, so its public route is suppressed from creation and the Control UI answers only on the provider's private address.
- A custom stack that uses this service without requiring Application Access gets a public address. The Control UI is an administration interface, so such a stack must require Application Access too.
- The service token
gateway_tokenis passed to the container asOPENCLAW_GATEWAY_TOKEN. Clients of the gateway and the Control UI authenticate with it. OPENCLAW_GATEWAY_CONTROLUI_ALLOWED_ORIGIN_JSONlists the origins allowed to open the Control UI: the service's primary route host, the service's address inside the cluster and the local address. OpenClaw also accepts a.ts.netaddress that matches the request's host.- The gateway binds to all interfaces of the container (
bind: "lan").
Open the Control UI
- Connect the device to the Access provider's private network.
- Open the address listed on the environment's Endpoints > Domains page.
- Paste
gateway_tokeninto Gateway secret. - A new browser waits for a one-time approval. In the container, run
openclaw devices list, thenopenclaw devices approve <requestId>. The page connects by itself.
Data
The data volume is mounted at /data, the OpenClaw state directory (OPENCLAW_STATE_DIR). Agent workspaces default to directories under ~/.openclaw/, which are outside that volume unless the workspace variables point elsewhere.
Changing configuration
Add or change environment variables on the service, or edit the "OpenClaw config" template, then deploy the service.
Check the result
openclaw health --json inside the container reports "ok": true when the gateway is up. The container's health command runs this check.
Overview
Technical profile and packaging
Versions
Source repository
Public Helm chart
Ports and protocols
Labels
Persistent volumes
Stacks
Use it inside ready-made stacks or your own
Runtime wiring
Reuse connectivity, storage, and runtime defaults
Endpoints
Technical domains
Volumes
Configs