Cloud@Customer looks like the best of both worlds. Independent TCO analysis shows it’s 30–60% more expensive than Oracle claims. This guide covers licensing rules, ULA interactions, and the contract protections you must secure before committing.
TCO comparison (C@C vs OCI vs on-prem vs AWS/Azure), BYOL rules, ULA interaction analysis, 8 contract protections, and 6 risk assessments.
This is not a product datasheet. It’s an independent commercial assessment that models real costs, identifies licensing traps, and lists the contract terms you must negotiate before signing.
5-year TCO: on-premises ($3.8M) vs public OCI ($4.5M) vs Cloud@Customer ($5.8M) vs AWS/Azure ($3.2M). Including hidden costs Oracle omits.
Processor counting on Exadata C@C, BYOL entitlement requirements, Autonomous DB consumption models, and the compliance grey zones Oracle exploits.
Does your ULA cover C@C? How do C@C deployments count at certification? What happens to C@C entitlements if you exit the ULA? Three questions worth millions.
Price caps, minimum commitment flexibility, data portability, BYOL confirmation, SLA guarantees, hardware refresh, audit scope limits, and workload portability rights.
Vendor lock-in acceleration, TCO miscalculation, BYOL compliance gaps, consumption unpredictability, data centre burden, and contractual asymmetry.
100% independent. Zero Oracle Cloud partnership. TCO data from real C@C deployments. Every recommendation in your commercial interest.
Cloud@Customer is 30–60% more expensive than Oracle’s TCO models suggest when you include infrastructure management fees, data centre costs, minimum commitment floors, and exit costs.
REDRESS COMPLIANCE — ORACLE CLOUD PRACTICE