Servers that scale themselves
Set a floor, a ceiling and how full is too full. Atlas starts another
bedwars when the current ones fill and stops it when they empty, without
anybody watching a player count.
Attach your own machines. Describe the groups you want — a lobby, a survival world, a minigame — and Atlas runs them, keeps every proxy pointed at the right backends, and adds servers as players arrive.
One node and three servers, free. No card, no trial clock.
Proxy
Groups
Every one of these is something a network operator normally maintains across a proxy config, a pile of server directories and a scheduler nobody wants to touch.
Set a floor, a ceiling and how full is too full. Atlas starts another
bedwars when the current ones fill and stops it when they empty, without
anybody watching a player count.
The proxy is a group like any other. Its list of backends is rewritten as servers come and go, and player-info forwarding is configured on both sides — no secret copied between two config files by hand.
Templates stack in layers: a base image, your plugins, per-group overrides. Change the
layer once and every server built from it agrees, instead of drifting apart one
scp at a time.
Edit the server list entry, the tab list and the maintenance gate in one place. It reaches every proxy while they are running — nobody is disconnected and nothing restarts.
Live console for any server in the network, streamed to the dashboard, with the command box you would expect. Finding out why a server died does not start with finding its machine.
Atlas schedules and supervises; the servers run on hardware you own or rent. One install command enrolls a box, and it keeps working through a reboot or a lost connection.
Run one install command on any Linux box. It fetches the agent, checks it against a published checksum, and enrolls with the control plane. Docker is installed for you if it is missing.
A proxy group and at least one game group. Pick a template, set how many servers should exist and when another should start. Atlas builds them and tells the proxy where they are.
Players connect, land in the group you nominated, and the network grows and shrinks underneath them. You go back to building the server rather than operating it.
$ curl -fsSL https://get.atlasgg.com/agent.sh | sudo bash -s -- \ --token atlas_enroll_7f2a… --network fadehq --node eu-west-1 ✔ docker present ✔ atlas-agent verified against SHA256SUMS ✔ enrolled — streaming to the control plane # the dashboard now shows this machine, and can # place servers on it node eu-west-1 online · 0 servers · 16 GB free
A busy night should cost you nothing extra. You pay for the hardware you attach, and put as many servers on it as it will hold.
Enough to run a real, small network and decide for yourself.
For a network that outgrew one machine.
Cancelling returns the account to the free tier rather than switching anything off, so the last thing you had running keeps running.
Attach one machine, describe one group, and watch it run itself. The free tier is a real network, not a demo.