Solo operator
One gateway can be enough when one trusted operator controls the machine, environment, channels, and workspaces.
This page shows the setup flow, verification ladder, trust-boundary model, and handover expectations included in the paid A$99 OpenClaw Multi-Agent Deployment Kit.
The kit assumes you have terminal access, your own machine or VPS, and your own model-provider keys. The paid archive includes the actual config files, workspaces, docs, and bootstrap scripts.
~/.openclaw/openclaw.json.~/openclaw-workspaces.config/env.example and replace placeholders with your own keys.npm install -g openclaw@latest mkdir -p ~/.openclaw cp config/openclaw.json5 ~/.openclaw/openclaw.json mkdir -p ~/openclaw-workspaces cp -R workspaces/* ~/openclaw-workspaces/ source config/env.example openclaw config validate openclaw gateway install
openclaw status openclaw status --all openclaw gateway status --json openclaw health --json openclaw channels status --probe openclaw doctor openclaw security audit --json openclaw agents list --bindings
The paid kit is built around provable operating state. Before connecting real workflows, the operator runs the checks that expose gateway status, channel bindings, health output, and security posture.
Not sure if this is for you? Run the free readiness checklist first. If your current stack cannot produce evidence for these checks, the operating baseline is probably the next constraint.
The kit separates solo operation, trusted-team use, mixed-trust users, and public-facing agents so tool access and workspace state are not treated as one vague permission bucket.
One gateway can be enough when one trusted operator controls the machine, environment, channels, and workspaces.
Use peer DM scope, group allowlists, mention gating, and explicit channel bindings instead of broad access.
Split by gateway, config, state, and workspaces. Public agents should run with restrictive tools and narrow action scope.
The kit is designed so the operator can hand over proof, not just a folder. The paid docs include a handover path for configured client or internal systems.
The paid product is A$99 one-time. After buying, send your use case and the machine type you plan to use so the first-buyer guidance can point you at the cleanest first workflow.