Status and roadmap

What Mistgate does in the current release, what is being tested now, what comes next, and the known limits.

Mistgate is in beta; the current release is v0.1.33. It runs in production, but the API, the stored settings and the node protocol may still change before 1.0. The rest of these docs describe only what the code does today.

Done

The fleet

• A panel and a node agent that talk over mutual TLS; a node enrolls with a one-time token and needs no inbound management port. See Architecture.
• Hysteria2 on the official core with Salamander, and AmneziaWG 2.0 and 3.1 in userspace or as a kernel module, several profiles per node.
• WARP egress that fails closed when the WARP link drops.
• One subscription link per person with the format each app reads, the person's user page, and DNS presets.
• Health: client-eye checks, the node doctor with safe fixes, and alerts.
• Per-node torrent protection.

Installing and recovering

• SSH installation from the admin, and through MCP with the owner's approval: root or sudo -n, a pinned host key, checks before any change, the host firewall prepared.
• Install jobs that can be cancelled, retried and resumed after an interruption.
• Saved SSH access, encrypted, with a verified password change; the access outlives a retired node until the owner forgets it.
• The one-line panel installer verifies the signed release before setup and systemd installation.
• Encrypted backups to Cloudflare R2 on a schedule, with retention and back-off, and an offline restore.
• Telegram alerts: health alerts, releases, failed backups, plans waiting for approval and sign-in security, sent to the admins who link their chat.

Updates

• Signed node agent updates, one node at a time, now or on a schedule, with a health gate and automatic rollback; signed bundles downloaded from GitHub by themselves.
• Panel self-update from signed GitHub releases, with a rollback when the new panel does not stay up.
• Reproducible releases signed offline from the tag: see Releases and signing.

Access

• The admin in English and Russian; sign-in with a passkey or a password with an authenticator code, optional Cloudflare Turnstile, an audit log. See Security.
• API tokens with the readonly, operator and admin profiles, and the MCP server with plan / apply and owner approvals; ready prompts in the AI agent guide.

Now

• Field testing of the current releases in production: torrent protection, the SSH installation and recovery, signed panel and node releases.
• VLESS REALITY with RAW + Vision and with XHTTP: the node engine on xray-core is merged; VLESS profiles and subscriptions in the panel are Planned.
• The edition of the panel that runs on Cloudflare Workers: a preview, not in a release. mistgate edge deploy installs it and is tested against a simulated Cloudflare; the first run on a real account is still ahead. Backups, Telegram alerts, MCP, tunnel checks and node and panel updates are not available in it yet. See Install the Cloudflare edition.

Next

• A Telegram bot beyond alerts: for the fleet and for users.
• More subscription formats (Xray JSON, sing-box) and subscription mirrors.

Known limits

• The SSH installation logs in with a password only; key login is not supported. Use the manual install for such servers.
• API tokens and MCP cannot create profiles or groups, or put a profile on a node: the owner does that in the admin.
• Backups go to Cloudflare R2 only, and a restore is a command-line step into a new data directory.
• The panel does not create a Cloudflare account, a bucket or a token: you supply a bucket-scoped token with read, write and delete access.
• Some defaults lean towards users in Russia (Yandex DNS for nodes in Russia, the doctor's control domains, split-DNS presets); all of them are settings.

---

_{Edit this page · View on mistgate.app}