How lowkruc/warp-proxy-manager works
Warp Proxy Manager operates a SOCKS5 forward proxy over managed Cloudflare WARP containers. A client request enters the proxy, which selects a backend and forwards traffic; separately, the manager monitors backends and scales the container pool. Operators use the CLI or REST API to manage containers, scaling, configuration, and monitoring. The graph includes the documented load-balancing, health, rolling-update, and metrics capabilities. Some runtime wiring is only partially excerpted, so unverified links are dashed rather than inferred as direct calls.
Main entry points: main.go Manager Runtime · handlers.go REST API · proxy.go SOCKS5 Proxy · metrics.go Metrics Collector
Components 18
Operator and API
- warpctl CLI
cmd/cli/main.go - REST API
internal/api/handlers.go - Manager Runtime
cmd/manager/main.go - Configuration
internal/config/config.go
Proxy Traffic
- SOCKS5 Proxy
internal/proxy/proxy.go - Load Balancer
internal/proxy/balancer.go - Connection Tracking
internal/proxy/tracker.go - Health Checker
internal/proxy/health.go
Pool Operations
- Docker Client
internal/docker/client.go - Auto Scaler
internal/scaler/scaler.go - Rolling Updater
internal/scaler/rolling.go - Scaling Alerts
internal/scaler/alerts.go
Metrics and State
- Metrics Collector
internal/store/metrics.go - Metrics and History
internal/store/store.go
Other components
- Proxy Client
- Operator
- WARP Containers
- Monitoring System
Connections 29
- Operator → warpctl CLI: runs commands
README.md - warpctl CLI → REST API: manages via API
- Operator → REST API: calls endpoints
README.md - Manager Runtime → Configuration: loads settings
cmd/manager/main.go - Manager Runtime → Docker Client: initializes
cmd/manager/main.go - Manager Runtime → SOCKS5 Proxy: starts
cmd/manager/main.go - Manager Runtime → Load Balancer: syncs backends
cmd/manager/main.go - Manager Runtime → Auto Scaler: starts
cmd/manager/main.go - Manager Runtime → REST API: registers routes
cmd/manager/main.go - Manager Runtime → Metrics and History: initializes
cmd/manager/main.go - Manager Runtime → Metrics Collector: starts
cmd/manager/main.go - Proxy Client → SOCKS5 Proxy: sends SOCKS5
README.md - SOCKS5 Proxy → Load Balancer: selects backend
README.md - SOCKS5 Proxy → WARP Containers: forwards traffic
README.md - Load Balancer → WARP Containers: balances across
README.md - Manager Runtime → Health Checker: starts checker
- Health Checker → WARP Containers: checks health
README.md - SOCKS5 Proxy → Connection Tracking: tracks connections
internal/proxy/proxy.go - REST API → Docker Client: manages containers
internal/api/handlers.go - REST API → Auto Scaler: requests scaling
internal/api/handlers.go - Auto Scaler → Docker Client: scales pool
internal/scaler/scaler.go - Auto Scaler → Load Balancer: reads backend load
internal/scaler/scaler.go - Rolling Updater → Docker Client: replaces containers
internal/scaler/rolling.go - Metrics Collector → Load Balancer: reads healthy backends
internal/store/metrics.go - Metrics Collector → Metrics and History: saves metrics
internal/store/metrics.go - REST API → Metrics Collector: serves metrics
internal/api/handlers.go - REST API → Metrics and History: reads history
internal/api/handlers.go - Monitoring System → REST API: scrapes metrics
README.md - SOCKS5 Proxy → Metrics Collector: reports responses