Scope and evidence posture

Oracle Corporation is four businesses that reinforce each other but obey different economic laws. First, it is a database rent collector with one of the deepest installed bases in enterprise computing. Second, it is a cloud-infrastructure challenger trying to convert old database gravity into new infrastructure consumption. Third, it is an enterprise applications vendor competing for the operating records of governments, hospitals, manufacturers, banks and large corporations. Fourth, and increasingly central to the equity story, it is an AI data-center capacity seller: a company taking on power, GPU, networking, financing and counterparty risk to sell scarce compute to model developers and large enterprises.

The central research question is whether Oracle’s old monopoly-like software economics can survive the company’s movement into a much more capital-intensive infrastructure model. The public evidence says Oracle has achieved a genuine inflection in cloud infrastructure growth. The skeptical reading is that this inflection is not a simple software-margin story. It is partly a project-finance story, partly an energy-procurement story, partly a GPU supply-chain story, and partly a counterparty-concentration story. Oracle’s fiscal 2026 results make this explicit: cloud infrastructure revenue grew much faster than the rest of the company, but free cash flow turned sharply negative as capital expenditures surged. Oracle’s own disclosure that much of its RPO increase came from large AI contracts, including prepaid or customer-supplied GPUs, is unusually important because it shows that reported backlog is tied to hardware financing and build-out execution, not only to conventional SaaS subscription visibility.

Canonical company record: Oracle Corporation. Public ticker: ORCL on the New York Stock Exchange. Canonical web properties include the corporate site, Oracle Cloud, Oracle Investor Relations and Oracle documentation domains. The company is not a narrow directory entry. Oracle is a critical enterprise infrastructure operator whose risk surface now includes software licensing, regulated workloads, multicloud interconnection, datacenter construction, power availability, GPU procurement, public-sector modernization and security incident response.

The public-company frame

Oracle’s latest public-company narrative is a sharp transition from mature software cash generator to AI infrastructure growth vehicle. In fiscal 2026, Oracle reported total revenue of $67.4 billion, up 17%, with total cloud revenue of $34.0 billion, up 39%. Within that, cloud infrastructure revenue was $18.1 billion, up 77%, while cloud applications revenue was $15.9 billion, up 11%. The contrast matters: the applications business is still material and sticky, but the company’s growth-rate story is now OCI, not legacy software or SaaS alone. In Q4 fiscal 2026, Oracle reported $19.2 billion of revenue, $9.9 billion of cloud revenue, $5.8 billion of cloud infrastructure revenue and $4.1 billion of cloud applications revenue. Software revenue for the fiscal year was $24.5 billion, down 1%, which supports the interpretation that Oracle is migrating customers from on-premise software and support toward cloud services rather than simply adding cloud revenue on top of an unchanged base.

The balance-sheet and cash-flow implications are more revealing than the growth rate. Oracle reported fiscal 2026 operating cash flow of $32.0 billion, but free cash flow was negative $23.7 billion. Its cash-flow statement shows capital expenditures of $55.7 billion in fiscal 2026, compared with $21.2 billion in fiscal 2025. Property, plant and equipment net of depreciation rose from $43.5 billion to about $100.0 billion. Non-current notes payable and other borrowings rose from $85.3 billion to $122.3 billion. Those numbers are the financial signature of a company moving from software rent collection into physical infrastructure ownership and operation.

Oracle’s reported remaining performance obligations were the most dramatic evidence. RPO ended Q4 fiscal 2026 at $638 billion, up 363% year over year and up $85 billion sequentially. Oracle said most of the RPO increase in both Q3 and Q4 came from large-scale AI contracts where the customer either prepaid Oracle for GPUs or bought and supplied GPUs to Oracle; the prepaid and customer-supplied hardware portions of large AI contracts totaled $75 billion. This is a strong signal of demand, but also a warning that the quality of backlog depends on delivery milestones, datacenter energization, customer concentration, GPU depreciation curves and the future financial strength of a few AI buyers.

The public-company thesis is therefore bifurcated. The software side of Oracle produces durable operating cash flow from entrenched enterprise systems. The infrastructure side demands large forward capital commitments and may produce attractive utilization if AI demand remains supply constrained. The risk is that the accounting appearance of backlog can run ahead of physical delivery, and that cloud-infrastructure revenue growth can absorb rather than release cash during the build-out period.

The database rent machine

Oracle’s deepest economic moat remains the installed base of Oracle Database. This is not only a product position. It is a transaction-cost position. Oracle databases sit under ERP systems, billing systems, banking systems, claims systems, government records, manufacturing systems, telecom mediation layers, hospital records, and custom applications written over decades. The value of the database is not only the engine. It is the accumulated schema, stored procedures, operational tooling, DBA knowledge, failover design, compliance validation, performance tuning, disaster-recovery procedures and application certifications around it.

The pricing evidence remains stark. Oracle’s May 2026 U.S. public-sector price list shows Oracle Database Enterprise Edition at $47,500 per processor for a perpetual license, with $10,450 listed for software update license and support. Real Application Clusters is listed at $23,000 per processor plus $5,060 support, Partitioning at $11,500 per processor plus $2,530 support, Advanced Security at $15,000 per processor plus $3,300 support, Diagnostics Pack at $7,500 per processor plus $1,650 support, and Tuning Pack at $5,000 per processor plus $1,100 support. Named User Plus pricing is also listed, including $950 for Database Enterprise Edition and $209 support. These list prices are not average realized prices, and large enterprises negotiate heavily, but they illustrate the modular rent stack: the core database license is only the beginning; high availability, security, tuning, diagnostics, partitioning and other options add separate chargeable layers.

This is the economic heart of Oracle’s historical pricing power. A customer running Oracle Database for a mission-critical workload rarely evaluates the renewal decision as a greenfield technology choice. It evaluates the cost of migration failure. The database rent is therefore protected by the cost of rewriting application logic, validating data equivalence, retraining administrators, retesting integrations, changing backup and recovery practices, and surviving audit or regulatory review. In banking, insurance, healthcare and public-sector systems, “migration” is not a weekend operation. It is a multi-year operational-risk program.

DB-Engines is not a revenue share source or market-share table. It is, however, a useful popularity and attention proxy. In June 2026, DB-Engines ranked Oracle first among database systems, ahead of MySQL, Microsoft SQL Server, PostgreSQL and MongoDB; the same ranking also placed Snowflake sixth, Databricks seventh and SAP HANA twenty-second. That positioning supports the view that Oracle remains central to database mindshare even as newer analytic and lakehouse systems are gaining attention.

The installed-base economics are also visible in Oracle’s license-management apparatus. Oracle License Management Services describes itself as the sole Oracle licensing authority that can verify Oracle program requirements and lists both Assurance Service and Audit Service. The official framing is compliance assistance, but from the customer’s perspective, the audit threat is part of the vendor’s bargaining leverage. Large customers do not only pay Oracle because they love the database. They also pay to avoid uncertainty over processor counts, option usage, virtualization boundaries, user counts and support obligations.

Practitioner commentary reinforces this. UpperEdge, an enterprise-technology negotiation advisory firm, describes Oracle licensing for VMware environments as a recurring customer pain point and argues that Oracle’s policy can require licensing an entire server farm or cluster because the database could potentially run across connected servers. That is not a court ruling or definitive law. It fits a long-running customer pattern: Oracle’s licensing model can turn infrastructure architecture choices into commercial exposure.

The result is a rent-collection machine with three reinforcing loops. First, mission-critical data stays where it is because migration is risky. Second, support and audit compliance convert technical dependence into recurring commercial leverage. Third, OCI gives Oracle a migration path that does not require surrendering the database rent to another hyperscaler. This is why Oracle’s cloud strategy should be read as defensive as well as offensive: OCI is a way to keep the database base inside Oracle’s economic perimeter.

OCI as a challenger cloud

Oracle Cloud Infrastructure is not trying to win the hyperscale market by copying AWS feature-for-feature at equal scale. Its more plausible strategy is to win specific workloads where Oracle has asymmetry: Oracle databases, regulated enterprise systems, sovereign cloud deployments, bare-metal and high-performance computing, multicloud database adjacency, and now AI training capacity.

The footprint is meaningful but uneven. Oracle documentation says OCI regions are localized geographic areas made up of one or more availability domains. Availability domains are isolated from each other and do not share infrastructure such as power, cooling or internal availability-domain network. The same documentation says Oracle has chosen to launch regions in new geographies with one availability domain to expand quickly. The table of commercial regions shows a broad global footprint, but many regions have a single availability domain, while some important regions such as Frankfurt, London, Ashburn, Chicago and Phoenix have three.

This architecture is commercially rational. A single-availability-domain region can satisfy data-residency, latency or government-access requirements faster and cheaper than a fully built multi-AD hyperscale region. It also fits Oracle’s enterprise sales motion: customers often want a local database region, a sovereign region, a government realm or a dedicated deployment rather than an enormous developer platform. The skeptical point is that single-AD regions are not equivalent to the mature multi-AD region designs customers associate with AWS, Azure or Google Cloud for the highest-availability cloud-native workloads. Oracle’s own documentation says multi-region deployment helps with business continuity and disaster protection. The availability-domain pattern therefore matters when evaluating whether OCI is a general-purpose hyperscale peer or a more specialized enterprise and database cloud.

Oracle’s public regions page states that OCI has 41 commercial cloud regions in 26 countries, including 14 countries plus the EU with two or more regions for in-country disaster recovery. It also advertises globally consistent pricing, a private Oracle-managed backbone between regions, encrypted traffic between regions and availability domains, 10 TB per month of outbound bandwidth at no cost, lower prices beyond that allowance, more than 40 regions globally, and more than 70 compliance standards including SOC, PCI DSS, HIPAA, HITRUST and GDPR. These claims are central to Oracle’s economic pitch: OCI is not only compute, storage and network; it is cost predictability plus compliance plus database proximity.

Oracle’s service-availability page says each OCI region supports more than 200 cloud services and that OCI offers uniform pricing across public cloud regions, including Dedicated Region. It also lists multicloud services including Oracle AI Database@AWS, Oracle AI Database@Azure, Oracle AI Database@Google Cloud, and interconnect services for Azure and Google Cloud. The specific region-pairing tables matter because they show Oracle’s multicloud strategy is not only marketing. Oracle is deliberately placing database services next to AWS, Azure and Google Cloud regions so applications can remain in the dominant hyperscalers while the database rent stays with Oracle.

This is a clever inversion of cloud competition. AWS, Azure and Google Cloud won much of the developer and application layer. Oracle is not trying to unwind all of that. It is trying to make the Oracle database an attached utility inside or adjacent to those clouds. The customer gets lower-latency access to Oracle databases without fully migrating to OCI. Oracle keeps the database consumption, support relationship and potentially the enterprise account control. In economic terms, Oracle is trying to tax data gravity even when application gravity belongs to another cloud.

AI infrastructure: the capacity seller

Oracle’s AI infrastructure strategy is larger and more unusual than a conventional cloud GPU product launch. The company is selling capacity into a market where frontier model developers need power, land, liquid cooling, high-speed networking, GPU supply, storage throughput and rapid execution. The scarcity is not just chips. It is energized, networked, permitted, operational capacity.

Oracle’s AI infrastructure page says OCI Supercluster can run up to 131,072 GPUs and lists scaling claims including more than 100,000 GB200 Superchips, 131,072 B200 GPUs, 65,536 H200 GPUs, 32,768 A100 GPUs, 16,384 H100 GPUs and 16,384 AMD MI300X GPUs per cluster. It also advertises bare-metal instances, custom-designed RDMA over Converged Ethernet, 2.5 to 9.1 microseconds of cluster-network latency, up to 3,200 Gb/sec of cluster network bandwidth, up to 400 Gb/sec of front-end network bandwidth, local NVMe storage and high-performance file storage. These are not ordinary enterprise cloud claims. They are AI-factory claims.

The OpenAI relationship is the clearest public signal of Oracle’s capacity strategy. In July 2025, OpenAI said it had entered an agreement with Oracle to develop 4.5 gigawatts of additional Stargate data-center capacity in the United States. OpenAI said that, together with Stargate I in Abilene, the partnership would bring Stargate to more than 5 gigawatts of AI data-center capacity under development, running more than 2 million chips. OpenAI also said parts of the Abilene facility were up and running and that Oracle had begun delivering Nvidia GB200 racks in June 2025, with early training and inference workloads underway.

In September 2025, OpenAI expanded the Stargate narrative, saying five new U.S. AI data-center sites with Oracle and SoftBank would bring planned Stargate capacity to nearly 7 gigawatts and more than $400 billion of investment over three years. It said the July Oracle agreement represented a partnership exceeding $300 billion over five years, and that Oracle-linked sites in Shackelford County, Texas; Doña Ana County, New Mexico; the Midwest; and a potential expansion near Abilene could deliver more than 5.5 gigawatts. This is public-company-scale infrastructure, but the economics look closer to energy-intensive industrial capacity leasing than to classic enterprise software.

Crusoe, Oracle’s Abilene infrastructure partner, stated in September 2025 that the first phase of the Abilene campus was live on OCI, that construction began in June 2024, that the first two buildings were energized within a year, that Oracle began delivering Nvidia GB200 racks in June 2025, and that the planned eight-building campus would support hundreds of thousands of GPUs on a single integrated network fabric. This is corroborated partner evidence, though still interested-party evidence. It supports the view that Oracle is not merely booking paper demand; it is participating in real physical deployment.

But capacity selling introduces a different risk class. A database license has negligible marginal cost once the software is built. A GPU cluster has depreciation, power, maintenance, networking, liquid-cooling, firmware, supply-chain and utilization risk. A customer delay, model-training shift, chip-generation transition or power constraint can impair returns. Oracle’s own RPO disclosure partially reduces the financing concern because customers prepaid or supplied GPUs, but it does not remove execution risk. It may even highlight the degree to which the largest AI customers are negotiating bespoke terms that differ from normal cloud consumption.

Capital intensity and power constraints

The main constraint on Oracle’s AI strategy is not sales demand. It is deliverable capacity. The practical bottlenecks are land, grid interconnection, power generation, transformers, switchgear, water or liquid-cooling design, permitting, fiber routes, GPU supply, labor, and the ability to operate high-density clusters reliably. Oracle’s 2026 cash-flow statement shows this transition clearly: capex reached $55.7 billion, and free cash flow turned negative despite strong operating cash generation. Oracle raised $43 billion of debt and $5 billion of equity financing in fiscal 2026 and said it expected to raise about $40 billion through debt and equity in fiscal 2027, including a previously announced $20 billion at-the-market equity issuance.

The power evidence around Abilene shows why this is an industrial infrastructure strategy. AP reported in March 2026 that Microsoft was taking over an adjacent Abilene AI data-center expansion after OpenAI declined to pursue it, while Crusoe continued completing six more buildings for OpenAI and Oracle. AP also reported that the broader Abilene complex was expected to supply 2.1 gigawatts of computing capacity, that the Microsoft project included a 900-megawatt on-site power plant, and that the existing OpenAI-Oracle project had a 350-megawatt gas-fired plant described by Oracle as backup power while the data centers primarily drew from the regional grid. This is journalistic evidence rather than a contract filing, but it is consistent with the physical scale implied by OpenAI and Crusoe’s official statements.

A second unofficial signal is local tax economics. Business Insider reported that Oracle was disputing the property valuation of its Stargate data-center site in Abilene and that the project was eligible for an 85% property tax abatement. The same report said Crusoe had committed to spending up to $3.5 billion and creating 357 full-time jobs, with Oracle benefiting as sub-lessee. This points to local-incentive economics and tax minimization, not wrongdoing. It does show that datacenter capacity is negotiated not only in boardrooms but also through local tax bases, property appraisals and economic-development agreements.

The capital-market concern is not imaginary. Reuters reported in September 2025 that Moody’s flagged counterparty risk in Oracle’s large AI contracts, noting reliance on a small number of AI companies and describing Oracle’s datacenter build as effectively one of the world’s largest project financings. Reuters reported Moody’s view that Oracle’s debt would rise faster than EBITDA, contributing to forecast leverage around 4x before EBITDA caught up, and that free cash flow would likely remain negative for an extended period before breakeven. This is a credit-analyst signal, not a default forecast, but it is a useful corrective to equity-market backlog enthusiasm.

Counterparty risk is amplified by the economics of frontier AI buyers. Reuters, citing The Information, reported in September 2025 that OpenAI had raised its projected cash burn through 2029 to $115 billion as it ramps infrastructure spending. The report also said OpenAI had deepened its Oracle tie-up and added Google Cloud among suppliers. This is a secondary report of a private-company forecast rather than audited evidence. It is nevertheless directly relevant: Oracle’s biggest AI-infrastructure upside depends on customers whose own cash flows, fundraising and strategic compute choices remain highly dynamic.

Interconnect economics and the multicloud bargain

Oracle’s multicloud strategy is a direct response to a structural problem: the enterprise application layer moved to AWS, Azure and Google Cloud faster than Oracle could convert those customers to OCI. Rather than insist that customers move everything to OCI, Oracle is embedding or adjacent-placing Oracle database services inside the customer’s chosen cloud topology.

The economics are straightforward. Moving a database is expensive and risky. Moving an application server or analytics workload is easier. If Oracle can reduce latency and egress pain between hyperscaler applications and Oracle databases, it can keep the database account while letting customers run the rest of their architecture elsewhere. The interconnect strategy therefore turns cloud rivalry into cloud adjacency. Oracle does not need to become the default cloud for all workloads to preserve database rent. It needs to remain the trusted system of record for the data that those workloads query and update.

OCI’s public-region economics support this positioning. Oracle advertises a private redundant backbone between regions and 10 TB per month of free outbound bandwidth, with lower prices beyond that. Its service-availability page lists Oracle AI Database@AWS, Oracle AI Database@Azure and Oracle AI Database@Google Cloud, along with specific interconnect pairings for Azure and Google Cloud. The implication is that Oracle is competing on the cost of data movement and operational continuity, not only on compute price.

For customers, the bargain is attractive but not neutral. Oracle database services inside or near other clouds reduce migration pressure and can avoid a forced rewrite. But they also preserve Oracle’s position in the architecture. The customer may escape on-premise hardware and some datacenter burden, yet remain tied to Oracle database semantics, support obligations, options and commercial negotiation cycles. Multicloud can therefore reduce operational friction while extending vendor dependency.

Enterprise applications and switching costs

Oracle’s applications business is less spectacular than the AI infrastructure story but remains strategically important. Fusion Cloud ERP, HCM, SCM, EPM, NetSuite, industry applications and Oracle Health give Oracle access to business processes rather than only technical infrastructure. Applications generate data, workflows and user habits. Databases store them. Cloud infrastructure runs them. AI features can be attached to them. This is the full-stack enterprise strategy.

Switching costs are especially high where Oracle applications intersect with regulated processes. ERP systems encode finance controls, procurement rules, tax logic, inventory processes and audit trails. HCM systems encode payroll, benefits, workforce classification and compliance. Healthcare systems encode clinical workflows, patient records and interoperability obligations. Public-sector systems encode procurement law, budget appropriations, personnel classifications and records-retention requirements. A customer can dislike Oracle and still remain economically rational in renewing it.

Oracle’s application position also strengthens OCI. A Fusion, NetSuite or Oracle Health customer is easier to sell OCI-adjacent services to than a neutral cloud buyer. Conversely, an OCI database customer is easier to sell application modernization to than a pure AWS-native account. This is not automatic. SAP, Workday, ServiceNow, Salesforce, Microsoft and industry-specific vendors all contest the process layer. But Oracle’s cross-sell logic is credible because the same CIO or agency technology office often owns the risk of both application continuity and database continuity.

The skeptical point is that enterprise applications have a different growth ceiling than AI infrastructure. Oracle Cloud Applications revenue grew 11% in fiscal 2026, versus 77% for cloud infrastructure. Applications are sticky and profitable but not the source of the current re-rating narrative. The application business is better understood as a stabilizer and data-gravity generator than as the main source of upside.

Public sector and regulated industries

Oracle has unusually deep exposure to public-sector and regulated workloads. Oracle’s U.S. defense cloud page says Oracle Cloud supports DoD customers through OCI, that Oracle U.S. Defense Cloud is authorized for DISA Impact Levels 2, 4 and 5, and that Oracle National Security Regions are air-gapped IL6-authorized environments for Secret and Top Secret workloads. The same page emphasizes consistent global pricing across deployment models and no egress fees in national-security regions. This matters because public-sector workloads value accreditation, isolation, procurement vehicles and continuity more than developer-fashion cycles.

Healthcare is the most important regulated-industry test because of Oracle’s Cerner acquisition. The Department of Veterans Affairs’ EHR modernization program remains a cautionary example. GAO testified in 2025 that VA’s EHR modernization had made incremental improvements but still lacked updated information on how long the modernization would take or reliable estimates of how much it would cost. GAO also said many users interviewed reported decreased productivity and that substantial prior recommendations remained open. This is not solely an Oracle failure; large public-sector health IT programs are complex and VA is the contracting authority. But it is a real signal that Oracle Health’s regulated-workload opportunity carries implementation and political risk.

The public-sector opportunity is therefore double-edged. Oracle can win because governments already run Oracle databases and back-office systems, and because accredited cloud regions are hard to replicate. But each public-sector win can become a public-sector performance record. Cost overruns, deployment delays, security incidents or user dissatisfaction become congressional, audit and media issues rather than private customer escalations.

Security and outage history

Oracle’s security and reliability record should be analyzed with nuance. All hyperscalers and enterprise software vendors experience vulnerabilities, outages and customer-impacting incidents. The question is not whether incidents occur, but whether the company communicates clearly, remediates quickly, and maintains trust in regulated environments.

Oracle’s public status model has a limitation that matters for intelligence work. Oracle documentation says the OCI Status dashboard shows service outages at the service or region level, while customer-specific outages are communicated through Console Announcements. This means the public status page may underrepresent incidents that affect specific customers, tenancies, identity paths or configurations.

Unofficial outage monitoring illustrates the visibility gap. DataCenterDynamics reported in May 2025 that users reported an OCI outage in Europe, with reports suggesting a roughly six-hour issue affecting identity and including Germany Central, while Oracle’s status page listed no incidents for that month at the time of writing. This is external reporting based partly on user reports and third-party outage signals, not an official root-cause analysis. It does not prove systemic unreliability, but it does show that public cloud status pages may not capture the customer experience cleanly.

Security reporting is more concerning because Oracle’s enterprise products are deeply embedded. Reuters reported in April 2025 that Oracle told customers a hacker broke into a system and stole old client login credentials, that the incident was being investigated by the FBI and CrowdStrike, and that the stolen data included Oracle customer login credentials from as recently as 2024 even though Oracle told customers the system had not been in use for eight years. Reuters also reported that Oracle said the incident was separate from a healthcare-customer incident. This is corroborated journalistic evidence based on customer communications and people familiar with the matter, not a full forensic report. It nevertheless matters because Oracle’s trust proposition rests heavily on regulated and mission-critical customer confidence.

The larger risk is not that Oracle has uniquely poor security. It is that Oracle’s footprint creates high blast-radius opportunities for attackers. E-Business Suite, PeopleSoft, JD Edwards, Siebel, Oracle Database, WebLogic, Java, Cerner/Oracle Health and OCI sit in sensitive enterprise workflows. The more Oracle sells itself as the secure home for public-sector, health and AI workloads, the more security transparency becomes a competitive variable.

Competition: hyperscalers, data clouds, applications and open source

Oracle competes with different vendors in different layers.

Against AWS, Azure and Google Cloud, Oracle is still a challenger. Synergy Research Group estimated Q1 2026 enterprise cloud infrastructure spending at about $129 billion, with AWS at 28% worldwide share, Microsoft at 21% and Google at 14%. Synergy also said the top three are even more dominant in public cloud, while Oracle appeared among the fastest-growing tier-two providers. CRN’s summary of Synergy data placed Oracle at 4% global cloud infrastructure share in Q1 2026, up from 3% in Q4 2025 and Q1 2025. This is the right scale comparison: Oracle may be growing fast, but it remains far smaller than the big three in general cloud infrastructure.

Oracle’s wedge against the big three is not generic cloud breadth. AWS has developer ecosystem depth, Azure has Microsoft enterprise distribution and identity adjacency, and Google has data/AI engineering credibility. Oracle’s wedge is narrower: database economics, bare metal, high-performance networking, predictable egress and multicloud database placement. It is more credible for Oracle to win “run Oracle Database, Exadata-like workloads, AI clusters and regulated enterprise systems” than to become the default home for all new startups and cloud-native development.

Snowflake competes with Oracle for analytic data gravity. Snowflake reported Q4 fiscal 2026 product revenue of $1.23 billion, up 30%, remaining performance obligations of $9.77 billion, net revenue retention of 125%, and 733 customers with trailing-12-month product revenue above $1 million. Snowflake’s pitch is not to replace every Oracle transaction database. It is to become the governed analytic and AI data layer across clouds. That threatens Oracle when customers move reporting, warehousing, data sharing and AI workloads out of Oracle databases into a neutral data cloud.

Databricks competes through the lakehouse and AI platform model. In February 2026, Databricks said it had crossed a $5.4 billion revenue run-rate, growing more than 65% year over year, with more than 800 customers consuming at over $1 million annual revenue run-rate and more than 70 at over $10 million. It also highlighted Lakebase, a serverless Postgres database for AI agents, and Genie, a conversational AI assistant. The strategic threat is not only analytics. Databricks is trying to pull enterprise data engineering, governance, AI development and increasingly operational AI data services into one platform.

SAP competes with Oracle at the application layer and, through HANA, at the database/application-platform layer. SAP’s 2026 outlook calls for €25.8 billion to €26.2 billion of cloud revenue at constant currencies, up 23% to 25%, and €36.3 billion to €36.8 billion of cloud and software revenue. Oracle’s Fusion ERP, HCM and SCM compete directly with SAP’s cloud ERP migration cycle, while SAP’s control over the ERP process layer can reduce Oracle’s database leverage where customers standardize on S/4HANA and SAP’s cloud stack.

Open-source database ecosystems are the long-term attrition threat. PostgreSQL, MySQL, MariaDB, SQLite, ClickHouse, Cassandra and other systems do not need to displace Oracle’s largest legacy databases immediately. They only need to become the default for new workloads. PostgreSQL in particular has become the enterprise default for many new relational applications because it is capable, extensible, cloud-managed by every major provider and free of Oracle-style license complexity. Oracle’s risk is not a sudden cliff. It is generational replacement: new applications start on Postgres or cloud-native databases, analytics move to Snowflake or Databricks, and Oracle remains concentrated in high-value legacy systems. That is still a large business, but it changes growth math.

Pricing power and its limits

Oracle has pricing power where three conditions hold: the workload is mission critical, the migration path is risky, and Oracle retains licensing or support leverage. This describes much of the database installed base. It also describes some government and regulated workloads. It does not necessarily describe commodity cloud compute.

In database, Oracle can maintain pricing through support renewals, option licensing, audits, enterprise license agreements and cloud migration credits. The customer may negotiate hard, but the outside option is often expensive. In applications, pricing power depends on process lock-in, integration depth and implementation history. In OCI, pricing power is weaker for generic compute and storage because AWS, Azure and Google Cloud set broader market expectations. Oracle’s cloud pricing pitch therefore emphasizes predictability, lower egress, license portability and performance for Oracle workloads rather than premium generic pricing.

In AI capacity, pricing power depends on scarcity. When GPUs, power and high-density datacenter capacity are scarce, Oracle can command attractive commitments from model developers. When supply loosens, when customers build their own chips, when training demand shifts toward inference optimization, or when GPU generations change faster than depreciation schedules, pricing power can compress. This is the main economic difference between database rent and AI capacity rent. Database rent is protected by accumulated switching costs. GPU capacity rent is protected by scarcity, which may be cyclical.

Unofficial signals and confidence

Corroborated public evidence: Oracle’s FY2026 financial results, RPO disclosure, capex, operating cash flow, free cash flow, cloud revenue and financing plans are official company disclosures and high-confidence for reported historical figures. Interpretation of future returns remains uncertain.

Corroborated technical evidence: OCI region documentation, service-availability tables, multicloud listings, AI infrastructure specifications and public-region claims are official Oracle evidence. They are high-confidence as descriptions of Oracle’s stated architecture and commercial offering, but not independent proof of customer satisfaction or delivered performance at all locations.

Corroborated partner evidence: OpenAI and Crusoe statements on Stargate, Abilene, GB200 rack delivery, capacity targets and site development are high-confidence as statements by involved parties. They are not independent audit evidence of final delivered capacity, utilization or economics.

Medium-confidence analyst signal: Moody’s risk framing, as reported by Reuters, is a credible credit-market signal. It does not prove Oracle’s AI contracts will underperform, but it correctly identifies project-finance, leverage, customer concentration and negative free-cash-flow duration as central risks.

Medium-confidence counterparty signal: Reuters’ report on OpenAI projected cash burn, citing The Information, is useful but not audited. It is relevant because Oracle’s AI backlog depends partly on the financial capacity and strategic consistency of a small number of AI buyers.

Medium-confidence local-infrastructure signal: AP reporting on the Abilene expansion and power plant, and Business Insider reporting on property valuation and tax abatements, are credible journalistic indicators of power and local-incentive dynamics. They are not complete project economics or legal conclusions.

Medium-confidence customer/operator signal: UpperEdge commentary on Oracle licensing and VMware reflects practitioner experience in enterprise negotiations. It is not an official legal interpretation, but it is relevant because customer fear of licensing exposure is part of Oracle’s economic moat.

Medium-confidence outage signal: DataCenterDynamics’ report on a Europe OCI outage relies partly on user reports and third-party outage indicators. It is an external signal rather than a confirmed Oracle incident report, and is useful mainly for assessing the gap between public status dashboards and customer-perceived incidents.

Evidence ledger

  1. Oracle FY2026 results: high-confidence official evidence for revenue, cloud growth, RPO, prepayments, capex pressure, operating cash flow and free cash flow. Key caveat: management guidance and AI-market commentary are forward-looking.
  2. Oracle public-sector price list: high-confidence evidence for list pricing of Oracle Database Enterprise Edition and options. Caveat: list prices are not realized enterprise contract prices.
  3. DB-Engines ranking: medium-confidence popularity signal for database mindshare. Caveat: not revenue share, installed-base share or workload volume.
  4. Oracle License Management Services: high-confidence official evidence that Oracle maintains a formal compliance/audit apparatus. Caveat: official framing emphasizes customer assistance, not negotiation pressure.
  5. UpperEdge licensing commentary: medium-confidence practitioner evidence of customer pain around Oracle licensing and virtualization. Caveat: vendor advisory perspective, not a court ruling.
  6. OCI regions and availability domains documentation: high-confidence evidence for region/AD architecture and single-AD expansion pattern. Caveat: does not measure actual uptime or capacity by region.
  7. Oracle public cloud regions page: high-confidence official evidence for commercial region count, backbone, egress allowance, compliance claims and pricing posture. Caveat: official marketing page, not independent performance benchmark.
  8. OCI service-availability and multicloud tables: high-confidence evidence for Oracle’s multicloud database strategy and service listings. Caveat: availability does not prove adoption or utilization.
  9. Oracle AI infrastructure page: high-confidence official evidence for stated GPU cluster scale and networking claims. Caveat: technical claims should be validated workload-by-workload.
  10. OpenAI July 2025 Stargate announcement: high-confidence involved-party evidence for the 4.5 GW Oracle partnership and early Abilene workloads. Caveat: not an audited delivery schedule.
  11. OpenAI September 2025 Stargate expansion: high-confidence involved-party evidence for planned site expansion, 7 GW planned capacity and Oracle-linked site capacity. Caveat: planned capacity can shift.
  12. Crusoe Abilene announcement: high-confidence partner evidence for energized buildings, GB200 rack delivery and design intent for hundreds of thousands of GPUs. Caveat: partner has commercial interest in the narrative.
  13. Reuters on Moody’s Oracle AI-contract risk: medium-high confidence evidence of credit-analyst concern around counterparty, leverage and free-cash-flow risk. Caveat: analyst assessment, not operational failure.
  14. Reuters on OpenAI cash burn: medium-confidence counterparty-risk signal. Caveat: Reuters attributes the forecast to The Information and OpenAI did not comment in that report.
  15. AP on Abilene expansion and power: medium-high confidence evidence of power-plant and site-allocation dynamics. Caveat: site allocation can change as customers renegotiate capacity needs.
  16. Business Insider on Abilene tax valuation and abatement: medium-confidence evidence of local-incentive economics. Caveat: not a full public-finance audit.
  17. Oracle U.S. Defense Cloud page: high-confidence official evidence for DISA/FedRAMP/IL authorization positioning. Caveat: accreditation does not equal workload performance.
  18. GAO on VA EHR modernization: high-confidence government oversight evidence on Oracle Health/Cerner implementation risk. Caveat: program risk is shared across agency, integrators, vendor and governance model.
  19. Reuters on Oracle credential incident: medium-high confidence security-history evidence based on customer communications and people familiar with the matter. Caveat: not a full forensic report.
  20. DataCenterDynamics on OCI Europe outage reports: medium-confidence external outage signal. Caveat: relies partly on user reports and third-party indicators.
  21. Synergy/CRN cloud-market share: medium-high confidence market-share context for hyperscaler competition and Oracle’s challenger status. Caveat: third-party estimates, definitions vary by market segment.
  22. Snowflake, Databricks and SAP financial disclosures/announcements: high-confidence current competitor scale indicators for data cloud, lakehouse/AI platform and enterprise applications competition. Caveat: Snowflake and SAP are public-company disclosures; Databricks is private-company self-reporting.

12–36 month watchpoints

First, track conversion of AI RPO into recognized OCI revenue. The key question is not whether Oracle can announce backlog, but whether it can energize sites, install clusters, meet service levels and convert commitments into revenue without margin disappointment.

Second, track capex, net debt and free cash flow together. A rising OCI revenue line with persistently negative free cash flow would imply Oracle is buying growth with capital intensity. A stabilization of capex intensity relative to revenue would support the bull case.

Third, track customer concentration in AI infrastructure. If OpenAI or a small group of AI companies accounts for a disproportionate share of backlog, credit-market scrutiny will remain justified.

Fourth, track power procurement and site execution. The relevant signals are interconnection queues, on-site generation, gas-turbine orders, transformer availability, local tax disputes, water/cooling constraints, and construction milestones in Abilene, Texas; Shackelford County, Texas; Doña Ana County, New Mexico; Wisconsin/Midwest sites; and any additional Stargate locations.

Fifth, track whether customer-supplied or prepaid GPU structures expand. These structures reduce Oracle’s upfront capital burden but may also indicate that large AI buyers have enough leverage to shape Oracle’s economics.

Sixth, track OCI region maturity. More multi-AD regions, clearer regional capacity disclosures, improved status transparency and evidence of non-Oracle workloads would support OCI’s claim to be a broader hyperscale challenger.

Seventh, track Oracle Database@AWS, @Azure and @Google adoption. This is one of Oracle’s most important strategic moves because it lets Oracle keep database rent inside competitor clouds.

Eighth, track database support and audit behavior. If Oracle intensifies audits or uses license pressure to push OCI migration, near-term revenue may benefit but customer resentment and open-source migration incentives will grow.

Ninth, track PostgreSQL and open-source displacement in new workloads. Oracle’s legacy base is hard to move, but new workload default choices determine the long-run addressable base.

Tenth, track Snowflake and Databricks penetration into Oracle-heavy accounts. The risk is not only database replacement; it is analytic data gravity moving away from Oracle systems of record.

Eleventh, track SAP cloud ERP migration. SAP’s success in moving ERP customers to S/4HANA Cloud can weaken Oracle’s application and database leverage in accounts historically running SAP on Oracle databases.

Twelfth, track Oracle Health. VA deployment progress, user satisfaction, cost estimates, congressional oversight, hospital references and cybersecurity posture will determine whether Cerner becomes a regulated-industry growth engine or a persistent drag.

Thirteenth, track security transparency. Oracle’s value proposition to governments and regulated industries depends on incident disclosure discipline, patch cadence, identity resilience and customer trust.

Fourteenth, track gross margin mix. Database and support economics are structurally different from GPU capacity economics. If AI infrastructure becomes too large a share of growth, Oracle’s consolidated margin profile may look less like classic software and more like capital-intensive infrastructure.

Fifteenth, track debt-market reaction. Moody’s and other credit-market signals may become leading indicators of how much AI infrastructure risk Oracle can absorb without raising its cost of capital.

Sixteenth, track whether Oracle’s AI infrastructure customers build internal chips or diversify cloud suppliers. Customer vertical integration can turn today’s scarcity premium into tomorrow’s pricing pressure.

Seventeenth, track regulatory and sovereignty demand. Oracle’s government, sovereign and dedicated-cloud positioning is a differentiated asset if data-residency and national-security requirements tighten.

Eighteenth, track public-sector procurement wins and delivery outcomes. New contracts help Oracle’s top line, but implementation performance determines whether public-sector exposure compounds trust or creates political risk.