---
title: "Government"
description: "Document Processing extracts applicant data from benefits and permit forms. Drex checks each requirement and routes complete files to the right office. Both run on-premises and fully air-gapped."
canonical: "https://nace.ai/industries/government"
updated: 2026-11-06
---

# Government

> Document Processing extracts applicant data from benefits and permit forms. Drex checks each requirement and routes complete files to the right office. Both run on-premises and fully air-gapped.

## Applications extracted, checked and routed, inside your walls.

Document Processing extracts applicant data from benefits and permit forms. Drex checks each requirement and routes complete files to the right office. Both run on-premises and fully air-gapped.

Runs on: Document Processing (reads), Drex (decides).

| Value | Result | Source |
| --- | --- | --- |
| Air-gapped | deployment, with nothing leaving your network | [Deployment options](https://nace.ai/developers) |
| Open weights | for Drex 2.0, on a single accelerator | [Drex benchmarks](https://nace.ai/drex) |
| <200 ms | model latency per decision, not end-to-end workflow time | [Drex benchmarks](https://nace.ai/drex) |

## Backlogs grow when every application is read by hand.

Benefits, permits and records requests arrive on paper and in every format. Nace extracts them, scores them against the rules and routes complete files, all on hardware you control.

## Where Nace fits

Each workflow names the model that does the work.

| Workflow | What it does | Model |
| --- | --- | --- |
| Application intake | Applicant and case data extracted from benefits and permit forms, scanned or digital. | Document Processing |
| Eligibility pre-check | A per-rule score on whether an application meets each requirement, for a caseworker to confirm. | Drex |
| Case routing | Each application sent to the right program, office and queue. | Drex |
| Redaction decisions | A call on whether each passage holds personal information that must be redacted. | Drex + Document Processing |
| Records digitization | Decades of archived paper turned into searchable, structured records. | Document Processing |
| Procurement bid review | Pricing, terms and compliance items extracted from every bid, side by side. | Document Processing |

## Permit applications, end to end

1. Application in: Forms and site plans
2. Document Processing reads: Every field, cited
3. Drex decides: Checks each requirement
4. Your reviewers: Get complete files only
5. Drex for Search finds: Any past permit, cited to its page

What it reads: Benefits applications, Permit applications, Paper forms, Archived records, Procurement bids, FOIA requests, Correspondence.

## Runs where your data already lives.

Same models and the same API at every tier. Only the boundary around your data changes.

- Managed Cloud: Our GPUs, our API, a key from Console.
- Dedicated Cloud: Your own cluster in our cloud, reached over private links.
- Your Cloud: Installs in your AWS or Azure account. Data stays inside.
- On-Prem & Air-Gapped: Your datacenter, your hardware, zero outbound.

SOC 2 Type II audited. [Visit the Trust Center](https://trust.nace.ai).

## See it on your own files.

Send us a file and the decision you make on it. We'll show you the result on your own documents.

- [Get started](https://console.nace.ai/?utm_campaign=industries&utm_content=industry-government_md&utm_medium=website&utm_source=nace.ai)
- [Talk to sales](https://nace.ai/contact?source=industry-government)

Related industries: [Legal](https://nace.ai/industries/legal) · [Healthcare](https://nace.ai/industries/healthcare) · [Construction](https://nace.ai/industries/construction)

## For agents

- [Drex API guide](https://nace.ai/drex.md): the decision model: request shape, question types, benchmarks and deployment, as markdown
- [Decision endpoint](https://console.nace.ai/v1/systemone): POST with model "drex-latest", a state string and typed questions (choice, noul, score); https://console.nace.ai/v1/models lists checkpoints
- [Document endpoints](https://console.nace.ai/v1/documents/{parse|split|classify|extract|ground}): POST a source (a public URL, an uploaded workspace file or a finished parse job) and poll GET https://console.nace.ai/v1/documents/jobs/{id}; the same key and credit as decisions
- [Console](https://console.nace.ai): API keys, the playground, usage and billing; send `Authorization: Bearer $NACE_API_KEY` on every request
- [Console docs](https://console.nace.ai/docs): quickstart, question types, the document routes, errors, limits and pricing
- [Nace Document Processing](https://nace.ai/perception.md): the Perception series: parse, split, classify, extract and ground any file type with a location on every value
- [Drex for Search](https://nace.ai/drex/search.md): Drex for Search: decision-powered retrieval for agents, Drex finds the page, cited search through the CLI, SDKs, MCP and REST, and the public benchmark ranks
- [Industries](https://nace.ai/industries.md): Nace by industry: the files Document Processing reads and the decisions Drex makes for accounting, banking, mortgage, insurance, legal, healthcare, government, construction, logistics and professional services
- [Developers](https://nace.ai/developers.md): The execution layer for agents: Perception, Decision and Search behind one key, the Drex Max frontier, install steps, a scripted agent session and the four deployment boundaries
- [Site index](https://nace.ai/llms.txt): every page on nace.ai; append `.md` to any page URL or send `Accept: text/markdown` for the markdown version