Oracle Autonomous Database hides three license decisions inside one product. The OCPU versus ECPU metric. BYOL versus License Included. Shared versus Dedicated. Each lever moves cost by ten to forty percent. This is the buyer side reference.
Oracle Autonomous Database is sold on a consumption metric that bills compute by the OCPU or ECPU hour and storage by the gigabyte month. The list rate looks simple. The total cost depends on three choices the buyer makes at deployment.
Pick the wrong metric and you pay roughly twice what you should. Pick License Included when you already own perpetual Database licenses and you pay for the same right twice. Pick Dedicated when Shared meets the workload and you carry a per region floor that does not flex.
Read this guide alongside the Oracle knowledge hub, the Oracle advisory practice, the Database 23ai licensing guide, the cloud licensing reference, the Oracle licensing master guide, and the Vendor Shield subscription.
Autonomous Database is a managed service, not a perpetual license. Oracle bills the compute, the storage, and the optional add ons by the hour and the gigabyte. The customer never holds a Database license number for the workload. The rate card sits inside the Universal Credit price list.
The Autonomous SKUs sit on the Universal Credit rate card under the Database family. Workload variants split into Transaction Processing, Data Warehouse, and JSON. Each variant has a Shared and a Dedicated SKU and each SKU has a BYOL and a License Included version.
The two metrics describe the same compute differently. OCPU was the original unit. ECPU launched in 2023 to align Oracle billing with the hyperscaler vCPU norm. The cost difference is structural, not cosmetic.
| Attribute | OCPU | ECPU |
|---|---|---|
| Definition | One Oracle CPU core (two vCPU) | One unit per two vCPU on shared compute |
| Per hour list rate | Higher | Roughly half OCPU rate |
| Minimum allocation | One OCPU | Two ECPU |
| Auto scale cap | Three times base | Three times base |
| Best fit | Large steady workloads | Bursty or small workloads |
| BYOL eligibility | Yes | Yes |
BYOL converts existing perpetual Database Enterprise Edition licenses into Autonomous compute. The conversion is two OCPU per processor license. The discount on the per hour rate is roughly forty percent, sometimes higher under negotiated rate cards.
Take a workload running at sixteen OCPU steady state on Transaction Processing Shared. License Included list rate runs into the high end of the Universal Credit table. BYOL drops the same OCPU hour to roughly sixty percent of the License Included rate.
The customer needs eight Database Enterprise Edition processor licenses to cover sixteen OCPU. If those licenses sit unused on premise, the BYOL move converts shelfware into active discount and saves materially over the year.
Most large Oracle estates carry idle perpetual Database licenses left from prior data center consolidations. BYOL converts the idle position into an Autonomous discount without renegotiating the support contract.
The buyer side discipline is to inventory the perpetual estate before the first Autonomous workload lands, not after.
Shared Autonomous runs on multi tenant Exadata infrastructure managed by Oracle. Dedicated Autonomous carves out a private Exadata rack inside an OCI region. The cost shape is different and the workload fit is different.
| Attribute | Shared | Dedicated |
|---|---|---|
| Tenancy | Multi tenant | Single tenant |
| Infrastructure floor | None | Per region rack commit |
| Provisioning time | Minutes | Days |
| Workload isolation | Logical | Physical |
| Best fit | Variable, mid scale | Regulated, large scale, predictable |
| Per OCPU hour | Lower | Higher with rack floor |
Autonomous cost control runs on three levers in parallel. Sizing and scaling discipline. Universal Credit commit shape. BYOL conversion and renewal alignment. Each lever moves the bill in a different direction.
| Lever | Where it sits | Effort | Typical impact |
|---|---|---|---|
| Right size base OCPU or ECPU | Console policy | Low | 10 to 25 percent |
| Cap auto scale ratio | Console policy | Low | 15 to 30 percent |
| Switch ECPU for small workloads | Migration | Medium | 20 to 40 percent on those workloads |
| Convert to BYOL | Procurement | Medium | 30 to 45 percent on the rate |
| Annual Universal Credit commit | Contract | High | 10 to 20 percent rate card discount |
| Storage tiering and archive | Operations | Low | 5 to 15 percent storage |
The two cheapest levers in Oracle Autonomous live before procurement: the metric you pick and the auto scale cap you set. A four OCPU workload with the cap left at default routinely bills at twelve OCPU on month end, and most teams never see it.
The seven step checklist below is the buyer side starting position for any Oracle Autonomous engagement.
Yes. Both metrics draw from the same Universal Credit pool. The choice is per workload, not per tenant. The buyer side discipline is to test ECPU on the smaller, bursty workloads first and migrate the larger steady workloads to OCPU only when the math holds.
The base BYOL conversion covers Database Enterprise Edition. Priced options used by the Autonomous workload still require their own perpetual licenses or License Included add on SKUs. The most common case is Real Application Clusters, which sits inside Autonomous on Dedicated and must be separately covered.
BYOL eligibility ends. The workload is then billed at License Included rates from the moment support lapses. The buyer side discipline is to align the support renewal calendar with the Universal Credit renewal calendar so neither slips out of step.
It is worth the floor when the rack is consistently used above seventy percent and when the workload demands single tenant isolation. Below that load level the Shared tier is materially cheaper. The deciding factor is rarely technology; it is the regulatory or risk position the workload sits inside.
Autonomous is a managed service, so the partitioning policy does not apply to the underlying compute. The policy still matters for any companion on premise or BYOL workload that runs Database Enterprise Edition on customer managed virtualization. Read the partitioning rules in the linked policy article before designing a hybrid pattern.
Redress runs Autonomous engagements inside Vendor Shield and the Renewal Program. The work covers the metric choice, the BYOL conversion, the Universal Credit rate card, the Dedicated versus Shared decision, and the auto scale cap policy. Always buyer side, never Oracle paid.
Redress runs Oracle Autonomous engagements inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The Oracle commercial leadership sits with the founders.
Read the related benchmarking framework, about us, locations, and contact pages.
A buyer side reference on the ULA certification math, the partitioning policy interpretation, the Autonomous BYOL conversion, and the OCI commit shape. Built from hundreds of Oracle engagements.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle estates. No Oracle influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The two cheapest levers in Oracle Autonomous live before procurement: the metric you pick and the auto scale cap you set. A four OCPU workload with the cap left at default routinely bills at twelve OCPU on month end, and most teams never see it.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Autonomous BYOL conversions, ULA exit patterns, partitioning addendums signed, OCI Universal Credit shapes, and the wider Oracle commercial leverage signals across every renewal we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
