Linux
- Ubuntu 22.04 or 24.04
- Debian 12 or 13
- Docker Engine 24+ — the installer offers to set it up if missing
- Root access (sudo)
Your machine
Rent a VPS or dedicated server from any provider, install the agent with one command, and the machine appears in the panel. You keep root and choose the hardware and location.
curl -fsSL https://api.shardox.net/install/install.sh | sudo sh -s -- --token <ENROLL_TOKEN>Requirements
Usually a VPS or dedicated server with a public IP. The CPU must be x86_64.
shardox health --ports shows what is blocked and the command to fix itInstall
After you click “Add node”, the panel shows this command with your token:
curl -fsSL https://api.shardox.net/install/install.sh | sudo sh -s -- --token <ENROLL_TOKEN>Binaries come from our servers and are verified against their signature.
The agent creates a key, gets a certificate with the one-time token and installs its services.
shardox health runs right after install: connectivity, runtime, disk and resources.
Agent
A single shardox service — both the daemon and the CLI. Game data lives on your machine; the panel gets it from the agent.
Creates servers from game templates, applies limits and keeps an eye on their state.
Console, logs and the file manager work through the agent — no SSH or RDP.
Restarts, commands, wipes and updates fire by the machine’s own clock.
Checks Steam for new builds and updates via SteamCMD according to your policy.
CPU, memory, network and disk — per server and per node.
New agent versions install without restarting game servers and roll back if anything goes wrong.
Command line
shardox status shows the panel connection, resources and servers, and shardox health tells you what keeps players from joining.
$ shardox statusShardox agent 1.4.2 · engine 1.4.2 (protocol 7) — okNode node-7f3a "fra-vds-1" Windows 11 24H2Panel connected 3d 4h, control ctl-1, rtt 18 msUpdate 1.5.0 available (stable)Resources CPU 34% of 16 cores · RAM 21.3/64 GiBServers 4 total · 3 running · 1 stopped rust-main Rust running 112/200 dayz-pve DayZ running 41/60 mc-paper Minecraft Java running 12/50 ark-island ARK: SA stopped$ shardox health --portsPorts rust-main 28015/udp listening ✓ firewall ✗ external ✗ → Windows Firewall blocks inbound UDP 28015. Fix (PowerShell, admin): New-NetFirewallRule -DisplayName "Shardox rust-main 28015/udp" -Direction Inbound -Protocol UDP -LocalPort 28015 -Action Allow mc-paper 25565/tcp listening ✓ firewall ✓ external ✓Windows
Our engine speaks the same API as Docker, so server templates are identical on Linux and Windows.
Each server runs as a separate hidden user that cannot sign in or use RDP.
AppContainer, a separate desktop and Job Object limits on CPU, memory and processes.
A server listens only on its own ports and cannot see the local network or agent ports.
An NTFS quota per server, with access to its own files only.
Isolation without virtualization shares the kernel with the system — like a browser sandbox. For your own servers on your own machine, that is enough.
Security
The agent is a guest on your machine, so it opens as little as possible and verifies everything it installs.
The agent connects to the panel over TLS 1.3 and never accepts inbound connections.
mTLS with automatic certificate renewal; deleting a node revokes its certificate.
Agent releases are signed with Ed25519 and images are pinned by digest. Nothing unsigned gets installed.
The local CLI and the Docker API are reachable only by root and administrators and are never exposed to servers.
Project members get the game console and server files, never a shell on the machine.
Every action in the panel and on the machine lands in the project log.
Signing up takes a minute, installing the agent a couple more.