Quick answer
Velocity is minecraft java proxy. Connect multiple backend Minecraft servers behind one public address with high performance, modern forwarding, extensibility, and strong network administration features.
| Developer / maintainer | PaperMC team and contributors |
|---|---|
| Software type | Minecraft Java proxy |
| Upstream / lineage | Standalone proxy built from the ground up; not a fork of BungeeCord. |
| Current status | Actively maintained |
| Best fit | Modern multi-server Java networks using Paper-compatible backends or other supported server software and needing a maintained proxy. |
Who develops Velocity?
PaperMC team and contributors develops or maintains this project. Standalone proxy built from the ground up; not a fork of BungeeCord.
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?
Connect multiple backend Minecraft servers behind one public address with high performance, modern forwarding, extensibility, and strong network administration features.
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?
Velocity does not run a Minecraft world. It sits in front of backend servers and routes players between them, so comparing gameplay mechanics to Vanilla is not meaningful.
“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?
Compared with BungeeCord, Velocity is a separate modern proxy architecture rather than a fork. Waterfall is the discontinued PaperMC 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 Velocity good for?
Modern multi-server Java networks using Paper-compatible backends or other supported server software and needing a maintained proxy.
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
Uses Velocity plugins, not Bukkit plugins. Backend compatibility/forwarding must be configured correctly.
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
Velocity is PaperMC’s current proxy and is actively maintained. PaperMC documents stable releases, security, forwarding, tuning, and migration.
Current version note: Current Velocity requires Java 25 according to PaperMC’s getting-started documentation.
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 Velocity
Migration checklist: Move proxy plugins to Velocity itself and keep Bukkit/Paper plugins on their supported backends. Enable a compatible player-forwarding mode, protect its shared secret and isolate backend TCP ports from the public internet.
How to verify: Verify a login through the proxy, a server switch, permissions/identity forwarding and that a direct outside connection to the backend cannot succeed.
Backend servers are commonly configured in offline mode behind a proxy, which creates impersonation risk if they remain directly reachable. PaperMC strongly recommends firewalling/securing backends.
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.