Industries
Defence & public sector
Classification boundaries, accreditation, and environments where the update path is a project in its own right.
What makes this sector different
Classification boundaries
Systems that span classifications are governed by rules that assume no automated flow across them. Design has to start there.
Accreditation
Approval is a process with its own evidence requirements and its own timeline, and it is rarely compatible with iterating in production.
Genuine air gaps
Not restricted egress, absent egress. Dependency resolution, telemetry and model updates all need rethinking rather than configuring.
Long service life
Systems outlive the frameworks they were built on. Anything with a retention requirement has to be framework-independent.
Workloads that come up
- Technical documentation and standards retrieval
- Engineering change impact analysis
- Intelligence and open-source summarisation within a boundary
- Bid and requirement traceability
- Maintenance record analysis
Frameworks in play
Two patterns we deploy here
Air-gapped grounded assistant
Self-hosted quantised model over a documentation corpus, with a signed-media supply line, an internal registry and a rehearsed rollback.
Provenance-first deployment
Artefact identifiers carried across the boundary intact, deployment records tying digests to serving windows, and model identity recorded on every inference.
Start with the constraint.
Most of these projects are shaped by what you cannot do rather than what you want. Data that cannot leave the estate, a model you cannot host with a third party, a decision somebody has to justify to a regulator. Tell us yours and we will say honestly whether we can work inside it.