# Remnawave vs. Marzban vs. 3x-ui: which panel for a VPN business

> Remnawave, Marzban and 3x-ui compared as of November 2026: node model, subscriptions, bots, migration paths. An operator's view for paid VPN services.

URL: https://ghostplane.app/en/kb/remnawave-vs-marzban-vs-3x-ui/

## In short

- **Remnawave** was built around a network of nodes and subscriptions from day one, and has an ecosystem of sales bots, Bedolaga above all. It's the panel we see most often at new paid services.
- **Marzban** still runs many services launched earlier. It handles multiple nodes and subscriptions; owners usually move when they need features or bots from the Remnawave ecosystem.
- **3x-ui** grew out of single-server management. Since version 3.0 it handles multiple nodes; it's popular with small services and for personal use.

This is an operator's view: Ghostplane runs Remnawave and moves services to it from Marzban. Check each project's release history on GitHub for its current state.

## Side by side

| | Remnawave | Marzban | 3x-ui |
|---|---|---|---|
| Node model | Panel + agent on each node | Panel + service on each node | Single server historically; multiple nodes since 3.0 |
| Core | Xray-core | Xray-core | Xray-core |
| Protocols | VLESS, Trojan, Shadowsocks; main use case VLESS + Reality | VLESS, VMess, Trojan, Shadowsocks | VLESS, VMess, Trojan, Shadowsocks and more |
| Subscription links | Yes, dedicated subscription page | Yes | Yes, built-in subscription server |
| Sales bot | Bedolaga and other ecosystem bots | Third-party bots | Third-party options |
| API | Yes | Yes | Yes |
| Path to Remnawave | — | Official Remnawave migration tool | Official Remnawave migration tool |

The protocol rows describe typical use, not an exhaustive feature list; details vary by version.

## Remnawave

An open-source panel designed for a fleet of nodes: an agent runs on each node, and the panel pushes configuration and subscriptions. An ecosystem of bots has grown around it; for Telegram sales, Bedolaga is the usual pick.

What to watch: panel, node agent and bot versions need to be compatible. Upgrading them independently without checking is a common cause of outages.

## Marzban

For a long time the default for small services: multiple nodes, subscriptions, an API. Marzban services usually start looking at a move when they need a feature or bot Marzban doesn't have.

Remnawave ships an official migration tool for Marzban. It carries over VLESS, Trojan and Shadowsocks users; it doesn't carry VMess connections, and some links can break on usernames the new panel doesn't accept. Details in the [migration checklist](/en/kb/marzban-migration-checklist/).

## 3x-ui

A friendly web panel: quick to install, easy to learn. It started as a single-server tool and has managed multiple nodes since 3.0. Remnawave's migration tool can import from 3x-ui too, but you probably won't be able to keep existing links.

## How to decide

- **Starting fresh with more than one node planned:** look at Remnawave with Bedolaga.
- **On Marzban and happy:** don't migrate for its own sake. Start with backups and node monitoring.
- **On 3x-ui and growing:** plan the move early, while you have fewer users; you probably won't be able to keep existing links.

Not sure? The [audit](/en/solutions/network-audit/) is free: we'll look at your setup and tell you whether a change makes sense.
