Skip to content

Your machine

A panel for your own server

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>
The panel shows this command with your one-time token

Requirements

What machine will do

Usually a VPS or dedicated server with a public IP. The CPU must be x86_64.

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)

Windows

  • Windows 10 version 1809 or later and Windows 11 — the primary platform
  • Windows Server 2019 or later
  • No Docker, WSL or Hyper-V required
  • Administrator rights

Any system

  • A public IP: the panel does not forward ports through NAT, so a home PC is not the main use case
  • Outbound internet access: games and mods download from Steam, Mojang and other official sources
  • You open game ports yourself — shardox health --ports shows what is blocked and the command to fix it

Install

One command — and the node is in the panel

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>
The token is single-use and valid for one hour.
  1. The script downloads the agent

    Binaries come from our servers and are verified against their signature.

  2. The node registers

    The agent creates a key, gets a certificate with the one-time token and installs its services.

  3. Diagnostics

    shardox health runs right after install: connectivity, runtime, disk and resources.

Agent

What the agent does on your machine

A single shardox service — both the daemon and the CLI. Game data lives on your machine; the panel gets it from the agent.

  • Deploys servers

    Creates servers from game templates, applies limits and keeps an eye on their state.

  • Serves console and files

    Console, logs and the file manager work through the agent — no SSH or RDP.

  • Runs schedules

    Restarts, commands, wipes and updates fire by the machine’s own clock.

  • Updates games

    Checks Steam for new builds and updates via SteamCMD according to your policy.

  • Collects metrics

    CPU, memory, network and disk — per server and per node.

  • Updates without downtime

    New agent versions install without restarting game servers and roll back if anything goes wrong.

Command line

Everything is visible from the machine, too

shardox status shows the panel connection, resources and servers, and shardox health tells you what keeps players from joining.

shardox status
$ 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
Node status
shardox health --ports
$ 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 ✓
Port check

Windows

Shardox Engine — containers on Windows without virtualization

Our engine speaks the same API as Docker, so server templates are identical on Linux and Windows.

  • A user per server

    Each server runs as a separate hidden user that cannot sign in or use RDP.

  • Sandbox

    AppContainer, a separate desktop and Job Object limits on CPU, memory and processes.

  • Network rules

    A server listens only on its own ports and cannot see the local network or agent ports.

  • Disk quotas

    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

How the agent protects your machine

The agent is a guest on your machine, so it opens as little as possible and verifies everything it installs.

  • Outbound connections only

    The agent connects to the panel over TLS 1.3 and never accepts inbound connections.

  • A certificate per node

    mTLS with automatic certificate renewal; deleting a node revokes its certificate.

  • Signature checks

    Agent releases are signed with Ed25519 and images are pinned by digest. Nothing unsigned gets installed.

  • Management access

    The local CLI and the Docker API are reachable only by root and administrators and are never exposed to servers.

  • Teams without a shell

    Project members get the game console and server files, never a shell on the machine.

  • Audit log

    Every action in the panel and on the machine lands in the project log.

Ready to connect your machine?

Signing up takes a minute, installing the agent a couple more.