VPS on the same contract
A VPS keeps the same instance_id and allocations as a game server. Guests are floki with libvirt, and that isolator cannot define a domain yet. Public create does not offer VPS. Machines share this contract later.
Same contract, different source
A Foxcore VPS is an instance kind on the hosting contract, not a parallel panel. It keeps the same instance_id and allocations. Game guests are foxd with rootless Podman. VPS guests are floki with libvirt, and that isolator cannot define a domain yet. Public create does not offer VPS.
The purchase is one Pro subscription. The selected size is the memory and CPU cap; disk is not quota'd. The title is a pack, not a price. There is no per-OS SKU and no competitor chrome. Guest workloads still run on the node agent; the Worker never hosts your VM.
Machines (Git, Dockerfile, or image) share this contract later. Create does not offer machine today — that tile stays UnavailablePanel-honest until it ships.
From the panel
Public create does not offer VPS. Services → Create is a game pack, a region, and a size. Switch-title stays on game packs. A VPS overview does not invent pack editors or a libvirt domain.
- Sign in and open Services.
- Create a game server from a pack. That guest is foxd with rootless Podman.
- Public create does not offer VPS.
- A VPS guest is floki with libvirt, and that isolator cannot define a domain yet.
- Include the instance id if you contact support.
Is a VPS a separate plan?
No. Game and VPS share one instance contract and one Pro subscription. They do not share an isolator. A game guest is foxd with rootless Podman. A VPS guest is floki with libvirt, and that isolator cannot define a domain yet. Public create does not offer VPS. The Worker never hosts your VM.