3x-ui vs Marzban vs Hiddify vs Remnawave: Which Panel?

15 Nov 2026 By ST Muntaha
3x-ui vs Marzban vs Hiddify vs Remnawave: Which Panel?

You want a branded VPN app, and someone told you to skip the custom backend and run your users through an open source panel. The shortlist is often the same four: 3x-ui, Marzban, Hiddify and Remnawave. Which one should you build on?

There is no single winner. The four differ most on license terms, whether device limits and webhooks are documented, how recently each one shipped, and how risky an upgrade looks. Choose by those, not by feature count. Everything below comes from reading each project’s repository, release pages, LICENSE file and docs on 10 November 2026. Nothing was installed or load tested, so this is a reading of the documents, not a benchmark.

What Does a Panel Do, and What Does It Not Do?

A panel manages users, limits, nodes and subscription links on top of a proxy core such as Xray-core. It is not your app and it is not the tunnel. The phone still needs native client code, and your business still needs accounts, billing and support. For the wider picture of what a VPN product contains, see the six components of VPN app architecture. For the core underneath, see Xray vs sing-box, and for the censorship side see REALITY, Xray and AmneziaWG.

This is an independent reading of public documents, not an endorsement of any project.

How Do the Four Panels Compare on Paper?

Repository state as of 10 November 2026

Panel Latest release Releases or tags since 31 Jul 2026 Latest commit License
3x-ui v3.11.0, 25 Oct 2026 7 versioned releases 6 Nov 2026, main GPL-3.0
Marzban v0.8.4, 9 Jan 2025 none master 9 Jan 2025, dev 8 Jun 2026 AGPL-3.0
Hiddify v14.2.0, 6 Nov 2026 50, mostly betas Manager dev, 10 Nov 2026 Manager GPL-3.0; Panel CC BY-NC-SA 4.0
Remnawave 3.4.9, 9 Nov 2026 19 Backend 9 Nov 2026 AGPL-3.0-only

Marzban needs a closer look. Its last tagged release and its master branch date from January 2025. Its dev branch was updated on 8 June 2026 and holds 72 commits that are not on master, a feature branch was updated on 2 November 2026, and the version string on dev still reads 0.8.4. That is unreleased work and not a stable release. It suggests the project is still being worked on, though we found no maintainer statement about a release plan.

What each project documents

3x-ui Marzban Hiddify Remnawave
Proxy core Xray-core Xray-core Xray and sing-box Xray-core on nodes; sing-box is an output format
Limits Quota, expiry, auto renewal Quota, expiry, reset strategy, on hold state Usage limit, package days, reset mode Quota, expiry, reset strategy
Subscription output Raw, JSON and Clash or Mihomo, chosen by path; User Agent matching is an optional setting Base64 list, Clash, Clash Meta, sing-box, Outline, Xray JSON /sub, /sub64, /auto, plus sing-box and Clash Meta endpoints Mihomo, Base64, Xray JSON, sing-box templates, client detected
Database SQLite or PostgreSQL SQLite, MySQL or MariaDB MariaDB and Redis PostgreSQL and Valkey (Redis compatible)
Install Script or Docker Script or manual Ubuntu 22.04, 24.04 or 26.04; Docker marked experimental Docker Compose only
Admin features Telegram and Discord bots, 14 UI languages, installable web app Telegram bot, CLI Multiple admin privileges, Telegram bot, dedicated user pages Internal and external squads, subscription templates in the web UI
Limits the docs state README: personal use only README lists multi admin as work in progress Docker marked experimental Comparison page: single maintainer

Two statements from the projects themselves deserve attention. The 3x-ui README says the project is intended for personal use only and not for a production environment, although its docs also describe multi node setups. And Remnawave’s comparison page says it is maintained by a single developer. That page was written by former Marzban users and carries its own disclaimer, so treat its claims about Marzban as one side’s view.

What Does a Branded App Need From a Panel?

A branded app talks to a panel through your own backend. These are the six things it usually needs, mapped to what each project documents.

Need 3x-ui Marzban Hiddify Remnawave
Provisioning API REST, scoped Bearer tokens REST, JWT admin token; Swagger only if DOCS=True OpenAPI, Hiddify-API-Key header REST, API tokens; official TypeScript SDK, pinned per panel version
Device binding IP limit via Fail2ban; HWID limit We did not find one Not verified HWID limit, off by default
Per user subscription URL subId per client Token in the path; revoke endpoint Per user link shortUuid, separate from the VLESS UUID
Multi node Master panel plus node panels Marzban Node, last tag v0.5.2, 22 Mar 2025 Parent and child panels Node containers; the panel runs no Xray
Usage counters Per inbound, client and outbound /usage and /info endpoints current_usage_GB in the admin API usedTrafficBytes per user
Webhooks We did not find panel webhooks (Xray routing rules have their own) Yes, x-webhook-secret header We did not find any Yes, signed with HMAC headers

“We did not find” means a keyword search of the docs and source returned nothing relevant for that feature. It does not prove the feature is absent, so an engineer should confirm each before you rely on it.

The device limit question

Device limits matter if you sell per device plans, and the four projects handle them differently. 3x-ui limits simultaneous source IPs through Fail2ban and also has an HWID limit; its source reads the same X-HWID request header and answers 404 when a limited client sends none. Remnawave’s HWID device limit is optional, and its docs say only a few client apps send the needed header. If the feature is on and the client sends no HWID header, the subscription request returns a 404. Your own app must therefore send x-hwid. For Hiddify, the user model in the source has a max_ips field, but the check that would enforce it is commented out and the admin API schema has no such field, so it is marked not verified. We did not find a device limit in the Marzban docs or source.

What Are the Risks of Building on a Panel?

Maintenance and bus factor

Marzban’s release gap is described above. Remnawave documents a single maintainer. Hiddify ships often, but most of its recent tags are betas, so decide which channel you will follow. 3x-ui shipped seven versioned releases in three months. A fast cadence helps with fixes and hurts with upgrade effort.

Breaking changes

Read the release notes before every upgrade. Examples from the release notes and upgrade docs read:

  • Remnawave 3.0.0 changed REST routes to use id instead of uuid for users, changed status codes for delete requests and moved some subscription settings into response headers.
  • 3x-ui v3.9.0 stopped inbound updates from changing clients, and v3.10.0 asked operators to upgrade every node and noted an Xray-core TLS roots change.
  • Hiddify v13, as described in the docs/main_changes.md file of the Manager repo (the GitHub release page itself carries no notes), changed the folder layout, did not carry over local edits to v12 config templates, and changed the parent usage API response. Parent and child must be upgraded together.

Security updates

The 3x-ui security policy says only the latest release receives fixes. Its release notes list security items: v3.8.5 stopped subscription responses from linking to a built in profile page that exposed the subscription URL, and v3.11.0 stopped trusting a client supplied X-Real-IP header behind a trusted proxy. The Remnawave backend SECURITY.md is the unfilled template. We did not find a SECURITY.md in the Marzban, Hiddify Manager or Hiddify Panel repositories, and we did not check organization level policies. Plan to track releases yourself.

License obligations

GPL-3.0 and AGPL-3.0 are copyleft licenses that permit commercial use. Their main duties arise when you distribute the software, modified or not: you pass on the license and make the corresponding source available under the same terms. The AGPL adds section 13: if you modify the program, you must offer the corresponding source of your version to users who interact with it remotely over a network. That can matter for a patched Marzban or Remnawave even if you never distribute it. Hiddify is split: the Manager is GPL-3.0, while the Panel submodule is under CC BY-NC-SA 4.0, whose license summary says the material may not be used for commercial purposes, alongside attribution and ShareAlike terms. How these terms apply to your product depends on your facts and jurisdiction. This is general information, not legal advice. Ask your own lawyer before you build a paid service on any of them.

How Should You Choose?

Use this as a decision framework, not a ranking.

If your priority is Look first at Verify before committing
Device limits at the panel 3x-ui, Remnawave Your app sends the HWID header; test the missing header behavior
Events pushed to your billing backend Marzban, Remnawave The event list for the exact version you pin
A standard open source license to review 3x-ui, Marzban and Remnawave (GPL or AGPL) Counsel review of the copyleft duties; Hiddify Panel’s NonCommercial term
Recent and frequent releases 3x-ui, Remnawave, Hiddify betas An upgrade rehearsal on staging
sing-box based clients Hiddify Stable or beta channel
Least dependence on any one project Treat the panel as a replaceable node controller Your own backend holds the user records

The last row is a design option, not a documented feature of any panel.

Five tests to run before you commit

  1. Create, suspend and delete a user through the API with a script, on the version you will pin.
  2. Fetch one subscription URL with the User Agent of each client you support, and on each format path, and compare the output.
  3. Exhaust a quota and let an expiry pass, then time how fast the client is cut off.
  4. Upgrade a staging copy by one release and replay your scripts.
  5. Stop the panel and check whether nodes keep serving users.

Our guide to VPN subscription URL formats covers what the app must parse from these outputs.

FAQ

Which panel is best for a branded VPN app?

None is best on every need, so match the panel to the need. Device limits, webhooks, license terms and release cadence differ, and the framework table above shows which project to check first for each.

Does 3x-ui support production use?

Its own README says it is not meant for production use. Its docs, however, describe setups from one VPS to many nodes, so the two messages do not fully agree. Read the README note, then run the five tests above before you decide.

Is Marzban still maintained?

Partly: its tagged releases stopped at v0.8.4 on 9 January 2025, but its dev branch and a feature branch show work in 2026. Pin a version and check the repo again before you commit.

Does Remnawave support device limits?

Yes, through an optional HWID device limit that is off by default. The client app must send a HWID header, or the subscription request returns a 404 when the feature is enabled.

Can I use Hiddify commercially?

It depends on the component. The Manager is under GPL-3.0, which permits commercial use. The Panel is under CC BY-NC-SA 4.0, whose license summary says the material may not be used for commercial purposes. Get your own legal advice on both before you sell access.

Takeaway

Pick the panel whose documented gaps you can live with, pin its version, and keep your own backend as the record of who is a customer. Read the release notes before every upgrade.

For our own work and our clients’ products we build custom admin panels rather than running any of these four, so this comparison is an outside reading of their code and docs. Not sure which panel fits your plan, or whether you need your own? Tell us what your app needs on the contact page, and we can talk through which checks to run first.

Last checked against the GitHub repositories, release pages, LICENSE files and docs of 3x-ui, Marzban, Hiddify Manager, Hiddify Panel and Remnawave on 10 November 2026.