Stop Fighting Config Files

Install Docker — OrbStack (recommended, free) or Docker Desktop on macOS, Docker Desktop with WSL2 on Windows, or Docker Engine on Linux. Then from your Zedly Setup dashboard, copy and run the one-command bootstrap shown for your OS (curl … | bash on macOS/Linux, irm … | iex in PowerShell on Windows). That single command pulls the latest Zedly OpenClaw image, creates the container, injects the session's SSH key, and opens a secure outbound tunnel back to Zedly — if the container already exists it just reconnects. Once connected, open the localhost:<port> link shown in the dashboard for the OpenClaw gateway UI (each instance gets its own host port so you can run multiple OpenClaws side-by-side). The Zedly setup agent then configures LLM providers, installs plugins, and verifies your first agent through the Setup chat. No SSH server on your host, nothing permanent installed, and docker stop ends the session at any time.

Yes. The Zedly OpenClaw container runs entirely on your hardware — no files are copied off your machine. The image is pinned and signed, pulled from GitHub Container Registry. The tunnel is outbound-only from inside the container to Zedly, so you never open an inbound port on your host. Every session uses a unique ed25519 SSH key that the bootstrap script injects into the container and that auto-revokes on the server when the session ends. The bootstrap token in the URL is one-time and session-scoped. The gateway UI binds only to localhost on your machine — each instance gets its own local port (never exposed to the internet). Every command the setup agent runs is logged to a per-session audit trail you can export. docker stop or docker rm cleanly disconnects and removes the container.

Anywhere Docker runs. macOS (Intel and Apple Silicon) via OrbStack (recommended, free) or Docker Desktop, Windows 10/11 via Docker Desktop with the WSL2 backend (the PowerShell bootstrap is native — no WSL shell required), and Linux via Docker Engine (Ubuntu, Debian, Fedora, and other major distributions). You do not need OpenSSH, Node, or any other tooling on your host — everything OpenClaw needs is inside the container.

A typical first-time session takes 15 to 30 minutes once the container is running. The first run includes pulling the container image (roughly 1–2 GB), which can add a few minutes on slower connections. The session itself covers LLM provider configuration, model routing, plugin install, gateway verification, and a test agent run. Complex setups with custom skills can take longer.

No. OpenClaw is already installed inside the Zedly container image along with Shield and the tunnel client. The only prerequisite is Docker — OrbStack or Docker Desktop on macOS, Docker Desktop with WSL2 on Windows, or Docker Engine on Linux. The one-command bootstrap from your Setup dashboard pulls the image, creates the container, and connects. Spin up additional isolated instances later from the same dashboard without touching your host OS.

Re-run the same one-command bootstrap from your Setup dashboard. The script checks GitHub Container Registry for a newer Zedly OpenClaw image, and if one is available it stops the old container, recreates it on the new image, and reconnects — all in one step. Your OpenClaw config, API keys, agent memory, and Shield settings are safe: they live in bind-mounted host folders (~/.zedly/containers/<instance>/.openclaw and ~/.codex), so the container can be replaced without touching your data. Want to test a new OpenClaw release without risking your main setup? Spin up a second instance from the dashboard — each instance gets its own config volume, so you can upgrade one while keeping the other on the stable version.

No. Each plan includes a monthly token allowance that covers the Zedly setup agent's LLM usage — Solo gets 2M tokens/mo, Consultant gets 10M, and Enterprise gets 100M. Allowances reset on your billing date and unused tokens do not roll over. If you hit the cap mid-month, either upgrade your plan (prorated at the next billing cycle) or contact sales to raise the Enterprise cap. Need help with a specific install? Buy a $99 Engineer Session — one-off credits that must be scheduled within 12 months of purchase.

A Zedly Setup subscription is the ongoing plan. Solo ($19/mo) covers up to 2 instances with Shield, the cloud dashboard, one standard workflow, and email support (48h). Consultant ($99/mo) adds multi-client fleet management, up to 15 instances, three workflows, and priority email and chat (24h). Enterprise ($999/mo) includes up to 250 instances, all marketplace workflows, SSO, audit-log export, and a dedicated support engineer with a 4h SLA. Need more than 250 instances? Contact sales to raise the cap. Need help one-off? Buy a $99 Engineer Session for stuck installs, migrations, or anything the dashboard agent can't handle alone.