--- title: "Velocity vs. BungeeCord vs. Waterfall: Choosing a Proxy | ZCS" description: "Compare Velocity, BungeeCord and Waterfall on performance, plugin support, security and maintenance to choose the right proxy." url: "https://www.zcraftstudios.com/blog/velocity-vs-bungeecord-vs-waterfall-comparison" updated: "2026-10-20T07:16:50.972429+00:00" source: "ZCraft Studios" --- > Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`. 1. [Home](https://www.zcraftstudios.com/) 2. [Blog](https://www.zcraftstudios.com/blog) 3. Velocity vs. BungeeCord vs. Waterfall: Choosing a Proxy [ All posts](https://www.zcraftstudios.com/blog) # Velocity vs. BungeeCord vs. Waterfall: Choosing a Proxy ZCraft StudiosOct 3, 2026Updated Oct 20, 2026 Compare Velocity, BungeeCord and Waterfall on performance, plugin support, security and maintenance to choose the right proxy. ## In this guide - [BungeeCord](#bungeecord) - [Waterfall](#waterfall) - [Velocity](#velocity) - [Why Velocity Is the Current Default Recommendation](#why-velocity-is-the-current-default-recommendation) - [When BungeeCord or Waterfall Might Still Make Sense](#when-bungeecord-or-waterfall-might-still-make-sense) - [Plugin Compatibility Is the Real Migration Blocker](#plugin-compatibility-is-the-real-migration-blocker) - [The Short Version](#the-short-version) - [Migration risks matter more than a feature checklist](#migration-risks-matter-more-than-a-feature-checklist) - [Compare supported dependencies, not only proxy names](#compare-supported-dependencies-not-only-proxy-names) - [Official documentation and links](#official-documentation-and-links) - [A practical verification exercise](#a-practical-verification-exercise) ## Velocity vs. BungeeCord vs. Waterfall: Choosing a Proxy _Three different proxies solving the same basic problem (one address, multiple backend servers) at different points in their development lifecycle._ ## BungeeCord The original Minecraft proxy, built by the Spigot team, and the one most older guides and plugins reference by default. Still functional, but development has slowed considerably compared to its earlier years, and it generally lags behind in supporting newer Minecraft protocol features and performance improvements. ## Waterfall A fork of BungeeCord built by PaperMC, created specifically to improve on BungeeCord's performance and fix long-standing bugs while maintaining compatibility with existing BungeeCord plugins. For a while, Waterfall was the natural upgrade path for anyone running BungeeCord. ## Velocity Also built by PaperMC, but written from scratch rather than forked from BungeeCord. It's a modern proxy with substantially better performance, built-in support for modern forwarding (more secure than BungeeCord's legacy forwarding method), and active ongoing development. Velocity doesn't support BungeeCord plugins directly, though many popular plugins now ship Velocity-native versions. ## Why Velocity Is the Current Default Recommendation PaperMC's own development focus has shifted to Velocity, and Waterfall has moved into a lower-maintenance state as a result, which mirrors the same pattern that made BungeeCord fall behind in the first place. For a new network being set up today, Velocity is generally the recommended starting point specifically because it's where active development and plugin support are concentrated going forward. ## When BungeeCord or Waterfall Might Still Make Sense An existing network already running BungeeCord-specific plugins without Velocity equivalents, or deeply reliant on legacy forwarding configurations, might reasonably delay migration until those dependencies are resolved. Rewriting a whole network's proxy layer isn't always a trivial weekend project, even when the destination is clearly better long-term. ## Plugin Compatibility Is the Real Migration Blocker The proxy software itself is rarely the hard part of switching. Checking whether every proxy-side plugin currently in use (chat bridges, punishment syncing, queue systems) has a Velocity-compatible version is usually what determines how straightforward a migration actually is. ## The Short Version For a brand-new network: **Velocity**. For an existing BungeeCord/Waterfall network without a pressing reason to migrate: evaluate plugin compatibility before committing to a timeline, but plan for Velocity as the eventual destination given where active development is heading. ## Migration risks matter more than a feature checklist Proxy selection affects your forwarding model, plugin compatibility and backend network isolation. If migrating an existing network, document the current proxy's forwarding settings and plugins before changing anything. | Area | Check on each option | | --- | --- | | Minecraft version | Project's documented compatibility | | Proxy plugins | Supported APIs and alternatives | | Player identity | Forwarding and backend authentication configuration | | Network exposure | Backends reachable only from trusted proxy hosts | | Operations | Logs, restarts, monitoring and backups | Use a disposable staging environment and test direct backend access, transfers between servers and reconnect behavior. Never assume a newly selected proxy can safely reuse all configuration files unchanged. Consult the [Velocity documentation](https://docs.papermc.io/velocity/) for current forwarding and configuration guidance. [![Velocity project artwork](https://repository-images.githubusercontent.com/142085119/ea2c0680-cc17-11eb-894c-501560eca79b)](https://papermc.io/software/velocity) _Velocity project artwork. [Official source](https://github.com/PaperMC/Velocity). Illustrative publisher image._ ## Compare supported dependencies, not only proxy names Build a list of the extensions and backend features your network requires. For each candidate, check current maintenance and explicit support from those projects. Separate a familiar configuration style from actual compatibility. A proxy that fits a new network may require substantial changes to an existing authentication or messaging setup. Record those changes before deciding that migration is a small switch of the startup jar. Rehearse the public join route, identity forwarding and fallback handling with test backends. Verify the security design as well as successful transfers. Keep secrets outside shared screenshots and confirm how direct backend access is restricted. Plan how you will return to the prior setup if a required extension fails. Compare staff commands and diagnostic access too, because the people operating the network need a workable process after the migration, not just a successful first login. ### Troubleshooting paths - Extension is unsupported: decide whether to replace it before migrating. - Identity differs: review forwarding and backend configuration together. - Transfer fails: inspect destination availability and fallback behavior. \* ## Official documentation and links - [Official project repository](https://github.com/PaperMC/Velocity) - [Velocity Proxy Setup: Connect Multiple Minecraft Servers](https://www.zcraftstudios.com/blog/velocity-proxy-network-setup) ## A practical verification exercise Evaluate proxies based on actively supported server versions, forwarding methods, operational security and plugin integrations. Run a test network that includes one proxy and two backends, then validate account identity, reconnects and behavior when a backend stops. Migration is more than changing the public port. ## Continue reading - [Velocity Proxy Setup: Connect Multiple Minecraft Servers](https://www.zcraftstudios.com/blog/velocity-proxy-network-setup) - [Velocity Modern Forwarding Setup and Security Checklist](https://www.zcraftstudios.com/blog/velocity-modern-forwarding-setup-checklist) - [Choosing a Minecraft Server Host: Shared, VPS, or Dedicated](https://www.zcraftstudios.com/blog/choosing-minecraft-server-host) [ Previous guide LiteBans vs AdvancedBan vs Essentials Punishments](https://www.zcraftstudios.com/blog/litebans-vs-advancedban-vs-essentials-punishments)[ Next guide Hosting and Setting Up a Custom Resource Pack](https://www.zcraftstudios.com/blog/custom-resource-pack-hosting-setup)