01
Sovereign Deployment
Run on AWS GovCloud, Azure Government, IL5/IL6 enclaves, or your own air-gapped data center — same APIs, same control plane, full sovereignty.
Solutions · Public sectorGENEDATA / 01
Connected services.Accountable decisions.
Bring agency data and public-service workflows together while keeping access, residency, and evidence in view.
Shared context · Lineage · Governance
Connected
Your sources
Agency systems
Service records
Policy requirements
Connected intelligenceGoverned intelligence
Governance
Business impactPublic-service delivery
Shared contextLineageGovernance
02
Cleared Workflows
Multi-level security tagging, mission-partner data sharing, and a governed export path with the lineage a FOIA response has to stand behind.
03
FedRAMP-Aligned
A SOC 2 control catalogue mapped to the code that enforces each control, with evidence collected from the running system rather than assembled by hand. Government baselines are not yet mapped.
Built On
The products behind this solution.
Sovereignty and authorisation constrain every architectural choice, so the products are evaluated on where and how they run as much as what they do.
GeneFlow
Runs identically in GovCloud, IL5/IL6 enclaves, and fully air-gapped environments with the same APIs.
Learn moreGeneCatalog
Enforces classification labels in the query path and produces the continuous evidence an authorising official needs.
Learn moreCortex SQL
Serves agency analytics and records workflows inside the accreditation boundary.
Learn moreCortex AI
Operates disconnected, so mission workloads at the edge get the same capability as the enterprise.
Learn moreIndustry use-case map
Public Sector workflows across one governed operating model.
These reference workflows connect the business decision to the data, controls, platform surfaces, and people required to operate it in production.
Public SectorReference workflow
Program performance
Connect service delivery, eligibility, funding, case activity, and outcomes into a shared measure of who was served and what changed.
How the work moves
- 01
Connect the signal
Cases, benefits, and service delivery · Grants, contracts, and procurement · Agency, partner, and open data
- 02
Apply control
Data quality contracts · End-to-end lineage · Immutable audit evidence
- 03
Build and deliver
Analytics & Reporting · GeneCatalog & Knowledge · Sharing & Interoperability
- 04
Decide and act
Program leaders and oversight teams work from the same outcome evidence.
Participating roles
Platform surfaces
Business outcome
Program leaders and oversight teams work from the same outcome evidence.
Explore the full industry solutionAuthorisation Boundary
Sovereignty is a property of every layer, not a hosting choice.
Running in a government region is necessary but not sufficient. Classification tagging, cleared operator access, and the residency guarantee each have to hold independently — so that a control failure at one layer does not silently become a data-sovereignty failure.
Path to ATO
Inherit, deploy, evidence, re-authorise.
Most of the effort in an authorisation is documentation rather than engineering. Inheriting controls and collecting evidence continuously is what shortens the timeline.
Inherit the control set
Start from a SOC 2 control catalogue that names the code enforcing each control, rather than writing a control narrative from scratch.
Deploy in your boundary
Stand up in GovCloud, Azure Government, an IL5/IL6 enclave, or fully air-gapped, with identical APIs across all of them.
Collect evidence continuously
Control effectiveness is recorded as the platform runs, so the assessment package reflects the live system rather than a point in time.
Re-authorise from live data
Continuous monitoring feeds annual assessment directly, turning re-authorisation into a review rather than a re-run.
Agency Requirements
What agencies actually have to satisfy.
These are the requirements that usually disqualify a commercial platform before the evaluation gets to features.
Air-gap operation
Full functionality with no egress, including updates delivered through a controlled offline process.
PIV/CAC identity
Native smartcard authentication alongside OIDC and SAML, mapped to agency directories.
Multi-level security
Classification labels enforced in the query path so results are filtered to the requester's clearance.
Mission-partner sharing
Governed cross-agency and coalition sharing with per-partner scoping and per-query audit.
FOIA-ready export
Records assembly with redaction workflows and a documented chain of custody for responsive material.
Cleared operations
Platform operations performable by cleared agency staff, with vendor access constrained and fully logged.
Across Government
Who this is for.
Civilian, defense, and oversight functions want different things from the same authorisation boundary.
Civilian Agency
Modernise without a new ATO cycle
Deploy inside an existing accreditation boundary with inherited control mappings rather than starting a fresh authorisation.
Months of assessment effort avoided.
Defense / Intel
Operate disconnected
Run the full platform in an IL5/IL6 or air-gapped enclave, with classification enforced at query time rather than by policy alone.
Same capability at the edge as in the enterprise.
Inspector General / Oversight
Answer from the record
Respond to FOIA and oversight requests from a per-query audit trail rather than reconstructing access after the fact.
Requests answered with documented provenance.
What Changes
What changes with sovereignty built in.
Commercial platforms retrofitted for government tend to lose capability at exactly the classification levels that matter most.
| Dimension | Before Genedata | With Genedata |
|---|---|---|
| Deployment | Commercial region only, or a reduced government edition | GovCloud, IL5/6, or air-gap with identical APIs |
| Authorisation | Control narrative written from scratch | Inherited mappings to FedRAMP-aligned and NIST 800-53 |
| Evidence | Assembled ahead of each assessment | Collected continuously from the running system |
| Classification | Enforced by process and user discipline | Labels enforced in the query path |
| Vendor access | Support requires broad operator reach | Cleared agency staff operate; vendor access is scoped and logged |
Per-control, collected from the systemEvidence
GovCloud · Sovereign · Air-gapDeployment
PIV/CAC · OIDC · SAMLIdentity
Per agency policyAudit Retention
The next step
Mission-critical data, on infrastructure cleared for the mission.
Genedata Public Sector lets agencies modernize without compromising on sovereignty, compliance, or operational tempo — the same platform civilian and defense teams already trust.
FAQ
Public sector, answered.
What authorising officials, security, and procurement ask.
Can the full platform run air-gapped?
Yes, with complete functionality and no external connectivity, including a controlled offline process for updates and patching. Disconnected operation is a supported deployment mode rather than a degraded one.
What control mappings are available?
A SOC 2 control catalogue mapped to the code enforcing each control, with per-control evidence collected from the running system. Government baselines (NIST 800-53, 800-171, CJIS) are not yet mapped — which lets an assessment inherit rather than author a control narrative from scratch.
How is classification enforced?
Multi-level security labels are enforced in the query path, so results are filtered to the requester's clearance by the engine rather than by process and user discipline.
Who operates the platform in a classified environment?
Cleared agency personnel. Vendor access is scoped, approved, and logged, and is not required for day-to-day operation.
Does this support mission-partner sharing?
Yes. Cross-agency and coalition sharing is scoped per partner with per-query audit, so what a partner saw is a matter of record.
Related content
Compliance
ATO Documentation Pack
Control mappings, SSP templates, and continuous monitoring evidence.
ArchitectureSovereign Deployment
GovCloud, IL5/IL6, and air-gapped reference architectures.
GuideMission-Partner Sharing
Scoped cross-agency sharing with per-query audit.
RelatedSecurity
Key custody, zero-trust model, and the tamper-evident audit chain.
Take the next step
Start inside your boundary.
Review deployment options and control mappings against your authorisation timeline.