Example 1
Small production web application
A common first-pass web tier might use 2 vCPU, 8 GB memory, Linux, balanced SSD block storage, and one always-on instance. In Stratos, start with the Web app preset or choose a custom 2 vCPU / 8 GB shape, set usage to 730 hours, and keep storage in the balanced SSD class.
Workload2 vCPU, 8 GB memory
Operating systemUbuntu/Oracle Linux
Runtime730 h/mo
StorageBalanced SSD, 100-250 GB
When reviewing the results, look for whether the provider used an exact shape or a closest fixed instance size. A fixed VM family with more memory than requested can be valid, but it means the estimate includes capacity you did not explicitly ask for. If the application is horizontally scalable, test a second scenario with two smaller nodes and compare the combined quote items.
Example 2
Database-like VM with larger memory
Self-managed databases often care more about memory and disk characteristics than the average stateless web node. Start with 8 vCPU, 32 GB memory, Linux, and a larger performance SSD or balanced SSD volume. Keep the comparison to the VM and attached disk unless you are ready to model backups, replicas, and network traffic separately.
Workload8 vCPU, 32 GB memory
Storage classBalanced SSD or performance SSD
Storage amount500 GB to 2 TB
Review focusDisk rounding, selected SKU, and memory fit
This is the kind of scenario where the meter table matters. Azure managed disks, AWS EBS classes, Google persistent disk, and OCI block volumes are not identical products. Stratos groups them by comparable class, then shows the selected meter so a user can decide whether the comparison is close enough for planning.
Example 3
Scheduled development environment
Development and test systems are often overestimated when every VM is priced as always-on. If the environment only runs during business hours, switch usage from 730 hours to 176 hours. This immediately separates providers with similar hourly rates from providers whose storage or license costs dominate the monthly total.
Workload4 vCPU, 16 GB memory
Runtime176 h/mo
StoragePersistent block storage remains monthly
Useful checkCompare Linux and Windows separately
Remember that stopping compute may not stop every charge. Block storage normally remains provisioned even when a VM is off, and Windows licensing can behave differently depending on the provider and license model. For scheduled workloads, run both the compute-hours change and a storage-size review.
Example 4
Object storage side workload
Some teams start with a VM comparison, then realize a storage-heavy side workload is more important than CPU. Enable object storage only when the application really stores user files, logs, exports, media, or backups in an object bucket. Choose the storage class that matches expected access patterns, then add request and retrieval amounts if they are material.
Storage classHot, cold/infrequent, or archive
Stored dataGB-month
ActivityRead requests, write requests, retrieval GB
ExcludedLifecycle transitions and replication
Object storage examples are especially sensitive to assumptions. Archive storage can look inexpensive until retrieval and minimum-retention rules matter. Keep a hot-storage scenario and an archive scenario as separate quote items so the comparison remains readable.