What Is Remote Gateway
OpenClaw's Remote Gateway feature lets you run Gateway nodes in different network environments and connect them to a central control plane. This is useful for multi-region deployments, cross-network access, and high-availability architectures.
Architecture Overview
- Primary Gateway: Central node managing configuration and routing
- Remote Gateway: Nodes deployed in other networks
Remote nodes communicate with the primary node via secure connections.
Configure the Primary Gateway
{
"gateway": {
"remote": {
"enabled": true,
"listenPort": 3100,
"authToken": "{{REMOTE_AUTH_TOKEN}}",
"tls": { "enabled": true, "cert": "/path/to/cert.pem", "key": "/path/to/key.pem" }
}
}
}
Configure a Remote Gateway
{
"gateway": {
"mode": "remote",
"primaryUrl": "https://primary-gateway.example.com:3100",
"authToken": "{{REMOTE_AUTH_TOKEN}}",
"nodeName": "remote-us-east",
"syncInterval": 30000
}
}
Multi-Region Deployment Example
Primary Gateway (Tokyo)
├── Remote Gateway (Beijing) ← Serves Chinese users
├── Remote Gateway (Frankfurt) ← Serves European users
└── Remote Gateway (New York) ← Serves American users
Each remote node can connect to different channels and use different model providers, with local providers and channels configured per-node.
Configuration Sync, Health Monitoring, and Failover
Remote nodes periodically sync configuration from the primary. The primary monitors all remote nodes and supports automatic failover with bandwidth optimization via compression and delta sync.
Summary
Remote Gateway is the key feature for OpenClaw global deployments. By deploying remote nodes in different regions, you can deliver low-latency service to users everywhere while maintaining unified configuration and monitoring through the central primary node.