endgateway.cccontrol surface
minecraft edge + operator surface

Give private Minecraft worlds a real End gateway.

endgateway.cc is a closed-by-default publishing layer for Minecraft Java Edition servers. It gives private machines a public game and voice edge, keeps DNS and access under operator control, and concentrates the sensitive parts of the workflow into one hardened surface instead of a pile of disconnected scripts and panels.

Java Edition
gameplay edge for private servers
Voice Ready
simple voice chat alongside live sessions
Closed by Default
public presence exists only when needed
endstone route
end watched edge
End dimension preview
Public entry for worlds that stay private by default
service preview
Private servers with a proper public edge
turnstile visible state
Server presence

Publish desktop-hosted Minecraft Java servers through one stable entry point instead of asking players to chase changing IPs or router workarounds.

Voice continuity

Simple Voice Chat stays part of the live route instead of becoming a broken side path.

Operator trust

Passkeys, TOTP, and visible challenge state back the operator side of the gateway.

chapter 01

Desktop-hosted worlds, public-ready

endgateway.cc is built for Minecraft Java servers that live on personal machines and still need a stable public presence without exposing the whole home network.

chapter 02

A cleaner edge for online hours

Players get a proper endpoint when a server is online, and that edge disappears again when the world goes down. Voice traffic and gameplay stay part of the same experience.

chapter 03

Operator security that belongs here

Account access, passkeys, TOTP, backup codes, and Turnstile checks are part of the operator surface because publishing private infrastructure should not rely on weak admin flows.

project overview

endgateway.cc is the edge layer between private machines and public play.

The tunnel service, DNS presence, voice support, and operator portal belong to the same product. The public site should explain that service clearly, while the auth routes handle who is allowed to run it.

Primary use case
Minecraft Java servers hosted behind NAT on desktop machines
What goes public
Only the live gameplay and voice edge for active servers
Operator access
Password login, passkeys, TOTP, backup codes, Turnstile
Deployment surface
Small VPS edge, Docker deployment, Cloudflare-backed presence