Google Public Sector introduced Gemini for government services on October 20 at its Washington summit. The pitch is deliberately unglamorous: take the paperwork of public service, the records requests, the intake piles, the expense audits, and hand the repetitive parts to agents. Google’s own phrase for the promise is less paperwork, more public service
. What actually arrived is a private preview, with no public price and no date for general availability.
Per Google’s summit recap, the platform combines pre-built partner agents, secure connectors, and deterministic skills, and it links Gemini to the case management, ERP, and agency collaboration systems that agencies already run, without migrating sensitive data out of them. The named work is specific: public records requests, document intake validation, expense auditing, and policy research grounded in federal regulatory sources, with citations attached.
The part doing the selling is the governance layer. When the Gemini agent arrived as a preview earlier this month, the finished thing was the stack around it: attested per-agent identity, agent-attributed audit logs, sandboxed execution, and policy enforced once at the network boundary. The federal version leans on the same wrapper. One claim worth narrowing before it hardens: this tool is not, on Google’s own say-so, FedRAMP High and Moderate authorized. A January post on Gemini for Government says the platform includes FedRAMP High-authorized security and compliance features, and the summit’s actual FedRAMP headline sat next door: Wiz for Gov runs in a FedRAMP Class D (High) certified environment. FedRAMP is the federal security review that cloud products have to clear before agencies can put them to work. The October 20 materials for the new add-on never name an authorization level for it.
Who is actually on it is a fair question, and Google’s answer mostly names work it already had. The Chief Digital and Artificial Intelligence Office picked Gemini for Government as the first enterprise AI on the Department of War’s GenAI.mil, which Google says reaches about 3 million civilian and military personnel. The FDA is deploying agentic AI across the agency. The Department of Energy’s Genesis Mission and the Army’s logistics modernization are on the list too. None of those is a named launch partner for Gemini for government services itself. Google named no agencies running the new product.
Google also commissioned a survey, through theCUBE and ECI Research, of several hundred public sector leaders, and its own numbers frame the opportunity. 96.3% of agencies have deployed agents in some form. 9% have reached agency-wide adoption. Karen Dahut, CEO of Google Public Sector, puts the gap this way: The bottleneck isn’t a lack of vision or ambition
, she says, it is the systemic friction of legacy data silos and integration complexity.
Now the money question, which nobody has answered with a price. Google’s entry sits in a market where the other sellers have each chosen a different way through the door. OpenAI’s OneGov deal puts ChatGPT, Codex, and API access in every federal, state, local, and tribal agency at $0 per user per month for 27 months. The Gemini Launchpads partnership with Accenture Federal Services puts 1,000 forward-deployed engineers behind the installation work, with pre-built agents for HR, finance, and supply chain. Google’s launch materials quote Thomas Kurian, CEO of Google Cloud: To deploy agentic capabilities in the public sector requires non-negotiable standards for security, confidentiality, and data sovereignty.
The deadline doing the pushing is January 1, 2027, when the FedRAMP Consolidated Rules become mandatory. The paperwork is not trivial. Authorization can take 12 to 36 months and cost upwards of $3.5 million, and a May 2026 USDA inspector general report found 73 of 82 operational AI use cases went live without an Authority to Operate, the formal permission to run a system in a federal environment. That is the lived version of this story. A caseworker staring at a records queue may get hours back, and somebody still has to sign for what an agent did to a citizen’s file. The tools that answer that question are arriving before the prices are.
So the preview stays the headline. What is still missing is what procurement needs most: a price, a general-availability date, the product’s own authorization status, and a single agency willing to say it is running the thing. The calendar is not waiting for any of them.
