OCI Autonomous Database Calculator
Price Autonomous Database on ECPUs with auto-scaling to three times the base, storage and BYOL licensing.
Inputs
ECPU databases must be provisioned with at least 2 ECPUs.
Autonomous Data Warehouse and Transaction Processing both list near $0.336 per ECPU-hour.
Auto-scaling allows bursts to three times the base ECPU count, billed only while used.
Capped at 3× the base ECPU count.
Monthly Cost
$1,476.72
ECPU Charge
$1,239.92
Storage Charge
$236.80
Peak ECPUs Available
12ECPU
Billed ECPU-Hours
3,690
Effective Price per ECPU-Hour
0.3360USD
Auto-Scaling Charge
$239.98
Annual Cost
$17,720.65
Step by step
Values used
Base ECPUs = 4 ECPU; Price per ECPU-hour = 0.3360 USD/ECPU-hour; Enable auto-scaling = Yes; Hours spent above the base = 20 %; Average multiple of base while scaled = 2.20 ×; Database storage = 2 TB; Storage price per TB-month = 118.40 USD/TB-month; Bring your own licence (BYOL) = No; BYOL rate as a share of licence-included = 63 %; Billed hours per month = 744 hours
OCI Autonomous Database
monthly = (base ECPUs × steady hours + base × scale multiple × burst hours) × ECPU rate × licence factor + TB × storage rate.
Monthly Cost
= 1,476.72
ECPU Charge
= 1,239.92
Storage Charge
= 236.80
Peak ECPUs Available
= 12 ECPU
Billed ECPU-Hours
= 3,690
Effective Price per ECPU-Hour
= 0.3360 USD
How it works
Autonomous Database bills ECPU-hours, so the compute line is the base allocation for the whole month plus the extra ECPUs consumed during auto-scaling bursts. Auto-scaling can reach three times the base but is metered only while it is actually in use, which makes a small base with scaling enabled cheaper than provisioning for the peak. Sizing the base to the peak wastes ECPU-hours for the 80% of the month that is quiet, and auto-scaling costs nothing when idle — the trade-off is that a base below the sustained load leaves you permanently scaled. Confirm the ECPU and storage rates, and the BYOL discount your agreement allows, in the Oracle Cloud cost estimator for your region.
Formula
OCI Autonomous Database
monthly = (base ECPUs × steady hours + base × scale multiple × burst hours) × ECPU rate × licence factor + TB × storage rate.
- ECPU
- Elastic CPU, the current Autonomous Database billing unit with a floor of 2
- scale multiple
- Average multiple of the base while scaled, capped at 3×
- licence factor
- BYOL rate expressed as a fraction of the licence-included rate
Frequently Asked Questions
How is OCI Autonomous Database calculated?
monthly = (base ECPUs × steady hours + base × scale multiple × burst hours) × ECPU rate × licence factor + TB × storage rate. Autonomous Database bills ECPU-hours, so the compute line is the base allocation for the whole month plus the extra ECPUs consumed during auto-scaling bursts. Auto-scaling can reach three times the base but is metered only while it is actually in use, which makes a small base with scaling enabled cheaper than provisioning for the peak.
Why does OCI Autonomous Database matter?
Sizing the base to the peak wastes ECPU-hours for the 80% of the month that is quiet, and auto-scaling costs nothing when idle — the trade-off is that a base below the sustained load leaves you permanently scaled. Confirm the ECPU and storage rates, and the BYOL discount your agreement allows, in the Oracle Cloud cost estimator for your region.
What values do I need to enter?
This calculator takes 10 inputs: Base ECPUs, Price per ECPU-hour, Enable auto-scaling, Hours spent above the base, Average multiple of base while scaled, Database storage, Storage price per TB-month, Bring your own licence (BYOL), BYOL rate as a share of licence-included, Billed hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
How far can Autonomous Database auto-scale?
Auto-scaling allows the database to use up to three times its base ECPU count, and you are billed only for the ECPU-hours actually consumed above the base. That is why this calculator asks how many hours you spend above the base and what average multiple you reach, rather than assuming the peak runs all month.