Google has launched an India-based deployment of Gemini for enterprises and public-sector organizations that cannot send sensitive workloads to a conventional public cloud. Announced on July 14, Google says the air-gapped Google Distributed Cloud offering keeps the AI environment inside Indian data centers.
The option targets government agencies and regulated industries such as banking, healthcare, and critical infrastructure. Local hosting may address some residency requirements, but buyers must still verify privileged access, encryption-key control, software-update procedures, and proof that data remains inside the approved environment.
Gemini moves inside the customer perimeter
Organizations can run Gemini on Google Distributed Cloud from Indian data centers. In its India AI announcement, Google said prompts, model weights, and outputs remain within the customer’s perimeter.
Supporting services operate without a connection to the public internet. Approved data and software enter through a controlled transfer process that Google calls a “physical airlock,” which is designed to limit exposure to external threats.
The architecture is a private AI platform, not an installed version of the consumer Gemini chatbot. Google made air-gapped Gemini generally available in August 2025; the July 2026 announcement extends the deployment option to Indian data centers.
Google also offers Gemini 3.5 Flash through Gemini Enterprise with in-region data storage and machine-learning processing. India-region access became generally available with an allowlist on June 30, according to the Gemini Enterprise release notes. It is a regional cloud service, not the disconnected Google Distributed Cloud installation.
The company announced related security initiatives at the same event. CAPSEM is an open-source runtime designed to isolate AI agents inside virtual machines and keep raw credentials outside their reach. Google is also giving selected government and enterprise testers, including Flipkart, access to Sec-Gemini v3 for incident investigation, digital forensics, and malware analysis.
That isolation addresses a growing concern as AI-agent permissions create security gaps when autonomous systems receive human-level access or operate without sufficient runtime monitoring.
These programs were announced separately and are not identified as standard components of every air-gapped deployment.
Device Bound Session Credentials are designed to make stolen session credentials harder to reuse on another device. DBSC remains a W3C First Public Working Draft, not a finalized standard.
Residency leaves governance questions open
Keeping data inside India addresses only part of the risk. Similar regional AI infrastructure expansions across APAC have raised questions about operational control and vendor dependence. Local hosting does not settle requirements for consent, access, retention, deletion, or incident response.
India’s sovereign AI debate also extends to service continuity and dependence on foreign model providers.
India notified its Digital Personal Data Protection Rules on Nov. 14, 2025, with major obligations taking effect on a phased schedule. Organizations must assess the deployment against those requirements and any additional rules governing their sector.
Contracts should identify who controls encryption keys and privileged access, including access to prompts, outputs, logs, and infrastructure during support incidents. Buyers should also require authenticated update packages, testing, approval controls, rollback procedures, and change records.
Organizations should require evidence covering network isolation, in-country processing, administrator access, retention, deletion, and support activity. Until Google details India-specific pricing, hardware, independent assessments, and production deployments, buyers cannot fully compare the offering’s cost, controls, or operational maturity.
Read more: India’s Gemini rollout forms part of a wider regional debate over control of critical infrastructure, including Australia’s unresolved technology-sovereignty questions.
Read the full article here
