We handle
- Hypervisor, host patching, dedicated capacity reservation, and storage
- Snapshots, off-host backup copies, and restores
- Capacity planning and priority during maintenance
- Additional block storage provisioning on request
Performance Virtual Server
More cores, more memory, and dedicated CPU rather than burst.
What this tier is
Burst CPU is fine until your workload is the burst. Compilers, video encoding, self-managed databases, and anything doing sustained work will exhaust a shared-core allocation and then perform unpredictably, which is worse than performing slowly.
This tier reserves its CPU allocation rather than sharing it opportunistically. It costs more because the capacity is genuinely held for you, including while you are not using it.
Specification
| vCPU | 4 cores, dedicated allocation |
|---|---|
| Memory | 8 GB |
| Storage | 200 GB on SSD-backed storage |
| Operating system | Supported Linux distribution of your choice |
| Access | Root over SSH plus independent console |
| Snapshots | Daily, 30-day retention, copied off-host |
| Additional storage | Block volumes on request |
| Maintenance | Priority scheduling during host windows |
What is included
- Four dedicated vCPU with reserved allocation
- 8 GB memory and 200 GB SSD-backed storage
- Scheduled snapshots with off-host copies and longer retention
- Priority scheduling during host maintenance windows
- Private networking to the managed data tier
- Console access and operator-assisted resizing
- Optional additional block storage attached on request
Typical use cases
- Continuous integration runners and build agents
- Self-managed databases where you need full control of the engine
- Media encoding, batch processing, or scientific workloads
- Applications that were unpredictable on a burst-CPU instance
Responsibility split
Written down so there is no argument about it later.
You handle
- The guest operating system and everything running on it
- Workload-level tuning and parallelism
- Telling us before a workload doubles so we can hold capacity
How provisioning works
Operator-provisioned. Because capacity is reserved, we confirm availability before taking payment where the estate is tight. Typical turnaround is one to two business days.
Order
Other tiers in Managed compute and containers
Entry
Container Workload
Your image, running on our cluster, described in a repository.
$14 /mo
- Declarative manifest held in Git, not clicked into a panel
- Public hostname with managed TLS, or internal only
- Restart policy, resource limits, and log access included
View details
Most common
Managed Virtual Server
A real machine with root, and somebody else responsible for the host.
$32 /mo
- Root access on a real virtual machine, not a container
- Scheduled snapshots with off-host backup copies
- Hypervisor, storage, and network operated by us
View details
Cron that somebody notices when it stops.
$9 /mo
- Execution history and exit codes, not silent failure
- Alert on failure or on a missed run
- Runs on maintained infrastructure, not somebody's desktop
View details
Background reading
- Docker for game servers: clarity over hype Reproducible builds, update flow, and where containers stop helping.
- Double NAT and CGNAT: the silent party crashers Symptoms, diagnosis, and when a hosted relay is the honest answer.