Oracle Cloud@Customer brings Oracle's cloud technology into your data centre. This guide covers every category of Oracle software supported: databases and enterprise applications, Fusion SaaS, middleware, and third-party workloads, plus licensing models (BYOL vs Licence-Included) and typical workload scenarios.
For pricing and benefits, see Oracle Cloud@Customer Pricing and Benefits. For the comparison with Dedicated Region, see Cloud@Customer vs Dedicated Region.
Oracle's flagship databases are fully supported on Cloud@Customer, which was initially centred around database services. The Exadata Database Service runs Oracle Database as a cloud service on Exadata hardware in your data centre.
Key takeaway. Any Oracle database that runs on Exadata or Oracle Cloud can run on Exadata Cloud@Customer. You get the same software capabilities delivered as a managed service in your data centre. Oracle ensures the database software stays current and patched while you manage databases to suit your application needs.
Important. Running applications on Cloud@Customer does not transform them into cloud SaaS. You still maintain and administer the applications (patches, configurations) as before. The benefit is operational: easier provisioning, scaling, and integrated infrastructure management.
Dedicated Region: Full SaaS on-premises. A customer with a Dedicated Region can request Oracle to include Fusion ERP, HCM, and SCM running on that dedicated region's infrastructure. Oracle operates these identically to the public cloud, but the servers are in your facility. For the customer, it appears to be the same SaaS application, except delivered from a private region.
Without Dedicated Region: No Fusion SaaS. If you only have Exadata Cloud@Customer (not a Dedicated Region), you cannot self-install Oracle's SaaS apps like Fusion ERP. They are not sold as installable software. You would continue using Oracle's SaaS in their public cloud or stick with on-premises applications.
Key distinction. Legacy Oracle applications (EBS, PeopleSoft, etc.) are supported by the customer on Cloud@Customer infrastructure. Modern Oracle Cloud applications (Fusion SaaS) can only be included through Oracle's management in a Dedicated Region arrangement.
Licensing responsibility. Cloud@Customer does not cover third-party software licences. If running Windows Server on a VM, you must properly licence Windows. Standard licence rules for all non-Oracle software apply.
| Factor | Licence-Included (Subscription) | Bring Your Own Licence (BYOL) |
|---|---|---|
| How it works | Oracle software licence "rented" as part of the Cloud@Customer subscription. No separate on-prem licence needed. | Use your existing Oracle licences on Cloud@Customer. Must have equivalent licences with active support. |
| Cost | Higher per-unit rate: bundles software licence cost into service | Lower infrastructure rate: you supply the licensing piece |
| Compliance | Oracle handles licensing internally: simpler compliance | You certify licence use: must maintain accurate entitlement mapping |
| Best for | Organisations without existing licences; prefer all-in-one subscription; want minimal compliance management | Organisations with surplus/underutilised licences; ULA holders; want to maximise ROI on existing investment |
Application licences are separate. For applications like EBS or PeopleSoft, the application software licences are typically separate from Cloud@Customer. You maintain your existing application licences as-is. Cloud@Customer can include underlying technology licences (database, WebLogic) if you choose licence-included for those.
Cost strategy. BYOL can be significantly cheaper if you have underutilised licences (the cloud service rate is lower). Licence-included is simpler if you want an all-in-one subscription with no spare licences to apply. CIOs should model both options. Oracle's Universal Credits apply to Cloud@Customer usage, so if you negotiated a pool of cloud credits, you can use them for on-premises services.
All editions of Oracle Database are supported on Exadata Cloud@Customer, including Enterprise Edition with options like RAC, Data Guard, Advanced Security, and Partitioning. You can also run Autonomous Database (both Transaction Processing and Data Warehouse). Oracle keeps the database software current and patched.
Yes. Deploy EBS application-tier servers on Oracle Compute Cloud@Customer VMs with an Oracle Database on Exadata Cloud@Customer as the backend. The entire EBS stack remains in your data centre while Oracle handles hardware management. The database component can even be an Autonomous Database.
BYOL lets you use existing Oracle licences (with active support) on Cloud@Customer at a lower service rate. Licence-Included bundles the Oracle software licence into the subscription fee at a higher per-unit cost but simpler compliance. BYOL is popular for organisations with surplus licences, especially ULA holders.
Only through an Oracle Dedicated Region Cloud@Customer. With a Dedicated Region, Oracle deploys and manages Fusion SaaS applications in your data centre. If you only have Exadata or Compute Cloud@Customer, you cannot self-install Fusion SaaS.
Yes. With Compute Cloud@Customer or a Dedicated Region, you can run custom applications, third-party software, and open-source tools on VMs. However, you must licence non-Oracle software separately.
Yes. Oracle's Universal Credits apply to Cloud@Customer usage. If you negotiated a pool of cloud credits, those credits can be consumed for on-premises Cloud@Customer services.
Since Oracle operates the Cloud@Customer infrastructure, they can detect usage levels including database OCPU consumption. If you use BYOL and exceed the licences you have brought, Oracle will identify the overage. Regular reconciliation of BYOL entitlements against actual usage is recommended.
Application software licences (EBS, PeopleSoft, Siebel, JDE) are separate from Cloud@Customer. You maintain your existing application licences as-is. Cloud@Customer can include the underlying technology licences (database, WebLogic) through Licence-Included or BYOL, but the application-layer licences remain your responsibility.