Oracle Cloud@Customer runs OCI inside your data centre — same infrastructure, same services, behind your firewall. This playbook covers strategic evaluation, contract negotiation, business case frameworks, and governance planning for CIOs, procurement, and IT operations teams considering or already running Oracle Cloud@Customer.
This playbook is part of the Oracle Knowledge Hub. See also our guides on Oracle OCI/Cloud Infrastructure licensing, the Oracle Contract Negotiation Service, and Oracle BYOL strategies.
Oracle Cloud@Customer Overview
Oracle Cloud@Customer is designed for enterprises that need cloud benefits (scalability, automation, agile provisioning) without moving data to a public cloud. It delivers a full public cloud experience in customer data centres, allowing organisations to consolidate applications and databases on high-performance cloud infrastructure without migrating to the public cloud.
Key capabilities and their CIO implications: The same OCI infrastructure and services running inside your data centre means cloud agility without data leaving your facility. Pay-as-you-go cloud economics with subscription pricing shifts capital expenditure to operational expenditure. All data stays behind your firewall, meeting strict residency, security, and compliance requirements — enabling cloud for regulated workloads in finance, healthcare, and government. Identical to public OCI, workloads can be moved to Oracle's public OCI regions in the future if desired.
Oracle Cloud@Customer's biggest advantage for integration is its consistency with the OCI public cloud. Applications can be developed once and deployed on public OCI or Cloud@Customer without refactoring. One set of cloud practices and skills covers both environments. This makes it much easier to modernise or extend legacy applications — deploy new microservices or analytics in Oracle's cloud environment on-prem and integrate them directly via the local network to the legacy system's database. The data gravity challenge (where large datasets are difficult to move to the cloud) is mitigated because computing comes to the data.
Key Strategic Considerations for Deployment
When evaluating an Oracle Cloud@Customer deployment, CIOs should consider four key strategic factors: data residency compliance, latency requirements, on-premises integration, and operational implications.
Data Residency and Regulatory Alignment
Data sovereignty: Cloud@Customer keeps all data and cloud infrastructure on your premises, crucial for organisations under strict data sovereignty laws. Your data never leaves your data centre, helping meet regulations that require local data storage (GDPR, national data residency laws). This is tailored for highly regulated industries (finance, healthcare, government) where using the public cloud is limited by compliance rules. Enterprises can leverage cloud innovation while meeting regulatory and security requirements.
Latency Requirements and Application Performance
Proximity matters for performance-sensitive workloads. Since the cloud hardware is on your network, it can directly connect to legacy databases, mainframes, and on-premises ERP. Batch jobs, ETL processes, and API calls between old and new systems run faster and more securely when executed locally rather than over external links. Applications requiring sub-millisecond latency to on-premises systems are strong candidates for Cloud@Customer rather than public OCI.
On-Premises Integration and Legacy Systems
Oracle allows the use of Universal Credits across public and on-premises cloud, meaning you can flexibly allocate cloud consumption between Oracle's public cloud and your Cloud@Customer as needs shift. Enterprises can treat Cloud@Customer as an extension of their existing IT estate — the same OCI Console, APIs, and tools manage both Cloud@Customer and public OCI resources. This unified operations model is a significant operational advantage for organisations managing large Oracle footprints.
Operational and Staffing Impact
Oracle provides and maintains the hardware and base cloud software in your data centre, offloading significant infrastructure management from your IT team. Oracle handles routine tasks: hardware provisioning, patching, upgrades, and database tuning (if using Autonomous Database). This lets your team focus on higher-value activities. However, you remain responsible for physical facility requirements: power, cooling, physical security, and network connectivity to Oracle's cloud infrastructure.
Contract Negotiation Strategies
Oracle Cloud@Customer contracts require careful negotiation to protect your organisation's interests over multi-year terms. Here are eight proven strategies from independent Oracle advisors:
- Negotiate Universal Credits flexibility: Push for Universal Credits that can be applied across both public OCI and Cloud@Customer without penalty. This gives you the ability to shift workloads between deployment models as your needs evolve without triggering additional costs.
- Demand transparent support and maintenance terms: Cloud@Customer support SLAs must be clearly defined. Oracle's response times for on-premises hardware failures are a critical negotiation point — establish resolution time commitments in writing, including hardware replacement timelines.
- Secure BYOL (Bring Your Own Licence) rights: Existing Oracle Database licences should transfer to Cloud@Customer under BYOL terms. Negotiate the exact licence types covered, the processor factor applicable, and whether licence mobility applies across Cloud@Customer and public OCI. See our Oracle advisory services for BYOL optimisation guidance.
- Cap annual price escalation: Multi-year Cloud@Customer contracts often include price escalation clauses. Negotiate caps on annual increases (typically limit to 3 to 5 percent) and ensure these are applied to the full contract value, not just base subscription components.
- Establish workload portability rights: Negotiate contractual rights to move workloads from Cloud@Customer to Oracle public OCI without financial penalty. This preserves your strategic flexibility if your data residency requirements change or public cloud economics become more attractive.
- Define hardware refresh obligations: Oracle must commit to hardware refresh cycles within your data centre. Negotiate the frequency of hardware upgrades, the notice period for planned upgrades, and your rights if Oracle delays a committed refresh.
- Include audit protection clauses: Cloud@Customer does not eliminate Oracle audit risk for on-premises licences running alongside it. Include contractual commitments that limit Oracle's right to audit Cloud@Customer-specific licensing and clarify the measurement methodology Oracle will use.
- Negotiate exit provisions: Define clear exit terms — what happens at contract end with the hardware Oracle has installed in your data centre, data migration rights, transition assistance obligations, and wind-down costs. Oracle's removal of hardware and data migration support should be clearly contractualised.
Business Case Evaluation Frameworks
Building the business case for Oracle Cloud@Customer requires a rigorous TCO comparison against alternatives: public OCI, Oracle on-premises, and third-party cloud alternatives.
Total Cost of Ownership analysis: Include hardware (avoided CapEx vs. Cloud@Customer OpEx subscription), data centre costs (power, cooling, space), IT staff (avoided infrastructure management), licence costs (BYOL economics vs. Licence Included pricing), support and maintenance, and migration costs. Cloud@Customer typically has higher total cost than public OCI but lower than maintaining equivalent on-premises infrastructure from scratch.
Regulatory compliance value quantification: For organisations in regulated industries, quantify the compliance risk mitigation value — fines avoided, audit costs reduced, and the competitive advantage of being able to use cloud services where public cloud is prohibited. These intangibles often make Cloud@Customer compelling when pure TCO analysis is borderline.
Latency and performance value: For database-heavy workloads where millisecond latency to on-premises applications drives business outcomes, quantify the performance advantage in business terms: transactions per second, user experience improvement, SLA achievement rate.
Strategic optionality value: Cloud@Customer preserves the option to migrate to public OCI when it becomes feasible. This optionality has real value in uncertain regulatory environments — you are not locked into on-premises forever, but you can meet today's requirements without forgoing tomorrow's cloud economics.
Governance Planning
Effective governance of Oracle Cloud@Customer requires attention to seven operational areas: capacity management, cost allocation, security posture, change management, vendor management, performance monitoring, and licence compliance.
Capacity management: Cloud@Customer does not eliminate capacity planning — Oracle's hardware has fixed limits within your data centre. Establish capacity governance: regular review cycles, expansion request processes, and pre-negotiated expansion terms in your contract.
Cost allocation: Universal Credits must be allocated across business units and workloads. Implement internal chargeback or showback to ensure consumption is tracked to cost centres and over-consumption is visible.
Licence compliance: Cloud@Customer creates a complex licensing environment where on-premises licences, BYOL, and Oracle-managed infrastructure coexist. Work with your Oracle licence management team to maintain a clean licence position and avoid audit exposure.
Oracle Cloud@Customer represents a genuine strategic option for enterprises with strict data residency requirements or latency-sensitive workloads. The decision requires rigorous business case analysis, careful contract negotiation, and sustained governance investment. Organisations that treat Cloud@Customer as simply "Oracle on-premises with a cloud label" underinvest in governance and overpay in contracts. Those who apply disciplined procurement and operating models consistently achieve better outcomes.
For support with Oracle Cloud@Customer contract negotiations, licence strategy, or business case development, explore Oracle advisory services, the full Oracle Knowledge Hub, and our Oracle audit defence services.