What breaks without openclaw gateway load balancer
Single point of webhook failure. Duplicate message processing on retry storms. No rate limiting on ingestion.
→
High availability webhook ingestion × deduplication and failover routing ÷ 30-minute setup ÷ no nginx custom config = a bot that survives instance crashes.
Security check — openclaw gateway load balancer
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.2; works with any adapter that uses HTTP webhooks compatibility.
Quick start — openclaw gateway load balancer in 30–60 minutes
Setup time: 30–60 minutes
!
You need:
- OpenClaw core
- multiple OpenClaw instances
- Node.js ≥18 or Docker
Install the package:
git clone https://github.com/ThisIsJeron/openclaw-better-gateway
cd openclaw-better-gateway && npm install
npm start
2
Define your OpenClaw instance endpoints in gateway.config.js
3
Configure routing rules (round-robin, hash-based, or failover)
4
Start the gateway with npm start or as a Docker container
5
Point your platform webhooks at the gateway URL
6
Verify traffic distribution via the gateway health endpoint
Compatibility & status
Works with: Linux, macOS; OpenClaw ≥1.2; works with any adapter that uses HTTP webhooks
advanced
Last updated: Oct 2025
★ 200 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — openclaw gateway load balancer
Does this gateway support WebSocket connections as well as HTTP webhooks?
Current version focuses on HTTP webhooks. WebSocket passthrough is on the roadmap.
Can I use nginx instead?
Yes for basic load balancing, but this gateway adds OpenClaw-specific features like signature header forwarding and event deduplication.
How does hash-by-user routing work?
Messages from the same user ID are always routed to the same instance, preserving in-memory session state.