GOVERNED AGENT RUNTIME FOR PUBLIC SECTOR
Deploy AI agents in sovereign, air-gapped, and mission-critical workflows.
For government agencies, defense-adjacent institutions, and any organization operating under sovereignty mandates, FedRAMP-aligned controls, or NIST 800-53. Air-gap deployment as first-class; data residency verified in-region; every agent action authorized against policy in-process; audit evidence signed and offline-verifiable.
Why this matters now
Public-sector AI adoption is not blocked on capability — it is blocked on the substrate that keeps data inside a national boundary, produces evidence that survives adversarial audit, and does not depend on a US-owned SaaS provider for its continued operation. The specific defect that stops most agentic pilots in government is not model quality — it is the inability to answer "where does the data go, who authorized this action, and can we operate this without external dependency."
Orkena is designed for exactly that posture. The air-gap deployment mode is not a downgrade; it is the primary path for public-sector engagements. Feature parity across SaaS (region-pinned), customer VPC, and air-gap is a first-class product commitment, from a single Helm chart.
How Orkena maps to the public-sector regime
| Regulation / requirement | What it requires | What Orkena provides |
|---|---|---|
| FedRAMP Moderate / High (US federal) | Continuous monitoring, access controls, incident response, audit trail | Continuous ledger event stream; per-user access with RLS; kill switch; multi-region DR posture |
| NIST SP 800-53 | Comprehensive security controls | Aligned to the NIST AI RMF mapping published in /compliance; an SP 800-53 control mapping is available to public-sector design partners on request |
| DoD IL5 (defense-adjacent) | Isolation, sovereignty, air-gap | Air-gap deployment mode is first-class; single Helm chart across SaaS / VPC / air-gap |
| EU sovereignty (EUCS) | European cloud, European operator, no US CLOUD Act exposure | Deployment in EU regions with EU-registered operator; VPC or air-gap options for full sovereignty |
| GCC / MENA sovereignty | In-region deployment; local KMS; no cross-border data movement | Managed region-pinned tier (roadmap); VPC in customer's own cloud; air-gap for the strictest cases |
| UK GovAssure / SC-cleared workflows | Documented control framework | Control mapping to UK Government Security Classifications; VPC / air-gap deployment |
Honesty note: Orkena is not FedRAMP authorized today. FedRAMP authorization is a multi-year process; readiness work is planned. For pre-FedRAMP engagements, Orkena is deployed in customer-controlled infrastructure (VPC or air-gap) — the mode most public-sector buyers will require anyway.
Four public-sector use cases Orkena runs today
1. Benefits eligibility triage.
Agent evaluates incoming benefits applications against policy, proposes decision, escalates to human caseworker for edge cases. Four-eyes for any denial. Complete audit trail for FOIA-eligible records.
2. Regulatory response drafting.
Agent drafts responses to regulator inquiries based on internal policy and case history; drafts never reach a system of record without human approval. Full deterministic replay for any inquiry response.
3. Intelligence analyst assistance (defense-adjacent).
Agent enriches classified intelligence products with retrieved sources; every retrieval logged; every source cited in the final product; complete audit trail air-gapped.
4. Public-service chatbot with mandatory citation.
Agent answers citizen questions; every answer must cite a source document; policy denies unsourced answers; audit trail for every citation for external oversight.
For each: authorize before execution, evidence in the same transaction, deterministic replay, evaluation-gated updates.
The demo you will see
- Air-gap deployment. Orkena runs the entire demo in an air-gapped environment — no outbound connectivity, local embedder, local classifiers, local models where possible. The same feature set as the VPC deployment.
- Data residency demonstrated. An agent attempts a cross-region call; the policy engine denies it based on data-residency labels. The denial is recorded with the specific residency rule that fired.
- Deterministic replay. A completed run is replayed step-by-step; every non-deterministic input reproduced from the ledger. Model-risk officers and external auditors get exact reproducibility.
- Evidence bundle verified offline. The bundle verification is dependency-free; runs on a fresh machine with no network access; produces a byte-level answer.
What Orkena is not for you (in public sector)
- Not FedRAMP authorized today. For agencies requiring FedRAMP authorization for a SaaS vendor, Orkena is deployed in the agency's own infrastructure (VPC / air-gap), where FedRAMP does not apply to Orkena as a vendor. FedRAMP readiness for future SaaS engagements is planned.
- Not a classified-processing service by Orkena. In air-gap deployments, Orkena has no access to your data, ever. All operation is by your team on your infrastructure.
- Not a substitute for the agency's own AI risk assessment. Every AI deployment in public sector requires an AI Impact Assessment or equivalent; Orkena produces the evidence that supports one, not the assessment itself.
- Not offering a self-service SaaS tier for public-sector. All public-sector engagements begin with a scoping conversation.
Ready for the conversation?
Also read:
- What is a Governed Agent Runtime — the category essay
- Technical brief — architecture deep-dive
- Compliance mappings — NIST 800-53, FedRAMP-aligned controls, sovereignty options
- Trust centre — sub-processors, deployment options, data residency
- Air-gap deployment and Incident response — kill switch — the two docs a sovereignty-focused reviewer asks for first
Not in public sector? See how the same runtime maps to fintech and healthcare, or browse all verticals.
Public sector is Orkena's Wave 3 vertical. Engagements typically begin with a technical evaluation in the agency's own environment.
▸ sales@orkena.com