How to deploy OpenClaw: self-hosted Gateway vs managed hosting.
Want to deploy OpenClaw without getting stuck between setup docs, VPS questions, pricing decisions, and the “where do I actually start?” moment? This page compares the official self-hosted Gateway path with the faster GetClaw managed route, so you can choose a deployment path before you worry about billing or login.
Quick deployment chooser
| If you need... | Start with | Why |
|---|---|---|
| Full Linux and Gateway control | Self-hosted OpenClaw Gateway | Best fit when your team is comfortable operating the VPS, secrets, and backups. |
| Faster hosted deployment with less infra work | GetClaw managed hosting | Best fit when you want the private runtime shape without becoming the ops team first. |
| Just testing the workflow locally | Official quickstart | Best fit for learning and short demos before you commit to a persistent runtime. |
Clear promise
This page is for people who want to deploy OpenClaw, not just read about it. The managed path emphasizes speed to a private hosted workspace.
Clear evidence
The official path still requires Node.js, provider credentials, onboarding, a running Gateway, and channel setup. That is the operational work GetClaw compresses.
Clear next step
If you are evaluating cost, go to pricing. If you already have an account, go straight to login and continue inside your workspace.
The fastest managed path to deploy OpenClaw
Use this path when your goal is to get a private OpenClaw-ready workspace online, not to spend the first session operating Linux services, backups, secrets, and remote Gateway access.
Choose the deployment path
Pick BYOK if you already have a model provider key, or Pro if you want dedicated VPS hosting, included monthly credits, and stronger isolation from day one.
Set billing and access
Decide whether you will bring your own provider key or use included Pro credits, then keep the next action simple: new visitors compare pricing, returning users log in.
Launch the hosted workspace
Open the hosted workspace as your always-on place for terminal access, files, channel configuration, and OpenClaw-style agent workflows without first wiring your own VPS.
The official self-hosted OpenClaw path
The official quickstart is still the right reference when you want to install and operate OpenClaw yourself. It starts with Node.js, a provider key, onboarding, and a running Gateway, then continues into channel and runtime operations that you own.
Install OpenClaw
The official quickstart starts with Node.js, an OpenClaw install, and an API key from a model provider.
Run onboarding
OpenClaw onboarding helps choose a model provider, set credentials, configure the Gateway, and prepare a working chat session.
Start or supervise the Gateway
The Gateway is the WebSocket service that owns channels, nodes, sessions, hooks, and the control plane.
Connect channels
After the Gateway is running, connect chat channels such as Telegram, Discord, Slack, WhatsApp, Signal, iMessage, or WebChat.
Choose where your OpenClaw Gateway should run
Local machine
Learning, demos, and local-first workflows.
The Gateway depends on your laptop or workstation staying available.
Generic VPS
Teams comfortable running Linux services, secrets, updates, backups, and remote access.
You own uptime, state backups, Gateway hardening, and channel/runtime troubleshooting.
GetClaw managed hosting
Builders who want a private hosted OpenClaw workspace without becoming the server operator.
You still choose your provider-key strategy and agent workflow, but infrastructure is packaged for faster deployment.
Pre-deployment checklist
OpenClaw deployment gets smoother when the operational decisions are explicit before you connect channels or expose remote access.
A model provider key or GetClaw Pro credits.
A decision on local, VPS, or managed hosting.
A plan for channel credentials and access policies.
A backup strategy for state, workspace files, and credentials if self-hosting.
A security posture for remote Gateway access, SSH, and Control UI exposure.
Frequently asked questions
Can I really deploy OpenClaw in 3 minutes?
With GetClaw, the landing-page promise is a fast managed start to an OpenClaw-ready private workspace. The official self-hosted quickstart is still the right reference for learning and control, but it depends on your machine, provider key, and channel choices.
What does the official OpenClaw setup require?
The official docs list Node.js, an OpenClaw install, onboarding, provider credentials, and a running Gateway as the core pieces of a self-hosted setup.
Should I deploy OpenClaw on a VPS?
A VPS is a good fit when you want the Gateway online beyond your laptop and you are comfortable operating Linux services, secrets, backups, and secure remote access.
Does GetClaw replace OpenClaw?
No. OpenClaw is the self-hosted Gateway and agent communication layer. GetClaw is a managed hosting layer for running private OpenClaw-style workspaces online.
When should I click pricing vs login?
Use pricing when you are still choosing between BYOK and Pro or want to understand credits and hosting differences. Use login when you already have an account and want to continue deploying inside your existing workspace.
Ready to deploy OpenClaw on private infrastructure?
Start with pricing if you are choosing a plan, or log in if you already know you want to continue inside your hosted workspace.