At its Brussels summit on November 17, 2026, Google Cloud announced that Gemini models are coming to Google Cloud Dedicated, its isolated cloud operated by local partners. Google gave no launch date. The company also described key-management and compliance controls aimed at specific data-access and resilience concerns, while broader questions of political trust remain a separate challenge. Google Cloud’s announcement set out the product plans at the European summit.

Match each sovereignty control to the risk it is meant to address: data location, key custody, local operations or service continuity.

What Google announced about Gemini

Google described Gemini on Dedicated as forthcoming. In the same announcement, it said selected Gemini models were available in Google Cloud with a commitment to process customer data in-region, including in the EU, and that Gemini was available on Distributed Cloud. Those are separate deployment options from Dedicated.

The distinction matters in Spain, too. Google announced a preview partnership with Telefónica for external key management. That announcement concerns custody of encryption keys, not Gemini availability on Dedicated.

How the cloud options differ

Google’s three deployment choices put different controls in different places. Data Boundary applies residency, access and encryption controls to Google’s public cloud. Dedicated uses isolated infrastructure operated by a local partner. Distributed Cloud runs in a customer’s own data center, either connected or air-gapped.

Google Cloud optionWhere it runsMain control described
Data BoundaryGoogle’s public cloudData residency, access and encryption controls
DedicatedIsolated infrastructure operated by a local partnerPartner operation of the environment
Distributed CloudThe customer’s data centerConnected or air-gapped deployment

These arrangements address different operational needs; choosing a deployment model does not, by itself, answer every question an organization may have about legal or political trust.

What external key management changes

Google announced Confidential External Key Management (cEKM) in preview. A customer or local partner holds the root keys outside Google Cloud, while key operations take place in a hardware-attested Confidential Computing environment. Google says the design is intended to address latency and availability risks that can arise when each key request must reach an external system.

For Dedicated, Google says an instance can continue operating for up to 12 months if its connection to Google is severed. The company also says a local partner can block software updates in exceptional circumstances. These are provisions Google describes for the service’s design, giving the partner a role in operational continuity as well as local infrastructure.

Google also said Switzerland’s Data Boundary framework was available and an EU framework for DORA was planned. Its Audit Manager can provide continuous, machine-readable evidence for auditors. Those tools add ways to apply and document controls; political trust still depends on more than technical configuration.

Ukraine’s example connects data control to resilience

Diginomica reported that Roman Kyslyi, an official with Ukraine’s Ministry of Digital Transformation, described removing personal data before sending anonymized requests to Gemini, restoring the answers on ministry infrastructure, and keeping backups on its own systems and other clouds.

That workflow puts several practical questions at the center: what information leaves an organization, where results are restored, and how services can continue across infrastructure. Technical controls can shape those decisions, while the broader judgment about trust in providers, partners and political arrangements remains separate.