Skip to content

Buyer Guides

Google’s Air-Gapped Search Preview Changes the Application Purchase

Assess Google’s October 20 GDC search preview by its private user workspace and the separate application scope needed for a shared team corpus.

Leviathan SystemsPublished 2026-10-204 min read

Google’s October 20, 2026 announcement puts Gemini on GDC enterprise search in preview. It introduces an integrated search application for Google Distributed Cloud air-gapped, alongside the separate availability of local models and infrastructure.[1] That changes what an enterprise can evaluate: the purchase can include the user’s document-to-answer experience, rather than ending with a model endpoint.

The decisive question is whose information that experience serves. Google’s companion architecture describes application access through identity-provider groups, with chats and uploaded files private to each user.[2] An application that admits a team can still leave the team’s shared-knowledge requirement unanswered. Buyers should match the supplied workspace and corpus to the actual information task.

A local model and a local search application supply different functions

A model endpoint gives software a way to request inference. The described search application adds user admission, document upload, retrieval, answer presentation and conversation persistence. The new announcement gives buyers a named application to assess across those functions.

Enterprise search remains a preview as of October 20. A generally available model or infrastructure item does not establish this feature’s readiness.[1] Ask the supplier which GDC air-gapped deployment and application scope the actual offer covers.

Follow the described user and document path

In Google’s account, administrators associate an application role with identity-provider groups. Membership admits users to the application. Uploads enter object storage; metadata enters managed PostgreSQL. The backend splits files into chunks, also kept in object storage, and a local embedding model represents the chunks as vectors held in PostgreSQL.[2]

For a question, the application uses conversation context to rewrite the query, embeds it, retrieves matching material and combines that material with the question and history for local Gemini generation. Google describes file citations in the answer and stored questions, answers and uploads that allow sessions to resume.[2]

These are the announced application’s functions, rather than an observed deployment result. The existing RAG-versus-fine-tuning guide explains the general information path. Here, its important boundary is the user’s workspace. A citation alone establishes neither a correct answer nor permission to receive it.

GDC-111: two admitted analysts, one private workspace

Consider fictional buying case GDC-111. Analysts A and B belong to the group admitted to the application. A uploads two invented files, Project Cedar Briefing and Cedar Options Note, into A’s chat. The enterprise separately requires B to question a shared, team-approved Cedar corpus from B’s own workspace. No actual upload, query or access test was performed.

There are three requirements to distinguish. Group membership addresses entry to the application. A’s uploads belong to the private user path Google describes. The requested shared-team function concerns which approved material B can query. Evidence for the first requirement does not establish the third.

A supplier showing how A asks about A’s two files would be demonstrating the kind of personal document task described in the announcement. That path may fit a one-user briefing requirement. The same explanation would leave B’s shared-corpus requirement to be matched to an expressly supported function in the actual offer.

The finding is an evidence gap in this comparison, rather than an observed denial to B. The published description does not establish that group membership shares A’s files, or rule out every other configuration or future feature. Ask the supplier to identify the offered shared-team function without assuming an undocumented connector or sharing route.

A private document workspace can therefore be a useful narrower purchase. A business case built around maintained common knowledge also needs an explanation of how the intended corpus reaches the intended users.

Keep adjacent platform decisions separate

The Microsoft external-key analysis concerns a compatible Azure service and its external key-operation dependency. That custody decision supplies no account of this in-perimeter search application. The Dell semantic-layer analysis concerns authoritative entity relationships used as answer evidence, a separate question from whose uploaded corpus is available to a search user.

Similarly, the disconnected GPU delivery guide addresses software artifacts and applicable licensing dependencies. Receiving the material needed to run local software and receiving a managed user-facing application are different delivery scopes. Each can matter to a project without answering the others’ purchasing questions.

Compare the actual offer with the information task

For the preview offer, have the provider connect the applicable deployment, admitted users and searchable material in one explanation. For GDC-111, record the private A-document task and the shared-team B task separately. Identify the supplied feature and responsible operating party for each; keep any unsubstantiated shared-corpus function open in the comparison.

That explanation should also say what happens when the intended team corpus changes: who supplies the approved material, who maintains its access scope and how the offered application receives the revision. A demonstration for one user can help assess that user’s task while leaving the differently scoped team requirement unresolved.

Google’s announcement creates a more specific application purchase to examine. The useful evidence connects the named preview to the enterprise’s intended users and information, with remaining work assigned explicitly.

Choosing the software does not itself establish a need for new equipment. If there is also a separately confirmed requirement for equipment receiving, rack integration, onsite installation or IT cabling, Leviathan’s Complete Physical Deployment service provides a route to discuss that physical package.[3]

Contact

Discuss Your Infrastructure Project

Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.