MuteCloud
A cloud system for Minecraft networks, written in Rust.
Release soon
MuteCloud has not been published yet. Download and install command follow with the first public release; this documentation describes the system as it will ship.
MuteCloud runs a Minecraft network from a single binary. It starts proxies and game servers as ordinary processes, brings its own Java runtime for every group, and keeps the whole setup in readable TOML files.
At a glance
| Type | Cloud system for Minecraft networks |
| Written in | Rust |
| Install | one command, published with the first release |
| Needs | nothing preinstalled, no Java, no screen, no sudo |
| Footprint | around 10 MB of RAM for the cloud itself |
| Supports | Paper, Purpur, Folia, Velocity, Minecraft 1.8 through current |
Design principles
Configuration remains under your control. Groups are TOML documents. MuteCloud reads them and never rewrites them, which allows them to be kept under version control.
Java runtimes are managed per group. A BedWars group on 1.8.8 receives Java 8 while a lobby on 26.2 receives Java 25, concurrently on the same machine. Package updates of the host system cannot replace the JDK beneath a running server.
Templates are layers rather than copies. A plugin update is placed in layers/global
and applies to every group referencing that layer, instead of being copied into each
template individually.
Crashes are preserved. Console history, exit code and crash report are written to
dumps/ before the working directory is cleaned up.
The control plane is a service, not a terminal session. MuteCloud does not rely on screen or tmux. The command line communicates with the daemon over WebSocket and remains available even when a server console is blocked.
Getting started
- Installation sets up the first network
- Groups describe what runs and how much of it
- Templates put files into every server, in layers
- Commands for everyday work
Concepts
| Term | Meaning |
|---|---|
| Node | a machine running MuteCloud |
| Group | a rule for what servers exist, such as Lobby or BedWars |
| Server | one running process from a group, such as Lobby-1 |
| Template | a layer of files copied into every server |
| Bridge | the plugin connecting a server to the cloud |
| Leader | the node making the decisions in a cluster |