Uebliche

Appearance

GatewayAPI-driven Minecraft TCP gateway

Headless relay nodes managed through Public API and Dash.

Getting Started
Deployment
Routing Lifecycle
Gateway

Headless control plane

Node registration, heartbeat, and route state come from the Public API.

Minecraft TCP data plane

mcproxy routes Minecraft traffic on 25565 based on active route snapshots.

Minimal port surface

Exactly three ports: 25565 (Minecraft), 9001 (Connect control), 80 (health).

Dash/API operations

Inventory, route ownership, and enable/disable are handled in Dash with API permissions.

Gateway ​

Gateway is the Connect network edge for Minecraft TCP traffic.

This project is intentionally headless:

  • no standalone gateway dashboard
  • no local gateway auth UI
  • no route editing inside the gateway runtime

All control-plane state is sourced from the Public API and operated via Dash + API permissions.

Runtime architecture ​

  • watcher (Rust): registers the gateway, sends heartbeats, fetches route snapshots, writes routes.json.
  • mcproxy (Rust): listens for Minecraft TCP and forwards connections to active route targets.
  • Public API: source of truth for gateway inventory and server route ownership.
  • Dash: operator UI for gateway visibility and admin actions.

Open ports ​

  • 25565/tcp: Minecraft client traffic.
  • 9001/tcp: Connect tunnel/control + runtime metrics endpoints.
  • 80/tcp: health endpoints (/health, /healthz).

Current docs ​

Legacy cleanup note ​

Older documentation sections about the previous watcher UI, topology canvas, and in-gateway Cloudflare management were removed from this section because they no longer match the current architecture.