Quick answer
BungeeCord is layer-7 minecraft proxy. Link multiple Minecraft servers so players can move between them through a single proxy/network entry point.
| Developer / maintainer | SpigotMC maintainers and contributors |
|---|---|
| Software type | Layer-7 Minecraft proxy |
| Upstream / lineage | Original long-running proxy project rather than a Paper fork. Waterfall historically forked it. |
| Current status | Actively maintained |
| Best fit | Existing networks built around BungeeCord plugins/configuration, legacy compatibility cases, and administrators who deliberately need BungeeCord. |
Who develops BungeeCord?
SpigotMC maintainers and contributors develops or maintains this project. Original long-running proxy project rather than a Paper fork. Waterfall historically forked it.
This matters because “Minecraft server software” covers very different kinds of projects. Some are direct forks of Paper, some are mod loaders, some are compatibility layers, some are proxies, and some reimplement the server from scratch. The lineage above tells you what ecosystem, APIs, and operational assumptions carry over.
What is its main goal?
Link multiple Minecraft servers so players can move between them through a single proxy/network entry point.
A good reason to choose a server implementation is that its design goal matches a real requirement you have. Switching only because a fork is advertised as faster, more configurable, or more modern usually creates extra compatibility work unless you can name the problem it solves for your server.
How is it different from normal Minecraft?
BungeeCord is not a game server and does not simulate a world. It routes connections to backend servers.
“Vanilla compatibility” can mean several things: the same client protocol, similar gameplay, identical redstone/farm behavior, the same world format, or simply the ability for an unmodified client to join. Those are not equivalent. For technical survival, modded worlds, or long-lived production servers, test the exact behavior you depend on.
How does it differ from its upstream or related forks?
Waterfall forked BungeeCord to focus on stability/features/scalability but is now discontinued. Velocity is a separate proxy implementation rather than a BungeeCord fork.
Fork relationships are especially important for plugins and configuration. A downstream fork usually inherits much of its upstream API, but extra patches can change internals, scheduling, defaults, and edge-case mechanics. The closer a plugin is to undocumented internals, the less useful a generic “Paper-compatible” or “Bukkit-compatible” label becomes.
What type of server is BungeeCord good for?
Existing networks built around BungeeCord plugins/configuration, legacy compatibility cases, and administrators who deliberately need BungeeCord.
For a new server, start with the simplest software that meets the requirement. More layers—especially hybrid plugin+mod stacks or multithreaded forks—mean more combinations to test when Minecraft, Java, plugins, or mods update.
Plugin, mod, and ecosystem compatibility
Deployment distinction: BungeeCord is a proxy layer, not a world-hosting gameplay server. Put gameplay plugins and worlds on backend servers; configure player routing on the proxy and protect backend addresses from direct connections.
Uses BungeeCord proxy plugins. Backend server security and IP forwarding must be configured properly.
Always match extensions to the exact Minecraft version and software family they target. A JAR being Java does not make it universally compatible, and a plugin/mod loading successfully does not prove every code path is safe.
Stability and project maturity
BungeeCord remains maintained by SpigotMC in 2026 and its official repository includes current copyright/update activity. It is mature but carries older design/API assumptions than newer proxy projects.
Current version note: SpigotMC continues to publish BungeeCord builds and source.
MSH does not assign a numeric stability score. Release status, maintenance activity, official warnings, supported Minecraft versions, architecture, and ecosystem compatibility are more useful than a single rating. A mature project can still be the wrong fit, while a beta project can be useful for a team that deliberately accepts the risk.
Before switching to BungeeCord
Staging validation: Do not copy Velocity modern forwarding settings into a BungeeCord network. Choose and test the forwarding approach supported by your proxy/backend pairing, then verify UUID/IP forwarding with a test account.
Because backends are often offline-mode behind BungeeCord, direct backend access can allow username impersonation unless firewalls or equivalent protections are used.
If the server contains modded blocks/entities, switching away from the loader or mods that created that data can permanently damage a world. If the change involves proxies or threading models, compatibility problems may appear only when players move between servers or when plugins access data concurrently.
Official references
These primary project sources were checked on September 23, 2026. Software status changes quickly, so the linked project documentation should win over this article if a newer release changes support or requirements.
Related server software
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.