Exadata Cloud at Customer Explained

Exadata Cloud at Customer, or ExaCC, is the answer to a specific problem: you want the engineered performance of Exadata and the consumption model of cloud, but your data is not allowed to leave your premises. ExaCC places a full Exadata system inside your own data centre, while Oracle manages it remotely as a cloud service. This article explains what ExaCC is, how it differs from running Exadata yourself, who it is for, and how to think about it alongside the public cloud alternative.

For the public cloud sibling and a direct comparison, see ExaCS vs ExaCC compared and our complete guide to Exadata Cloud Service.

What ExaCC actually is

ExaCC is a full Exadata engineered system, the same hardware and software that powers Exadata in Oracle's cloud, installed in your data centre. The difference from buying an Exadata outright is the operating model: Oracle owns and manages the system, delivers it as a service with cloud style consumption billing, and reaches in over a secure management connection to patch, monitor and maintain it. You provide the space, power, cooling and network, and you keep your data physically on your premises, but you do not own or operate the machine in the traditional sense. It is cloud delivered onto your floor.

Why it exists

ExaCC exists because a large class of organisations cannot place certain data in a public cloud, for reasons that are usually regulatory, contractual or about data residency law, but still want the benefits of a managed, consumption based platform. Banks, government bodies, healthcare organisations and others operating under strict data residency rules often fall into this category. Before ExaCC, their only options were to buy and run Exadata themselves, taking on the full operational burden, or to accept a less capable platform. ExaCC gives them the engineered performance and the managed cloud model while satisfying the constraint that the data stays local. It is a deliberate compromise that trades the elimination of data centre responsibility, which public cloud provides, for the data residency that the public cloud cannot.

What you still own and what Oracle handles

The division matters because it shapes what your team still needs to do. Oracle handles the lower layers of the engineered system, but the databases on top remain your responsibility to administer, tune, back up and secure, unless you bring in a partner to run them. This is where an independent operator adds value, because the database layer of an ExaCC needs the same active management as any Exadata, and that is exactly what our managed services practice provides.

ExaCC and the rest of OCI

Although ExaCC sits in your data centre, it integrates with OCI services across the management connection, so it can participate in a wider hybrid estate rather than being an island. This lets organisations run the data tier locally on ExaCC for residency reasons while running other workloads in the public cloud, connected together. The architecture of such a hybrid estate needs care, particularly around connectivity and latency, but it is a well established pattern for organisations that have some data that must stay local and other workloads that can move freely. Designing this kind of hybrid is part of our implementation and migration practice.

How to think about ExaCC versus ExaCS

The decision between ExaCC and the public cloud ExaCS comes down to the data residency question first and the latency question second, as we set out in ExaCS vs ExaCC compared. If your data must stay on your premises, ExaCC is the answer. If it can leave but you have on premises applications that need very low latency to the database, ExaCC may still win on placement. If neither constraint applies, ExaCS removes the data centre burden entirely and is usually the cleaner choice. The sizing method is the same for both, covered in sizing Exadata Cloud Service, as is the performance behaviour in Exadata Cloud Service performance.

The cost picture is different

ExaCC's cost includes something ExaCS does not require you to count separately: the data centre itself. With ExaCS, Oracle absorbs the facility cost into the service. With ExaCC, you continue to bear the space, power and cooling, and those costs belong in any honest comparison. Against that, ExaCC can avoid the network egress and connectivity considerations that come with reaching a public cloud region, and it can keep latency to local applications low. Modelling both options with all costs included, rather than comparing only the Oracle charges, is the only way to make the comparison fairly. The licensing question, which often dominates Exadata economics, applies to both and is the area we most strongly recommend getting independent advice on.

Running ExaCC well

Because Oracle manages the lower layers, it is tempting to assume ExaCC runs itself, but the database tier needs the same active operation as any Exadata: performance tuning so the workload exploits the platform, backup and recovery designed and tested rather than assumed, capacity managed against real demand, and security maintained. An ExaCC left on autopilot at the database layer drifts toward the same overspend and underperformance as any neglected Exadata. The ongoing operation of the database tier is where an independent partner adds the most value, and it is the heart of our managed services practice. If you are weighing ExaCC for a residency constrained workload and want help with both the decision and the run, an assessment is the place to start.