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.
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 uses a shared secret between proxy and backend, eliminating the IP spoofing risk.
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
| Feature | BungeeCord | Velocity |
|---|---|---|
| First release | 2012 | 2018 |
| Architecture | Single-threaded core | Multi-threaded |
| IP forwarding security | Trust-based (firewall required) | Secret-based (modern forwarding) |
| Plugin ecosystem | Very large | Growing, most essentials covered |
| Paper integration | Supported | Native, preferred |
| Forge/NeoForge support | Limited | Better, actively maintained |
| Resource usage | Higher | Lower |
| Active development | Maintenance mode | Active |
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
This is where Velocity has a clear advantage. BungeeCord's "legacy" forwarding sends the player's UUID and IP to the backend in plain text. If someone connects directly to your backend server (bypassing the proxy), they can impersonate any player, including an admin. The only protection is a properly configured firewall that blocks all direct connections to backend ports.
Velocity's "modern" forwarding uses a shared secret (a key) that both the proxy and backend know. A connection without the correct key is rejected. Even if someone reaches a backend port, they cannot forge player identities. This is a fundamentally safer design.
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.
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?
Velocity has better Forge and NeoForge support than BungeeCord, and the team actively improves it. Simple mod setups work well. Complex modpacks with many client-side mods may require additional configuration. Test your specific pack before committing to a proxy.
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.
