Oracle Cloud@Customer brings Oracle's cloud technology into your data centre. This guide covers every category of Oracle software supported — from databases and enterprise applications to Fusion SaaS, middleware, and third-party workloads — plus licensing models (BYOL vs Licence-Included) and typical workload scenarios.
Oracle's flagship databases are fully supported on Cloud@Customer, which was initially centred around database services. For a detailed pricing and benefits overview, see Oracle Cloud@Customer Pricing & Benefits.
This is Oracle's primary offering for databases on-premises. It runs Oracle Database as a cloud service on Exadata hardware in your data centre. All editions of Oracle Database (Enterprise Edition and features like RAC) are supported, and you can deploy Autonomous Database on Exadata Cloud@Customer — Oracle's machine-learning-powered automation for tuning, patching, and backups.
Cloud@Customer supports modern Oracle DB versions offered in Oracle Cloud — including Autonomous Transaction Processing and Autonomous Data Warehouse. Most Oracle Database options (Advanced Security, Partitioning, etc.) can be used, with some included by default in Autonomous deployments. The service encourages upgrading to supported versions, but importing older data or running compatibility modes is possible.
One Exadata Cloud@Customer rack can host many container or pluggable databases — ideal for consolidation projects. Move dozens of separate Oracle databases from ageing hardware onto one cloud-managed Exadata system. Oracle RAC and Data Guard are fully supported for HA and DR configurations within Cloud@Customer (or use a second Cloud@Customer for DR at another site).
Many organisations run Oracle's enterprise applications on-premises. With Cloud@Customer, you can continue running these applications while leveraging cloud-managed infrastructure.
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 stays in your data centre while Oracle handles hardware management. The database can be an Autonomous Database, reducing DBA workload for EBS users.
All are supported and certified to run with Autonomous Database on Cloud@Customer. For example, migrate your PeopleSoft HR system's Oracle database into an Autonomous DB on Exadata Cloud@Customer and run PeopleSoft application servers on local OCI compute instances. The application benefits from an auto-tuned database without moving to public cloud.
Many Oracle applications rely on WebLogic Server. Install WebLogic on a VM on Compute Cloud@Customer just as on any OCI compute instance. Cloud@Customer supports Oracle Linux and other OS images, so deploying Oracle middleware like WebLogic, Oracle Internet Directory, Oracle SOA Suite, and Oracle Forms is fully feasible.
Host Oracle Business Intelligence (OBIEE/OAS) or Oracle Analytics Server on Cloud@Customer VMs, connecting to your Exadata Cloud@Customer database for reporting. These applications run on servers provided by Cloud@Customer, with Oracle's cloud provisioning and potentially better performance on optimised hardware.
Oracle's newest applications (Fusion Cloud ERP, HCM, CRM, SCM) are provided as cloud services. Normally, customers don't run these themselves on-premises — Oracle hosts them. However, Oracle Dedicated Region Cloud@Customer uniquely allows Fusion SaaS applications in your data centre.
A customer with a Dedicated Region can request Oracle to include applications like 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. See Cloud@Customer vs. Dedicated Region for the distinction.
If you only have Exadata Cloud@Customer (not a Dedicated Region), you cannot self-install Oracle's SaaS apps like Fusion ERP — they aren't sold as installable software. You would continue using Oracle's SaaS in their public cloud or stick with on-premises applications (EBS, PeopleSoft, etc.) as described above.
Planning a Cloud@Customer deployment? Get independent guidance on licensing, sizing, and contract terms.
Oracle Contract Negotiation →Cloud@Customer is not limited to Oracle-only workloads. With Compute Cloud@Customer or a Dedicated Region, you can run custom applications, third-party software, and open-source tools just like in any cloud or virtualised environment.
Run Linux VMs and install non-Oracle databases (MySQL, PostgreSQL), application servers (Apache, Tomcat), or any enterprise software. Oracle explicitly states you can run "third-party and custom apps" on Cloud@Customer. This helps keep integrations local when your Oracle systems connect to other software components.
Many third-party applications (SAP, for instance) have their own support requirements and may not be officially certified on Oracle Cloud@Customer. Treat it as running on Oracle Linux or Windows on standard x86 servers — as long as the OS environment is supported, the software should run. Always check with the third-party vendor for support caveats.
Cloud@Customer doesn't cover third-party software licences. If running Windows Server on a VM, you must properly licence Windows (Oracle has guidance for Microsoft licensing on OCI that applies similarly). Standard licence rules for all non-Oracle software apply.
When running Oracle software on Cloud@Customer, licensing is a critical consideration. Oracle provides two licensing models:
| 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 |
For applications like EBS or PeopleSoft, the application software licences are typically separate from Cloud@Customer. If migrating an existing EBS instance, you maintain your EBS application licences as-is (usually perpetual user or module licences). Cloud@Customer can include the underlying technology licences (database, WebLogic) if you choose licence-included for those. Many Oracle apps come with a restricted-use database licence when on-prem; in a Cloud@Customer scenario, BYOL using your existing licence or converting to an Autonomous BYOL credit may be cleaner.
Oracle's Universal Credits apply to Cloud@Customer usage — if you negotiated a pool of cloud credits, you can use them for these on-premises services. Note that compliance is monitored: since Oracle operates the infrastructure, they can detect if you use more database OCPUs than your BYOL covers. Address any overage proactively to avoid compliance issues.
A manufacturing company runs EBS for finance and supply chain. Due to data privacy rules, it stays on-premises. They deploy Exadata Cloud@Customer and migrate the EBS database to an Autonomous Transaction Processing instance. The EBS application tier runs on Compute Cloud@Customer VMs. Result: lower DBA effort, improved performance, no change in user experience. BYOL for the database; licence-included for Exadata infrastructure.
A retail enterprise moves a large Oracle data warehouse onto Exadata Cloud@Customer using Autonomous Data Warehouse. Oracle Analytics Server runs on a VM on the same Cloud@Customer rack. All BI reporting runs on-premises. Licence-included for Autonomous DB (no existing DB licences); BYOL for Oracle Analytics Server. Performance improves drastically thanks to Exadata, with no data leaving the facility.
Production Oracle databases and apps stay on Exadata Cloud@Customer on-premises for latency and control. Oracle's public cloud handles bursty workloads and disaster recovery via Data Guard. PeopleSoft runs on-premises with a DR standby in Oracle's public cloud. Same OCI automation scripts work in both environments. BYOL stabilises licensing costs across on-prem and cloud.
A bank has a .NET application using Oracle Database. The database deploys on Exadata Cloud@Customer; the application runs on Windows Server VMs on compute nodes. Windows and .NET are licensed through Microsoft separately. Proximity of app and database yields low latency, and Oracle manages all infrastructure. Demonstrates Cloud@Customer hosting mixed Oracle + non-Oracle stacks.
Oracle continues to expand Cloud@Customer offerings. Smaller-footprint Dedicated Regions and the Compute Cloud@Customer were introduced to widen the range of on-premises applications customers can run. This trend suggests more Oracle software will be seamlessly supported over time.
Cloud@Customer is designed to be evergreen: when Oracle develops new cloud services (AI services, new database features), a Dedicated Region customer can run them on-premises once rolled out. Updates to Oracle software (database upgrades, new app versions) are made available in Cloud@Customer as they are in the cloud, keeping your environment current.
From a CIO perspective, the Cloud@Customer environment can host virtually all Oracle software your enterprise uses, provided you have the appropriate configuration (Exadata for databases, Compute for apps, or a full Dedicated Region for everything). It extends Oracle's public cloud compatibility to your premises.
Move existing Oracle-based workloads onto Cloud@Customer with minimal changes, gaining cloud-like management. It's a way to modernise how Oracle software is delivered without abandoning the software you rely on.
Evaluating Cloud@Customer for your Oracle estate? Get independent cost modelling and licensing analysis.
Oracle Licence Management →Whether you're planning a Cloud@Customer deployment, negotiating a Dedicated Region contract, or evaluating BYOL vs Licence-Included models, Redress Compliance delivers vendor-independent advisory with a track record of saving Fortune 500 enterprises millions.
Also managing Java, middleware, ULA, or on-prem Oracle contracts? We cover the full Oracle stack.
All Oracle Advisory Services →