Executive Summary: Oracle Cloud Infrastructure (OCI) AI Infrastructure

OCI occupies a structurally unique position in this assessment series: it is the only hyperscaler whose AI infrastructure strategy is anchored by a database franchise. AWS builds down from managed services. Google builds out from a frontier model. OCI builds up from the enterprise data layer: Oracle AI Database 26ai, Autonomous AI Database, and the Fusion Applications estate that runs 97% of the Fortune 100. Every other hyperscaler treats the database as one service among many. Oracle treats the database as the gravitational center around which AI infrastructure orbits.

The infrastructure story is more aggressive than the enterprise positioning suggests. OCI Zettascale10 connects up to 800,000 NVIDIA GPUs across multi-gigawatt clusters delivering 16 zettaFLOPS: the fabric underpinning the Stargate supercluster built with OpenAI in Abilene, Texas. Oracle Acceleron, a custom RoCE networking architecture with 2.5–9.1 microsecond latency, is genuine 0B IP that positions OCI alongside AWS (Nitro/EFA/SRD) and Google (Virgo) as hyperscalers with proprietary networking stacks. The AMD partnership (50,000 MI450 GPUs, Q3 2026) makes OCI one of two hyperscalers with meaningful multi-vendor GPU strategy alongside AWS.

The DAPM profile is heavily Ceded: structurally identical to AWS and Google Cloud in that the enterprise consumes managed services without controlling underlying architecture. But OCI adds a distinctive wrinkle: the database layer creates a gravitational pull that concentrates not just infrastructure authority but data authority. An enterprise running Fusion Applications on Autonomous AI Database on OCI Superclusters has Ceded compute, networking, database, application runtime, AND business logic to a single vendor. This is deeper vertical integration than AWS (which doesn't own the application layer) and comparable to Google's model-integrated stack, but achieved through the application and data layers rather than through a frontier model.

OCI Enterprise AI (GA March 2026) is a credible but late entry to the agentic platform space. OpenAI Responses-compatible API, managed agent hosting, vector stores, MCP support, guardrails, and observability: the capabilities parallel AWS Bedrock AgentCore and Google's Gemini Enterprise Agent Platform. The differentiator is database-native AI: Select AI for natural language to SQL, AI Vector Search inside the database engine, and the Private Agent Factory pattern that keeps agent reasoning co-located with enterprise data. Whether 'AI at the database layer' is a structural advantage or an architectural constraint is the central DAPM question for OCI.

The Stargate partnership and $553B RPO validate infrastructure demand. The Fusion Agentic Applications validate the application-layer strategy. The multicloud database deployments (Oracle Database@AWS, @Azure, @Google Cloud) validate the data-gravity thesis. But the 4+1 framework asks a different question: where does authority reside, and has the enterprise made that placement explicit? For OCI, the answer is that authority concentrates in the database, and the database concentrates in Oracle.

Layer-by-layer status: Layer 0A (Bare-Metal NVIDIA and AMD Superclusters, Rented by the Shape), Layer 0B (Acceleron RoCE and the RDMA Cluster Network, a Fabric Oracle Designed), Layer 0C (File Storage With Lustre Feeds the Accelerators), Layer 1A (Database-Native Classification, Data Safe Discovery and a Catalog With Lineage), Layer 1B (Database-Native Retrieval), Layer 1C (Database-Centric Pipelines), Layer 2A (OKE + Karpenter + Cluster Networks), Layer 2B (OCI Enterprise AI Platform), Layer 2C (Intelligence 2C: Emerging | Infra 2C: Implicit), Layer 3 (+1) (Strongest Application-Layer Authority).

Assessment framework: 4+1 Layer AI Infrastructure Model. Scoring model: Decision Authority Placement Model (DAPM) — Retained, Delegated, or Ceded. Published by The CTO Advisor LLC (DBA The Advisor Bench). Author: Keith Townsend. Date assessed: October 27, 2026. Version: v1.40 - 4+1 v3: Layer 0 Sub-Layers.

Disclosure: The CTO Advisor has a commercial relationship with this vendor. Assessment findings are independent. See disclosure policy.

Oracle Cloud Infrastructure (OCI) AI Infrastructure

Mapped to the 4+1 Layer AI Infrastructure Model

v1.40 - 4+1 v3: Layer 0 Sub-LayersAssessed October 27, 2026Sources & revision history
ACTIVE ASSESSMENT

Summary Finding

OCI occupies a structurally unique position in this assessment series: it is the only hyperscaler whose AI infrastructure strategy is anchored by a database franchise. AWS builds down from managed services. Google builds out from a frontier model. OCI builds up from the enterprise data layer: Oracle AI Database 26ai, Autonomous AI Database, and the Fusion Applications estate that runs 97% of the Fortune 100. Every other hyperscaler treats the database as one service among many. Oracle treats the database as the gravitational center around which AI infrastructure orbits.

The infrastructure story is more aggressive than the enterprise positioning suggests. OCI Zettascale10 connects up to 800,000 NVIDIA GPUs across multi-gigawatt clusters delivering 16 zettaFLOPS: the fabric underpinning the Stargate supercluster built with OpenAI in Abilene, Texas. Oracle Acceleron, a custom RoCE networking architecture with 2.5–9.1 microsecond latency, is genuine 0B IP that positions OCI alongside AWS (Nitro/EFA/SRD) and Google (Virgo) as hyperscalers with proprietary networking stacks. The AMD partnership (50,000 MI450 GPUs, Q3 2026) makes OCI one of two hyperscalers with meaningful multi-vendor GPU strategy alongside AWS.

The DAPM profile is heavily Ceded: structurally identical to AWS and Google Cloud in that the enterprise consumes managed services without controlling underlying architecture. But OCI adds a distinctive wrinkle: the database layer creates a gravitational pull that concentrates not just infrastructure authority but data authority. An enterprise running Fusion Applications on Autonomous AI Database on OCI Superclusters has Ceded compute, networking, database, application runtime, AND business logic to a single vendor. This is deeper vertical integration than AWS (which doesn't own the application layer) and comparable to Google's model-integrated stack, but achieved through the application and data layers rather than through a frontier model.

OCI Enterprise AI (GA March 2026) is a credible but late entry to the agentic platform space. OpenAI Responses-compatible API, managed agent hosting, vector stores, MCP support, guardrails, and observability: the capabilities parallel AWS Bedrock AgentCore and Google's Gemini Enterprise Agent Platform. The differentiator is database-native AI: Select AI for natural language to SQL, AI Vector Search inside the database engine, and the Private Agent Factory pattern that keeps agent reasoning co-located with enterprise data. Whether 'AI at the database layer' is a structural advantage or an architectural constraint is the central DAPM question for OCI.

The Stargate partnership and $553B RPO validate infrastructure demand. The Fusion Agentic Applications validate the application-layer strategy. The multicloud database deployments (Oracle Database@AWS, @Azure, @Google Cloud) validate the data-gravity thesis. But the 4+1 framework asks a different question: where does authority reside, and has the enterprise made that placement explicit? For OCI, the answer is that authority concentrates in the database, and the database concentrates in Oracle.

Strength
Moderate
Gap
Partner
Layer 0A · ComputeComputeBare-Metal NVIDIA and AMD Superclusters, Rented by the Shapedecides: vendor · Ceded▼

CPUs, accelerators, servers, integrated systems, OS and hypervisor, physical plant

Vendor-Provided

OCI SuperclustersCeded

Scales from 8 GPUs to 131,072 B200 GPUs, 100,000+ GB200 Superchips per cluster. Bare metal GPU instances with RDMA cluster networking.

NVIDIA GPU Instances on OCI (B300, B200, H200, H100, A100, L40S, RTX PRO 6000 Bare Metal)Retained

Bare metal shapes from BM.GPU.A100-v2.8 through BM.GPU.B300.8 (eight B300, 263 GB each), plus L40S and BM.GPU.RTXPRO.8 (eight RTX PRO 6000 Blackwell on Xeon 6 hosts), per OCI's compute shapes doc. NIXL support for disaggregated inference. Standard NVIDIA instances: a CUDA or PyTorch workload moves to another cloud's NVIDIA instances or an OEM server without a rebuild. Retained under the Layer 0 runtime rule, read from the customer's seat; the CUDA dependency is NVIDIA's and sits in the NVIDIA column.

NVIDIA NVL-Class Rack-Scale Capacity on OCI (GB200 and GB300 Superchip Shapes)Ceded

BM.GPU.GB200.4 (four B200 on two Grace CPUs) and BM.GPU.GB300.4 (four B300, 278 GB each), OCI's Grace Blackwell shapes. The NVL72 rack framing rests on Oracle's June 12, 2025 announcement; the shapes doc doesn't describe the rack. DGX Cloud hosted on OCI is NVIDIA's service, read on NVIDIA's row. Ceded on the integrated-system rule, the Lenovo NVL-class reading: a rack-scale system built around a captive NVLink fabric can't be lifted as deployed.

AMD Instinct MI300X and MI355X Instances on OCIRetained

BM.GPU.MI300X.8 (eight MI300X, 192 GB) and BM.GPU.MI355X (eight MI355X, 288 GB), the MI355X generally available since October 14, 2025 on OCI's Supercluster platform. Standard instances on third-party silicon: a ROCm or PyTorch workload moves to another cloud or an OEM server without a rebuild. Retained under the Layer 0 runtime rule, read from the customer's seat; AMD's runtime is read on AMD's row.

OCI Dedicated Region25 + Oracle AlloyCeded

Full OCI stack (200+ services including SaaS) in customer data center, starting at 3 racks. 60+ Dedicated Region/Alloy regions live. EU Sovereign Cloud (Frankfurt, Madrid). Isolated Cloud Regions for classified workloads. Oracle Alloy enables partner-operated OCI. Fujitsu, SoftBank, Vodafone as anchor customers.

Intel Xeon 6 Compute on OCI (X12 Standard: VM.Standard4.Ax.Flex, BM.Standard4.Ax.120)Retained

X12-based standard compute on the Intel Xeon 6987P-C: flex VMs up to 39 OCPUs and 360 GB, and a 120-core bare metal shape with 1,152 GB.

NVIDIA-Provided

NVIDIA GPU Silicon

B200 and B300, H200, H100, A100, L40S, RTX PRO 6000, and the GB200 and GB300 shapes. DGX Cloud on OCI is NVIDIA's service, read on NVIDIA's row.

◆ Gap Analysis

OCI rents bare-metal NVIDIA from A100 through B300 and RTX PRO 6000, the GB200 and GB300 Grace Blackwell shapes, AMD Instinct MI300X and MI355X (the MI355X generally available since October 14, 2025) and Xeon 6 standard compute. Superclusters scale from 8 GPUs to 131,072 B200s. Dedicated Region25 puts the full OCI stack, 200+ services including SaaS, in the customer's data center from three racks, and Oracle Alloy lets partners operate it. The buyer gets GPU access without a hypervisor in the way. The architect's concern is the runtime and the rack. A CUDA, ROCm or PyTorch workload on standard bare-metal shapes keeps its exit. Superclusters and NVL72 racks are integrated systems, and Dedicated Region's services run only on Oracle's stack. Calibration: AWS, Azure and GCP read strong on the same rented shape; Dell and HPE strong on hardware the enterprise owns.

◆ Borrowed Judgment

Rented, so the runtime call is Oracle's. Bare metal hands the enterprise the OS, but Oracle decides which host a shape lands on, cluster placement and maintenance: vendor decides, visible, not overridable, Ceded. Portability splits by runtime: the NVIDIA, AMD and Xeon shapes read Retained; Superclusters, the NVL72 racks, Dedicated Region and Alloy read Ceded.

◆ Working Notes

Named, not scored (October 5, 2026 GA gate): the AMD MI450 fleet in Helios racks, dated to calendar Q3 2026 with no GA documented. At GA it reads Ceded on the integrated-system rule. Named, not scored (October 23, 2026): Zettascale10, up to 800,000 NVIDIA GPUs and 16 zettaFLOPS, announced October 2025 for the second half of 2026 with orders taken and no OCI documentation; BlueField-4 integration, a GTC 2026 announcement; Vera Rubin on OCI, committed with no shape. Confidence flag: the GB200 and GB300 shapes are documented, but their NVL72 rack framing rests on Oracle's announcement: neither the shapes doc nor OCI's GPU page (read October 23, 2026) describes the rack. The GPU page documents the Supercluster at up to 131,072 B200 GPUs, and the Dedicated Region page starts a region at "as few as 3 racks."

Layer 0B · FabricNetwork FabricAcceleron RoCE and the RDMA Cluster Network, a Fabric Oracle Designeddecides: vendor · Ceded▼

Interconnects, switching and routing, network virtualization

Vendor-Provided

Oracle Acceleron NetworkingCeded

Custom-designed RDMA over Converged Ethernet (RoCE v2). 2.5–9.1 microsecond GPU-to-GPU latency. Multiplanar network architecture with dedicated RoCE fabrics. Congestion-control-first (not PFC-dependent). Zero-Trust Packet Routing (ZPR) at the physical layer. Up to 3,200 Gb/s cluster network bandwidth. Oracle-owned networking IP.

OCI Superclusters: RDMA Cluster NetworkCeded

The RDMA cluster network the Supercluster is wired on; the fabric's own design is read on the Acceleron chip.

GB200 NVL72 on OCI: NVLink FabricCeded

The captive NVLink fabric inside the rack-scale system. Ceded with the system on the integrated-system rule.

OCI Virtual Cloud Network (Subnets, Route Tables, Security Lists, Network Security Groups, Gateways)Ceded

A virtual private network in one OCI region covering one or more CIDR blocks: subnets, custom route tables, stateful or stateless security lists, network security groups, and gateways.

OCI Dedicated Region + Oracle Alloy: NetworkingCeded

The VCN, load balancing, FastConnect and VPN services delivered in the customer's data center, read like OCI's other regions. Facet of the Dedicated Region + Alloy chip.

NVIDIA-Provided

NVLink in GB200 NVL72

The rack's NVLink domain is NVIDIA's, captive inside the integrated system.

BlueField-4

Integration for next-generation Superclusters, announced at GTC 2026.

◆ Gap Analysis

Oracle Acceleron is Oracle's own networking IP. It runs RDMA over Converged Ethernet (RoCE) v2 with a congestion-control-first design that doesn't depend on Priority Flow Control, on dedicated multiplanar fabrics with Zero-Trust Packet Routing at the physical layer. It runs at 2.5 to 9.1 microseconds GPU to GPU and up to 3,200 Gb/s of cluster bandwidth. The Virtual Cloud Network (VCN) wraps it in subnets, route tables, security lists and network security groups the enterprise writes. The buyer gets a training fabric that isn't leased NVIDIA networking. The architect's concern is that every piece is Oracle's design. Acceleron runs nowhere else, and the NVL72 racks add a captive NVLink fabric inside the rack. Calibration: AWS's EFA and GCP's RoCE GPU network read strong on the same shape; HPE's Slingshot and NVIDIA's Spectrum-X strong as fabrics the enterprise buys.

◆ Borrowed Judgment

Ceded where the grade rests. The route tables and security lists are the enterprise's code, but Acceleron's congestion control, multiplanar routing and Zero-Trust Packet Routing make the transport calls with no per-decision override: vendor decides, visible, not overridable, Ceded. Portability: Acceleron, the cluster network and VCN are single-vendor surfaces, Ceded.

Layer 0C · StorageStorage SubstrateFile Storage With Lustre Feeds the Acceleratorsdecides: vendor · Delegated▼

Arrays, storage servers and software, front-end protocols: where the data sits

Vendor-Provided

S3 Compatibility API on OCI Object StorageDelegated

The S3 Compatibility API on OCI Object Storage, which supports a documented subset of S3 operations. Workloads confined to the supported common S3 operations move by changing endpoints, credentials and provider-specific configuration; the data, policies and unsupported service features migrate or adapt. Delegated. The service behind it, with its replication and storage classes, is the Object Storage chip, Ceded.

OCI Object Storage, through the native Object Storage APICeded

Standard object storage for unstructured data, embeddings, model artifacts. Regional and cross-region replication. Storage Classes for cost optimization. The service, its replication and storage classes, and the native Object Storage API are Oracle's: Ceded. The S3 Compatibility API is its own chip.

OCI Block Volume (iSCSI and Paravirtualized Attachments; Cross-AD and Cross-Region Replication; Volume Groups)Ceded

Block and boot volumes with ongoing asynchronous replication to another availability domain or region, backups that restore to any AD and copy across regions, and volume groups.

OCI File Storage (NFSv3; Snapshots; File System Replication)Ceded

Managed NFSv3 file systems held in one availability domain with 5-way replicated, erasure-coded storage across fault domains, copy-on-write snapshots, and up to three replication jobs per file system to another AD or region. NFS is its own chip. The service, its snapshots and replication jobs, is Oracle's and doesn't lift: Ceded.

OCI File Storage with Lustre (Managed Lustre 2.15.5; Four Performance Tiers)Ceded

Fully managed Lustre for AI training and HPC: Oracle runs the metadata, management and storage servers, with tiers from 125 to 1000 MBps per provisioned TB. Not offered in every region. The Lustre client is its own chip. The service Oracle runs, its tiers and servers, doesn't lift to another Lustre: Ceded.

OCI Dedicated Region + Oracle Alloy: Block Volume and Native-API Object StorageCeded

Block Volume and Object Storage through the native Object Storage API, as endpoints in the customer's data center, read like OCI's other regions. Facet of the Dedicated Region + Alloy chip. Ceded, with Block Volume and the native API in OCI's regions: the opinions accumulate in Oracle's APIs.

OCI Dedicated Region + Oracle Alloy: File Storage, File Storage with Lustre and S3-Compatible Object StorageCeded

File Storage over NFSv3, File Storage with Lustre, and Object Storage through the S3 Compatibility API, as endpoints in the customer's data center where offered in the specific region, read like OCI's other regions. Facet of the Dedicated Region + Alloy chip. The protocols are their own chip; the services behind them are Oracle's, as in OCI's regions: Ceded.

Front-End Protocols on OCI File Storage (NFSv3)Delegated

NFSv3, which independent implementations share: hosts and applications re-point to another server or target speaking the same protocols, and the data and provider-specific policies migrate with it. Delegated. The managed service is the File Storage chip, Ceded.

Lustre Client Protocol on OCI File Storage with LustreDelegated

Customers deploy and tune their own Lustre clients, the open client DDN, HPE and the other clouds' managed Lustre services share: the client and its tooling stay usable against another Lustre, while service topology, stored layouts, backups and integrations are revalidated or recreated. Delegated. The managed service is the File Storage with Lustre chip, Ceded.

Front-End Protocols on OCI Dedicated Region + Oracle Alloy File and Object Storage (NFSv3, Lustre Client, S3)Delegated

NFSv3, the Lustre client and the S3 Compatibility API in the customer's data center, where the specific region offers them, which independent implementations share: hosts and applications re-point to another server or target speaking the same protocols, and the data and provider-specific policies migrate with it. Delegated. The services behind them are the Dedicated Region facet, Ceded.

NVIDIA-Provided

Assessment pending

◆ Gap Analysis

OCI covers the substrate end to end. Object Storage holds training data, embeddings and model artifacts, Block Volume handles block with replication to another availability domain or region, and File Storage serves NFSv3. File Storage with Lustre is the managed parallel file system for AI training. Its four tiers run from 125 to 1,000 MBps per provisioned TB, about 1 TB/s aggregate for 1 PB at the top tier. Oracle's August 2025 benchmark white paper backs the numbers. The buyer gets AI-throughput storage sized to the workload. The cell rests on File Storage with Lustre, and that's where the enterprise keeps a handle. Oracle runs the Lustre servers, the enterprise builds and tunes its own upstream clients, and Oracle's benchmark paper sets striping with lfs setstripe and lfs setdirstripe. The architect's concern is reach: Lustre isn't offered in every region. Calibration: AWS, Azure and GCP read strong on managed Lustre; DDN and WEKA strong on the same function sold as software or appliances.

◆ Borrowed Judgment

Delegated where the grade rests. File Storage with Lustre places data across its storage targets, and the enterprise can override a file's or a directory's layout from its own Lustre client: vendor decides, visible, overridable, Delegated. Portability: the Lustre client and NFS are multi-vendor standards, Delegated, and Object Storage splits by interface, Delegated through the S3 Compatibility API and Ceded through the native API; Block Volume and Dedicated Region's block and native-API object storage read Ceded, and Dedicated Region's File Storage, Lustre and S3-compatible storage read Delegated, as in OCI's regions.

Layer 1A · DataData Foundation & GovernanceDatabase-Native Classification, Data Safe Discovery and a Catalog With Lineagedecides: vendor · Delegated▼

The data itself, organized and governed: the Governance Catalog that Layer 2C queries

Vendor-Provided

Oracle Autonomous AI DatabaseCeded

Self-managing, self-securing, self-patching database built on Oracle AI Database 26ai engine. AI Vector Search (native vector data type, HNSW/IVF indexes, SQL-based similarity search), Select AI (natural language to SQL), ONNX embedding models, Private AI Services Container integration, NVIDIA NIM container support. Autonomous AI Lakehouse with Apache Iceberg support for open multi-vendor data lakehouse. RAFT-based replication, JSON Relational Duality, quantum-resistant encryption, in-database SQL firewall. Platinum and Diamond-tier availability (Apr 2026). Anomaly detection, auto-indexing, auto-tuning. Autonomous AI Vector Database variant in Limited Availability (March 2026). Available on OCI, AWS, Azure, Google Cloud via multicloud deployments.

Oracle Database@AWS / @Azure / @Google CloudCeded

Oracle AI Database running inside other hyperscalers' infrastructure with private interconnects. Multicloud Universal Credits for cross-cloud procurement. Teams use familiar AWS/Azure/Google tools and billing while running Oracle AI Database on OCI infrastructure within the hyperscaler. Oracle-AWS Interconnect expanded April 2026.

Oracle Data Safe (Sensitive Data Discovery and Sensitive Data Models)Ceded

Discovers sensitive columns against more than 170 predefined sensitive types and the enterprise’s own, from column names, comments and sampled data, and records each column’s sensitive type and confidence in a sensitive data model per target database, returned through the console, REST API, CLI and Terraform. The models and sensitive types are Oracle’s format: Ceded.

OCI Data Catalog (Glossary, Custom Properties, Tags, Lineage)Ceded

Business glossary terms, custom properties and tags on entities and attributes, with table- and column-level lineage from OCI Data Integration, Data Loader and Data Flow tasks and an import API in OpenLineage format. A proprietary catalog with a standard door for lineage import: Ceded.

NVIDIA-Provided

NVIDIA cuVS + CAGRA (Future)

GPU-accelerated vector indexing with NVIDIA CAGRA and cuVS designed for integration with Oracle AI Database. Not yet GA: future GPU acceleration for vector workloads.

◆ Gap Analysis

Oracle treats the database as the governance layer. Autonomous AI Database on Oracle AI Database 26ai carries classification, audit, encryption and access control natively, beside vector search, Select AI and an Apache Iceberg lakehouse. Database@AWS, @Azure and @Google Cloud put that authority inside other clouds. Oracle Data Safe discovers sensitive columns and records each one’s sensitive type and confidence in a model the API returns. Schema annotations carry the enterprise’s own name-value pairs on tables and columns, queryable in SQL. OCI Data Catalog adds glossary terms, custom properties, tags and column-level lineage. That answers what the data is at the column level. Object Storage holds the bytes, a 0C function. The architect’s concern is that every one of those opinions is in an Oracle format. Strong. Calibration: Azure reads strong on Purview classification a curator can edit; IBM strong on watsonx.data intelligence; NetApp strong on inferred sensitivity per file.

◆ Borrowed Judgment

Data Safe infers each column’s sensitive type from names, comments and sampled data, and the enterprise can reject a result or invalidate a column, which later runs respect: vendor decides, visible, overridable, Delegated. Annotations and catalog terms the enterprise writes execute as written. Portability: Autonomous AI Database, Data Safe, Data Catalog and the Database@ services are Oracle’s, Ceded.

◆ Working Notes

Unscored on its badge: the Autonomous AI Vector Database variant (Limited Availability, March 2026).

Layer 1B · RetrievalContext Management & RetrievalDatabase-Native Retrievaldecides: vendor · Delegated▼

Low-latency retrieval for RAG — vector/hybrid search, context windows

Vendor-Provided

AI Vector Search (Oracle Autonomous AI Database)Ceded

Native vector data type, HNSW and IVF vector indexes, SQL-based similarity search. Hybrid search combining vector similarity with relational predicates. Permission-aware retrieval through database access control. No separate vector database required.

OCI Enterprise AI: Managed Vector StoreCeded

Managed vector storage with file ingestion, semantic search, and metadata filtering for RAG and NL2SQL use cases. Schema enrichment into semantic vector store for natural language queries that produce and execute SQL against customer databases with permission control.

Select AI + SQL Search (NL2SQL)Ceded

Natural language to SQL generation and execution. Applications and analytics use LLMs to understand natural language questions and generate Oracle SQL. Bridges unstructured (vector) and structured (SQL) retrieval in a single query surface.

OCI Generative AI: Embeddings + RerankCeded

Managed embedding and reranking services. Supports Cohere, NVIDIA Nemotron, and other embedding models. Served through OCI's native inference API: Oracle documents its OpenAI-compatible endpoints for chat and responses, not embeddings or rerank. Dedicated AI clusters for consistent latency.

NVIDIA-Provided

NVIDIA NIM Containers for Embeddings

NVIDIA embedding models available through OCI Generative AI Model Import. cuVS acceleration planned for future vector indexing.

◆ Gap Analysis

OCI's Layer 1B collapses into Layer 1A, and that's the architectural point. AI Vector Search lives inside Oracle AI Database, not as a separate vector database service. RAG queries execute as SQL against the same database that holds the enterprise's transactional data. Permission-aware retrieval inherits the database's existing access control model without a separate security overlay. This is the same architectural pattern as VAST (InsightEngine inside the data platform) but at the database level rather than the storage level. The comparison to AWS is instructive: Bedrock Knowledge Bases composes OpenSearch + S3 + embedding models across service boundaries. Oracle eliminates those boundaries by making vector search a database capability. The SQL Search (NL2SQL) capability adds a dimension no other vendor's Layer 1B provides: agents can retrieve structured enterprise data through natural language queries that generate and execute SQL. This bridges unstructured retrieval (vector search for documents) and structured retrieval (SQL for business data) in a single query surface: a genuine differentiation. The gap: Oracle's Layer 1B is database-bounded. Data outside Oracle AI Database isn't retrievable through AI Vector Search. AWS's Bedrock Knowledge Bases can index data from any S3-accessible source. Google's BigQuery can federate queries across storage boundaries. Oracle's retrieval requires data to be IN the database or accessible through database links. SyncEngine-like capabilities for ingesting external enterprise data (Google Drive, Jira, Confluence) are not evident in Oracle's published materials.

◆ Borrowed Judgment

Low for vector search infrastructure: AI Vector Search, indexing, and SQL-based retrieval are Oracle IP inside the database engine. No external retrieval service dependency. Moderate for embedding quality: embedding models are either ONNX (customer-provided), NVIDIA NIM containers, or third-party models through OCI Generative AI. The quality of retrieval depends on embedding model choice, which the enterprise controls but doesn't build. The NL2SQL capability introduces a specific borrowed judgment: when Select AI generates SQL from natural language, the accuracy of retrieval depends on the model's understanding of the database schema. Schema enrichment into a semantic vector store (announced in OCI Enterprise AI) mitigates this, but the enterprise inherits the model's interpretation of table relationships and business logic. Decision authority (October 5, 2026): AI Vector Search chooses the access path, but each query can set its target accuracy and choose exact or approximate search, a per-request override. Vendor decides, overridable, Delegated, the Elastic, MongoDB, and Redis 1B reading.

◆ Working Notes

The Private Agent Factory pattern (announced March 2026) keeps agent reasoning co-located with enterprise data inside Oracle AI Database: agents query the database directly rather than through external RAG pipelines. This reduces network hops and latency for retrieval but deepens the database dependency. Every agent built on Private Agent Factory inherits Oracle AI Database as a non-substitutable Layer 1B dependency. The Exadata for AI announcement (vector search offloaded to intelligent storage for dramatic speedups) bridges Layer 1A and Layer 1B at the hardware level: the storage system itself accelerates retrieval. This is comparable to VAST's CNode-X collocating cache and compute, but implemented at the database storage layer rather than the file system layer.

Layer 1C · PipelinesData Movement & PipelinesDatabase-Centric Pipelinesdecides: code · Retained▼

Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering

Vendor-Provided

OCI GoldenGateCeded

Real-time data replication, transformation, and streaming across heterogeneous sources. Continuous data availability. Database migration, disaster recovery, real-time analytics. The deepest database connector ecosystem of any cloud data movement service.

OCI Data Integration + Data FlowCeded

Data Integration: managed ETL/ELT service with visual design. Data Flow: managed Apache Spark for large-scale data processing and ML data preparation. Integration with Autonomous AI Database and OCI Object Storage.

OCI Data Science PipelinesCeded

Managed ML pipelines whose steps are Data Science jobs or custom scripts against Autonomous Data Warehouse or Object Storage: "In an ML context, pipelines usually provide a workflow for data import, data transformation, model training, and model evaluation." The data steps are the enterprise's own code on Oracle's runner; the pipeline definitions are Oracle's: Ceded. The notebooks, training and model deployment are read at 2B.

NVIDIA-Provided

Assessment pending

◆ Gap Analysis

Layer 1C reveals the database-centric trade-off. Oracle's data movement capabilities are strong for database-to-database flows (GoldenGate) and analytics pipelines (OCI Data Integration, OCI Data Flow). But the ML-specific pipeline orchestration that Dell (Dataloop), HPE (Ezmeral Unified Analytics), VAST (DataEngine), and AWS (Glue + SageMaker Unified Studio) provide is less integrated. OCI Data Science provides notebooks, model training, and deployment but is a separate service from OCI Enterprise AI, creating a multi-surface problem similar to AWS's pre-Unified Studio fragmentation. There is no single governed environment that collapses data engineering, model training, and agent development the way SageMaker Unified Studio or Google's BigQuery ML attempt. GoldenGate is the most mature real-time data replication service in the assessment series: purpose-built for heterogeneous data movement across on-premises and cloud. No other hyperscaler has an equivalent with Oracle's depth of database connector support. The multicloud data movement story is strong: Oracle Database@AWS/@Azure/@Google Cloud moves the database layer to the customer's cloud of choice. But this is database replication, not general-purpose data pipeline orchestration. An enterprise needing Airflow-style DAG orchestration for ML workflows must deploy it on OKE, which is possible but not Oracle-managed. Decision authority: GoldenGate and Data Integration carry the grade and execute what the enterprise configured. DDL replication follows parameters the enterprise writes, and replication lag is monitored in documented metrics. Code decides, visible, overridable, Retained, the judgment test and its defaults clause (October 4 and 5, 2026).

◆ Borrowed Judgment

Low to moderate. GoldenGate and OCI Data Integration are Oracle IP. Data Flow (managed Spark) and OCI Data Science (managed notebooks) are Oracle-managed wrappers around open-source technology (Apache Spark, JupyterLab). The enterprise retains pipeline logic but Cedes execution infrastructure. The pipeline gap means enterprises often bring third-party orchestration (Airflow, Kubeflow) to OCI, introducing borrowed judgment from those communities and creating governance boundaries that don't exist when using Oracle-native services.

◆ Working Notes

The absence of a unified ML pipeline platform is the most significant gap relative to AWS and Google Cloud. Both competitors have invested heavily in collapsing the data engineering → model training → model serving → agent development pipeline into single governed surfaces. Oracle's approach is service-by-service composition: GoldenGate for replication, Data Integration for ETL, Data Flow for Spark, Data Science for ML, Enterprise AI for agents, without the horizontal integration layer. Oracle Fusion Applications data is already 'in Oracle': the pipeline problem for Fusion customers is different than for greenfield AI. The data doesn't need to be moved; it needs to be made AI-ready. Select AI and AI Vector Search address this for Fusion customers in a way that no amount of pipeline tooling could match. The question is whether non-Fusion enterprises find the pipeline story compelling. Oracle Interconnect and the Database@ clouds' connectivity are private networking ("over private, low-latency connections"), not query federation, so they're not scored at 1C.

Layer 2A · OrchestrationInfrastructure OrchestrationOKE + Karpenter + Cluster Networksdecides: vendor · Ceded▼

GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization

Vendor-Provided

OCI Compute Management (Instance Pools, Cluster Networks, Capacity Reservations)Ceded

Documented in OCI product docs with CLI and SDK surfaces: instance configurations and pools for fleet management, cluster networks for RDMA-connected GPU/HPC groups, capacity reservations for predictable accelerator supply. Single-vendor management APIs: pool definitions and reservation opinions are OCI-captive, consistent with the instrument's treatment of hyperscaler-native management surfaces.

OCI Kubernetes Engine (OKE)Delegated

Managed Kubernetes with GPU-aware node pools. Bare metal and virtual machine compute shapes. RDMA cluster networking for training workloads. MIG support for fractional GPU allocation. Autoscaling at pod level with GPU Device Plugin metrics. Karpenter support for node autoprovisioning. Free managed control plane. A managed service behind the standard Kubernetes API: manifests lift to another conformant cluster, so Delegated (operation delegated to Oracle; the standard interface keeps the opinions portable).

NVIDIA-Provided

NVIDIA GPU Operator + Device Plugin on OKE

GPU discovery, health monitoring, scheduling within OKE clusters. MIG support for fractional GPU allocation. Node Manager for GPU/networking monitoring. NVIDIA DCGM integration.

◆ Gap Analysis

OCI's Layer 2A reads strong on the same three legs as AWS, Google Cloud, and Azure: Kubernetes-based GPU orchestration through a managed service (OKE) with NVIDIA GPU scheduling underneath. OKE provides managed Kubernetes with GPU-aware node pools, autoscaling, bare-metal RDMA networking, and MIG support for fractional GPU allocation. The distinction from AWS: OCI's bare-metal GPU instances give customers more direct hardware control than AWS's virtualized GPU instances. OKE autoscaling operates at the pod level using NVIDIA GPU Device Plugin metrics, and the Karpenter Provider for OCI (GA April 2026) brings flexible node autoprovisioning, matching AWS's Karpenter capability for just-in-time compute shape selection based on workload requirements. GPU scheduling authority follows the same pattern as Dell and HPE: NVIDIA controls GPU scheduling through the GPU Operator and Device Plugin. Oracle controls infrastructure orchestration through OKE. Policy-driven GPU scheduling (which workload gets which GPU based on cost, compliance, and performance) is not an OCI-native function: the same gap every vendor shares. The Dedicated Region model adds a Layer 2A dimension other hyperscalers don't match: OCI orchestrates infrastructure across public cloud, 60+ dedicated regions, isolated regions, and Alloy partner regions from a single control plane. The orchestration scope is broader than AWS (Outposts, AI Factories) or Google (GDC) in terms of the number and variety of deployment targets. Re-graded October 5, 2026: the cell had calibrated to AWS and landed a grade below it. AWS 2A is strong on managed Kubernetes, Karpenter, and capacity management, and OCI has all three GA: OKE with GPU node pools and automatic cluster healing, the Karpenter Provider for OCI (release note, April 9, 2026), and instance pools and cluster networks for GPU fleets, which are long GA. Kueue appears only in OCI AI Blueprints, not in OKE documentation, and isn't scored; AWS's strong doesn't rest on it either.

◆ Borrowed Judgment

GPU scheduling: NVIDIA-controlled, same as every other vendor except AWS (Karpenter) and Google (TPU scheduling). Infrastructure orchestration: Oracle-controlled through OKE and the OCI control plane. Orchestration is consumed through the standard Kubernetes interface; the enterprise's manifests lift to another platform (Delegated: managed K8s service; the enterprise could switch without rebuilding). GPU scheduling intelligence is the Ceded part (NVIDIA-controlled). The bare-metal model creates a subtly different borrowed judgment profile: with bare metal, the enterprise has more direct GPU control (no hypervisor overhead, direct RDMA access) but also more operational responsibility. The judgment about GPU sharing, isolation, and scheduling is partially Retained by the customer: a more favorable DAPM position than fully managed GPU instances.

◆ Working Notes

OCI's GPU monitoring through Node Manager is actively developing: the tool surfaces GPU, networking, and infrastructure metrics in a Kubernetes-native way. This is an operational foundation that could evolve toward Layer 2C if enriched with policy-driven decision-making. The multi-accelerator scheduling problem (NVIDIA vs AMD GPUs, different instance types) will become acute when AMD MI450 GPUs arrive Q3 2026. OCI will need workload-to-silicon matching capabilities (a Layer 2C function) to help customers choose between NVIDIA and AMD for each workload. No productized capability for this exists today. Corrected October 5, 2026: OCI Compute Management (instance pools, cluster networks, capacity reservations) had been watch-listed as Q3 2026, but it's long GA (cluster networks documentation carries no preview badge) and is scored. GPU Node Manager's GA status is unconfirmed and doesn't carry the grade. To notes under the GA evidence table (October 24, 2026): GPU Node Manager + Monitoring (no Oracle page names a GPU Node Manager; the nearest match, OCI GPU Scanner, is titled "(Preview)").

Layer 2B · RuntimeApplication Runtime & ExecutionOCI Enterprise AI Platformdecides: model · Delegated▼

Model serving, agent execution, inference APIs, distributed inference

Vendor-Provided

OCI Enterprise AI PlatformCeded

End-to-end agentic AI platform (GA March 2026). OpenAI Responses-compatible API with multi-model routing. Enterprise AI agents with modular, composable primitives. Managed agent hosting for OSS frameworks and MCP servers. Vector stores, semantic search, NL2SQL, memory, tools. IAM integration, guardrails, observability, auditability. Dedicated AI clusters for isolated compute.

Model Serving via OpenAI-Compatible APIs (OCI Generative AI)Delegated

Foundation model access served through OpenAI-compatible APIs: xAI Grok (4.1 Fast, 4.3), Cohere Command A (Vision, Reasoning), NVIDIA Nemotron 3 Nano Omni, and gpt-oss open-weight models. A managed service behind a multi-vendor standard interface, so the integration opinions lift to any compatible endpoint. Embeddings and rerank are excluded from this call and scored Ceded at 1B under the embeddings carve-out. Not scored within this chip under the GA evidence table: xAI Grok 4.1 Fast ("This model was deprecated on May 15, 2026 , and retires on August 15, 2026 . After retirement, you no longer have access to this model.").

Customer-Created and Managed Tools (Function Calling / Client-Side)Retained

GA through OCI Generative AI's OpenAI-compatible APIs. The enterprise owns and operates the business logic, APIs, commands and deterministic validators invoked through tool calls: the seam where control passes from instructing the model to executing code outside it. The opinions are the enterprise's and run against a multi-vendor interface, so they lift to another provider with an adapter and re-evaluation, not a rebuild. What the enterprise cedes at this seam is the decision to act: the model chooses whether, when and with which arguments to call, and that judgment is inherited under the serving component above. Added instrument-wide on September 2, 2026 (M4): the seam exists on every runtime that hands control to portable customer code, and a real Retained position is scored, not narrated.

OCI Generative AI Platform Surface (Model Import, Sovereign Hosting)Ceded

The surface beyond the standard interface: Model Import for custom models and the sovereign data-hosting options, both configured against Oracle-only control surfaces. Opinions accumulated here do not lift.

Applications and Deployments (Hosted Runtime)Ceded

Container-based hosting for custom agentic applications. Managed infrastructure, networking, storage integration, identity configuration. Public and private endpoint support. Build-in security. Supports OSS frameworks and custom runtimes.

Private Agent Factory (Oracle Autonomous AI Database)Ceded

Agents run inside Oracle AI Database with direct data access. Co-locates agent reasoning with enterprise data. Eliminates external RAG pipeline latency. Private AI Services Container for on-premises inference without sending data to third-party services.

NVIDIA-Provided

NVIDIA NIM + Nemotron on OCI

NVIDIA Nemotron models (including Nemotron 3 Nano Omni multimodal) available through OCI Enterprise AI. NIM containers deployable on OCI GPU instances. Model Import capability for custom NIM deployment.

◆ Gap Analysis

OCI Enterprise AI (GA March 2026) is Oracle's unified agentic platform. The capabilities are comprehensive: OpenAI Responses-compatible API, managed agent hosting for OSS frameworks and MCP servers, vector stores, semantic search, NL2SQL, guardrails, observability, and auditability. The OpenAI API compatibility is strategically important: it reduces migration friction from OpenAI's platform and positions OCI as a drop-in alternative. The model catalog includes xAI Grok (4.1 Fast, 4.3), Cohere Command A (Vision, Reasoning), NVIDIA Nemotron 3 Nano Omni, and custom models through Model Import. The notable absence: no Anthropic Claude and no Meta Llama in published model availability. This is a narrower model selection than AWS Bedrock or Google's Model Garden. The agentic runtime distinguishes between three patterns: (1) OCI Generative AI APIs for direct model access, (2) Enterprise AI agents with managed orchestration, tools, memory, and retrieval, and (3) Applications and Deployments for container-based hosted agentic applications with custom runtimes. This three-tier model parallels AWS's Bedrock / AgentCore / SageMaker hierarchy. Dedicated AI clusters provide isolated compute for enterprise workloads: the opposite of shared-tenant model serving. This addresses a specific enterprise concern: inference latency predictability and data isolation. The trade-off is cost: dedicated clusters have fixed cost regardless of utilization. The Fusion Agentic Applications (22 agents across HR, finance, supply chain, CX; GA March 2026) represent Layer 2B and Layer 3 simultaneously: the runtime executes agents that are pre-built for Oracle's application estate. No other hyperscaler ships pre-built enterprise application agents at this scale.

◆ Borrowed Judgment

Model providers (xAI, Cohere, NVIDIA) bring training data, alignment, and safety decisions as borrowed judgment. Oracle's guardrails constrain output but reasoning in model weights is not customer-configurable: same pattern as every other hyperscaler. The Fusion Agentic Applications introduce a unique borrowed judgment dynamic: these agents execute decisions within business processes by accessing unified enterprise data, workflows, policies, approval hierarchies, and permissions. The enterprise inherits Oracle's judgment about how HR, finance, and supply chain processes should be automated. This is not model-level borrowed judgment. It's business-process-level borrowed judgment. When a Fusion Agentic Application automates a talent review or maintenance troubleshooting, the enterprise inherits Oracle's encoding of what 'good' process execution looks like.

◆ Working Notes

The Private Agent Factory pattern (Oracle AI Database 26ai) is architecturally significant: agents run inside the database, with direct access to enterprise data without external API calls. This eliminates the retrieval latency that plagues cloud-native RAG architectures but creates total database dependency for the agent runtime. OCI Enterprise AI's MCP support and OSS framework hosting (container-based deployment with managed infrastructure, networking, storage, and identity) position Oracle to benefit from the open agentic ecosystem without building a proprietary framework. This is a pragmatic strategy: let the frameworks proliferate, provide the managed hosting. The IBM partnership (watsonx Orchestrate agents on Red Hat OpenShift on OCI, IBM Granite models via OCI Data Science) adds an enterprise-focused model and agent ecosystem that differentiates from the consumer-AI-focused model catalogs of AWS and Google. Out of the Model Serving via OpenAI-Compatible APIs chip under the GA evidence table (October 24, 2026): xAI Grok 4.1 Fast ("This model was deprecated on May 15, 2026 , and retires on August 15, 2026 . After retirement, you no longer have access to this model.").

Layer 2C · ReasoningAgentic Infrastructure — The Reasoning PlaneIntelligence 2C: Emerging | Infra 2C: Implicitdecides: vendor · Delegated▼

Policy-driven placement and resource coordination — the Autonomy Layer

Vendor-Provided

OCI Enterprise AI GovernanceCeded

IAM-based access control for AI resources. Guardrails for content safety and policy enforcement. Observability for agent behavior, tool usage, and data flow monitoring. Auditability with audit logs capturing all AI interactions. Sovereign AI options. Project-level isolation for agent workloads.

Autonomous Database Self-ManagementCeded

Self-managing, self-securing, self-repairing database operations. Auto-indexing, auto-tuning, anomaly detection, autonomous performance optimization. Infrastructure 2C at the database layer: autonomous placement and resource decisions within the database boundary.

NVIDIA-Provided

No NVIDIA Layer 2C Dependency

All Layer 2C components are Oracle IP. NVIDIA does not control governance, policy, or reasoning in the OCI stack.

◆ Gap Analysis

Intelligence Layer 2C (partially present): OCI Enterprise AI governance includes IAM-based access control, guardrails for content safety, observability for agent behavior monitoring, and auditability for compliance. Oracle's blog series on runtime governance (April–May 2026) articulates sophisticated 2C concepts: runtime budget guardrails, approval-aware execution, pre-execution veto, safe degradation, evidence-backed runtime control, and the WORM Evidence Vault for audit-grade trace preservation. But there is a gap between the conceptual architecture Oracle's engineering team has published and the productized capabilities in OCI Enterprise AI GA. The runtime governance blog describes a governed execution layer with budget guardrails, circuit breakers, and safe-mode execution. The GA product offers IAM, guardrails, and observability: necessary but not sufficient for the full 2C vision Oracle's own engineers have articulated. Infrastructure Layer 2C (not built): No OCI service answers 'given data residency, cost, latency, GPU availability across NVIDIA and AMD, and compliance requirements, should this workload run on dedicated clusters in us-ashburn-1 or on Dedicated Region infrastructure in Frankfurt?' The capacity management primitives exist. The policy-driven placement engine does not. The Autonomous AI Database is the closest OCI comes to Infrastructure 2C: it self-manages, self-secures, auto-indexes, auto-tunes, and detects anomalies autonomously. But this autonomy operates at the database layer, not at the infrastructure-wide placement layer that the 4+1 model defines. OCI's unique 2C opportunity: Oracle is the only hyperscaler with both the application layer (Fusion) and the data layer (AI Database) under one authority. A Layer 2C that queries Fusion application state, database governance metadata, GPU utilization, and compliance posture to make autonomous placement decisions would have richer context than any other hyperscaler's 2C, because Oracle sees from application logic through data governance to infrastructure. The data to build 2C exists. The product does not. Read across the instrument by shape rather than by roster. Three positions exist at 2C. One cohort ships nothing and the enterprise owns the function by default. A second and now larger cohort ships productized Intelligence-2C (agent identity, gateways, registries, runtime policy enforcement, audit), and reads moderate or strong on it, with authority Ceded to whoever built the control plane. Nobody ships Infrastructure-2C as a configurable product. Naming which vendor sits where is what the heat map is for; repeating it inside a cell only guarantees the cell goes stale the next time a peer moves. OCI's position within that second cohort is early. Guardrails, observability, and auditability ship; the conceptual vision is published and the product is not yet built out behind it. Infrastructure-2C is implicit, made inside managed services rather than exposed as a control.

◆ Borrowed Judgment

Intelligence 2C: Low: guardrails, observability, and auditability are Oracle IP. Customer defines IAM policies; Oracle enforces. Infrastructure 2C: Ceded (implicit): the Autonomous AI Database makes placement, scaling, and optimization decisions autonomously. These are 2C functions at the database layer that the enterprise has Ceded without explicit classification. The parallel to AWS's implicit 2C (managed service decisions) applies, but OCI's implicit 2C is concentrated in the database rather than spread across managed services.

◆ Working Notes

Oracle's engineering blog series on runtime governance for agentic AI (April–May 2026) is the most sophisticated published thinking on Layer 2C from any hyperscaler's engineering team. The concepts (runtime budget guardrails as governed execution, evidence-backed observability with WORM vaults, approval-aware execution with pre-execution veto) map directly to what the 4+1 model defines as Intelligence Layer 2C. These capabilities are not yet shipping as GA products, but the engineering direction signals that Oracle understands the 2C problem and is building toward it. The question is execution velocity: can Oracle productize these concepts faster than AWS (which already has AgentCore Policy GA) or Google (which already has Agent Identity + Gateway + Registry GA)? Oracle's published vision is ahead of its shipped product: a familiar pattern for Oracle, which historically leads with database innovation and follows with cloud operationalization. The Fusion Agentic Applications contain implicit 2C: these agents make and execute decisions within business processes by accessing policies, approval hierarchies, and permissions. The agent governance is embedded in the application logic, not exposed as a configurable control plane. This is 2C, but it's Ceded 2C, where Oracle defines the governance model and the enterprise consumes it. Instrument note: live Infrastructure-2C (a policy engine deciding at request time where inference runs relative to the data, which model serves the request, and how cost, latency, and compliance are arbitrated) does not ship from any vendor on this instrument. It is recorded here as a universal finding about the market, not as a charge against this vendor. The sibling finding applies here as well: you cannot prompt your way to deterministic output. The controls credited in this cell answer whether an action is legal (permissions, schema and policy checks, rate and token limits, approval gates), and none of them validates whether the outcome was right under a graduated escalation policy. Controls that work by instructing the model shift the output distribution without pinning it. That deterministic outcome-validator is missing instrument-wide, and like live placement it is noted as universal rather than charged to one vendor.

Layer 3 (+1) · ApplicationsAI Application Layer — The Value PlaneStrongest Application-Layer Authoritydecides: model · Delegated▼

AI-powered business capabilities — business logic, workflow automation

Vendor-Provided

Oracle Fusion Agentic ApplicationsCeded

22 specialized AI agents across HR, Finance, Supply Chain, and CX (GA March 2026). Outcome-driven, proactive, reasoning-based. Execute decisions within business processes by accessing unified enterprise data, workflows, policies, approval hierarchies, permissions, and transactional context. Built into Oracle Fusion Cloud Applications.

ISV + Model EcosystemDelegated

xAI Grok, Cohere Command A, NVIDIA Nemotron, IBM Granite models. IBM watsonx Orchestrate agents on Red Hat OpenShift on OCI. SoftBank sovereign cloud with custom AI models on OCI. Oracle Analytics with AI-powered assistants. Not scored within this chip under the GA evidence table: IBM Granite (not on either OCI model list); watsonx Orchestrate on OCI and the Oracle Analytics assistant (no owner quote captured); SoftBank (a customer deployment, not an OCI offering).

NVIDIA-Provided

NVIDIA NIM + Nemotron Models

NVIDIA models via OCI Enterprise AI alongside xAI, Cohere, and customer models.

◆ Gap Analysis

Layer 3 is OCI's most distinctive position in the assessment series. Oracle is the ONLY vendor that owns a comprehensive enterprise application suite AND the AI infrastructure to power it. AWS provides infrastructure and some first-party applications (Q, Connect). Google provides infrastructure and productivity applications (Workspace). Neither owns ERP, HCM, SCM, or CX at Oracle's scale. Fusion Agentic Applications (22 agents, GA March 2026) demonstrate what happens when the application vendor controls the AI infrastructure: agents that can access unified enterprise data, workflows, policies, approval hierarchies, permissions, and transactional context, without integration middleware, without API gateways, without cross-vendor authentication. This is not an ISV ecosystem (Dell's model) or a curated partner program (HPE's Unleash AI). This is first-party AI applications running on first-party infrastructure accessing first-party enterprise data. Specific agent domains: workforce scheduling, payroll issue resolution (HR), financial process automation (Finance), supply chain optimization (SCM), and customer experience enhancement (CX). Each agent is pre-trained on Oracle's understanding of enterprise processes: borrowed judgment at the business logic layer. The Oracle AI Data Platform for US Federal Government bundles OCI, Autonomous AI Database, and Enterprise AI with FedRAMP High and DISA IL4/IL5 authorization, extending Layer 3 into classified and sovereignty-constrained environments. The US Department of War agreement (May 2026) for AI on classified networks across 10 cloud regions at DISA IL2 through Top Secret demonstrates sovereign Layer 3 that no other hyperscaler matches in classification depth with equivalent application-layer integration. Custom agent development uses the OCI Responses API (OpenAI-compatible) with managed hosting for OSS frameworks and MCP servers: the same runtime surface described at Layer 2B, consumed here as an application development platform. The IBM partnership adds watsonx Orchestrate agents on OCI for HR use cases, extending the agentic ecosystem beyond Oracle's own applications. IBM Granite models via OCI Data Science provide additional model options. The SoftBank sovereign cloud platform on OCI (May 2026) demonstrates Layer 3 for sovereign AI: SoftBank's own generative AI models running on OCI Enterprise AI with full data control within Japanese data centers. The DAPM question: Fusion Agentic Applications are the deepest expression of Ceded authority in this assessment. The enterprise Cedes business logic, process automation, and decision-making to agents that Oracle built, Oracle trained, and Oracle hosts. The efficiency gains are real. The authority concentration is total.

◆ Borrowed Judgment

The highest borrowed judgment of any Layer 3 in this assessment. Fusion Agentic Applications encode Oracle's interpretation of enterprise processes: what constitutes a complete talent review, how maintenance troubleshooting should proceed, when payroll exceptions should escalate. The enterprise inherits decades of Oracle's process design as embedded agent behavior. Model providers (xAI, Cohere, NVIDIA) add model-level borrowed judgment. Oracle's application logic adds process-level borrowed judgment. The combination is unique: no other vendor in this assessment embeds both model judgment AND business process judgment into a single managed AI application layer. DAPM Action 3 applies with maximum force: when you move off Oracle, what judgment doesn't move with you? Answer: the process logic, the data governance, the application state, the agent memory, and the transactional context: essentially everything above Layer 0. Decision authority (October 5, 2026): Fusion's AI agents carry the grade. AI Agent Studio documents an approval step before actions such as sending an email or updating a record, and shows the actions an agent took. Model decides, visible, overridable, Delegated; whether the prebuilt agents ship with the step on by default isn't documented.

◆ Working Notes

The Oracle AI Data Platform for US Federal Government (March 2026) combines OCI, Autonomous AI Database, and Enterprise AI into a unified offering for government agencies with FedRAMP High and DISA IL5 authorization. This is Layer 3 for regulated environments: AI agents operating within classified and sovereignty-constrained boundaries. The US Department of War agreement (May 2026) for advanced AI capabilities on classified networks, leveraging 10 cloud regions at DISA IL2 through Top Secret and Special Access Program levels, demonstrates sovereign Layer 3 that no other hyperscaler matches in classification depth with equivalent application-layer integration. The 531% growth in multicloud database revenues suggests enterprises are increasingly running Oracle's data layer inside other hyperscalers, creating a cross-cloud data authority that could enable cross-cloud Layer 3 applications. Oracle's vision may be: own the data and application layers, be agnostic about the infrastructure layer. This is the inverse of AWS's strategy (own the infrastructure, be agnostic about the application layer). Out of the ISV + Model Ecosystem chip under the GA evidence table (October 24, 2026): IBM Granite (not on either OCI model list); watsonx Orchestrate on OCI and the Oracle Analytics assistant (no owner quote captured); SoftBank (a customer deployment, not an OCI offering).

Sources & revision history · v1.40 - 4+1 v3: Layer 0 Sub-Layers

Oracle AI World 2025, GTC 2026, OCI Enterprise AI GA (Mar 2026), Fusion Agentic Applications (Mar 2026), Oracle AI Database 26ai, Stargate/OpenAI partnership, NVIDIA/AMD partnerships, analyst coverage, Oracle Q3 FY2026 earnings. v1.3 (instrument reconciliation): 1A OCI Object Storage and 2A OKE Retained→Delegated: a managed service behind a multi-vendor standard interface is Delegated, not Retained. Also aligned the VAST Layer 2C cross-reference to VAST's current gap status. v1.4 (July 12, 2026, /reconcile): statusLabels moved to capability vocabulary per the instrument convention; no grades or chips changed. v1.5 (July 12, 2026, /ga-check): OCI Compute Management promoted from the watch-list on OCI product documentation (instance pools, cluster networks, capacity reservations), scored as a Ceded 2A component; status holds moderate. /reconcile (September 1, 2026): inference-interface rule applied as a scored facet. Model access consumed through a multi-vendor standard interface (OpenAI-compatible completions, Anthropic Messages) split out as Delegated; the platform surface beyond the interface stays Ceded. Matches the Azure v1.4 treatment. /reconcile (September 1, 2026): retired status vocabulary replaced with gap. /reconcile (September 1, 2026): shared 2C findings stated explicitly (live-placement universality, outcome-validation finding). /reconcile (September 1, 2026): the hard-coded cross-vendor 2C roster replaced with a shape-based reading. The roster had drifted out of agreement with the rows it described (HPE 2C scored three Ceded, not Retained plus Delegated) and went stale on every peer promotion. /reconcile (October 5, 2026): Layer 0 runtime rule (ruled September 28 and October 4, 2026). NVIDIA GPU fleet split: standard bare metal instances Ceded to Retained from the customer's seat, GB200 NVL72 Ceded on the integrated-system rule. Grade unchanged. /reconcile (October 5, 2026, same pass): the MI450 Helios fleet descored under the GA-gate (Q3 2026 deployment, no documented GA) and replaced by the GA MI355X instances, Retained from the customer's seat. /reconcile (October 5, 2026): 1C authority column (rulings of September 15 and October 4 and 5, 2026). 1C authority vendor / Ceded to code / Retained: GoldenGate DDL replication is set by parameters the enterprise writes (DDL INCLUDE MAPPED), and lag metrics are documented. Grade unchanged. /reconcile (October 5, 2026): authority visible set from the cell's own text where it settles it: layer2a true. Direction, grades, and components unchanged. /ga-check (October 5, 2026): Oracle AI Database 26ai engine confirmed GA in the paid tier across commercial regions (docs.oracle.com); watch item cleared. Grade unchanged. /reconcile (October 5, 2026): authority re-read against product docs under the judgment test, override rule, and Layer 3 ruling: layer1b to vendor / Delegated; layer3 to model / Delegated. Grades and components unchanged. /reconcile (October 5, 2026): Layer 2A moderate to strong (Keith, October 5, 2026): OKE, the Karpenter Provider for OCI (GA April 9, 2026), and instance pools and cluster networks meet the AWS, Google Cloud, and Azure 2A bar the cell calibrated against; the stale Compute Management watch note corrected (long GA). Authority unchanged. /reconcile (October 5, 2026): authority read against product docs: layer0 visible true; layer1b visible true. Grades and components unchanged. v1.17 (Layer 0 sub-layers, October 16, 2026): Layer 0 split into 0A Compute, 0B Network Fabric and 0C Storage Substrate by runtime decision (Keith, October 16, 2026); storage left 1A for 0C, and 1A, now Data Foundation & Governance, is graded on the catalog that classifies the data. 0A strong, 0B strong, 0C strong; summary edits (summary worksheet, Keith, October 16, 2026). v1.18 (October 19, 2026, /reconcile): plain-language pass: methodology rule numbers in the prose and audit notes replaced with the reasoning they stood for; no grade, chip or authority reading changed. v1.19 (October 19, 2026, /reconcile voice pass): em-dashes in the prose replaced with periods, colons, commas or parentheses; wording, grades, chips and authority readings unchanged. v1.20 (October 22, 2026, /reconcile): 0C Dedicated Region storage facet split into block and native-API object (Ceded) and File Storage, File Storage with Lustre and S3-compatible object (Delegated), from reconcile's peer calibration: the facet read Ceded only because it held both halves, while the same services read Delegated in OCI's regions. Grade and cell authority unchanged; the cell rests on File Storage with Lustre. v1.21 (October 22, 2026, /reconcile): the 0B calibration line cites GCP's RoCE GPU network in place of Virgo, which GCP v1.26 moved to a named, unscored note. Grade and authority unchanged. v1.22 (October 22, 2026, /reconcile): the 0A NVL-class chip cites Lenovo's NVL-class racks as its precedent in place of Dell's XE9812, which Dell v2.22 moved to a named, unscored note. Grade and authority unchanged. v1.23 (October 23, 2026, /reconcile): 0A follows OCI's compute shapes doc. BM.GPU.RTXPRO.8 joins the NVIDIA chip, BM.GPU.GB300.4 joins the Grace Blackwell chip, and BM.GPU.MI300X.8 joins the AMD chip. Zettascale10 (announced for the second half of 2026, no documentation) moves to a named, unscored note. The Stargate and "1M+ GPUs" claims come out as market-position claims, and BlueField-4 (a GTC announcement) goes to notes. The NVL72 framing is flagged: the shapes doc doesn't describe the rack, and oracle.com, where it may be, refuses access. Found by the 0A compute research. Grade and authority unchanged. v1.24 (October 23, 2026, /reconcile): the 0A confidence flag records what oracle.com now shows: the Supercluster scale and Dedicated Region's three-rack start are documented on Oracle's product pages, and the NVL72 rack framing still rests on an announcement. Grade and authority unchanged. v1.25 (October 23, 2026, /reconcile): Layer 1 research pass. 1C: rewritten (the chip described the ML platform; the 1C function is the pipelines). 1C: "Multicloud Database Connectivity" removed (private interconnect between clouds is network connectivity, not query federation). Found by the Layer 1 slot cut. Grade and cell authority unchanged. v1.26 (October 23, 2026, storage door pass): The S3 Compatibility API, NFS, the Lustre client and the Dedicated Region's front ends are doors; the managed services read Ceded. Grade unchanged. v1.27 (October 23, 2026, Layer 1 managed-services pass): OCI Generative AI embeddings are served through OCI's native API, not the OpenAI-compatible endpoint. Grade unchanged. v1.28 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 1B chips under the GA evidence table. Grade unchanged. v1.29 (October 24, 2026, /reconcile): Layer 1B GA evidence migrated to the GA evidence table version 2. Grade unchanged. v1.30 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 1A chips under the GA evidence table version 2. Grade unchanged. v1.31 (October 24, 2026, /reconcile): GA evidence recorded on 3 of 3 Layer 1C chips under the GA evidence table version 2. Grade unchanged. v1.32 (October 24, 2026, /reconcile): GA evidence recorded on 5 of 5 Layer 0B chips under the GA evidence table version 2. Grade unchanged. v1.33 (October 24, 2026, /reconcile): GA evidence recorded on 6 of 6 Layer 0A chips under the GA evidence table version 2. Grade unchanged. v1.34 (October 24, 2026, /reconcile): GA evidence recorded on 10 of 10 Layer 0C chips under the GA evidence table version 2. Grade unchanged. v1.35 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 3 Layer 2A chips under the GA evidence table version 2. Grade unchanged. v1.36 (October 24, 2026, /reconcile): GA evidence recorded on 5 of 6 Layer 2B chips under the GA evidence table version 2. Grade unchanged. v1.37 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 2 Layer 3 chips under the GA evidence table version 2. Grade unchanged. v1.38 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 2 Layer 2C chips under the GA evidence table version 2. Grade unchanged. v1.39 (October 24, 2026, /reconcile): GA evidence table version 2.1 applied: 2 chips recorded or narrowed, 1 to notes. Grade unchanged. v1.40 (October 27, 2026): each component now carries a durable offering id; nothing else changed.

4+1 Layer AI Infrastructure Model · Vendor Assessment Series · The CTO Advisor LLC (DBA The Advisor Bench) · thectoadvisor.com