Geyser and Floodgate
A protocol bridge between Bedrock clients and a Java server. Useful for mixed friend groups. It does not let the Java server run Bedrock add-ons, and some Java plugins assume Java client behaviour.
Java Edition · planned
Java hosting for plugin and mod communities.
Planned Java Edition hosting built around the three software families that actually matter to server owners: Paper for plugins, Fabric and Forge for mods, and Vanilla as the baseline. None of it is provisioned yet.
Java at a glance
- Status
- Planned — not available
- Planned software
- Vanilla, Paper, Fabric, Forge
- Not planned
- NeoForge, Purpur, Spigot
- Client requirement
- Java Edition, matching version
- Live servers
- 0
Who this is for
Communities that already run Java servers and know what they need.
Java Edition hosting is for survival SMPs, plugin-driven public servers and modded communities. The common thread is that the operator cares about control, not just a player count.
Java Edition is the original desktop edition. Its server ecosystem is the reason hosting is a real product rather than a rented VM: plugins and mods let a community change how the game works, and those changes need somewhere to live.
The planned Java product is opinionated about software. Paper is the default for plugin servers because it is widely compatible and actively maintained. Fabric and Forge cover the two main modding ecosystems. Vanilla stays available for communities that want official behaviour with no third-party layer.
This page describes intent. No Java server, world, plugin directory or port exists in the prototype, and no price is an offer.
Software support
What is planned, and what is deliberately not.
A short catalogue. The full comparison, including third-party Bedrock servers, is on the server software page.
| Software | Extensions | Support status | Why |
|---|---|---|---|
| Vanilla (Java) | None | Planned, not built | Planned as the baseline Java option. Update handling and version pinning are not implemented. |
| Paper | Plugins | Preview only | Selectable in the create-server preview. No Paper jar, plugin directory or update pipeline exists in this prototype. |
| Fabric | Mods | Preview only | Selectable in the create-server preview. No mod loader, mod resolution or compatibility checking exists. |
| Forge | Mods | Planned, not built | Shown in the preview as an intended option. Forge installer pipelines and modpack handling are not built. |
| NeoForge | Mods | Not planned | Not in the planned first-release set. Revisit only if customer research shows demand. |
| Purpur | Plugins | Not planned | Not in the planned first-release set. Paper is the supported plugin path; forks add maintenance burden. |
| Spigot | Plugins | Not planned | Not planned as a separate option. Paper already accepts the same plugin API. |
Software names belong to their respective projects. Listing an implementation here is not an endorsement, and no third-party software is redistributed by this prototype.
Planned inclusions
What a Java plan is meant to include.
- A dedicated RAM allocation per plan, not a shared player-count cap
- Java version selection with a stable default
- Plugin directory for Paper servers; mod directory for Fabric and Forge
- Console access with command history and an audit trail
- Scheduled off-node backups with a tested restore path
- A published address and port once provisioning is real
Every item above is a plan. None is implemented or selectable today.
Honest limits
Version churn is real
Every Minecraft release breaks some plugins and many mods. A host cannot promise that any plugin or mod keeps working across a version change; we plan to let you pin a version instead.
Plugins and mods are different worlds
Paper plugins do not load on Fabric or Forge. Fabric mods do not load on Forge. Mixing them requires separate server types or dedicated bridging mods, and we will not pretend otherwise.
RAM is not the only limit
Modded servers are usually bound by single-core CPU performance and world generation, not RAM alone. Plan tiers list RAM because owners compare RAM, but CPU matters at least as much.
Migration is a process, not a button
Moving an existing world means transferring the world folder, plugin or mod sets and configuration, then testing compatibility. Guided migration is planned, not implemented.
Cross-play
Java players and Bedrock players can share one server — with caveats.
A protocol bridge can let Bedrock clients join a Java server. That is a convenience, not the same thing as Bedrock hosting.
Version translation
Tools such as ViaVersion or ViaProxy can translate protocol versions. Helpful during updates, but they cannot make incompatible plugins or mods work, and they add another component to maintain.
Cross-play support is planned, not offered. No bridge is deployed.
Java or Bedrock?
Check the other edition before you decide.
If your community plays on phones or consoles, Bedrock hosting is the relevant product — and it uses different server software entirely.
Pre-launch prototype · No live Minecraft server · No payment collected