Oracle Autonomous Database licensing decoded for buyers.

Oracle Autonomous Database is priced on ECPU consumption rather than a perpetual processor license. This guide covers the service flavors, the Bring Your Own License math, the auto scaling cost traps, and how to model the real bill before you commit universal credits.

How is Oracle Autonomous Database actually priced in 2026?

Oracle Autonomous Database prices on consumption, not on a perpetual license. You pay for compute by the ECPU per hour and for storage by the terabyte per month. There is no upfront processor license.

Oracle moved the default compute metric from OCPU to ECPU on Autonomous Database for new deployments. One OCPU maps to roughly eight ECPU for budgeting. The shift changed the math on small workloads.

What are the Autonomous Database service flavors?

• Autonomous Transaction Processing: tuned for mixed transactional and operational reporting workloads.
• Autonomous Data Warehouse: tuned for analytics and large scan queries.
• Autonomous JSON Database: a lower cost option for document style workloads.
• Dedicated and Cloud at Customer: isolation on Exadata infrastructure, in Oracle cloud or in your data center.

The published rate card sits on the Oracle Cloud price list. Read it with the universal credits discount in mind, because the list rate is rarely the rate a committed buyer pays.

What is the difference between BYOL and license included on Autonomous Database?

License included bundles the database software rights into the hourly ECPU rate. Bring Your Own License lets you apply existing Oracle Database licenses and pay a much lower infrastructure rate.

The BYOL discount on Autonomous Database is large. For Enterprise Edition with options, BYOL can cut the compute rate by more than half versus license included, per the Oracle universal credits policy.

How do you count licenses for BYOL?

One owned Enterprise Edition processor license covers a defined number of ECPU under the BYOL rules. Count owned licenses first. Map them to the ECPU envelope before you provision, not after.

The trap is double counting. If the same processor license is claimed on premises and on Autonomous Database at the same time, you are out of compliance on one side.

White Paper · Oracle

The Oracle Buyer Side Framework

The moves we use across Oracle Database, Java and ULA estates. Read it free.

Read the white paper

Where do Autonomous Database costs spiral on auto scaling?

Auto scaling is the single largest source of bill shock we see. Autonomous Database can scale compute to three times the baseline ECPU automatically, and it bills the peak by the hour.

Which auto scaling settings drive runaway cost?

• Unbounded auto scale: a baseline of 4 ECPU can bill at 12 ECPU during a runaway query.
• Idle instances not stopped: non production instances left running overnight bill the full baseline.
• Storage growth: autonomous storage auto extends and rarely shrinks without intervention.

Oracle documents the auto scale behavior in the Autonomous Database documentation. Set a ceiling. Treat the ceiling as a budget control, not a performance tuning knob.

How should a buyer model Autonomous Database total cost?

Model the floor and the ceiling, never the floor alone. Oracle sales models the baseline ECPU. Your real bill includes auto scale peaks, storage growth, and backup.

What belongs in the cost model?

• Baseline ECPU per instance across all environments, not just production.
• Auto scale peak hours estimated from current workload patterns.
• Storage at projected twelve month growth, plus long term backup retention.
• The BYOL credit if you own licenses you can migrate.

Where the common advice on Autonomous Database pricing is wrong

The standard Oracle pitch is that Autonomous Database removes administration cost so the consumption rate pays for itself. We disagree. In roughly six out of ten Autonomous Database estates we have modeled, the consumption bill ran 20 to 40 percent above the original sales estimate once auto scaling and idle non production instances were counted. The administration saving was real but smaller than the overspend. The buyer side move is to cap auto scale, schedule non production instances to stop, and migrate owned licenses through BYOL before you ever sign a universal credits commitment. The autonomous label describes the database, not the bill.

Autonomous Database is consumption priced. The word autonomous describes the database administration, not your invoice. Cap the auto scale before you sign the credit.

What to do next on this estate

Use this sequence. It works whether you are 60 days or 270 days from a renewal or audit.

1. Pull a current ECPU and storage report across every Autonomous Database instance, production and non production.
2. Cap auto scale on each instance to a defensible ceiling tied to a budget, not to peak performance.
3. Schedule non production instances to stop outside working hours.
4. Inventory owned Enterprise Edition licenses and map them to the BYOL ECPU envelope.
5. Rebuild the twelve month cost model with the ceiling, storage growth, and the BYOL credit applied.
6. Only then negotiate the universal credits commitment against the corrected envelope.

Frequently asked questions

How is Oracle Autonomous Database licensed?

Oracle Autonomous Database is not licensed perpetually. It is priced on consumption, billed by the ECPU per hour for compute and per terabyte per month for storage. Software rights are either included in the rate or supplied through Bring Your Own License.

What is the difference between OCPU and ECPU?

ECPU is the current default compute metric for Autonomous Database, while OCPU is the legacy metric. For budgeting, roughly eight ECPU correspond to one OCPU. Oracle steers new deployments to ECPU.

Does BYOL save money on Autonomous Database?

Yes. Bring Your Own License lets you apply owned Oracle Database licenses and pay a lower infrastructure rate. For Enterprise Edition with options, BYOL commonly cuts the effective compute rate by more than half versus license included.

Why is my Autonomous Database bill higher than the quote?

The most common reason is auto scaling. Autonomous Database can scale to three times the baseline ECPU automatically and bills the peak. Idle non production instances and storage growth add the rest of the gap.

Can I run Autonomous Database in my own data center?

Yes. Autonomous Database on Exadata Cloud at Customer runs the service on Oracle managed infrastructure inside your data center, which can satisfy data residency requirements while keeping the consumption model.

How do I stop auto scaling overspend?

Set an auto scale ceiling on each instance tied to a budget rather than to peak performance. Schedule non production instances to stop outside working hours, and review storage growth monthly.

Is there a free tier?

Yes. Oracle offers an Always Free Autonomous Database tier with small fixed limits, which is useful for development and testing but not for production scale workloads.

Should I choose license included or BYOL?

Choose BYOL if you own Enterprise Edition licenses you can migrate, because it is materially cheaper. Choose license included for net new workloads where you hold no transferable licenses.