Mistgate/mistgate

<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="./.github/assets/banner-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="./.github/assets/banner-light.svg"> <img alt="Mistgate: a lightweight, self-hosted VPN panel" src="./.github/assets/banner-dark.svg" width="100%"> </picture> <p><b>English</b> · <a href="README.ru.md">Русский</a> · <a href="https://mistgate.app/">Documentation</a></p> </div>

Mistgate is a lightweight, self-hosted panel for your own VPN fleet: one Go binary for the panel, one for the node agent, no Docker. Hysteria2 and AmneziaWG live side by side, in one subscription, in one admin UI. The panel keeps users, profiles and nodes; the agent on each node runs the protocols and keeps the host in the state the panel asks for.

Install with an AI agent. Claude Code, Codex CLI or any agent that can run ssh on your computer can install the panel for you: copy the install prompt from the AI agent guide. It asks before every change and hands you the setup link; you create the owner account yourself.

Why another panel

• Light. SQLite, systemd, two static binaries. No Docker, no database server. The panel's memory target at idle is 80 MB (a target for now, not a benchmark).
• AmneziaWG users are not a blind spot. Every AmneziaWG device is a peer the panel knows about: who is online, traffic per user and per device.
• A doctor that knows hosters. Disk and journals filling up, a resolver that cannot resolve, clock drift, port conflicts, network settings that drifted from the baseline (fq, BBR). Found, explained in plain words, fixed with one confirmed click where that is safe.
• Looked at from the client's side. The panel connects to every profile on every node the way a real client does (Hysteria2 and AmneziaWG), so a node is green only if traffic really flows.
• Hidden by default.