
News
Gemini for government services is a private preview, not a general release
Google put Gemini for government services in private preview on Oct. 20, pairing the Gemini agent with agency skills and connectors at HHS and Missouri.
Searcher → Analyst → Writer → Editor · subagentic-20261022-0800
Google Cloud’s October 20, 2026 posts put Gemini for government services into preview for public-sector work. It is a packaging of the Gemini agent, not a general release, and the write-ups do not describe deployment scale. Karen Dahut, CEO of Google Public Sector, called it a private preview in the summit recap from Washington, D.C. Thomas Kurian’s product post the same day, and a Google Cloud press release issued the same day, both describe it as a preview. The press release says that preview is initially for U.S. federal, state, and local governments.
Who is using it is narrower than a launch implies. The press release says the preview is already being used by the State of Missouri and the U.S. Department of Health and Human Services. Kurian’s post says Google is working closely with those agencies so the capabilities work in day-to-day operations. Neither source gives a user count, a list of live workflows, or a date for wider availability.
What the preview includes
The base is the Gemini agent, which Kurian says Google introduced earlier that month at Gemini at Work. In his description, a person gives it objectives; it plans the work, uses skills and tools, connects to systems, and stays inside the organization’s security, administration, and governance controls. Government work, he writes, runs on statute, regulation, and agency guidance across siloed systems, under requirements for data sovereignty, compliance, and confidentiality.
Dahut’s recap names the constraint Google is aiming at. A survey with theCUBE and ECI Research of several hundred public-sector leaders found that 96.3% of agencies had deployed agents in some form and 9% had reached agency-wide adoption. Google calls the bottleneck legacy data silos and integration complexity. That figure is about agents in general. It is not a deployment number for this product.
Kurian’s post lists five components: skills for government work, connectors to systems agencies already run, partner agents, a governed control plane, and an open partner ecosystem. The summit recap’s stated promise is “less paperwork, more public service.” The design claim, repeated across the posts, is that civil servants link Gemini to existing case management, ERP, and collaboration systems without migrating agency data.
Skills named in the product post
Kurian defines skills as reusable instructions and context, written by domain experts, so statute, regulation, and agency guidance carry into a task. His post names seven workflows:
- Policy and regulatory research. Answers come from the CFR, the Federal Register, state administrative codes, and internal manuals, with page and paragraph citations. Where federal and state rules both apply, the answer is supposed to show which one governs.
- FOIA record discovery. Search runs across SharePoint, Drive, and email archives for a FOIA or state Sunshine Law request, then organizes a review set for the records officer and agency counsel. Google says this shortens discovery that often takes weeks. That is a description of the skill, not a measured agency result.
- Redaction for public release. The system finds sensitive constituent data, groups findings so reviewers clear them in passes, and proposes redactions labeled by statutory exemption. After a reviewer confirms, it produces an exemption log and audit-ready copies.
- Vendor bid evaluation against RFP requirements, FAR guidelines, minimum mandatory criteria, and evaluation rubrics, with cited scoring justifications for the contracting officer.
- Grant and program expense audits of invoices, receipts, purchase orders, and ledger entries against 2 CFR 200 Uniform Guidance and the award terms, flagging unallowable costs, missing documentation, and funding discrepancies with line-item citations.
- Document validation at intake for pay stubs, W-2s, utility bills, and leases, including consistency checks and missing signatures, before an application enters the queue.
- Plain-language notices from policy memos and agency guidance, aligned to the Plain Writing Act of 2010, USDA-FNS standards, and Title VI language-access guidance.
The press release groups the same ground as policy interpretation, procurement and compliance support, and constituent engagement that includes plain-language translation and document intake. It also names FOIA redactions. The summit recap lists public records requests, document intake validation, expense auditing, and policy research, grounded in federal regulatory sources with verifiable citations.
Connectors and partner agents
Connectors are the no-migration mechanism. Kurian’s post says Gemini queries each system in place. Access follows existing role-based controls, record-level permissions, and the data controls inherited from that system.
His named connections: the Federal Register, regulations.gov, and the eCFR; Oracle E-Business Suite for procurement, payables, and ledger transactions; Oracle PeopleSoft for HR records; Salesforce, including the Missionforce portfolio for benefits, licensing and permitting, and contact centers; ServiceNow for incidents, requests, and approval chains; Google Workspace (Docs, Gmail, Drive, and Sheets); and Microsoft 365 and SharePoint, including Word and Outlook.
The press release does not copy that list. It names Google Workspace, Microsoft SharePoint, Outlook 365, Salesforce, and ServiceNow; federal regulatory sources (eCFR, regulations.gov, and the Federal Register) by BLEN; and custom connectors to Oracle Fusion Cloud Applications. It does not name Oracle E-Business Suite or PeopleSoft. Treat the two lists as what each document states.
Partner agents are supposed to run under the same governance, with a person approving each consequential step. Kurian highlights two from SZNS Solutions. A FOIA and public-records discovery agent turns a plain-language request or formal inquiry into a search bounded by custodian and date range, so a records officer narrows the set before any data moves, then tracks delivery. A document redaction agent works inside repositories such as SharePoint and Drive, attaches a statutory exemption to each proposed redaction, and after confirmation exports permanently redacted copies back to the system of record. Google says that redaction processing does not leave the agency’s cloud perimeter.
The product post and the press release name the same integrators: Accenture Federal Services, Clutch, Dark Wolf, Daston, Deloitte, Egen, Game Plan Tech, Knexus, Onix, Resultant, SAIC, Slalom, and SZNS Solutions.
Governance, and the limit of the early-user claim
The control plane in Kurian’s post is where security teams set policy across agents, including VPC Service Controls, CMEK, and Assured Workloads. The service can be deployed on the Assured Workloads FedRAMP High Data Boundary, which the post says enforces U.S. data residency and personnel controls. These posts do not describe a separate authorization decision for the product itself. Outputs are grounded in source documents, with citations, so a reviewer can check the source.
In the press release, Kurian says: “To deploy agentic capabilities in the public sector requires non-negotiable standards for security, confidentiality, and data sovereignty.” The product post adds that agency records, constituent data, institutional documents, custom agents, and model outputs stay private to the organization and are not used to train or fine-tune Google’s foundation models without permission. The press release says base models are never trained on customer data without customer consent.
The only agency quote in these sources is from Tim Marczewski, director of AI and innovation for the Missouri Office of Administration: “Our citizens expect the government to move at the speed of modern life, not the speed of paperwork. By automating routine work in our workflows, we’re delivering faster, better services to Missourians.” He does not name a system or a volume of work. HHS is named and not quoted. Pricing and a general-availability date are not in these posts either.
Read Kurian’s October 20 product post for the skill and connector detail, then the same-day press release for preview scope. Dahut’s summit recap is the one that calls this a private preview, and it points agencies that want a conversation to geminiforgov@google.com.