Assistant Vanishes When Your Laptop Sleeps? Move the Gateway to a VPS
Your assistant should not go offline just because your laptop decided to take a nap.
This article shows how to move the Gateway to the cloud and keep your assistant online all day.
What You'll Learn
- Know where a Gateway can run
- Complete a basic VPS deployment
- Understand remote authentication
- Use Tailscale to build a safe private network
- Understand the difference between Gateway and Node
Where Can the Gateway Run?
| Location | Best for |
|---|---|
| Local computer | Personal testing and occasional use |
| VPS / cloud server | 24/7 availability |
| Home NAS / old PC | Always-on without VPS bills |
What Does VPS Installation Look Like?
Log into your VPS, preferably Ubuntu or Debian, then follow the Linux installation steps from docs.openclaw.ai. It is almost the same as a local install, just happening on a remote machine instead.
Remote Authentication Basics
Once the Gateway is on a VPS, OpenClaw still needs to confirm that you are an authorized user:
- You must use a token or device pairing
- If you see
unauthorized, checkgateway.bindand confirm the token is correct
Tailscale Is the Cleanest Option
Tailscale is a VPN that makes your phone, computer, and VPS feel like they are on the same private network:
- Install Tailscale on both your VPS and your own computer
- Set
gateway.bind: tailnet - Connect to the Gateway through Tailscale from any device
π‘ Tailscale can also expose HTTPS with Serve, which is usually much safer than exposing a raw port directly.
What Is a Node?
Here is the cool part: Gateway and Node can live on different machines.
- Gateway: runs on the VPS and handles conversations, memory, Telegram, and all the "brain" work
- Node: runs on your home computer and provides the "hands" such as browser control, local file access, and screen interaction
Real-world example: while you are outside, you message your assistant on Telegram and ask it to open a browser on your home PC and check a website. The Gateway sends the task to the Node at home, then returns the result to you.
How is this different from SSH?
With SSH, you log in and type the commands yourself. With a Node, the assistant does it for you, fully integrated with Skills, workspaces, and conversations.
Next Up
Once the Gateway lives on a VPS, your assistant is always on duty. Next, we let it work automatically with schedules.
β Previous: Multi-agent bindings | π Let your assistant work automatically with Cron