Controlled AI. Real results.
Run the full platform without any outside connection
For classified and isolated environments, Arqent runs fully airgapped: operators, checks, approvals and evidence stay inside your boundary, and local models do the work.
Product view
The full platform inside your boundary
Operators, independent checks, approvals, case graph and evidence storage run inside the isolated network – with local models and no outside dependency.
Platform
Runs entirely inside your network
Models
Local models in your infrastructure
Evidence
Case records and artifacts stay local
Transfer
Only what you approve, when you approve it
DEPLOYMENT
Same platform, your data boundary
What isolated teams get back
Same platform
The operators, checks and approvals you know from SaaS or on-premises – without compromise.
Local models
Models run inside your infrastructure. No prompt and no result leaves.
Local evidence
Cases, findings, reports and tool outputs stay usable inside the isolated environment.
Controlled transfer
You define what may move, when it may move and which approvals apply.
Where cloud-first AI fails
Classified and isolated environments cannot rely on cloud connectivity, external APIs or model providers outside the boundary.
Arqent runs the full platform airgapped: operators, checks, approvals, memory and evidence stay inside, and local models do the work.
ISOLATED
Local operation
The platform, its data and its operators run entirely inside your network.
MODEL BOUNDARY
Local models
Models run in your infrastructure. No prompt and no result leaves the environment.
CASE RECORD
Evidence storage
Findings, tool outputs and reports stay available inside the isolated environment.
DATA MOVEMENT
Controlled transfer
You define what may move, when and after which approval.
Use cases
Airgapped workflow
Use this pattern when intelligence work must run without any connection to the outside.
Classified environments
Airgapped intelligence
The full platform runs without any connection to the outside – with local models, local evidence storage and the same checks and approvals as everywhere else.
Explore workflowSystems and sources
What the operator does
Results
Product view
Keep case work inside the isolated environment
Analysis, tool outputs, reports, review notes and approved data transfers stay tied to the case record.
Intake
Local data and source material
Analyze
Approved local tools and models
Preserve
Evidence, notes and generated outputs
Transfer
Reviewed export when allowed
EVIDENCE TRAIL
Every result stays linked to its sources
Trust model
Built for isolated operation
Airgapped operation needs explicit control over models, data movement and evidence.
Environment boundary
Everything runs inside – nothing leaves without a decision.
- Airgapped
- On-premises
- No outside dependency
Model control
Models run where the data is.
- Local models
- Approved models
- No external provider
Evidence persistence
Outputs stay available inside the isolated environment.
- Case record
- Artifacts
- Reports
Transfer governance
Rules for data movement are set before operation starts.
- Approval gates
- Controlled package
- Audit trail
Plan an airgapped deployment
Bring your network, model and data transfer requirements into the first conversation.