OpenClaw VPS Self-Managed Architecture
Self-managed OpenClaw VPS deployment with gateway, workspace, firewall/auth layer, and commercial LLM provider access from any device.
Managed cloud OpenClaw deployment using platforms like Railway or Northflank with a hosted gateway, integrations, monitoring, and commercial LLM APIs.
User { # User
n1: circle label:"Start"
n2: rectangle label:"Click Deploy on Railway"
n3: rectangle label:"Configure API key in wizard"
n4: rectangle label:"Chat via Telegram / Discord"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left)
n3.handle(right) -> n4.handle(left)
n4.handle(bottom) -> Cloud.n5.handle(top) [label="Internet"]
}
Cloud { # Managed Cloud Platform
n5: rectangle label:"OpenClaw Gateway (managed)"
n6: rectangle label:"Auto-updates + Monitoring"
n7: rectangle label:"Pre-configured Integrations"
n5.handle(right) -> n6.handle(left)
n6.handle(right) -> n7.handle(left)
n5.handle(bottom) -> LLM.n8.handle(top) [label="API Request"]
}
LLM { # Commercial LLM API
n8: rectangle label:"Claude / GPT / Gemini"
n9: rectangle label:"Generate response"
n8.handle(right) -> n9.handle(left)
n9.handle(top) -> Cloud.n5.handle(bottom) [label="Response"]
}
Self-managed OpenClaw VPS deployment with gateway, workspace, firewall/auth layer, and commercial LLM provider access from any device.
OpenClaw deployment on your everyday machine with the gateway, workspace, and commercial LLM API connected locally through the web UI.
OpenClaw Docker deployment with an isolated gateway runtime, mounted workspace and config volumes, and a commercial LLM API.
OpenClaw architecture for a dedicated Mac Mini or homelab server with persistent workspace, agent state, and remote messaging access.
Hybrid OpenClaw architecture with a cloud gateway, local nodes for device actions, persistent agent state, and commercial LLM provider calls.
A microservices API gateway architecture diagram showing request routing, JWT authentication, rate limiting, service discovery, and response aggregation across distributed backend services. This template models the entry point for all client traffic in a microservices ecosystem, enforcing security policies before requests reach internal services. Ideal for platform engineers designing scalable API infrastructure with centralized cross-cutting concerns.