Oracle Autonomous Transaction Processing (ATP) is Oracle's flagship managed cloud database service — but choosing between Shared and Dedicated infrastructure, navigating the OCPU-to-ECPU billing transition, and activating BYOL correctly can mean a 76% difference in what you pay. This guide cuts through Oracle's complexity to give you the commercial facts.
Oracle ATP Shared starts at $0.1008 per OCPU-hour — but enterprises migrating from on-premises Oracle Database under BYOL can reduce that cost by up to 50% using existing processor licences. Understanding the conversion rate and the Dedicated vs Shared cost trade-off determines whether ATP is commercially competitive with Azure SQL or AWS RDS for your workload profile.
The "autonomous" designation refers to Oracle's use of machine learning to automate database tuning, patching, backup, scaling, and security — tasks that traditionally require dedicated DBA effort. For organisations that want the performance characteristics of Oracle Database on Exadata hardware without the operational overhead of managing the database platform themselves, ATP is Oracle's primary proposition.
Understanding how ATP is licensed — and the significant cost implications of each deployment and billing option — is essential before committing to any ATP deployment. Oracle's cloud pricing is substantially more transparent than its on-premises licensing model, but the interaction between BYOL rights, billing metrics, and deployment infrastructure types creates complexity that has real financial consequences at scale. Redress Compliance's Oracle Autonomous Database licensing guide covers the full family context, while this page focuses specifically on ATP's shared versus dedicated decision and the ECPU transition.
In one engagement, a retail group was provisioning Oracle ATP Shared at list price across 12 workloads after a cloud migration. Redress Compliance identified $890,000 of eligible BYOL credits from the client's existing Oracle Database Enterprise Edition estate. After restructuring to Dedicated infrastructure with BYOL applied, annual ATP costs fell from $1.4M to $510,000. The engagement fee was less than 3% of the saving.
Every ATP deployment choice begins with one fundamental decision: Shared (Serverless) or Dedicated infrastructure. The financial and operational implications differ substantially, and Oracle's sales team will frequently default to Dedicated for larger enterprise deployments — a preference that does not always reflect the customer's actual requirements.
ATP Shared, also called ATP Serverless, provisions your autonomous database on infrastructure shared with other Oracle Cloud tenants. Oracle's multi-tenant isolation model ensures logical separation between customer data and workloads, but the underlying Exadata hardware is pooled. In exchange for sharing infrastructure, you gain maximum flexibility: billing is by the second, auto-scaling adjusts ECPU allocation dynamically based on workload demand, and the minimum commitment is one hour and one ECPU. There is no minimum term commitment for Shared ATP — you can provision, run, and terminate databases with no upfront cost and no ongoing commitment.
Shared ATP is particularly well-suited for development and test environments, departmental applications, variable workloads that scale significantly between peak and off-peak periods, and organisations that are adopting cloud infrastructure incrementally. The pay-as-you-go model means that idle databases cost nearly nothing (storage is charged separately at low per-GB rates), and auto-scaling prevents performance degradation during demand spikes without requiring manual intervention.
ATP Dedicated provisions your autonomous databases on reserved Exadata infrastructure — dedicated physical hardware that no other tenant shares. The dedicated model provides complete isolation of compute, memory, network, and storage resources. There is no shared infrastructure, no noisy-neighbour risk, and no resource contention from adjacent tenants.
The operational control available in Dedicated ATP is significantly greater than in the Shared model. Customers can customise patching schedules — specifying the quarter, month, week, day, and time window for Exadata infrastructure updates — rather than accepting Oracle's automated patch deployment timeline. Network configuration defaults to private (no public internet exposure), making ATP Dedicated the preferred architecture for regulated workloads, high-security environments, and organisations with strict data residency and network isolation requirements.
The cost difference is substantial. ATP Dedicated requires provisioning an Autonomous VM Cluster (AVM), which represents a minimum commitment of Exadata hardware capacity that runs continuously whether you deploy databases into it or not. The economics only work when the reserved capacity is consistently utilised across multiple production databases. Organisations deploying a single moderate-sized ATP database into Dedicated infrastructure typically find the cost far exceeds what Shared ATP would provide for the same workload.
Use Redress Compliance's Oracle Cloud cost analysis to model ATP Shared vs Dedicated economics for your specific workload — including BYOL impact.
Model Your ATP CostsThe most significant structural change in ATP licensing over the past two years is Oracle's migration from OCPUs (Oracle CPU units) to ECPUs (Elastic CPU units) as the primary billing metric. Understanding this transition — and whether your existing ATP deployments have migrated — is important for cost forecasting and licence compliance.
An OCPU was defined as the equivalent of one physical CPU core with hyperthreading enabled, providing a direct mapping to physical hardware specifications. This made OCPU pricing predictable but also tied it to specific hardware generations. An ECPU is a hardware-agnostic compute unit that Oracle can adjust as underlying infrastructure evolves, providing what Oracle describes as "a durable pricing metric not tied to specific processor make, model, or clock speed."
From May 2025, OCPU is no longer available for new Autonomous VM Cluster provisioning on Dedicated infrastructure. Existing OCPU-based Dedicated ATP clusters can be converted to ECPU billing via a service request to Oracle, with Oracle guaranteeing same or better price-performance after conversion. For Shared ATP, the ECPU transition has been similarly phased — customers on existing OCPU-based Shared ATP instances should verify their billing metric status in the OCI Console to confirm whether automatic migration has applied.
Oracle's ECPU pricing typically results in lower nominal per-unit costs but a different relationship between billing units and actual compute capacity. Organisations accustomed to OCPU-based cost forecasting need to re-baseline their ATP cost models after the ECPU transition to ensure budget projections remain accurate.
For organisations with existing on-premises Oracle Database licences with active support, BYOL (Bring Your Own Licence) for ATP is the most significant cost reduction lever available. Oracle's BYOL discount for Autonomous Database is 76% off the standard License Included rate — among the largest cloud BYOL discounts in the enterprise software industry.
The BYOL calculation is straightforward: 1 on-premises Oracle Database Processor licence (or 25 NUP licences) entitles the customer to use 2 ECPUs in ATP under BYOL pricing. Oracle Database Standard Edition and Enterprise Edition licences both qualify for the same 76% discount, making the conversion of older SE licences to ATP BYOL particularly attractive for organisations with large SE estates that are more valuable as ATP BYOL credits than as on-premises perpetual licences.
To activate BYOL correctly, organisations must declare their on-premises licence count during ATP provisioning in the OCI Console, select "Bring Your Own License" rather than "License Included," and ensure that the on-premises licences applied to BYOL are removed from active on-premises use — Oracle's licence terms do not permit the same licence to be used simultaneously on-premises and for BYOL cloud credit. This de-commissioning requirement is a common source of compliance gaps for organisations in a hybrid transition phase.
Redress Compliance helps organisations maximise the BYOL value of their existing Oracle Database estate — identifying which on-premises licences can be converted to ATP BYOL credits most efficiently and ensuring the transition is compliant.
Maximise Your BYOL PositionWhether you're evaluating ATP Shared vs Dedicated, managing the ECPU transition, or optimising BYOL — independent advice from Redress Compliance ensures you don't overpay.
Book a Free ATP ReviewOracle's ATP billing model has several characteristics that can generate unexpected costs if not actively managed. Auto-scaling in Shared ATP is enabled by default and will scale ECPU consumption up to three times the provisioned ECPU count during peak demand — a feature that improves performance but can significantly increase monthly costs if workloads are more variable than anticipated. Monitoring actual versus provisioned ECPU consumption and adjusting auto-scaling limits is essential for predictable ATP cost management.
Storage costs in ATP are billed separately from compute, at a per-TB per-hour rate. As database sizes grow — particularly for workloads that accumulate historical data — storage billing can become a material component of total ATP cost. Oracle's Autonomous Database includes automated compression and tiering, but storage billing reflects the provisioned storage allocation, not just the data volume actually written. Right-sizing storage provisioning and using Oracle's storage reclamation features actively can reduce this component of the bill.
For ATP Dedicated customers, the minimum viable Autonomous VM Cluster represents a significant committed cost. Oracle's sizing tools and Redress Compliance's independent modelling can help determine whether your intended database workload justifies the Dedicated model financially, or whether a combination of Shared ATP and contractual BYOL commitments achieves the same technical outcome at lower cost. Book a call to discuss your specific ATP architecture and cost optimisation options with an independent Oracle expert.
Expert guidance across Oracle's cloud licensing landscape
Independent expertise. Zero Oracle commercial relationships.
Independent review of your ATP architecture choices — Shared vs Dedicated, ECPU sizing, and BYOL activation — to confirm cost efficiency.
Learn MoreIdentify the on-premises Oracle licences best suited for ATP BYOL conversion — maximising the 76% discount while maintaining on-premises compliance.
Learn MoreOngoing Oracle Cloud cost monitoring, anomaly detection, and optimisation recommendations — preventing bill shock at Oracle's quarterly billing cycle.
Learn MoreRedress Compliance's Vendor Shield programme provides continuous Oracle cloud cost monitoring, BYOL compliance tracking, and commercial negotiation support.
Continuous Oracle Cloud cost monitoring
BYOL compliance reporting
Immediate audit response support
Renewal negotiation included