Velocity vs BungeeCord in 2026: Is BungeeCord Really Dead?

If you are choosing a proxy for a Minecraft network, or deciding whether to replace BungeeCord, start with security and plugin requirements. This comparison explains why Velocity can be an attractive choice, where BungeeCord still makes sense, and what the maintenance evidence actually shows as of 29 October 2026.

1. Velocity: Modern forwarding and a separate plugin ecosystem#

Velocity is PaperMC's Minecraft proxy, built around its own plugin API. Its appeal comes from a combination of performance goals, modern player forwarding and an API that does not have to preserve compatibility with BungeeCord plugins.

Velocity Free PaperMC's modern Minecraft proxy with its own plugin API and secure modern player forwarding. On PaperMC

What it does well#

• Authenticated player forwarding: modern forwarding uses a message authentication code and a shared secret to protect the player information passed to backends.
• A separate API: Velocity's FAQ explains that supporting BungeeCord plugins directly would prevent some of its capabilities.
• A clear development direction: PaperMC recommends Velocity and says its future proxy development is focused there.

PaperMC also describes Velocity as faster and more stable than BungeeCord. That is the project's own assessment, so it should inform a shortlist rather than serve as a promised performance gain for your network.

Who it suits#

Velocity is a good starting point for a network whose required plugins have supported Velocity versions. It is particularly worth evaluating when your backend requirements allow modern forwarding, which works with Minecraft 1.13 and newer.

What to watch out for#

BungeeCord plugin compatibility is the main migration cost. Velocity does not directly support plugins written for BungeeCord or Waterfall, so an existing network may need replacements or ports. Velocity 4.0 and newer also require Java 25, which belongs on your requirements checklist before you commit.

2. BungeeCord: Continuity for an existing plugin stack#

BungeeCord is SpigotMC's proxy and API for connecting multiple Minecraft servers. Its plugin system lets networks provide server switching through commands or plugin-operated features such as portals.

BungeeCord Free SpigotMC's long-running proxy with a plugin system and API for connecting multiple Minecraft servers. On GitHub

What it does well#

• Existing plugin compatibility: it runs plugins written for the BungeeCord API without requiring a move to a different proxy API.
• Established integrations: even PaperMC's Velocity page acknowledges that BungeeCord has historically had more third-party software.
• Continuity: a network with required BungeeCord integrations has a concrete reason to evaluate the cost of replacing them before switching.

Its maintenance record also matters. The official repository shows October 2026 commits and a September change adding Minecraft 26.3 support. That is evidence of ongoing work, rather than an abandoned project.

Who it suits#

BungeeCord remains a reasonable option to evaluate when a required proxy plugin or custom integration depends on its API. Keeping that integration can matter more than choosing a different proxy for architectural reasons alone.

What to watch out for#

Backend access restrictions are essential. BungeeCord's own README warns that backends with authentication disabled can accept direct connections under arbitrary usernames. Its forwarding arrangement should not be treated as a substitute for controlling who can reach those servers.

Staying also means accepting the existing API and architecture. PaperMC argues that BungeeCord's strict backward compatibility limits improvements, but that is its assessment of a competing design, not proof that every BungeeCord network needs replacing.

Compare the differences that affect your network#

There is no single row that decides every network. Our team would give required plugin compatibility and backend security more weight than an unverified promise of lower resource use.

Is BungeeCord really dead in 2026?#

No, the official repository does not support that claim. Its master branch shows commits dated 23 October 2026, including dependency updates, while September's history includes Minecraft 26.3 support and cookie and login payload API improvements.

PaperMC's proxy comparison marks BungeeCord's active development as unknown and acknowledges possible bias toward Velocity. For the narrower question of whether BungeeCord is abandoned, BungeeCord's own recent commit history is stronger evidence.

Waterfall, PaperMC's BungeeCord fork, is the project whose repository explicitly says it has reached end of life and is no longer maintained. Its README recommends moving to Velocity.

Waterfall Free PaperMC's BungeeCord fork, now end of life with Velocity as the recommended replacement. On GitHub

Velocity has current maintenance activity too. Its 4.3.1 release, dated 27 October 2026, is described by the project as a recommended security update for all users, improving buffer handling for legacy plugin messages and rejected packets.

Understand what modern forwarding protects#

Velocity's modern forwarding authenticates the player information sent from the proxy to a backend. Its forwarding documentation describes a shared secret stored in forwarding.secret and a message authentication code used to verify that information.

Modern forwarding works with Minecraft 1.13 and newer. Velocity also offers legacy forwarding in the BungeeCord format, reaching back to 1.7.2, but its documentation calls that format fundamentally insecure. Those are forwarding limits, not a complete list of client versions supported by every current proxy build.

This gives modern forwarding a practical advantage, but it does not make a default installation secure by itself. Before opening a network, follow our guide to restricting access and securing a Velocity backend.

Check plugins before deciding to switch#

Start with the features your network must retain. For each proxy plugin or custom integration, identify a supported Velocity version, a suitable replacement, or a reason to remain on BungeeCord.

Keep proxy plugins separate from backend plugins in that review. Velocity's FAQ says backend plugins using the BungeeCord plugin messaging channel can often work through Velocity. That does not mean a BungeeCord proxy plugin will load on it.

Snap attempts to load BungeeCord and Waterfall plugins on Velocity, but its listing calls it experimental and warns against production use without extensive testing. The checked listing specifies Velocity 3.4 to 3.5 and documents missing capabilities, so it is not evidence that your plugins will work on Velocity 4.x.

Some common requirements have options on both proxies. ViaVersion, which lets newer Java clients connect to older servers, lists both BungeeCord and Velocity as supported platforms.

ViaVersion Free Lets newer Java clients join older servers, and runs on both Velocity and BungeeCord. On Modrinth

Geyser, which lets Bedrock players join Java servers, also lists both platforms. Bedrock access alone therefore does not decide this comparison.

Geyser Free Lets Bedrock players join Java servers, with Velocity and BungeeCord among its supported platforms. On Modrinth

Choose based on requirements, then test the change#

• Shortlist Velocity for a fresh network when your required integrations support it and you can use its modern forwarding arrangement.
• Evaluate staying on BungeeCord when a required plugin or custom integration has no suitable Velocity route.
• Do not switch for a promised speed multiplier. The checked sources do not establish a measured gain for your workload.
• Review forwarding separately from version support. An older backend requirement can change which forwarding mode is available.

Before approving a migration, define what must work: joining the network, switching between servers, proxy commands, plugin integrations and any supported cross-play connections. Use those requirements to judge the result.

Once Velocity fits those requirements, our Velocity network setup guide covers the installation and backend connection steps. The reason to move is a better fit for your network's needs, while the reason to stay should be an identified dependency rather than a claim that either project has disappeared.