01 $ overwing enroll
Enroll your node.
Mint a single-use token in the panel and run one command on your machine. The agent dials out to the control plane — no inbound management ports — and earns trust on its first verified heartbeat.
$ overwing init --fleet yours
Your hardware.
Your clients.
Our panel.
Run hosted game servers or enroll your own machines with one command. Invite your clients and manage 95 games from the same real-time dashboard, with unmanaged and hands-on managed service available.
overwing — the control plane for game servers
$ overwing status
games_supported ······ 95
one_click_content ······ 1257
node_enrollment ······ 1 command
dashboards ······ real-time
$ overwing enroll --node yours
✓ trust established on first heartbeat
✓ credentials rotate monthly
$
$ overwing enroll --help
From bare metal to hosting business in three steps.
02 $ overwing invite
Invite your people.
Organizations with owner, manager, and member roles. Send email invitations; your clients get their own portal, scoped to exactly what's theirs and nothing else.
03 $ overwing deploy
Deploy game servers.
Pick from 95 supported games. Every action runs as a durable, audited job with automatic retries — and the console is live while the server installs.
$ overwing panel --show
Everything your hosting business runs on.
This is the actual client portal — the same control plane and real-time streams we run our own fleet from. Click through the sidebar to explore each section: overview, servers, nodes, storefront, and billing.
panel.overw.ing/orgs/legacy-hosting/servers interactive demo
LLayover LabsClient portal
Organization
Legacy hosting
Moperator@studio.ggowner
Game servers
This organization's game server instances, their reserved resources, and live utilization.
Servers
3
2 running
CPU reserved
6 vCPU
≈ 0.2 cores in use
Memory reserved
24 GB
7.4 GB in use
Players
7 / 30
players online now
| Server | State | Resources | Live | Created |
|---|---|---|---|---|
Survival SMP minecraft-java-01 | running | 8 GB · 2 vCPU 16 GB disk | CPU 6% · 6.4 GB 4/20 players | Jul 12 |
Valheim — Midgard valheim-01 | running | 6 GB · 2 vCPU 12 GB disk | CPU 13% · 1.0 GB 3/10 players | Jul 09 |
Zomboid — Knox County project-zomboid-01 | stopped | 10 GB · 2 vCPU 20 GB disk | — | Jul 15 |
Console · Survival SMP
live[Server thread/INFO]: Starting minecraft server version 1.26.2 [Server thread/INFO]: Preparing level "world" [Server thread/INFO]: Done (4.812s)! For help, type "help" [Server thread/INFO]: Steve joined the game > whitelist add Alex [Server thread/INFO]: Added Alex to the whitelist
Type a console command…Send
- Live console
- A streaming web console with command input for every server. Watch installs, restarts, and player joins as they happen.
- Durable job engine
- Every create, restart, install, and backup runs as a durable job with automatic retries, a full audit trail, and dead-letter review. Nothing disappears into a queue.
- Multi-tenant by design
- Organizations with owner, manager, and member roles, plus per-server grants. A tenant can never see — or even discover — another tenant's servers or nodes.
- Players & whitelist
- See who's online. Kick, ban, op, and manage the whitelist from the panel — no config files.
- One-click content
- 1101 curated Minecraft plugins and mods from Modrinth across Paper, Fabric, Forge, and NeoForge, plus 156 Steam Workshop picks. Installed into the right folder for the right version.
- Backups that run themselves
- Scheduled backups on by default, on-demand snapshots any time, restore from the panel.
- Files & firewall
- A full file manager with uploads, plus firewall controls for the ports each server actually uses.
- Trust-gated nodes
- Single-use enrollment tokens, first-heartbeat verification, version compatibility checks, and automatic monthly credential rotation — a node earns its place before it runs workloads.
- Game-aware extras
- Minecraft world controls — time, weather, game rules — from the panel. Install Simple Voice Chat and its port opens automatically.
$ overwing portal --for clients
Your clients get their own front door.
Invitation-only accounts, organization-scoped access, and a live view of exactly what belongs to them — their servers, their nodes, their activity. You control who gets in and what role they hold; the tenant boundary does the rest.
- 01 Email invitations you issue
- 02 Servers & nodes, org-scoped
- 03 Live activity feed
- 04 Self-service node enrollment
panel.overw.ing — whoami
$ overwing whoami --scope
- Their game servers, with live state
- Their nodes, with workload readiness
- Real-time job & node events
- Nothing that belongs to anyone else
$ overwing games --list | head -21
If your clients play it, the panel runs it.
…and 74 more, from Factorio to DayZ to open.mp. Browse all supported games → See the content library →
overwing — access request
$ overwing access --request
Early access is invitation-only
We’re onboarding operators and hosted game-server customers one at a time while the white-label layer lands. Review the plans now, then we’ll confirm the right fit before provisioning.
$ overwing faq
Questions operators actually ask.
Do you host the game servers?
Yes, in two distinct ways. Operators can bring their own nodes and use the panel, while direct customers can choose Layover-hosted unmanaged or managed game-server capacity. The pricing page keeps those service levels explicit.
What do I need to connect a node?
A Linux machine with systemd that you control. Mint a single-use enrollment token in the panel and run one command on the box — the agent dials out to the control plane, so you don't open inbound management ports.
Which games does the panel support?
95 games today, from Minecraft and Valheim to Counter-Strike 2 and Project Zomboid, with 1257 curated plugins, mods, and Workshop items installable in one click.
Can my clients manage their own servers?
Yes. Every organization gets the client portal: your clients sign in with email invitations you control, see exactly their own servers and nodes, watch a live activity feed, and hold roles you assign — member, manager, or owner.
How do nodes stay secure?
Enrollment tokens are single-use and expire. A node is only trusted after its first verified heartbeat, must pass version and conformance checks before it's marked ready for workloads, and its credentials rotate automatically every month. Every privileged action is audited.
How do I get access?
The platform is in an invitation-only private beta while we finish the white-label layer. Pricing is published now so early customers can choose the right server before we provision it; existing clients sign in through the client portal.