Security & Trust
Built to be trusted with the hard problems.
The architecture starts from a single assumption: the data cannot leave, and the network is not there. Everything else follows from that.
No data egress
Nothing is transmitted, logged off-box, or sent to a third party. The system has no outbound network path by design.
No telemetry
No analytics, no usage beacons, no model phone-home. What runs on the device stays on the device.
U.S.-origin models
The deployment path uses U.S.-origin foundation models. No foreign-origin models touch sensitive material.
Operator-controlled
You own the hardware, the data, and the update cadence. Updates arrive as signed packages on removable media.
Compliance roadmap
Where we are, and where we're headed on controls and authorization.
- Complete
Architecture
Air-gapped by design
Full stack runs disconnected on operator-controlled hardware. No telemetry, no external dependencies, no data egress.
- In progress
Posture
Controls & supply-chain hygiene
Mapping to NIST 800-171 / CMMC controls and maintaining a U.S.-origin model supply chain - no foreign-origin foundation models in the deployment path.
- Planned
Authorization
FedRAMP High path (hosted option)
For teams that want a hosted enclave, a FedRAMP High authorization track on government cloud - kept fully separate from the air-gapped on-prem product.
Data handling
Source material, translations, extracted entities, and generated briefs are written only to storage the operator controls. There is no external processing step, no third-party sub-processor, and no retention outside the perimeter. Deletion is immediate and local.
Accessibility
We build toward Section 508 / WCAG 2.1 AA conformance - keyboard-navigable interfaces, sufficient contrast, and screen-reader-friendly structure - so the tooling is usable across the full analyst workforce.
