Buy the resource ratio your workload needs
The cloudscale pricing page checked on 8 November 2026 provides an unusually direct comparison within one memory size. Flex-4-1 is the memory-optimized shape with 4 GB RAM and one shared vCPU; general-purpose Flex-4-2 has the same memory and two shared vCPUs; CPU-optimized Flex-4-4 has 4 GB RAM and four shared vCPUs. All three list a 10 GB root Volume.
These are actual entries in the cloudscale catalog, not hypothetical configurations. A memory-bound small service and a parallel build worker need not buy the same CPU-to-RAM ratio. The family names do not prove a speedup, exclusive physical cores or permission to sustain any workload indefinitely. Establish application memory and permitted usage first, then compare the appropriate current tariff.
The included disk does not grow with the CPU count
The checked page calls the root storage distributed NVMe SSD, includes 10 GB in every listed Flex plan and permits expansion in 1 GB steps during operation. Moving from the one-vCPU 4 GB shape to the four-vCPU 4 GB shape does not, from these rows, increase the included root disk.
For a development worker, list the operating system, dependencies, container layers, build output and temporary files before choosing a shape. If that inventory needs more than 10 GB, obtain the additional-storage component price for the selected configuration. More CPU is not a substitute for missing disk space. The GPU scratch-disk note elsewhere on the page is a separate product detail and must not be attached to these shared-vCPU Flex rows. NVMe is the provider’s storage description, not an independent I/O result.
Treat daily traffic and daily rounding as their own rules
The page includes public static IPv4 and IPv6 and states 100 GB of free traffic per 24 hours. That is not a published fixed monthly allowance for every instance lifetime. A workload sending most of its data on one day needs the actual metering rules; multiplying 100 GB by thirty does not establish a freely transferable monthly pool. Direction, aggregation and any boundary not established by this page need confirmation before a bulk transfer.
The FAQ says costs are calculated to the second per calendar day, rounded upward to whole CHF 0.01 per cost component, then charged shortly after midnight in Europe/Zurich. A short task split across several components and calendar days therefore cannot be budgeted solely by adding unrounded seconds. No precise task bill is calculated here without its component tariffs and timing. The same page says powered-off services remain billed because resources stay reserved.
A short trial still needs a credit and exit budget
The provider states a CHF 10 minimum credit purchase and enough balance to cover at least 24 hours of service before starting a server. It also says purchases of credit are final and non-refundable. Consequently, a very short evaluation can leave unused account credit; rental precision does not imply refundability of that balance.
VAT is charged on credit purchases for Swiss and EU customers, with the stated exception for EU business customers after successful VAT-ID verification. That verification and an individual buyer’s eligibility remain unknown. Before funding, establish the selected components, tax treatment and an amount of credit you are prepared to consume. Do not assume that stopping the machine releases its billable resources.
Use the Black Friday hub to assess separately verified seasonal offers. These Flex specifications and credit terms are ordinary product evidence, not a campaign announcement. A Launch link does not verify current capacity, and VPSSpy has not created a cloudscale account or tested a server.