Editorial photograph of a database team reviewing Oracle Autonomous Database consumption metrics on a wall sized dashboard
Article · Oracle · Database

Oracle Autonomous Database licensing. The metric, the math, the levers.

Autonomous Database moved Oracle from processor licensing to consumption. The ECPU metric, the BYOL discount, the storage band, and the four buyer side levers that protect the contract from a quiet OCI consumption ramp.

Read the Framework Oracle Hub
40 to 60%BYOL discount versus license included
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Oracle Autonomous Database runs in three deployment shapes inside OCI. Autonomous Data Warehouse for analytics. Autonomous Transaction Processing for OLTP. Dedicated for isolated infrastructure. Each shape consumes ECPUs and storage on an elastic, per second basis.

The licensing model is consumption not perpetual. The buyer side question is no longer how many processor licenses to size. The question is how many ECPU hours the workload will burn, whether to bring existing Oracle Database licenses across as BYOL, and what discount applies on a multi year OCI commit.

Read this alongside the Oracle knowledge hub, the Oracle services page, the Oracle Cloud services page, and the Vendor Shield subscription.

Key Takeaways

What a CIO and procurement leader need to know in 90 seconds

  • Three deployment shapes. ADW for analytics, ATP for OLTP, and Dedicated for isolated infrastructure on Exadata.
  • ECPU is the active metric. Oracle moved off OCPU on shared infrastructure in 2023.
  • BYOL cuts the headline rate by forty to sixty percent. Existing Database EE plus options licenses transfer.
  • Storage bills separately. At a published rate per terabyte per month with backup and exadata storage tiers.
  • Auto scaling caps at three times the base ECPU. The cap is a buyer side leverage point.
  • Dedicated shape requires a quarter rack minimum. The math only works above 32 ECPU sustained.
  • Discount stacks on OCI Universal Credit commits. Plus the Database BYOL discount on top.

Service tiers and deployment shapes

Autonomous Database lives in three shapes. The tier choice drives both the unit rate and the negotiation surface.

Three deployment shapes

ShapeWorkload fitInfrastructureMinimum sizeUse case
ADW sharedAnalytics, BI, reportingMultitenant Exadata2 ECPUDepartmental analytics warehouse
ATP sharedOLTP, microservicesMultitenant Exadata2 ECPUTransactional workload on shared estate
ADB DedicatedMixed analytics and OLTPDedicated Exadata Cloud Service32 ECPU quarter rackIsolated workload, regulated data
ADB on Cloud at CustomerData residency requiredExadata rack in customer DCQuarter rackBanking, government, defense

When each shape fits

  • ADW shared. Sub fifty ECPU steady state on analytics workload with predictable concurrency.
  • ATP shared. Microservices and SaaS application back ends below five hundred ECPU peak.
  • Dedicated. Sustained workload above three hundred ECPU plus isolation or regulatory requirements.
  • Cloud at Customer. Data residency mandates that block public OCI regions.

The metric and the pricing

Oracle moved Autonomous Database from OCPU to ECPU on shared infrastructure in 2023. The ECPU is a virtual CPU billed on a per second basis. Dedicated still uses OCPU for the underlying Exadata infrastructure.

Published rates 2026

ServiceLicense included rateBYOL rateStorage rateAuto scale cap
ADW shared$1.34 per ECPU hour$0.336 per ECPU hour$118 per TB per month3x base ECPU
ATP shared$1.34 per ECPU hour$0.336 per ECPU hour$118 per TB per month3x base ECPU
ADB DedicatedOCPU based, includes RACBYOL OCPU rate plus infraIncluded to a capCluster sizing

OCPU to ECPU conversion

The official Oracle conversion runs one OCPU to roughly eight ECPUs. The math is workload dependent. CPU bound analytics convert closer to one to six. IO bound transactional workloads convert closer to one to ten.

BYOL economics

Bring Your Own License lets the customer apply existing perpetual Database licenses against the Autonomous service. The rate drops by roughly seventy five percent versus license included.

BYOL eligibility rules

  • Database EE perpetual license. Plus current support contract in good standing.
  • Database options included. Partitioning, Advanced Compression, Advanced Security, RAC, Active Data Guard.
  • One processor license maps to four ECPU on shared. The conversion is published in the OCI services description.
  • BYOL audit risk applies. The customer must hold sufficient licenses for the peak ECPU consumed.

BYOL math on a typical estate

A 200 ECPU steady state ADW workload runs roughly $19,500 per month on BYOL versus $78,000 per month on license included. The annual delta is around $700K. The customer must hold 50 processor licenses of Database EE to cover the peak.

BYOL is not free

BYOL still requires the customer to carry support on the underlying perpetual licenses. Annual support runs twenty two percent of net license fee. The breakeven against license included sits around forty percent ECPU utilization across a year on a typical estate.

Buyer side negotiation levers

Autonomous Database lands inside an OCI Universal Credit commit on most enterprise estates. The Universal Credit envelope is the primary negotiation surface.

Four levers that work

  1. OCI Universal Credit discount tier. Discounts stack from fifteen percent on one million dollar commits to forty five percent above ten million dollars.
  2. Autonomous Database service credit. A line item discount on top of the Universal Credit discount, typically ten to twenty percent.
  3. Storage cap. Negotiate a fixed storage allowance per ECPU to contain the storage line.
  4. Auto scale cap reset. Negotiate a contractual cap below the default three times multiplier on cost runaway risk workloads.

Three traps to avoid

  • License included by default. If BYOL is not specified at provisioning, the service runs at the license included rate.
  • Storage drift. Backup retention defaults stretch storage costs past compute on long running workloads.
  • OCPU and ECPU mismatch. The Dedicated shape still uses OCPU and bills the underlying Exadata infrastructure separately.

Autonomous Database licensing is not about how many processors you own. It is about ECPU consumption, BYOL eligibility, the storage cap, and the Universal Credit discount tier. Get all four lined up before the OCI order form is signed.

What to do next

The seven step checklist is the buyer side starting position before any Autonomous Database commitment lands in procurement.

  1. Baseline current Database EE estate. Count processor licenses, options, and support contracts.
  2. Size the workload in ECPU. Use the OCPU to ECPU conversion ratio appropriate to the workload pattern.
  3. Decide BYOL or license included. Run the breakeven against expected utilization across twelve months.
  4. Negotiate the Universal Credit discount tier. Stack the Autonomous service credit on top.
  5. Cap storage and auto scaling. In writing in the order document.
  6. Provision with BYOL flagged. The default at provisioning is license included.
  7. Monitor ECPU and storage monthly. Drift catches every estate that runs without active FinOps.

Frequently asked questions

What is the difference between OCPU and ECPU?

OCPU is the original Oracle Cloud Processing Unit, equivalent to one physical core with hyperthreading. ECPU is the Elastic CPU, a virtual CPU that bills per second on shared infrastructure. Oracle moved Autonomous Database shared services to ECPU in 2023.

Does BYOL cover all Database options?

BYOL covers Database EE plus the options the customer holds on the perpetual licenses. Partitioning, RAC, Advanced Compression, Advanced Security, and Active Data Guard all transfer when the customer holds them. Options not held must be licensed separately or via the license included rate.

How does auto scaling affect the cost?

Auto scaling extends the base ECPU up to three times during peak load. The customer is billed for the active ECPU on a per second basis. The buyer side lever is to negotiate a contractual cap below three times to contain cost runaway on volatile workloads.

When does the Dedicated shape make sense?

Dedicated makes sense above three hundred ECPU sustained workload or where data residency and isolation requirements rule out shared infrastructure. Below that band, the Exadata infrastructure cost outweighs the consolidation benefit.

How does Redress engage on Autonomous Database deals?

Redress runs Autonomous Database sizing, BYOL math, and OCI Universal Credit negotiation as part of the Oracle advisory practice. The work fits inside the Vendor Shield subscription or as a standalone engagement before the OCI order form is signed.

Can ADW and ATP share licenses?

Yes. The same Database EE perpetual license can cover ADW and ATP workloads under BYOL. The customer needs to hold enough processor licenses to cover the peak ECPU consumed across both services combined.

How Redress engages on Oracle OCI

Redress runs Oracle OCI advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former Oracle commercial executive on the buyer side.

Read the related benchmarking, about us, locations, and contact pages.

Score your Oracle OCI commit in under five minutes.
Open the Oracle Calculator →
White Paper · Oracle

Download the Oracle ULA Decision Framework.

A buyer side reference on Oracle ULA, PULA, MUC, and OCI commit vehicles. The discount math, the certification risk, the shortfall risk, and the renewal posture across every Oracle commit shape.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle commit vehicles. No Oracle influence. No sales kickback.

Oracle ULA Decision Framework

Open the white paper in your browser. Corporate email only.

Open the Paper →
$0.336
BYOL ECPU hour
3x
Auto scale cap
500+
Enterprise clients
$2B+
Under advisory
100%
Buyer side

Autonomous Database licensing is not about how many processors you own. It is about ECPU consumption, BYOL eligibility, the storage cap, and the Universal Credit discount tier. Get all four lined up before the OCI order form is signed.

Chief Data Officer
Global insurance group
More Reading

More from this practice.

Oracle Hub →
Oracle Cloud ERP Pricing
Oracle · Guide
Oracle Cloud ERP Pricing
Fusion Cloud commercial mechanics.
12 min read
Oracle Database 23ai Licensing
Oracle · Guide
Oracle Database 23ai Licensing
EE, SE2, processor, NUP.
20 min read
Oracle Knowledge Hub
Oracle · Hub
Oracle Knowledge Hub
Master Oracle reference.
20 min read
Oracle Cloud at Customer
Oracle · Guide
Oracle Cloud at Customer
Dedicated cloud in customer DC.
10 min read
Oracle Advisory Services
Oracle · Service
Oracle Advisory Services
The Oracle practice.
10 min read
Editorial photograph of enterprise contract negotiation strategy

Autonomous Database fits the workload when the ECPU sizing, the BYOL math, and the storage cap are agreed before the OCI order form.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Oracle OCI intelligence, monthly.

Autonomous Database sizing, BYOL math, Universal Credit negotiation, and OCI consumption monitoring across every Oracle Cloud engagement we run on the buyer side.