One game server, one customer, on machines you already own.
The customer gets an address to hand their players, a live console, a file manager, backups and scheduled restarts. You get a product to price, a plan to size it with, and a capacity model that says how many more you can sell before a machine is full.
Not a separate product. A second job for the same machines.
Game hosting is a section of the VPS module, running on the same machines, watched by the same people. A machine that runs virtual servers also runs game servers unless you tell it not to.
Every machine is listed, including the ones not hosting games
Deliberately: a list of game nodes alone would silently drop the machine that has not converted yet and the machine somebody switched off — exactly the two rows you go looking for.
| State | Meaning |
|---|---|
| Running games | A live game node that can take new servers. |
| Preparing | Being converted. Machines are prepared one at a time, a few minutes apart, so the guest network can be checked between each. |
| Not prepared yet | Queued. Converting a machine that already carries customer virtual machines is not a free operation, so the pass stops at the first sign of trouble rather than working through the list. |
| VPS only | Somebody switched game hosting off for this machine — a box can be kept for virtual servers alone. |
| Blocked | Something prevents it, and the reason is printed in the row: no agent installed, the agent has not been heard from, the machine is bare metal handed to a customer, or its agent reports a role that cannot run containers. |
Sold and used are two different numbers, and never mixed
Sold is what has been committed to customers. Used is what the machines are actually doing. A node at 40% used and 200% sold is what overselling looks like and is fine; the same node at 95% used is not. Where nothing has reported a figure the dashboard prints Not reported rather than a zero — an unmeasured machine must never read as an idle one.
The whole dashboard is one reading taken at one moment, refreshed about once a minute. If a refresh fails, the figures on screen are kept and a line appears saying they are older than they look.
- Active nodes
- Live now, out of every machine registered.
- Game servers
- Total, with how many are running.
- Memory sold
- Committed, against usable memory — physical memory times the oversell ratio, less what the node reserves for itself.
- Memory in use
- What the machine itself reports, against its physical memory.
- Free ports
- Free right now, out of the total seeded, with how many are cooling down. Nothing can be provisioned without port inventory, and the panel says so plainly when none is seeded.
- Disk sold
- Committed to customers, and whether the node can actually enforce a quota.
Over-limit is frozen, never destructive
Register more nodes than your licence covers and the nodes past the limit are marked Frozen. Servers already on a frozen node keep running and customers keep their console and their files. Creating a server there and changing an existing one are blocked. Nothing is deleted and nothing is stopped.
The panel also checks the entitlement before it installs anything, so a licence problem never leaves you with a converted machine you cannot attach.
Everything a game customer expects to do themselves
A game plan is edited on the product that sells it, alongside the price and the billing cycle — the catalogue of games you offer, and anything waiting on your approval, lives in the module’s own catalogue. Renewals, suspension and termination are the same lifecycle as every other service, so an unpaid game server behaves like an unpaid anything — see Billing.
What game hosting is built on
One node licence — €6 a month — covers a machine for virtual servers and game containers alike. Everything below is included in the tier itself.
- VPS moduleThe nodes, groups and agent that game hosting runs on.
- ProvisioningHow a paid order becomes a live service, for every product type.
- BillingRenewals, suspension and the invoice behind each game server.
- IPAMThe address space the nodes draw from.
- Reseller programLet partners sell your game plans under their own portal.
- PricingTiers, node licences and the 14-day refund window.
Try it on your own data. Refund inside 14 days if it’s not the fit.
Pick a tier and provision a tenant in under two minutes — isolated K3s namespace, your own database, the full product. If FluxBilling isn’t the right fit inside 14 days, open a ticket and we’ll refund the subscription. No sales call, no qualification gate.
- 01.< 1 minPick a tierLite from €4.95/mo. Upgrade later, no migration.
- 02.< 2 minProvision the tenantIsolated K3s namespace + your own PostgreSQL database. Full product, your data.
- 03.d0 — d14Refund inside 14 daysNot the fit? Open a ticket within 14 days and we refund the subscription. No questions, no qualification gate.