GeyserLite
GeyserLite is Minekube's managed runtime packaging for GeyserMC. Gate uses it for Bedrock cross-play without requiring operators to run and wire a separate Geyser process for the common case.
For operator setup and configuration examples, use the Bedrock support guide.
Topology
Bedrock player
-> GeyserLite
-> Gate classic
-> optional ViaLite
-> backend serverGeyserLite is the Bedrock ingress layer. It translates Bedrock protocol into Java protocol before the connection reaches Gate. Gate then owns routing, events, forwarding, Connect integration, and backend login.
If ViaLite is enabled, it sits behind Gate. Bedrock traffic is already translated to Java before ViaLite handles backend version translation.
Runtime Scope
GeyserLite is responsible for the managed Geyser runtime shape:
- Native executable for managed subprocess mode.
- Shared library for embedded integrations where supported.
- Container image for standalone deployments.
- Release artifacts and checksums that Gate can consume as a managed dependency.
Gate decides which runtime mode to use for the current platform and configuration. The Bedrock guide covers the Gate config surface.
Version Policy
GeyserLite tracks upstream Geyser through a pinned source ref and a managed release chain. Production guidance follows upstream Geyser support:
- If Geyser officially supports the relevant Java and Bedrock versions, Gate's managed Bedrock mode is the stable path.
- If a backend updates to a brand-new Java version before Geyser supports it, production networks should usually wait before upgrading Bedrock-critical servers.
- Preview pins are exceptional. They should require a concrete upstream Geyser preview build or PR and a clear user-impact reason.
ViaLite may help when only the Java backend protocol is newer, but it cannot fix unsupported Bedrock client protocols or missing Geyser Bedrock-to-Java translation.