Bedrock is a platform, not a version of Java.

Bedrock and Java are two editions

Minecraft ships in two editions that look similar and are not compatible by default. Java is the original, runs on desktop, and is the edition with plugins and mods. Bedrock runs across mobile, console and Windows, uses Microsoft accounts, and has its own official server software and its own content system.

If your players are on phones, an Xbox or a Switch, they are on Bedrock. If they are on a desktop with the Java launcher, they are not. The two cannot join the same server without a translation layer, which is the single most important thing to understand before you choose.

The Vanilla Bedrock server

The Rynox panel lists the same server software for every Minecraft plan, and one of the available spells is Vanilla Bedrock — the official Bedrock server. Installing it gives you the unmodified Bedrock experience, which is the closest thing to a stock server that the edition offers.

• It is the official server for the Bedrock edition, so it tracks the same releases as the client.
• It uses Bedrock accounts and the Bedrock protocol, so only Bedrock clients can connect.
• It supports the Bedrock add-on system rather than Java plugins or mods.
• It pairs naturally with plans that list both Java and Bedrock, where you can run either edition or one of each.

Ports and protocols

Java and Bedrock do not collide, because they use different ports and different protocols. A plan can host both at once.

One practical consequence: if you also run a Java server, players connect to a different address for each edition. Bedrock clients use the Bedrock address and the client’s own add-server flow, which is a little different from typing a Java address into a server list.

Cross-play with Geyser and Floodgate

The common way to let Bedrock players join a Java server is a plugin called Geyser, which sits on the Java server and translates between the two protocols. A companion plugin, Floodgate, lets those Bedrock players connect without needing a full Java account.

This is genuinely useful and it is not invisible. A translation layer is a best effort, not a perfect copy, and you should go in expecting rough edges.

• Visual and mechanical differences. Combat timing, some animations and certain blocks behave differently between the editions, and the layer cannot fully reconcile them.
• Plugin and mod limits. Java content that depends on deep server internals may not translate cleanly for Bedrock clients.
• Resource packs. Custom Java textures and models do not automatically reach Bedrock players, who use the Bedrock resource pack system instead.
• Performance overhead. Translation costs some processor time on the Java server, which comes out of the same tick budget as everything else.

If your audience is mostly console and mobile, running Vanilla Bedrock directly is simpler and steadier than translating a Java server. If your audience is mostly Java with a few Bedrock friends, Geyser is the pragmatic bridge.

Add-ons are not mods

Bedrock content comes as add-ons, which split into behaviour packs that change how things work and resource packs that change how things look. They are installed through world and server configuration rather than through a mod loader, and their reach is narrower than Java mods.

Add-ons also need to be available to the clients to work correctly, which is a different distribution problem from Java mods. Plan for that before promising a heavily modded Bedrock experience, because the Bedrock add-on ecosystem is smaller than the Java one and not every idea translates.

Region matters just as much on Bedrock

Bedrock clients are still clients. A player on a phone in India talking to a server overseas has the same physics problem as a Java player, and the same fix: host on the node nearest the players. The India node is IN-1, and US-1 and US-2 cover North America.

Mobile players are often on variable connections, so a short, clean route matters more here than on a wired desktop. Choosing the right region is the single cheapest improvement you can make to a Bedrock server, and it is decided at checkout.

Running it from the panel

Once the Vanilla Bedrock spell is installed, day-to-day management is the same as any other Rynox server. The panel at panel.rynoxhosting.online gives you console access, file management and live specs, so you can edit server settings, upload add-ons and watch resource use without leaving the browser.

Support runs through Discord and the on-site ticket system. If you are not sure whether a plan supports the edition mix you want, check the editions listed on the plan on the pricing page, or ask before you buy.

Bedrock hosting — questions