Autonomous Database on Dedicated Exadata Infrastructure offers two deployment possibilities for operational control and isolation; Oracle Public Cloud or Exadata Cloud@Customer. Even though both platforms support a standard set of features for Autonomous Databases, there are a few differences among them.

Feature Comparison

The following table lists the Autonomous Database features exclusive to either Oracle Public Cloud or Exadata Cloud@Customer deployments.

Feature	Oracle Public Cloud	Exadata Cloud@Customer
Add a cross tenancy Autonomous Data Guard standby database
Change the license type on an Autonomous Exadata VM Cluster (AVMC)	Supported via service request (SR) in My Oracle Support. See Create a Service Request in My Oracle Support for instructions.
Create a cross tenancy clone from a database instance or its backup
Configure Zero Trust Packet Routing (ZPR) security attributes for an Autonomous Exadata VM Cluster (AVMC)		-
Connect Python applications using the python-oracledb driver	-
Deploy Autonomous Database to X10M Exadata Database Machine Systems	-
Deploy Autonomous Database to Exadata Base Machine Systems		On Exadata Cloud@Customer deployments, Base Shape is offered as a fixed shape (Base Rack) while provisioning an Exadata system such as X8M-2, X9M-2 and so on.
Use Database Management Service to monitor databases		-
Use Ops Insights on Autonomous Database		-
Bring Your Own Keys (BYOK) on Oracle Public Cloud deployments		-
Use OCI External Key Management System (EKMS) Keys with Oracle Public Cloud deployments.		-