Oracle Cloud at Customer is a managed service hosted on customer premises. It mixes hardware ownership, software consumption, and Oracle support into one bundle. The bundle simplifies operations but locks the relationship. The playbook is to model TCO against alternatives, validate license transfer rules, and refuse to bundle without exit terms.
Cloud at Customer is a managed service. Oracle owns the hardware. Customer consumes via the cloud model. Support is bundled.
Bring your own license to C@C is allowed under rules that vary by product. Database, Apps, and Middleware each have different rules.
Consumption is by ECPU or OCPU at C@C rates. The math is different from perpetual. Validate before signing.
C@C uses Oracle hard partition technology. The partition counts toward licensing. The math benefits some workloads, hurts others.
Hardware refreshes every 4 to 5 years on Oracle's schedule. The refresh is the lock in. Negotiate refresh terms upfront.
Oracle offers Cloud Lift incentives for customers moving from on premises to C@C. The incentives have terms. Read carefully.
Exit from C@C requires hardware return and re licensing. The exit is hard. Plan before signing.
Build a 5 year TCO model across on premises, OCI, and C@C. Include consumption, support, refresh, and exit. The model is the defense.
This white paper draws on Redress Compliance engagements, public vendor documentation, and the active Redress benchmark program.
Twenty years on the buy side. 500+ enterprises. $2B in client savings.
Once a month. Vendor moves, audit patterns, renewal alerts. For IT and procurement leaders.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
