Introduction
Elchi is a visual control plane for Envoy proxy fleets: typed config validated and pushed over xDS, edge agents on VMs, WAF, API discovery and GSLB.
Quick Start
Run the full Elchi stack on any Kubernetes cluster with one Helm command, with bundled MongoDB, VictoriaMetrics and ClickHouse, then connect your first edge.
Core Concepts
How Elchi splits work across the registry, controller and control plane plus the edge agent, and how a configuration change flows to Envoy.
Architecture
The map of the Elchi stack: the three backend processes, datastores and observability tier, the edge node, and every connection with its port and auth.
Network & External Access
Firewall checklist for Elchi: what the platform exposes, what it must reach, what edge hosts running elchi-client, Envoy and Shield need, and optional ports.
The Dashboard
The first screen after login: a per-project widget overview of Envoy resource counts, service errors, traffic and security health, linking into every area.
Global Search
Find every place a domain or IP appears in your Envoy config (virtual hosts, routes, filters, endpoints, clusters, listeners) and jump straight to the resource.