Storage VPS vs Regular VPS: Which One You Need
Storage VPS give you cheap terabytes but slower disk and less CPU. See the exact spec differences and which plan fits backups, archives, databases, or busy sites.
Storage VPS vs regular VPS: the short answer
Storage VPS na virtual private server wey provider dey sell based on terabyte, while regular VPS dey sell based on core. Storage plan give you plenty more disk for the money, usually with slower disk and less CPU per terabyte. Standard plan give you fast SSD, many times na NVMe (non-volatile memory express), wey often dey twenty times smaller, plus more processor and more memory for the same money. Everything else about the two products dey the same: same hypervisor, same root shell, same Ubuntu image, same network stack.
Na this one difference decide which one fit your need. Storage VPS good for backup targets, media libraries, cold archives, and anything wey you write once and read rarely. E no good for database, or any page wey user go wait for, because those workloads need small random reads to finish for about one millisecond. Cheap capacity cheap because e no fit do that.
Plan names wey you go see for pricing page
Four labels cover almost every provider, but na only two get specific meaning.
- Standard VPS. Normally e get two to eight vCPU, 2 GB to 32 GB RAM, and 20 GB to 400 GB NVMe or SATA SSD wey dey for the host node itself. Some ranges dey go far pass this: for 2026-10-17, Contabo Cloud VPS line reach maximum of 18 vCPU, 96 GB RAM, and 600 GB SSD (or 300 GB NVMe).
- Storage VPS. E start from some hundred GB reach 20 TB or more. Most times, na spinning SATA disks or high-capacity SATA SSDs, with shared vCPU, often one to four, and small amount of RAM for the capacity. Entry plans fit dey far below 1 TB (Contabo smallest Storage VPS list 300 GB SSD on 2026-10-17), while the biggest plans fit get more cores (e Storage VPS 50 list 14 vCPU and 50 GB RAM). E often cost the same per month as small standard plan.
- VDS. Na short form of virtual dedicated server. No shared definition dey for this word, and the section below explain wetin you suppose read instead.
- Block storage volume. This one no be plan at all: na network-attached disk wey you add to existing VPS and pay for per GB per month. Na only this one among the four wey you fit grow without moving the server.
Those ranges na the common pattern for the market, no be offer from any one company. The label for the plan na category, so e tell you roughly which chassis your server dey run on. E no tell you the disk type, CPU allocation policy, or bandwidth allowance. Na those details decide whether your workload go run well.
Wetin really dey change between the two plans
Disk type and quantity. Na this be the complete difference between the products. Standard plan normally go put you for SSD, and many times na NVMe flash wey dey reach through PCI Express bus, but the category no guarantee say na NVMe: for example, Contabo list its Cloud VPS 6 to Cloud VPS 18 plans on 2026-10-17 as either SSD or smaller NVMe disk ("200GB SSD / 100GB NVMe" for Cloud VPS 6), while its entry Cloud VPS 4 list only "100 GB SSD". Storage plan go put you for large array of spinning disks or high capacity SATA SSDs. If you no sure which of these terms matter to you, start with wetin SSD VPS be and how e different from older disk plans and then the practical difference between NVMe and SATA SSD.
CPU ratio. Storage plans get fewer vCPU per terabyte, and dem vCPU almost always dey shared with other tenants. This no be problem. Backup target dey spend most of its time waiting for network, so e no need many cores.
RAM. Storage plans get small RAM for their price. This dey cause problem for one particular place: filesystem metadata. Millions of small files need memory for directory and inode cache, and without that, every listing go return to the disk.
Network allowance. Read this line carefully for storage plan. Capacity wey you no fit restore from no be backup. Check the monthly transfer allowance for TB and the port speed for Gbit/s, because full restore of 4 TB through 1 Gbit/s port go take about nine hours at line rate, and much longer if dem dey share the port.
Di data wey dey behind dis chart
[
{
"plan": "Storage VPS, HDD",
"usd_per_tb_month": 3
},
{
"plan": "Storage VPS, SATA SSD",
"usd_per_tb_month": 9
},
{
"plan": "Standard VPS, NVMe",
"usd_per_tb_month": 40
},
{
"plan": "Block storage add-on",
"usd_per_tb_month": 90
}
]These figures na rounded values wey come from public price pages across several providers for August 2026, no be quotation from one company, and dem dey change. Na the general shape remain stable. One terabyte for spinning storage plan cost around 3 US dollars every month. The same terabyte of NVMe for standard plan cost about 40, while network attached block volume na the most expensive of the 4 options, at 90. For broader explanation of wetin make up monthly bill, see how much VPS really cost every month.
Wetin make price per TB and price per core dey pull for opposite directions
Storage node na chassis wey hold twelve to sixteen big disks, with one modest processor for front. Compute node na the opposite: many cores, plenty RAM, and two or four NVMe drives. Provider dey sell whatever spare capacity dey inside that chassis. So plan wey cheap per terabyte go cost more per core, while plan wey cheap per core go cost more per terabyte. No plan dey cheap for both, because no chassis dem build that way.
Na why the honest answer to “which one should I buy” often be “both”. Small NVMe VPS wey dey run the application, plus storage VPS wey dey hold its backups, go cost less than one machine wey big enough to handle both jobs well. If one machine really must handle both, you don comot from VPS territory: see when dedicated server dey better than VPS.
Random reads na wetin cheap disk no fit do
Di data wey dey behind dis chart
[
{
"disk": "7200 rpm SATA HDD",
"random_read_iops": "180",
"typical_latency_ms": 8.5
},
{
"disk": "SATA SSD",
"random_read_iops": "75,000",
"typical_latency_ms": 0.2
},
{
"disk": "NVMe SSD",
"random_read_iops": "600,000",
"typical_latency_ms": 0.08
}
]Those figures na datasheet class figures, no be benchmark for any provider. A 7200 rpm disk dey handle roughly 180 random 4k reads every second because the head must physically move go the track, then wait for the platter to bring the sector under am. This one dey cost about 8.5 ms each time. Flash no get anything wey need move, so SATA SSD fit reach about 75,000, while NVMe device fit reach around 600,000 IOPS at 0.08 ms. That difference pass three thousand times, and no amount of RAM or CPU fit close am.
Sequential work na completely different matter, na why storage plans dey useful at all. One spinning disk still dey stream 150 MB/s to 250 MB/s, and array of dem fit stream more. For raw hardware, that one enough to saturate 1 Gbit/s port. But your guest fit no get the full speed: providers fit cap throughput per server, and Time4VPS, for example, document 50 MB/s I/O limit for its storage servers, roughly 400 Mbit/s. Check the plan for I/O cap before you assume say backup upload go run at full network speed. Your figures still depend on how dem build the array, because striping dey write data in chunks wey rotate across several disks. So, several disks fit serve one large request at the same time: how RAID 10 dey change storage plan performance cover that matter.
VDS mean wetin?
Most times, na marketing label. Three meanings dey common, and provider rarely talk which one dem mean. Some providers use VDS for pinned or dedicated CPU cores, so no other tenant dey compete for your CPU cycles. Some use am for full virtualization like KVM, unlike container virtualization like LXC or OpenVZ where una dey share the host kernel. Others no use am for anything beyond name wey sound stronger than VPS.
You fit confirm part of am from inside the server. systemd-detect-virt dey print kvm for full virtual machine, and lxc for container. Container mean say you no fit load kernel modules or run your own kernel. You need measure the dedicated CPU claim yourself, using the steal time check wey dey further down. Treat the letters for the plan as hint, and treat the specification lines as the contract.
Which spec lines to check instead of the name
- The word wey dem print next to the capacity:
NVMe,SSD,SATAorHDD. If no disk word dey anywhere for the page, assume say na the cheapest hardware wey fit the price. - Check whether the disk dey local to the node or na network attached. Network attached storage dey add latency for every request and e fit survive node failure. Local disk dey faster but e dey fail together with the node.
- The CPU wording: "dedicated" or "pinned" versus "shared", "fair share" or nothing at all.
- Any IOPS or MB/s cap wey dem write for the plan. Cap of 500 IOPS fit make disk type almost irrelevant.
- Monthly transfer allowance and port speed. Dem determine how long full restore go take.
- Check whether snapshots, backups and extra IP addresses dey included or dem dey bill am separately.
How to check the disk wey you actually get
Start with wetin the kernel report, then stop to trust am.
lsblk -d -o NAME,ROTA,SIZE,MODEL
df -h /
nproc
free -hROTA na 1 for rotational device and 0 for flash. No rely on am inside VPS: virtio disk usually report ROTA=1 no matter wetin dey behind am, even NVMe, because virtio-blk driver dey mark every disk wey e create as rotational and guest no dey see the physical drive. MODEL empty for the same reason. The flag describe wetin the virtual device declare, no be wetin dey spin for the rack, so measure am instead.
sudo apt update && sudo apt install -y fio
fio --name=randread --filename=/var/tmp/fio.test --size=1G --bs=4k --rw=randread \
--ioengine=libaio --direct=1 --iodepth=32 --runtime=30 --time_based --group_reporting
rm -f /var/tmp/fio.test--direct=1 bypass page cache, so you measure disk instead of RAM. The line wey you need read na read: IOPS=, with the distribution under clat percentiles (usec) below am. Standard NVMe plan dey report tens of thousands of IOPS with 99th percentile under one millisecond. Spinning storage plan dey report few hundred IOPS with 99th percentile for double-digit milliseconds. If fio report say libaio engine no fit load, use --ioengine=psync --iodepth=1 and expect lower numbers, because that engine dey issue one request at a time.
vmstat 1 5
sudo apt install -y sysstat
iostat -x 1 5For vmstat, st column na steal time: the share of time wey your vCPU ready to run while host give those cycles to another guest. Steady figure above 5 mean say node dey oversubscribed, and na the real test of "dedicated CPU" claim. For iostat -x, monitor %util, r_await and w_await. For device wey dey serve requests one at a time, like single spinning disk, %util near 100 with w_await for tens of milliseconds mean say disk don saturate, and na only changes wey reduce or reorganize the IO go help. For RAID arrays and SSDs, wey dey serve requests in parallel, sysstat manual warn say %util no reflect their performance limits, so rely more on await figures and fio run instead. For flash-specific checks, verify whether NVMe disk really be NVMe go deeper.
Choose based on workload
- Backup target for restic, Borg or rsync. Storage VPS, and na this work dem build am for. Writes dey large and sequential, deduplication dey happen for the source machine, and nothing dey wait for the result. One caveat:
restic pruneandrestic check --read-datadey read the whole repository in small pieces, so budget hours for dem and run dem on schedule. See how to run restic backups to a VPS. - Immich or Jellyfin media library. Storage VPS for the files, but make you watch the CPU. Immich dey generate thumbnails and run machine learning jobs during import, while Jellyfin dey transcode during playback. Two shared vCPU go crawl when e dey do the first import of 200 GB photos. Keep the database and thumbnail cache for the fastest disk inside the box. how to self-host Immich as Google Photos replacement explain the sizing.
- PostgreSQL or MySQL. Standard NVMe plan. With the default durable commit settings (
synchronous_commit = onfor PostgreSQL), every commit dey wait for anfsyncto reach durable storage before the transaction return, so commit latency na disk latency. An index lookup na random read of one page (8 kB for PostgreSQL, 16 kB by default for MySQL's InnoDB), exactly the kind of operation spinning disk dey handle worst. - Web application, API or control plane. Standard plan. Dem need cores and predictable latency, and dem rarely need pass 100 GB.
- CI cache or artifact store. E depend on file size. Large tarballs dey stream well from storage plan, at network speed or the plan's I/O cap, whichever one lower. A cache of hundreds of thousands of small files, wey several runners dey pull in parallel, na random IO in disguise and e go disappoint you.
Wetin e look like when you get am wrong
The failure no dey happen immediately. Database for spinning storage plan fit look fine with one user, but e go collapse under ten users, because queries wey RAM dey handle before don start hit disk. Each query now dey cost milliseconds instead of microseconds. Load average dey rise while top dey show say CPU mostly idle with high %wa figure. This one mean say processes dey blocked as dem dey wait for disk, instead of dem dey compute anything. iostat -x 1 dey show %util pinned near 100.
PostgreSQL talk am clearly for its own log, because log_checkpoints dey enabled by default from version 15:
LOG: checkpoint complete: wrote 8241 buffers (2.5%); ... write=112.402 s, sync=9.318 s, total=121.914 sNa the sync= figure matter pass. E be the time wey checkpoint spend waiting for fsync to return. So, value for seconds mean say disk no fit absorb writes as fast as database dey produce dem. Client connections go stall during that period, even though the query itself cheap. Configuration change no be the solution. Move the data directory go NVMe, and keep the storage plan for wetin e good for: to hold the backups of that database.
FAQ
Storage VPS dey slower than regular VPS?
For random reads and writes, yes, by plenty. Spinning storage plan fit handle few hundred small random requests per second at around 8 ms each, while NVMe plan fit handle tens of thousands below 1 ms. For sequential transfers, the two dey much closer, because spinning array fit stream 150 MB/s or more for raw hardware. This one enough to fill 1 Gbit/s port, unless provider cap guest I/O lower. Time4VPS dey cap its storage servers at 50 MB/s. Use fio --rw=randread --bs=4k --direct=1 measure your own before you decide.
I fit run PostgreSQL for storage VPS?
You fit start am, and e go work until working set no longer fit inside RAM. After that, with default synchronous commit, every commit go wait for an fsync on slow disk. Postgres go log am as a sync= figure in seconds inside checkpoint complete, while iostat -x 1 go show %util near 100 with high w_await. The usual arrangement na small NVMe VPS for the database and storage VPS as target for its dumps.
VDS mean say I get dedicated hardware?
No be reliable. VDS no get standard meaning. Some providers use am for pinned CPU cores, some use am for full KVM virtualization instead of shared kernel container, and some use am only as name. Run systemd-detect-virt to see whether you dey on kvm or lxc, and run vmstat 1 5 then watch st column to see whether other tenants dey take your CPU cycles.
How I fit know whether my VPS disk really be NVMe?
No trust lsblk -d -o NAME,ROTA,MODEL, because virtio disk normally report ROTA=1, even when NVMe dey underneath, and empty model string no matter the hardware wey dey underneath. Run 30 second fio random read test with --direct=1, then read the IOPS and 99th percentile latency. Hundreds of IOPS with double-digit milliseconds mean say na spinning array. Tens of thousands below one millisecond mean say na flash.