What your machine needs
The Linux systems Aperture runs on, how much processor, memory and disk to plan for, and what setup installs on your machine.
Last updated 13 November 2026
Use a computer you control that can stay on while people play: a spare PC, a home server or a rented server (VPS). A fresh installation is the simplest start.
| System | Ubuntu 22.04 or 24.04, or Debian 12 or 13, with systemd and cgroup v2 (the default on all four). You need root or sudo. |
|---|---|
| Unraid | Unraid 6.12 or newer runs Aperture as an app on its Docker tab instead of the installation command. See Aperture on Unraid. |
| Processor | 64-bit x86 (AMD64), with at least 2 cores. The panel gives each game server 1 to 4 cores; most get 2. ARM64 machines can connect, but no games run on them yet; Minecraft: Java Edition for ARM64 is coming soon, so use AMD64 for now. |
| Memory | About 1 GB for the system plus each server’s share. The panel reserves 0.5 to 2 GB for small games (Terraria 1 GB, Minecraft 2 GB), 4 GB for Valheim, 8 GB for 7 Days to Die or Satisfactory, 12 GB for Rust and 16 GB for Palworld. 8 GB is a comfortable start. |
| Disk | At least 8 GiB of free disk under /var/lib to install, then 1 to 40 GB per game server plus room for its backups. |
| Network | Normal outbound internet access, including TCP 7443 to relay.aperture.sh, which carries the panel’s connection to your machine. For players, a public IPv4 address you can forward ports to, a VPS, or a tunnel if you can’t open ports (see Open your ports). |
Virtual machines and LXC containers
A virtual machine works like any other machine. An LXC container works too, for example on Proxmox VE: make it an unprivileged container with Nesting and keyctl turned on (under Options, then Features), give it Cores rather than only a CPU limit, and restart it before you install. Without Nesting the install finishes, but no game server can start. Tested on Proxmox VE 9.
What setup installs
The installer adds the packages it needs and Docker if it’s missing. It reuses a working Docker installation; a Podman alias isn’t enough. It won’t replace a Wings installation that’s already running. Back up anything important on a machine that already runs other services.
Setup stores programs in /usr/local/lib/aperture-node, configuration in /etc/aperture-node, and installation state, game files and local backups under /var/lib/aperture-node.
It installs an FRP client alongside official Calagopus Wings and creates a separate Docker network. aperture-wings.service and aperture-relay-client.service start at boot; aperture-relay-refresh.timer keeps the client’s routes current. During setup, aperture-node-install-recovery.service can resume interrupted enrollment. Setup disables it once linking finishes.
What Aperture can do on your machine
Wings runs with root privileges and controls Docker on your host. The hosted panel uses it to manage your game servers and their files. You keep your SSH credentials, but linking the machine still grants Aperture privileged management access. Use a host you control and keep backups outside that machine.
If setup is interrupted
Keep the terminal open until installation finishes. If it’s interrupted, use Copy resume command in your account and run it on the same machine. Do not claim the same panel from a different machine. Your account shows progress and any setup errors.