Status and roadmap

What Mistgate releases already do, what is being tested now, what comes next and what 1.0 needs, and the known limits of the current release.

Mistgate is in beta; the current release is v0.1.51. 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; the plans are on this page. The plans have no dates: "Next" and "Later" give the order, not a schedule.

Released

v0.1.0 – v0.1.51

Everything below is in a release and in the docs. First what the current release brought, then the rest by admin section.

New in the current release

v0.1.51

• Cloudflare edition: Enable WARP. The panel registers the WARP account through the Worker's own fetch instead of refusing. A refused registration, on either edition, now says what Cloudflare answered ("Cloudflare refused the registration (HTTP 429)") instead of "Something went wrong". See Enable WARP.
• The manual update commands close once the node no longer needs them.

Profiles

• Hysteria2 on the official core with Salamander.
• AmneziaWG 2.0 and 3.1 in userspace or as a kernel module, several profiles per node.
• VLESS on xray-core: REALITY over XHTTP or TCP (RAW + Vision), with the node's own site or another site as the target; TLS over XHTTP or WebSocket, direct or behind a CDN.
• VLESS and Hysteria2 on one node, TCP 443 included.

Nodes

• SSH installation from the admin, and through MCP with the owner's approval: a pinned host key, checks before any change, jobs that can be cancelled, retried and resumed after an interruption.
• Saved SSH access, encrypted, with a verified password change.
• WARP egress that fails closed when the WARP link drops, and torrent protection on every node.
• Check ports: UDP delivery and a TCP connection to every port of the node from another node of the fleet.
• Measuring the network capacity of a node's link.
• A decoy site per node: the built-in one, the panel's site or an archive of its own.

Users

• Users and groups: traffic quotas with periods, terms, devices by device ID with a limit in three modes, speed per person and per device.
• The People tab sorted by any column, with device counts, and bulk actions on several users at once.

Subscriptions

• One subscription link per person: a link list for Happ and similar apps, Mihomo YAML for apps on the mihomo core, Xray JSON and sing-box JSON for apps on those cores.
• The device limit for apps on the link in the modes Only count, Limit and Strict.
• The user page: per-platform instructions, QR codes, vpn:// keys for AmneziaVPN, and the person's own devices, which they can rename and remove, with a button to copy the link.
• DNS presets; on the user page, a DNS choice for the link apps and one per server for the keys.

Health

• Client-eye checks: every 5 minutes the panel connects to the servers the way an app does, VLESS included (REALITY and TLS, directly or through the CDN).
• The node doctor: host checks and safe fixes, among them Refresh the service, which rewrites the agent's systemd unit from the admin.
• Reachability, a section of its own with each node's week: probes inside Russia through Globalping, the antifilter block lists and a TSPU probe from your own node in Russia, each switched on separately and off by default, with an alert when a node is unreachable from the country.
• Response time through an open tunnel and connect time apart from it, and a notice when the panel's host loses UDP.
• Alerts in the admin and in Telegram.
• The panel watcher: a Cloudflare Worker checks the panel every minute and writes to Telegram when it does not answer.

Updates

• What's new: the release notes between your version and the available one, in the interface language.
• Signed node agent updates, one node at a time, now or on a schedule, with a health gate and automatic rollback.
• Panel self-update from signed GitHub releases, with a rollback when the new panel does not stay up.
• A one-line panel install that verifies the release signature.
• Reproducible releases signed offline from the tag.

Integrations

• API tokens with the readonly, operator and admin profiles.
• The MCP server with plan / apply and owner approvals; ready prompts in the AI agent guide.
• Telegram alerts to the admins who link their chat: health, releases, failed backups, plans waiting for approval, sign-in security.

Settings

• The admin, the user page, the node install page, Telegram messages and these docs in English, Russian and Simplified Chinese; sign-in with a passkey or a password with an authenticator code, optional Cloudflare Turnstile, an audit log. See Security.
• A decoy site at the panel's address hides the admin from strangers.
• Encrypted backups to Cloudflare R2 on a schedule, with retention, and an offline restore.

Now

v0.1.34 – v0.1.51

What the latest releases added is being tested in production; fixes and corrections to the docs come out of it.

VLESS in production

REALITY since v0.1.34, the node's own site as the target since v0.1.35, TLS and a CDN since v0.1.36. VLESS has not been tried behind a real CDN yet: in the end-to-end test the node itself stands in for the CDN. See VLESS behind a CDN.

Devices by device ID in production

Existing panels run in Only count, so you see who is over the limit before you switch to Limit. See How to move from Only count to Limit.

Xray JSON and sing-box JSON in production

No rule hands out Xray JSON by default: add one for the apps you want, or try an app first with ?format=xray-json on its link. See Who gets what.

A decoy site on every node

The built-in site, the panel's site or an archive of its own for each node. Nodes created before v0.1.36 stay on the built-in page until you pick another option. See Your own decoy site.

The country check in production

Every source is off by default. Switch one on and watch the From Russia column before you rely on its alert: the Globalping probes are not the panel's own, and listed is a registry mark, not a measurement. See Reachability.

Next

The next items in the queue.

The Cloudflare edition on a real account

Preview

The first run of mistgate edge deploy on a real Cloudflare account: the six Workers, the router with the domain, and --rollback. So far the command and the panel have been tested against a simulated Cloudflare only. See Install the Cloudflare edition.

The Cloudflare edition on par with the VPS

Bring to the six-Worker edition what it does not have yet:

• encrypted backups and restore;
• Telegram alerts;
• MCP and new API tokens;
• client-eye tunnel checks;
• node and panel updates from the admin;
• live node logs, an Own site decoy for a node, and WARP registration.

Later

Planned, but not next in the queue.

A Telegram bot beyond alerts

Today the bot only sends alerts and links an admin's chat. Later: running the fleet from Telegram, and a bot for users. See Telegram alerts.

Subscription mirrors

Copies of the subscription at other addresses, so that apps still get it when the panel's address is unreachable.

Moving between the VPS and the Cloudflare edition

Moving users, nodes and subscription links either way, with the links still working. Today a fleet is set up again for the other edition. See Moving.

Road to 1.0

The conditions for 1.0. Until then, breaking changes are possible.

The node protocol and the stored settings are fixed

A panel and agents of different 1.x versions understand each other, and the panel's data moves from version to version without manual steps.

Upgrades from older versions are tested

Every release passes an automated upgrade test from earlier versions: a panel with its data and the nodes connected to it.

A stable API

The API, API tokens and MCP tools without breaking changes within 1.x. See API and MCP.

Known limits

• Client-eye checks skip VLESS when the node agent does not report the required capability. Agents before v0.1.34 have no VLESS engine; TLS profiles also require vless-tls/1 (v0.1.36 or later).
• Check ports looks from one vantage point: another node of the fleet or the panel host. On VLESS ports it runs a TLS handshake with the expected name, not a REALITY handshake.
• The SSH installation logs in with a password only (keyboard-interactive included); 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 the offline mistgate backup restore command 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.
• The Cloudflare edition is a preview, not yet tried on a real Cloudflare account: some features are not available in it yet (see the list), and a fleet cannot be moved between it and a VPS panel.
• A device ID is what the app reports. Blocking refuses that ID; an app that reports another ID is a new device and takes a free place. To cut off a link that was passed on, issue a new link as well.
• Speed per person is per node, so a person on two nodes at once can get up to twice the limit. Node agents before v0.1.39 hold each device to the smaller of the two limits.
• In the Cloudflare edition the digest of what was sent to a node must fit one D1 row (2 MB), about 38,000 credentials per node. See the limits of this edition.
• sing-box JSON has no XHTTP and cannot pin a self-signed Hysteria2 certificate; Gecko and AmneziaWG go out only in Mihomo YAML. A server a format cannot carry is left out of that format. See What works where.
• The country check looks from a few probes, not from every network, and the block lists cover Russia only. listed means the address is in a registry, not that its traffic is cut.
• 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}