Skip to content
unmatrixai

Secure public-sector AI services

AI agents for government and the public sector

AI agents for government are systems that process cases, applications and enquiries against published rules, with every decision explainable and every record kept. Unmatrix AI builds them for departments and agencies on sovereign cloud or on-prem infrastructure, using open-source models where required, with engineers who work onsite for the length of the deployment.

Last updated

Workflows

What do we build for government?

The workflows we usually start with, and the architecture each one is built on.

  • Permit and licence processing

    Check applications for completeness against the published checklist, request missing items, and prepare the case for an officer.

    Built as

    LangGraph workflow agents
  • Benefits and grants casework

    Verify eligibility evidence, calculate entitlements under the rules, and route exceptions to a caseworker.

    Built as

    LangGraph workflow agents
  • Citizen enquiries

    Answer questions from policy, guidance and legislation with citations, in plain language, and hand off to a person when unsure.

    Built as

    RAG agents
  • Records and information requests

    Locate, classify and redact records for information requests, with a reviewer approving every release.

    Built as

    Autonomous agents (ReAct)

Constraints

What shapes the build?

Sovereignty and classification
Deployment on-prem or in an accredited sovereign cloud region, with open-source models for material that cannot go to a hosted API.
Explainability
Decisions that affect a person's rights carry a plain-language reason and the rule that was applied. Officers can override with a reason.
Accessibility
Citizen-facing outputs meet WCAG and plain-language standards.
Procurement and clearance
We work through your procurement frameworks, and our engineers obtain the clearances your site requires before the onsite phase begins.

Worked example

A typical build: planning permit intake

A city planning department receives thousands of applications a year. Officers spend the first week of each one chasing missing documents.

  1. 01

    Receive

    An application arrives through the portal with its attachments.

  2. 02

    Check

    The agent checks the documents against the published list, looks up zoning in the GIS and calculates the fee.

  3. 03

    Request

    Missing items generate a plain-language letter to the applicant, sent after an officer's one-click approval.

  4. 04

    Flag

    Heritage adjacency or other overlays route the case to a planning officer with the reason.

  5. 05

    Record

    The case is updated with every check, its result and the rule applied.

Officers open complete cases. Applicants hear about gaps in a day rather than a month, and every step is on the record.

Integration

Which systems do we work with?

  • Salesforce Public Sector Solutions
  • Microsoft Dynamics 365
  • ServiceNow
  • SAP
  • Esri ArcGIS
  • OpenText Content Manager
  • SharePoint

Anything with an API or a file interface can be integrated. These are the systems we meet most often in government.

Questions

What government teams ask

Can this run on-prem or in a sovereign cloud?

Yes. Most of our public-sector deployments run on-prem or in an accredited region with open-source models.

How do you make decisions explainable?

The agent records which rule it applied and why, in plain language, alongside the evidence. Officers can override with a reason, and that is logged too.

Do your engineers hold security clearances?

Our engineers obtain the clearances your site requires before the onsite phase begins. Tell us the level in the scoping call and we plan for it.

Does this replace caseworkers?

No. It removes the document chasing and checking so caseworkers spend their time on judgement and on people.

Next step

Pick one workflow. We will be at your office in two weeks.

A thirty-minute call to find the right first workflow, followed by a written scoping note. No deck, no pilot.