ConduitDocs
ende

Run a Minecraft network like infrastructure

Conduit is a self-hosted control plane for Proxmox. Deploy servers, move players between them without a loading screen, back the whole fleet up, and watch it from one panel that survives losing a node. Join a second cluster at another provider and run both from either panel.

Install Conduit Source

Start here

InstallTwo shapes: a single-process development setup, and the production 3-node HA topology this project actually runs in. A guided installer under install/ drives both and verifies every stage; the…
ArchitectureHow Conduit turns a Proxmox VE cluster into a self-operating game network.
Feature referenceEvery feature Conduit ships, what it is for, and what it deliberately does not do. The longest document here, split into twelve sections.

One cluster over joined clusters

Two Proxmox clusters at two providers can be joined. Each keeps its own store; the panels reach each other's nodes over an encrypted mesh, accounts and roles replicate, every change goes to the cluster that owns the record, and a panel hostname is taken over by the other cluster when its owner falls silent and handed back when it answers again.

Federation — more than one cluster, and the link between themDesign 2026-08-21. Status: not built. This document exists so that the parts which are already true are written down, and so the parts that are not are described precisely enough to argue with…
Domains and TLSWhat the Domains page manages: one zone, one list of public hostnames, the DNS records that follow the panel's public address, the certificate in front of the panel, the SSH gateway's own name, and…
DatabasesThe Databases page covers the engines Conduit runs for itself, a browser and editor over the two SQL ones, a read-only view of the Valkey, a SQL console with stated limits, and managed databases…

Find your way in

Running itDay to day: servers, players, permissions, backups, updates.and 8 more
Building on itThe API, the CLI, and how the difficult parts work.and 7 more
Evaluating itWhat it is, what it measures, and how it compares.and 2 more

The panel

The overview — fleet pulse, node and container counts, live cluster metrics, and every service in one table, with a joined cluster's rows marked as its own

The overview — fleet pulse, node and container counts, live cluster metrics, and every service in one table, with a joined cluster's rows marked as its own

Measured on the live cluster

9 ms

Agent round trip

against 393 ms for `pct exec`

1.2 s

Proxy failover

socket death to traffic restored

32 KB

Upload memory

peak for a 64 MB file — 256 MB before

207 ms

Fleet log search

351 hits across 12 servers

Every figure is reproducible — the method is in Benchmarks.

Start here

What Conduit is, and getting it running.

InstallTwo shapes: a single-process development setup, and the production 3-node HA topology this project actually runs in. A guided installer under install/ drives both and verifies every stage; the…
ArchitectureHow Conduit turns a Proxmox VE cluster into a self-operating game network.
Feature referenceEvery feature Conduit ships, what it is for, and what it deliberately does not do. The longest document here, split into twelve sections.

Install & operate

Standing it up and keeping it up.

Migrating a live network onto ConduitHow to move a running Minecraft network — CloudNet-style templates, static services, Skript systems, databases, worlds — onto a Conduit cluster without losing what makes it that network. This is…
Updates & the HubHow a Conduit cluster learns that a new version exists, how it installs one on itself, and what — if you leave telemetry on — it says about itself while doing so.
Domains and TLSWhat the Domains page manages: one zone, one list of public hostnames, the DNS records that follow the panel's public address, the certificate in front of the panel, the SSH gateway's own name, and…
SecurityThe security model as implemented — auth, authorization, machine trust, credential handling, and audit. File references are the authoritative source.
PermissionsEvery permission Conduit checks in-game — what it gates and who should hold it. These are LuckPerms nodes like any other; grant them to groups on the panel's /permissions page. Wildcards work…
DatabasesThe Databases page covers the engines Conduit runs for itself, a browser and editor over the two SQL ones, a read-only view of the Valkey, a SQL console with stated limits, and managed databases…

Reference

Every feature, API and command.

APIThe panel exposes a JSON HTTP API under /api. Every route documented here exists in dashboard/src/app/api/** — methods and auth were read from the handlers, not inferred.
CLIcli/conduit is the command-line client for the panel — a thin layer over the same HTTP API the dashboard uses, plus the console proxy for live terminals. Zero dependencies, plain Node ≥ 20 (the…
DevelopmentHow to work on Conduit without breaking a live network.
ContributingConduit is developed against a live production network, which shapes how changes land.

Under the hood

How the difficult parts actually work.

Proxy HA — the last data-plane SPOFDesign 2026-08-11; built, deployed and rehearsed the same day. Status: live — two proxies on two nodes behind the health-followed VIP. 2026-08-13: failover moved from the 10 s reconcile tick to a 1…
Seamless backend transferStatus: working, owner-verified on the test cluster (2026-07-26). A player walks across a shard seam and keeps the world — no loading screen, no protocol error, no snap-back to the boundary.…
Federation — more than one cluster, and the link between themDesign 2026-08-21. Status: not built. This document exists so that the parts which are already true are written down, and so the parts that are not are described precisely enough to argue with…

Evidence

Measurements, and comparisons against them.

Measured, on the live clusterNumbers Conduit's design claims rest on, taken from the running fleet rather than from a synthetic harness. Where a claim is structural — true because of how something is built, not because of what…
CloudNet (screens) vs Conduit — a measured comparisonTwo real networks, measured on the same evening (2026‑07‑30): the production network running CloudNet 3 with screen sessions on a single 192 GB node, and the Conduit cluster — three Proxmox nodes…

Reviews

Point-in-time audits, kept as written.

Architecture review — 2026-08-06A structural read of the panel ahead of V1, measured against the live cluster rather than inferred from the code alone. Findings are ordered by likelihood × blast radius. Where the design is sound…
Security review — 2026-08-23A sweep over every API route, every authentication path and every open connection across the three installs (the main cluster, edge-01, edge-02). Everything below was measured against the running…