Price Autonomous Database on ECPUs with auto-scaling to three times the base, storage and BYOL licensing.
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.
OCI Autonomous Database
monthly = (base ECPUs × steady hours + base × scale multiple × burst hours) × ECPU rate × licence factor + TB × storage rate.
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.
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.
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.
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.