Exadata Cloud vs AWS Outposts is the on-premise comparison where Oracle's licensing rules quietly punish the AWS option — and where Exadata Cloud@Customer wins almost every time on 5-year TCO.

What ExaCC and AWS Outposts actually are

Exadata Cloud@Customer (ExaCC) is Oracle-owned Exadata X10M (or earlier-generation) hardware shipped to and installed inside the customer's own datacentre. Oracle retains ownership, performs all hardware maintenance, applies all patches, and operates it as a managed cloud service. The customer's data and database licences sit inside the customer's premises. Billing is by the OCPU-hour drawn down against OCI Universal Credits. Support Rewards apply (25 percent of qualifying spend converts to Oracle support credits; 33 percent for ULA customers).

AWS Outposts is AWS-owned rack hardware installed inside the customer's datacentre, presented as an extension of an AWS Region. Three relevant patterns exist for Oracle Database:

• Amazon RDS for Oracle on Outposts. AWS manages the database service; the customer brings Oracle Database licences under BYOL with conventional Standard Edition 2 or Enterprise Edition licensing rules applied to the underlying physical cores.
• Oracle Database EE BYOL on EC2-on-Outposts. The customer provisions EC2 instances on Outposts dedicated hosts and installs Oracle Database EE themselves. Same on-premise licensing rules apply.
• Oracle Database SE2 BYOL on EC2-on-Outposts. Standard Edition 2 with its 2-socket limit and 10-licence-per-server cap applies.

AWS Outposts is not on Oracle's Authorised Cloud Environment list (which currently covers only AWS public regions, Azure public regions, and select Alibaba regions). The licensing implications of that absence are the single most important fact in this comparison.

Oracle Database licensing on each platform

ExaCC licensing. Exadata Cloud@Customer inherits the OCI Authorised Cloud Environment rules. BYOL Oracle Database EE licences convert at 2 vCPUs per Processor metric (for Linux x86 platforms with hyperthreading enabled). The Core Factor Table is not applied — the 2:1 conversion replaces it. The customer can scale OCPUs up and down at will; only running OCPUs count toward licence consumption. ExaCC also offers a "Database As A Service" licensing model where Oracle Database EE licences are included in the OCPU-hour rate (no BYOL required) — useful for customers without sufficient existing licences.

AWS Outposts licensing. Outposts inherits the on-premise rules. For Oracle Database EE on EC2-on-Outposts:

• The Outposts dedicated host is a physical server. Every populated core counts.
• The Core Factor Table applies (typically 0.5 for x86 with Intel or AMD modern CPUs, so 2 cores = 1 Processor licence).
• Hard partitioning is allowed only through Oracle-approved technologies (e.g. capped Solaris Zones, IBM LPAR). VMware vSphere, KVM, and the Nitro hypervisor underneath EC2 are treated as soft partitioning — meaning the whole physical host must be licensed if any one VM on it runs Oracle Database EE.
• EC2 on Outposts dedicated hosts can be configured to expose physical-host topology to Oracle LMS, but this does not change the on-premise rule set. There is no 2:1 multiplier on Outposts.

The structural consequence: a 48-core Outposts rack running Oracle Database EE costs 24 Processor licences. The same workload on ExaCC running with 24 OCPUs costs 12 Processor licences (24 vCPUs at 2:1). On a $47,500-per-Processor licence at typical discount, that is the difference between $570K and $1.14M in net new licence purchase — before any annual support.

Commercial models compared

The Support Rewards differential alone moves the answer for most customers. A $400K annual OCPU spend on ExaCC generates $100K of Oracle support credits per year. That credit reduces annual Oracle support bills directly. Outposts generates zero support credits.

Oracle support entitlement and back-licence risk

Oracle's support and licensing terms for ExaCC are written into the OCI Subscription Agreement and the Oracle Master Agreement (OMA). The support is unified: hardware, OS, Exadata software, and Oracle Database all sit under one Oracle support entitlement. There is no support-coverage gap.

For Oracle Database on Outposts, the customer holds Oracle Database licences and Oracle support contracts independent of the AWS hardware. Oracle's support response covers the database tier. AWS Enterprise Support covers the Outposts hardware. Where the gap shows up:

• Oracle LMS will treat the Outposts deployment as an on-premise installation for compliance purposes. Customers have been challenged on the licensing of cores activated for non-Oracle workloads on the same physical Outposts hosts where Oracle is also running. Back-licence claims for the full host are not uncommon.
• RDS for Oracle on Outposts is BYOL only, and Oracle's official position on RDS BYOL outside ACE regions has historically been narrow. We have seen LMS challenge whether RDS-on-Outposts deployments qualify for the conventional RDS for Oracle BYOL pricing model.

Our forensic position with new clients running Oracle on Outposts is to assume worst-case full-host licensing for every Outposts host with any Oracle process and then negotiate down with LMS using documented hardware topology and approved hard-partitioning technology. The defence works, but the audit exposure is real where the deployment was not designed with Oracle's playbook in mind.

Performance and operational model

ExaCC delivers Exadata-class performance: Smart Scan offload to storage cells, Hybrid Columnar Compression, RDMA over RoCE between database servers and storage cells, persistent memory acceleration. For high-throughput OLTP and mixed-workload Oracle Database, the platform is the reference design for Oracle's own benchmarks. The X10M generation pushes 27 million OLTP IOPS per rack and sub-100µs read latency.

AWS Outposts with EC2 i4i or similar instances running Oracle Database EE delivers good but unremarkable performance for Oracle workloads. The Nitro hypervisor adds a measurable but small latency overhead. NVMe-based storage with EBS-equivalent IOPS is competitive for moderate OLTP. For Exadata-class workloads (data warehouse with Smart Scan, large Hybrid Columnar Compression scans, sub-millisecond OLTP at scale), Outposts cannot match ExaCC because the storage offload and Smart Scan are Exadata-exclusive features.

Operationally: ExaCC is fully Oracle-managed (Oracle applies CPU patches, GI patches, Exadata software updates, with customer-controlled maintenance windows). Outposts deployments are customer-managed for the Oracle Database layer (the customer or a managed service provider applies all database patches). The operational labour delta is meaningful — typically 0.5 to 1.0 FTE per significant Oracle estate.

Worked TCO example: 48-core Oracle DB EE estate

Scenario: A regulated financial services organisation has a 48-core (96-vCPU) Oracle Database EE estate with Partitioning, Advanced Compression, Multitenant, Advanced Security, Diagnostics, and Tuning. Data residency requires the database stay inside the customer's primary datacentre. Annual Oracle support today (on-premise legacy hardware): $580K. Five-year TCO across the two platforms.

The $2.05M five-year TCO gap is structurally driven by three differentials: the Oracle licensing rule asymmetry (2:1 multiplier on ExaCC absent on Outposts), the Support Rewards offset on OCI spend, and the operational labour saving from the Oracle-managed model. The Outposts hardware cost saving (no rack fee on ExaCC versus a 3-year Outposts reservation) is real but materially smaller than the licensing and support deltas.

The picture changes only at the margin. Scenarios where Outposts wins: very small Oracle Database SE2 footprints (no 2:1 advantage to chase), or workloads where AWS-native integration (S3, Glue, Kinesis on Outposts) is operationally critical and the database licensing is already paid.

Audit exposure on each platform

ExaCC audit exposure is low because the platform is Oracle-operated and Oracle has full visibility into deployed OCPUs through the OCI control plane. There is essentially nowhere to hide unlicensed cores; conversely, there is essentially no surprise back-licence claim because the metering is Oracle's own.

Outposts audit exposure is elevated. The patterns we defend most often:

• Hyperthreading on dedicated hosts. Oracle's position is that hyperthreaded logical CPUs do not reduce the physical-core licence count. Customers occasionally configure Outposts EC2 instance types where the published vCPU count looks lower than the physical cores; LMS will demand physical-core licensing regardless.
• VMware vSphere on Outposts (VMware-on-Outposts). Triggers full-cluster soft-partitioning rule. Customers who put Oracle Database on a single VM inside a vSphere cluster on Outposts have been hit with back-licence claims covering every host in the cluster.
• RDS-on-Outposts BYOL coverage scope. Oracle has challenged whether RDS-on-Outposts deployments fall under the RDS Authorised Cloud Environment rules. The position is unsettled.
• Stretched clusters across Outposts and AWS Region. Movement of Oracle workloads between Outposts and a paired Region triggers full licensing of every host the workload ever touched in a 6-month window unless documented carefully.

The forensic defensible position on Outposts is to dedicate specific Outposts hosts exclusively to Oracle Database EE, document the hardware topology meticulously, never co-locate Oracle with hyperthreaded soft-partitioned workloads, and treat every host as fully licensed even when subdivided. We cover the broader audit pattern in our piece on Oracle audit risk at hyperscalers.

Buyer-side negotiation moves

1. Get the ExaCC quote first, then walk it into the AWS conversation. Oracle's ExaCC pricing for a like-for-like configuration is the floor. AWS will discount Outposts and EC2-on-Outposts reservations to keep the workload in their estate. The Outposts discount typically lands at 20 to 35 percent for committed multi-year deployments where Oracle is also on the table.
2. Force Oracle to quote Database-as-a-Service ExaCC and BYOL ExaCC side by side. The Database-as-a-Service pricing (licence included) is sometimes more attractive than BYOL ExaCC when the customer has limited existing Oracle EE licences. Oracle's account team will reflexively quote BYOL because it preserves Oracle's licence revenue base — push for both options.
3. Quote a credible exit to OCI public regions in the ExaCC negotiation. ExaCC pricing softens when Oracle believes the alternative is OCI public Exadata Cloud Service rather than retention on legacy on-premise hardware.
4. Never accept a multi-year ExaCC commit without a Support Rewards uplift commitment. Get the Support Rewards mechanic written into the order form, not just referenced from the standard documentation. The 33 percent rate (for ULA customers) should be explicit if it applies.

Where each platform fits

Exadata Cloud@Customer is the right answer when:

• Oracle Database EE is the dominant workload and the database must stay on-premise.
• The customer has an existing pool of Oracle Database EE licences and wants to deploy them under the 2:1 multiplier.
• Oracle support is currently a six- or seven-figure annual cost where Support Rewards offset is meaningful.
• Operational labour saving from Oracle-managed Exadata is valued.
• The workload benefits from Exadata-specific features (Smart Scan, Hybrid Columnar Compression, RoCE storage fabric).

AWS Outposts is the right answer when:

• The Oracle Database is a small component of a larger AWS-native estate already running on Outposts.
• The database is Oracle Database SE2 or a small EE deployment where the licensing differential is modest.
• Operational integration with AWS services (S3 on Outposts, Glue catalog, Lambda) is critical.
• The customer has decided strategically against deeper Oracle commercial engagement and is willing to absorb the licensing premium.

For most enterprise Oracle estates that must remain on-premise, ExaCC wins. We have not encountered a case where Outposts won the 5-year TCO comparison for an Oracle Database EE-dominant workload at scale.

FAQ — Exadata Cloud@Customer vs AWS Outposts

What is Exadata Cloud@Customer?

Exadata Cloud@Customer (ExaCC) is Oracle-owned Exadata hardware installed inside the customer's own datacentre, operated as a managed cloud service by Oracle, and billed by the OCPU-hour against OCI Universal Credits. The customer's data and database licences stay inside the customer's premises; Oracle ships, owns, and maintains the hardware. ExaCC is licensed under the same OCI BYOL and Authorised Cloud Environment rules as Exadata Cloud Service public, including the 2:1 vCPU-to-Processor multiplier.

Is AWS Outposts certified for Oracle Database?

AWS Outposts is not on Oracle's Authorised Cloud Environment list. Running Oracle Database Enterprise Edition on AWS Outposts triggers the on-premise licensing rules: hard-partitioning where supported, full-host counting where not. AWS RDS for Oracle on Outposts is supported with BYOL but the underlying compute counts on the same physical-server basis as a private datacentre. Outposts does not enjoy the 2:1 multiplier that applies to AWS public regions.

Which is cheaper, ExaCC or Oracle on Outposts?

For Oracle Database Enterprise Edition workloads kept on-premise, ExaCC almost always wins on 5-year TCO. ExaCC gets the OCI 2:1 multiplier, Support Rewards eligibility, and managed-service operational savings, while Outposts is licensed on a physical-server basis with no Oracle commercial concessions. The Outposts hardware itself is cheaper in raw infrastructure, but the Oracle licence count is materially higher, and the gap usually exceeds the infrastructure saving.

Can we run Oracle Database EE on AWS Outposts without a back-licence claim risk?

Yes, but only with a clean LMS-defensible architecture: physically dedicated hosts (no over-subscription), formally hard-partitioned where the technology allows, and full processor licences for every populated core. Any use of VMware vSphere or any soft-partitioning technology on Outposts triggers full-cluster counting. We have defended several Outposts deployments in audit and the boundary is narrower than the AWS solution architects typically present.

Does ExaCC count toward an Oracle ULA?

Yes. ExaCC deployments count toward the ULA-certified processor count at exit. For organisations approaching ULA exit, ExaCC is often the lowest-risk landing platform for the existing Oracle estate because the OCPU-to-Processor conversion is unambiguous and Oracle-controlled.

Can we use Database@Azure or Database@Google Cloud instead of ExaCC?

Database@Azure and Database@Google Cloud are public-cloud offerings — the Oracle hardware physically sits inside Microsoft or Google datacentres respectively, not the customer's. For data residency or sovereignty workloads that require the database stay inside the customer's own facility, ExaCC remains the only Oracle-managed option. We compare these head-to-head in our piece on ExaCC vs Database@Azure.

Independence statement: Oracle Licensing Experts is an independent buyer-side advisory firm. Not affiliated with Oracle Corporation. We have no commercial relationship with AWS. All numbers above reflect published list pricing and benchmark enterprise negotiated rates as observed in buyer-side engagements.

Related guides