Side-by-side monthly cost calculator comparing baseline pricing across AWS, Azure, GCP, and OCI.
Output will appear here...The calculator applies hand-maintained approximate hourly compute and memory rates, per-GB storage rates, and per-GB egress rates (defined per provider in the tool's source) to your vCPU/memory/storage/egress inputs, multiplies compute and memory by 730 hours per month, sums the three cost components per provider, and sorts the four estimates to surface the cheapest and most expensive along with the dollar gap between them; validate any figure you plan to rely on against each provider's live pricing calculator before using it for a real budget.
Estimates monthly compute, storage, and egress cost across AWS, Azure, GCP, and OCI from a simple vCPU/memory/storage/egress input, using approximate per-unit rates (e.g., AWS ~$0.0208/vCPU-hr plus $0.0052/GB-memory-hr on a t3-equivalent, OCI ~$0.0250/vCPU-hr but with a notably lower $0.0015/GB-memory-hr and $0.0085/GB egress after a 10TB free allowance) baked into the calculator rather than a live pricing API call. Egress pricing specifically is where OCI's rate structure diverges most from the other three (roughly 10x cheaper per GB than GCP's premium-tier egress), which matters disproportionately for a data-egress-heavy workload versus a compute-heavy one.
Run the same input through the calculator with a high egress figure and a near-zero egress figure to see how much the provider ranking shifts, egress-sensitivity is one of the most underappreciated variables in a naive compute-cost comparison.
Because the rates are approximate and instance-family-representative rather than exact, don't use the calculator's output as a final budget number, use it to decide which one or two providers merit a deeper, live-pricing-based comparison.
Memory-heavy workloads (large in-memory caches, JVM services with generous heap sizes) are disproportionately affected by the per-GB-memory-hour rate difference between providers, worth an explicit separate check beyond the calculator's blended total for memory-dominant sizing decisions.
No, they're approximate, hand-maintained rates representative of a general-purpose instance family per provider (noted in the tool's source as things like 't3 family equivalent' for AWS or 'e2 family w/ sustained use' for GCP), not a live pull from each provider's pricing API. Treat the output as directionally useful for comparing relative cost shape across providers, and get exact current pricing from each provider's calculator before finalizing a budget.
The built-in rates reflect OCI's publicly lower egress pricing (roughly $0.0085/GB after a 10TB free monthly allowance) compared to AWS (~$0.09/GB for the first tier), Azure (~$0.087/GB), and GCP's premium tier (~$0.12/GB). This is a genuine, well-known pricing differentiator for OCI, not a calculation quirk, egress-heavy workloads consistently show OCI more favorably in this and most independent cost comparisons.
No, it models on-demand pricing only. Reserved Instances, Savings Plans, Committed Use Discounts, and similar multi-year commitment discounts (which can meaningfully undercut on-demand pricing, often 30-60%+) aren't factored in, if your actual deployment would use committed pricing, treat this calculator's output as an on-demand ceiling, not the number you'd actually pay.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.