Velocity vs BungeeCord (2026): Which Minecraft Proxy?

Once your Minecraft project outgrows a single server, you need a proxy. A proxy sits in front of multiple backend servers (lobby, survival, minigames) and lets players move between them without disconnecting. BungeeCord and Velocity are the two main options. Both do the job, but they differ in design, performance and where they are heading.

Want your own Minecraft server? At HostValues from €2.80 per month, online within minutes. View plans →

What a proxy does

Players connect to the proxy, not directly to a backend server. The proxy authenticates them, then forwards the connection to whichever backend server they belong on. When a player types /server survival, the proxy moves the connection from one backend to another. The player sees a brief loading screen instead of having to disconnect and reconnect manually.

Proxies also handle global chat, cross-server messaging, shared permissions and network-wide bans. Without a proxy, each backend server is an island.

BungeeCord

BungeeCord has been around since 2012. It was the original Minecraft proxy and almost every tutorial, guide and plugin assumes it. The BungeeCord plugin ecosystem is massive: thousands of plugins exist, and most developers test their work on BungeeCord first.

The downside is age. BungeeCord was designed over a decade ago and carries design decisions that made sense then but limit it now. Its threading model handles connections on a single thread by default, which becomes a bottleneck on large networks with hundreds of concurrent players. Security has also been a sore point: IP forwarding in BungeeCord relies on a trust model that requires you to firewall backend servers carefully, because any connection claiming to come from BungeeCord is trusted.

Velocity

Velocity was built from scratch by the team behind the Paper project. It launched in 2018 with modern design choices: a multi-threaded architecture, a proper plugin API (not patched Minecraft internals), and a security model called "modern" forwarding that authenticates forwarded player information using a shared secret on supported backends. Modern forwarding adds protection but does not replace restricting direct access to backend servers.

Velocity is noticeably lighter on resources. On the same hardware, Velocity handles more concurrent connections with lower CPU usage than BungeeCord. Its startup time is faster and memory usage is lower. For networks that expect to scale, this headroom matters.

Feature comparison

Plugin compatibility

BungeeCord plugins do not run on Velocity and vice versa. The APIs are completely different. However, most popular plugins now have Velocity versions or alternatives. LuckPerms, LibertyBans, Geyser, ViaVersion and most essentials support both proxies. If you rely on a niche BungeeCord plugin with no Velocity equivalent, that might keep you on BungeeCord for now. Check your plugin list before deciding.

Security

Legacy forwarding alone does not authenticate forwarded player identities. If direct backend connections are left accessible, an attacker may be able to impersonate a player. Restricting direct backend access is therefore essential. The Velocity forwarding documentation also describes BungeeGuard as a secret-based option for legacy forwarding; its requirements differ from Velocity modern forwarding.

Velocity modern forwarding checks player information using a shared secret on supported backend software. It is an additional layer of protection. The Velocity security guide explicitly says it is not a replacement for a firewall and recommends restricting backend access with any Minecraft proxy setup. Keep the forwarding secret private and follow the guidance for your exact backend and hosting environment.

Which should you choose in 2026?

For new networks, Velocity is the clear recommendation. It is faster, safer and actively developed. The Paper team, which maintains the most popular Minecraft server software, builds Velocity and recommends it as the primary proxy.

For existing networks already running BungeeCord with many custom plugins, migrating takes effort. Every BungeeCord plugin needs a Velocity replacement. If your network is stable and your plugins have no Velocity equivalents, staying on BungeeCord is reasonable, but plan the migration eventually.

Running a network? Each backend server and the proxy need their own plan. Check HostValues Minecraft hosting for servers optimised for proxy setups, or use a VPS for full control over the entire stack.

Paper vs Velocity: what is the difference?

Paper is a Minecraft: Java Edition server: it runs the world, the players and your gameplay plugins. Velocity is a proxy: it runs no world of its own, but sits in front of one or more servers and moves players between them. A network uses both, with Velocity as the entry point and Paper servers behind it. The Velocity project recommends Paper for public servers, and modern forwarding works from Paper 1.13.2. Velocity has its own plugin API, so Paper plugins do not run on the proxy.

Can I run BungeeCord and Velocity at the same time?

Not in a useful way. Players connect to one proxy. You could technically run both on different ports, but there is no reason to. Pick one for your network and route all connections through it.

Does Velocity work with Forge modpacks?

Check the exact Minecraft version, loader and forwarding mod in the current Velocity compatibility documentation. Forge support differs between versions and may require an extra plugin or mod. The documented Forge cases do not establish blanket NeoForge or modpack compatibility. A supported proxy version alone does not prove that a particular pack works.

How much RAM does a proxy need?

Very little compared to a game server. A proxy does not load worlds, run mob AI or process redstone. For a small network (under 100 concurrent players), 512 MB is enough. For larger networks, 1 to 2 GB gives comfortable headroom. The proxy's job is forwarding packets, not running the game.