The 41% spread
We priced the same modernized Oracle Forms workload — 280 forms, 1.2 TB database, 600 concurrent users, three environments — across AWS, Azure, and Google Cloud in February 2026. The annual run cost ranged from 184,000 USD on the cheapest configuration to 311,000 USD on the most expensive. That’s a 41% spread for the same application.
The hyperscaler decision is rarely made on cost alone, but the cost gap is large enough to matter.
What the workload actually needs
A modernized Oracle Forms application has four cost drivers: compute for the application tier, database (Oracle, PostgreSQL, or managed equivalent), storage and backup, and egress. Egress is the line item that surprises most teams.
For a typical mid-market deployment, compute is 25 to 35% of the bill, database is 40 to 55%, storage is 8 to 12%, and egress is 5 to 15%. The relative shares shift based on architecture decisions made during migration.
AWS: the database question dominates
On AWS, the dominant cost decision is whether to keep Oracle Database or move to Aurora PostgreSQL. RDS for Oracle on a db.r6i.2xlarge with License Included pricing runs roughly 4,200 USD per month for the instance, before storage and IOPS. The same workload on Aurora PostgreSQL Serverless v2 typically lands at 1,400 to 1,900 USD per month.
The catch with RDS for Oracle is that License Included is only available for Standard Edition 2. Enterprise Edition requires Bring Your Own License, which means the existing Oracle agreement still applies.
Azure: the Oracle partnership matters
Azure’s relationship with Oracle is the closest of the three hyperscalers. Oracle Database@Azure places real Oracle Exadata hardware inside Azure regions, billed through the Azure Marketplace. For enterprises with existing Oracle commitments, this is the lowest-friction path.
Azure’s compute pricing is broadly comparable to AWS for general-purpose workloads. The differentiator is licensing portability — Azure Hybrid Benefit lets enterprises apply existing Windows Server and SQL Server licenses, which matters if the migration target stack includes .NET components.
For pure Oracle Forms to TypeScript migrations, the Azure cost advantage is smaller. For mixed-stack environments, it’s substantial.
Google Cloud: the price-performance leader
Google Cloud was the cheapest of the three on our test workload, primarily because of two factors: AlloyDB for PostgreSQL pricing and sustained-use discounts that apply automatically. AlloyDB delivered the test workload at roughly 1,150 USD per month, the lowest of the comparable managed PostgreSQL services.
The trade-off is ecosystem maturity. Enterprise procurement, compliance certifications, and regional coverage are still narrower on GCP than on AWS or Azure. For European regulated industries especially, the regional question matters.
Egress is the trap
Every hyperscaler charges for data leaving the cloud. Egress costs typically run 0.08 to 0.12 USD per GB after the first GB. A modernized Oracle Forms application that exposes REST APIs to mobile clients, partner integrations, and reporting tools can easily move 10 TB per month — adding 800 to 1,200 USD to the monthly bill.
Egress is also the hardest cost to forecast at design time. We recommend modeling worst-case egress at 3x the expected baseline.
Reserved capacity changes the math
All three hyperscalers offer significant discounts for one- and three-year commitments. For Oracle Forms migration workloads — which are typically stable, predictable, and long-lived — reserved pricing is the right default. The discounts range from 30 to 65% depending on commitment term and payment structure.
Migrations that run on on-demand pricing for the first 12 months overpay by roughly 40%. The reservation should be modeled into the original budget, not added later.
The bottom line
The cheapest hyperscaler for Oracle Forms modernization in 2026 is the one where the database licensing exit is cleanest. For most enterprises, that’s GCP with AlloyDB or AWS with Aurora PostgreSQL. Azure wins when there’s an existing Oracle estate that can move via Database@Azure without re-platforming.