Ferrix Systems
Orders & provisioning

Placing an order

May 3, 2026

Ordering a service is done through a multi-step flow. Paths differ slightly depending on product type (virtual machine, LXC/container, game server, or Quick App), but billing and checkout work the same.

Where to start

Open Services → Deploy/Order, or use a dashboard shortcut when available.

Choose product and workload

Pick the workload that fits your deployment:

Type Typical use
Virtual machine (QEMU VPS) Full Linux/Windows VMs, SSH/console, CPU/RAM resizing when supported
LXC/container Lightweight Linux workloads with SSH access—no QEMU console UI
Game server Pterodactyl-backed workloads with egg/start variables reviewed at order time
Quick Apps One-click installs (examples may include stacks like WordPress) with prompts for required credentials

Prices, limits, HA, backups, coupons, templates, SSH keys/passwords update based on selections.

Location, template / egg, sizing

Pick a location plus hardware role tier when prompted. VMs need an image/template; Quick Apps/game servers may expose game eggs or presets and ask for identifiers like hostnames/server names plus optional variables.

Game servers validate capacity before checkout—if a location lacks allocation you may switch regions or retry later.

Add-ons when offered

Eligible products might offer high availability, hosted convergence, managed backups (frequency/schedule picks), plus coupon codes. Only apply what applies to your SKU.

Credentials and payment

Traditional VMs/containers commonly accept SSH public key or root password. Quick Apps use product-specific prompts; game servers omit traditional root credentials.

Proceed to Stripe Checkout via Deploy now. After payment succeeds you return automatically and provisioning begins unless staff approval gates the SKU.

Keep the tab steady—don't double-submit while checkout or provisioning spins.

More in Orders & provisioning

Other articles you might find useful.