Oracle offers two distinct models for deploying its cloud services: Oracle Cloud at Customer (C@C) and Oracle Cloud Infrastructure (OCI). Both provide access to Oracle’s cloud portfolio but differ significantly in terms of infrastructure location, management responsibility, licensing policies, and cost structures. Understanding these differences is critical for organizations seeking to align their cloud strategy with regulatory, financial, and operational requirements.

Deployment Models Defined

Oracle Cloud at Customer is a private cloud deployment model that brings Oracle’s cloud infrastructure into the customer’s data centre. It enables organizations to leverage Oracle Cloud services while retaining control over data locality and compliance within their own premises. Oracle manages the hardware, software updates, and monitoring remotely.

Oracle Cloud Infrastructure (OCI) is Oracle’s public cloud offering. It provides highly scalable infrastructure services across Oracle’s global data centres. Customers access OCI resources on a pay-as-you-go or reserved-capacity basis.

Licensing Models Explained

Cloud at Customer Licensing

With Cloud at Customer, Oracle offers two main licensing paths:

• License Included: Customers pay for the full software stack, including Oracle Database and any required options, bundled into the C@C subscription. No separate software license or support agreement is needed.
• Bring Your Own License (BYOL): Customers use existing Oracle licenses on the C@C platform. This requires maintaining active Oracle support contracts for those licenses .

Importantly, C@C licensing mirrors OCI's metrics and definitions (e.g., OCPU-based usage), but contractual terms such as commitment period, support bundling, and regional availability differ.

OCI Licensing

In OCI, Oracle supports both License Included and BYOL models:

• License Included: Customers pay an hourly or monthly rate that includes both the infrastructure and Oracle software license. This is ideal for short-term projects or variable workloads.
• BYOL: Customers apply their on-premises Oracle licenses to run workloads in OCI. This provides cost savings, assuming existing license ownership and support.

OCI uses OCPU-based billing (1 OCPU = 1 license unit) for most services. Customers can leverage Oracle License Manager to track usage and maintain compliance.

Cost Considerations

License Included pricing is higher than BYOL because it encompasses the full cost of the Oracle software stack. In OCI, this can result in a 50–75% cost premium per OCPU hour compared to BYOL.

For example:

• Oracle Database Enterprise Edition in OCI (License Included): ~$0.43 per OCPU-hour
• Oracle Database EE in OCI (BYOL): ~$0.193 per OCPU-hour
• Cloud at Customer License Included: ~$0.336 per CPU-hour
• Cloud at Customer BYOL: ~$0.0807 per CPU-hour

BYOL provides the lowest cost per hour, especially in environments with high or sustained usage, where existing licenses can be applied efficiently.

Operational Flexibility

Cloud at Customer provides on-premise deployment with cloud-like management, offering:

• Data sovereignty and compliance control for regulated industries
• Predictable performance with dedicated infrastructure
• Enhanced security and isolation
• Local network latency benefits

However, it involves upfront subscription commitments (typically 3 years or more), and capacity planning must be performed at provisioning.

OCI delivers greater elasticity and global reach, with:

• Instant scalability and provisioning
• No hardware maintenance responsibilities
• Pay-as-you-go billing for unpredictable workloads
• Multi-region deployment capabilities

OCI is suitable for rapidly evolving environments and hybrid workloads spanning cloud and on-prem systems.

Support and Contractual Differences

Support Inclusions:

• In License Included models, support is built into the subscription. There’s no need for a separate Oracle Support agreement.
• In BYOL models, customers must maintain an active Oracle support contract to qualify for cloud usage rights.

Contractual Duration:

• OCI services can be consumed hourly, monthly, or reserved annually.
• Cloud at Customer requires longer-term contracts, with pricing tied to capacity and term.

Audit Risk & Compliance:

• OCI offers Oracle License Manager for usage tracking and compliance.
• Cloud at Customer deployments, though managed by Oracle, still require careful internal tracking for BYOL workloads.

Real-World Use Cases

Cloud at Customer Use Case: A global bank with strict data residency laws needs to run Oracle Database workloads locally while using cloud-native automation and patching. Cloud at Customer enables full compliance without sacrificing cloud functionality.

OCI Use Case: A technology startup building a multi-region SaaS platform requires rapid elasticity and global availability. OCI enables dynamic provisioning, low-latency performance, and flexible billing.

Strategic Licensing Recommendations

1. Evaluate Existing License Portfolio: Maximize ROI by identifying opportunities to reuse on-premises licenses under BYOL in either model.
2. Match Licensing Model to Workload Type: Use License Included for short-lived, unpredictable workloads; BYOL for steady-state, high-usage environments.
3. Negotiate Contractual Flexibility: Seek provisions for upward/downward scaling in C@C contracts. In OCI, use reserved capacity models for predictable savings.
4. Implement Governance Tools: Use Oracle License Manager and internal controls to prevent over-deployment and ensure license alignment.
5. Align Cloud Strategy with Data Compliance: For jurisdictions with strict residency rules, favor C@C; for global operations, prioritize OCI.

Conclusion

Oracle Cloud at Customer and Oracle Cloud Infrastructure both enable enterprise access to Oracle’s powerful cloud services but serve different strategic purposes. C@C excels in regulated, on-prem environments where data sovereignty and latency are key, while OCI provides unmatched scalability, flexibility, and reach. Understanding the licensing models—particularly the differences in BYOL and License Included pricing and support—can significantly impact long-term cost and compliance.

Choosing the right model requires a careful assessment of your operational, legal, and financial landscape. By aligning licensing strategy with business goals, organizations can leverage the full potential of Oracle Cloud while minimizing unnecessary spend and audit exposure.