Google announced in Brussels on November 17 that Gemini is coming to partner-operated Google Cloud Dedicated, alongside Confidential External Key Management in preview. Dedicated is designed to continue operating for up to 12 months if its connection to Google is severed; that is not a universal guarantee for every Gemini function. Kaldata also covered the announcement.

Different layers of control

Google distinguishes constrained public cloud, partner-operated infrastructure and deployment at the customer’s site. These options do not establish identical service availability; coming and preview remain material qualifications.

Google’s Confidential Computing overview supplies complementary technical context: protecting data during processing through isolated, attestable computing environments. It is not an independent test of every commitment in the new sovereign offering. That distinction helps separate an architectural mechanism from a conclusion about an entire deployment.

Key control is a specific authority

Our editorial interpretation starts with who can authorize use of a key and how that authority can be demonstrated. Data location, the environment’s operator and access to cryptographic operations are related but distinct properties. A map of European facilities cannot answer all those questions on its own.

In a hypothetical pilot, we would document one service and its dependencies. Which components operate locally, which need an external connection, and what happens during a temporary interruption? We would then examine how normal operation resumes. This is a suggested technical evaluation method, not a Google Cloud scenario tested by SIExpo.

Continuity is more than one number

A period of disconnected operation has practical value only alongside its scope. A component remaining active does not establish that every model, update and connected service behaves identically. A useful acceptance document would list the functions that must remain available and the checks used to confirm them. That also makes limitations easier to compare between configurations.

The same reasoning applies to update control. An organization needs to understand what can be deferred, who decides and how versions remain traceable. A mechanism’s existence differs from evidence that it suits every workload. We do not infer legal compliance from a technical product description or treat a local operator as a substitute for examining the actual deployment.

The announcement broadens options for AI under local operation. A practical choice depends on the verified configuration and agreed scope. SIExpo has not tested the claimed autonomy: the periods and capabilities remain attributed to Google, with currently available features separated from planned additions.