Beta · self-hosted · open source · AGPL-3.0
A self-hosted panel for a small VPN
For a few servers of your own and the people you share them with. You put the panel on one server and add your VPN servers to it as nodes. Each person gets one subscription link, and their app picks up every server they may use.
- Hysteria2
- VLESS REALITY
- AmneziaWG 2.0 / 3.1
- Cloudflare WARP
- Linux amd64 / arm64
- SQLite, no Docker
- English · Русский · 简体中文 · فارسی · Türkçe
What it does
Nodes from the browser
Add a node by its IP with the panel's own SSH key (added once at your hoster) or the root password. The panel pins the SSH host key, checks the server, opens the ports in an active UFW or firewalld and installs the signed agent; the node's card changes the password and manages the server's SSH keys. A one-time install command works too. Add a node
One link per person
Mihomo apps (kl!ck, FlClash, Clash Verge Rev) get all three protocols from it, Happ gets Hysteria2 and VLESS, and AmneziaVPN takes a key per device from the person's page. The Mihomo and sing-box apps move to a working server by themselves. Client apps
Checks and alerts
Every 5 minutes the panel connects to every server the way an app does. A doctor on each node runs 21 host checks and offers eight fixes that run only after you confirm. Alerts go to the admin and to Telegram. Health
Relays through your other nodes
When some networks cannot reach a server, people get to it through another of your nodes, which only forwards the encrypted traffic. The panel checks the path before switching it on and watches it afterwards; Ways in on the node page is a graph of how people reach the server, and the Nodes page maps the whole fleet. Relays through an entry node
Seen from inside a country
Optional checks of whether your servers open from inside a country, network by network: Globalping probes on home and mobile networks over IPv4 and IPv6, volunteer and SIM probes, block lists and a TSPU probe from your own node. Most sources work only in Russia. Reachability
Two Go binaries
No Docker, no database server: SQLite and systemd. The panel idles at 16–20 MiB of memory on a 1 vCPU / 1 GB server. Benchmarks
A decoy site
Strangers who open the panel's address see a decoy site; the admin is behind a secret path or host name. Your own decoy site
Assistant and MCP
A built-in assistant (a cloud model you connect with your own key) answers about your nodes and people and prepares changes you apply. MCP lets an outside AI agent read the fleet, test paths between your nodes and plan changes; risky ones wait for your approval in the admin. An API token can disable or rewrite at most 10 people an hour unless you lift the limit for it. Assistant
Not there yet: an app of our own (planned), a Telegram bot beyond alerts, and the Cloudflare Workers edition is still a preview. Some defaults lean towards users in Russia; all of them are settings.
How it fits together
Two programs: the panel and an agent on every server. A person's app talks to the panel only to fetch its link; VPN traffic goes straight to the node.
Protocols
Hysteria2 and VLESS can share a node, TCP 443 included. Not supported yet: VMess, Trojan, Shadowsocks, TUIC and plain WireGuard. More protocols are planned; each plugs into the same subscription link through the protocol plugin contract.
Is it stable?
It is beta, and young: v0.1.0 was tagged on 2026-10-03. The maintainer runs it on their own six servers for family and friends.
CI
Every push and pull request: Go tests and vet, the race detector on the panel-agent session,
govulncheck, the admin's lint and tests, the docs build, the installer on Debian and Ubuntu. ci.ymlEnd-to-end run
Before every release: a real panel and node with real Hysteria2, AmneziaWG, Xray, mihomo and sing-box clients, plus agent updates, rollbacks and an install over SSH. By hand in WSL or a VM, not in CI. e2e-wsl.sh
Signed builds
GitHub Actions builds each tag as a draft. The maintainer rebuilds it from the tag on a machine with the offline release key and signs only binaries that match byte for byte; the panel and nodes install only signed builds. Releases and signing
Updates with rollback
Nodes never update on their own. A rollout starts with one canary node and a 5-minute health gate; a node that fails gets its previous build back and the rollout pauses. The panel updates itself only when you confirm, and restores the old build if the new one does not stay up. A node on a bad link can finish its download from GitHub (a setting, on by default). Updates
Mistgate is written with AI coding agents: the maintainer reviews what they write and decides what is merged and released, and their code goes through the same checks as anyone's.
Quick start
From an empty Linux server to the first person with a working link
Install the panel
One command on a fresh Linux server: the installer verifies the signed panel manifest, starts Mistgate under systemd and prints a one-time setup link. Or give the install prompt to an AI agent.
Add a node
Nodes → Add node installs the agent over SSH, or gives you a one-time command to run on the server yourself.
Give people their links
Put a profile on the node, create a user and send them the link.
Alerts, security, backups
Link Telegram for alerts, check the security settings and set up encrypted backups before others depend on it.
Compared with other panels
| Mistgate | 3x-ui | Remnawave | Hiddify | PasarGuard | s-ui | |
|---|---|---|---|---|---|---|
| Runs without Docker | yes | yes | no | yes | partial | yes |
| Panel RAM, idle¹ | 16–20 MiB | 68–74 MiB | 426–454 MiB | not measured | 262–265 MiB | not measured |
| Add a node from the panel (SSH) | yes | no | no | no | no | ? |
| Hysteria2 | yes | yes | partial | yes | yes | yes |
| AmneziaWG | 2.0 and 3.1 | 3.1 | ? | ? | ? | ? |
| VMess, Trojan, Shadowsocks | no | yes | partial | yes | yes | yes |
| Telegram bot | alerts only | yes | partial | yes | yes | ? |
¹ Private memory of the whole panel group, idle, no node attached, on a 1 vCPU / 1 GB test server; for 3x-ui it includes its Xray core and fail2ban. “?” means the project's own README and docs do not say. Others are ahead in protocol breadth, community size and full Telegram bots.
The docs by admin section
Each section of the admin and the pages about it
Start here
What Mistgate is, what servers you need, and how to install the panel
Nodes
Servers in your fleet, their protocols, load and the wizard to add a new one
Users
People with access: apps, devices, traffic quotas and expiry dates
Profiles
Ready-made protocol setups that you roll out to nodes and users
Subscriptions
Subscription formats, delivery rules and the page users see
Health
Alerts, client-eye checks and the fleet doctor
Updates
Panel and node agent versions, staged rollouts and rollback
AI
The assistant, MCP and the plans waiting for you
Integrations
Telegram alerts: every admin links their own chat
Settings
Admins, security, backups and domains
Reference
Commands, flags, variables, the architecture and answers to common questions
Mistgate is in beta: releases are 0.1.x, and until 1.0 the API, the stored settings and the node protocol may still change. Status and roadmap