This article is based on reporting originally published by SDxCentral in May 2020.
Oracle Throws Down the Gauntlet on Cloud Pricing
Oracle made a pointed move against Amazon Web Services (AWS) by launching the Oracle Cloud Workload Cost Estimator, a tool designed to compare the total cost of running workloads on Oracle Cloud Infrastructure (OCI) versus AWS. The implicit — and explicit — message: Oracle believes its cloud is cheaper, and it wants enterprise and DevOps teams to do the math themselves.
The tool was positioned as an “apples-to-apples” comparison, covering the four cost dimensions that most directly affect cloud operating budgets for high-performance workloads:
- Compute – virtual machine and CPU costs
- Storage – block and object storage pricing
- I/O operations per second (IOPs) – storage throughput costs
- Data egress – the cost of transferring data out of the cloud
Data Egress: The “Wild Card” in Cloud Cost Comparisons
Of the four dimensions, Oracle singled out data egress as the factor most likely to catch organisations off guard. Moving data into a cloud provider is typically free or very low-cost. Moving data out is where traditional providers apply significant markups — a practice sometimes called “egress tax” in the industry.
Oracle’s own blog post on the calculator highlighted the contrast directly:
“Traditional cloud companies charge a markup after a given amount of data flows out. So once you hit that magic monthly number — 1 GB for AWS — data egress charges kick in. At Oracle, the meter doesn’t start running until after 10,000 times more data egress — or 10 TB — per month.”
For teams running data-intensive workloads — analytics pipelines, media delivery, machine learning training jobs, or large-scale database replication — egress costs can become a significant and underestimated line item. This is the specific use case Oracle was targeting with the calculator.
How the Oracle Cloud Workload Cost Estimator Works
The estimator was designed to let teams enter their workload specifications and receive a side-by-side cost breakdown comparing OCI and AWS. Rather than forcing users to manually cross-reference pricing pages from two different cloud providers — each of which uses different terminology and pricing structures — the tool attempts to normalise the comparison into equivalent configurations.
Oracle’s stated goal was to demonstrate that for many high-performance enterprise applications, OCI delivers a lower total cost of ownership (TCO). DevOps teams evaluating cloud providers for latency-sensitive or data-heavy workloads may find this type of structured comparison useful, regardless of which vendor they ultimately choose.
Cloud Cost Calculators Across the Major Providers
Oracle is not the only cloud vendor offering a cost estimation tool. All three major hyperscalers provide pricing calculators, though they vary in scope and approach:
- AWS Pricing Calculator – Allows teams to model environments and estimate costs across AWS services, including the impact of Reserved Instances and Savings Plans.
- Microsoft Azure Pricing Calculator – Includes support for comparing pay-as-you-go versus reserved pricing, and factors in Azure Hybrid Benefit for organisations with existing Microsoft licenses.
- Google Cloud Pricing Calculator – Covers Compute Engine, Cloud Storage, Cloud SQL, and other GCP services, with estimates for sustained use discounts automatically applied.
What distinguishes Oracle’s approach is that it was explicitly designed as a cross-vendor comparison tool, rather than simply helping users estimate their own spend within a single provider’s ecosystem. That framing is inherently competitive, and teams should weigh Oracle’s claims accordingly — the assumptions baked into any vendor-produced comparison tool will naturally favour that vendor.
Context: Oracle’s Cloud Ambitions in 2020
At the time of this announcement, Oracle was actively working to expand its cloud presence. The company had announced plans to hire approximately 2,000 cloud-focused employees, a signal of its intent to compete more aggressively with AWS and Microsoft Azure. However, the company had also undergone significant layoffs in the preceding period, and several senior executives had departed — reflecting the internal challenges of pivoting a legacy enterprise software business toward cloud-native infrastructure.
The launch of the cost estimator in May 2020 also coincided with the early months of the COVID-19 pandemic, a period in which many organisations were scrutinising cloud spend more carefully and reconsidering vendor lock-in. Oracle’s timing positioned the tool as a response to that environment, framing OCI as a cost-efficient alternative worth evaluating during a period of economic pressure.
What DevOps Teams Should Take Away
Vendor-produced calculators are a useful starting point, but they should be treated as one input among many. When evaluating cloud costs for a real workload, consider the following:
- Model your actual egress volume. If your workload moves large amounts of data out of the cloud regularly, egress pricing deserves careful scrutiny across all candidate providers.
- Use multiple calculators. Run the same workload specification through each provider’s own tool and compare results. Differences in how you model the workload can significantly affect outcomes.
- Account for operational costs. Raw infrastructure pricing is only part of TCO. Tooling, managed services, support tiers, and staff familiarity with a given platform all affect real-world costs.
- Validate vendor claims independently. Any comparison produced by a vendor will reflect assumptions favourable to that vendor. Seek independent benchmarks or run proof-of-concept workloads in parallel where possible.