Plans & sizing

Documentation Index

Fetch the complete documentation index at: https://docs.rafftechnologies.com/llms.txt

Use this file to discover all available pages before exploring further.

_{Updated May 8, 2026} A plan is a fixed bundle of CPU, RAM, and base disk, billed at a single rate. Outbound bandwidth is unlimited on every plan. Picking the right plan is the main sizing decision when creating a VM. The full price list lives on Pricing; this page is the how-to-pick guide.

​

The two tiers

In simple terms:

• Standard — the platform may share the underlying physical core with other VMs. Performance is great most of the time but can have brief jitter when neighbors get busy. Best price/CPU.
• Premium — your vCPU is yours alone on the physical core. Performance is predictable and steady. Higher price/CPU but no noisy-neighbor dips.

If you can’t tell which fits, start with Standard. Move workloads to Premium when you can point to a specific symptom (latency p99 spikes, database query timeouts under load, real-time-stream stutter) that a dedicated CPU would solve.

​

Recommended starting plans by workload

Each row below names a starting plan — the place to begin, then resize up if you outgrow it. All prices are monthly subscription rates; see Pricing for yearly / 24-month locks.

​

Web and application servers

​

Databases

Databases are CPU-and-disk-sensitive — almost always pick Premium for consistent I/O. For databases above ~80 GB, attach a Volume for the data directory so disk size and VM size scale independently.

​

Background workers, batch, ML

​

CI/CD runners

​

Bastion / jump host

​

Windows workloads

Premium is generally the right pick for Windows — UI responsiveness benefits from dedicated CPU, and Windows has a higher RAM floor than Linux.

​

Game servers

Latency-sensitive — Premium is the right pick for any production game server.

​

How to size in practice

Three rules that beat any sizing chart:

1. Start one size below what you think you need. Resize up is fast (one reboot, prorated billing). Right-size at month-end with real metrics.
2. Watch RAM, not CPU. Most “I need a bigger VM” moments are RAM-bound — the OS starts swapping and everything slows down. CPU saturation is rarer than memory pressure for typical web/app workloads.
3. Move data off the VM. If the disk is filling up, attach a Volume; if backups are the issue, Object Storage is cheaper per GB than VM disk. Don’t size up the VM to gain disk.

You can change plans on a running VM — see Resize. Disk can grow but cannot shrink, so be conservative there.

​

Plan vs storage vs network — what’s billed where

​

Related