Oracle Cloud Infrastructure Documentation

Autonomous Database Billing Summary

You are billed for Autonomous Database usage according to the values of two parameters: compute and storage. You select values for these parameters when you provision or scale an Autonomous Database instance.

When you provision an instance you select a workload type based on the workloads you want to run on your database. The pricing for compute and storage resources is based on the workload type you select.

The workload types are:

  • Data Warehouse: optimized for analytic workloads, including data marts, data warehouses, data lakes, and data lakehouses.
  • Transaction Processing: optimized to run transactional, analytical, and batch workloads concurrently.
  • JSON: a cloud document database service that makes it simple to develop JSON-centric applications.
  • APEX: a fully managed, low-code application development platform for building and deploying modern cloud, mobile, and data-driven applications.

Depending on the workload type, you select an Autonomous Database billing model:

  • ECPU Billing Model: (Recommended billing model) Based on the number of cores allocated from the pool of compute servers and storage servers.

  • OCPU Billing Model: (Legacy billing model) Provides compute capacity equivalent of a physical core of a processor with hyper-threading enabled.

See the Autonomous Database Cloud Price List for up-to-date pricing for each workload type.

Use the Cloud Cost Estimator to estimate the monthly cost for an Autonomous Database.

For complete cost details, refer to the Oracle PaaS and IaaS Universal Credits Service Descriptions document available on the Oracle Cloud Services contracts page.

Compute and Storage Billing Summary

Compute Billing

Compute billing is based on the value you specify for ECPU Count and on the additional features you use. For example, if you use additional compute resources with Compute auto scaling selected, you are billed for the additional compute resources.

Storage Billing

Billing for database storage is based on the value you specify for Storage and based on the features you use that require additional storage. For example, you are billed for additional storage usage if you select Storage auto scaling and you use additional storage resources.

The storage for backups is billed in addition to database storage.

  • Data Warehouse workloads:

    • Database storage is provisioned in Terabytes (TBs) and charged in TB increments. The minimum database storage size is 1 TB.

    • Backup storage is separately charged in TB increments.

    See Billing Information: Autonomous Data Warehouse ECPU Compute Model.

  • Transaction Processing, JSON, or APEX workloads:

    • Database storage is provisioned in Gigabytes or Terabytes (GBs or TBs) and charged in Gigabyte increments. The minimum database storage size is 20 GB.

    • Backup storage is separately charged in GB increments.

    See ECPU Compute Model Billing Information.

Also see Oracle Autonomous Database Serverless Features Billing

Compute Billing

Compute billing is based on the value you specify for OCPU Count and on the additional features you use. For example, if you use additional compute resources with Compute auto scaling selected, you are billed for the additional compute resources.

Storage Billing

Billing for database storage is based on the value you specify for Storage and based on the features you use that require additional storage. For example, you are billed for additional storage usage if you select Storage auto scaling and you use additional storage resources.

  • For all workload types database storage is provisioned in Terabytes (TBs) and charged in TB increments.

  • For all workload types, the storage for automatic backups is included in the cost of database storage at no additional cost.

See OCPU Compute Model Billing Information and Oracle Autonomous Database Serverless Features Billing