Defense & Intelligence

AI for defense and intelligence.
Inside your environment.

A defense AI platform for persistent agents on your infrastructure, including air-gapped environments, where you decide exactly which tools each agent may use.

Agent tool access settings: python_exec and run_command denied for this agent, other tools marked by severity with Deny buttons.
Per-agent tool access: two code-execution tools denied for this agent. Actual product UI with demo data.

Air-gapped deployment

Internal APIs and MCP

Defense and intelligence experience

01 / Your operating environment

Know what each agent could reach.

Your infrastructure, model choices, and access rules shape how the work runs. The audit profile shows what an agent could reach if it were compromised, and what still needs a decision.

  • Air-gapped operation with inference and tools inside the boundary
  • Approved API operations and MCP tools exposed per agent
  • Owners, Team access, credentials, and supported approvals
Review air-gapped deployment

Watch the blast radius demo. Inspect recorded actions and evidence coverage and the access and approval controls. Place collectors, provider ingestion, and query inside an isolated deployment or leave external routes disabled.

Agent audit profile, Blast radius tab: 9 observed, 8 reachable now, 2 dormant, and 7 critical or high paths.
Blast radius for one agent after two tools were denied: 8 paths reachable now, 2 dormant. Actual product UI, fictional data.

02 / Why security says yes

Built for the review that usually stops AI projects.

Most agent projects stall at the security gate, not on capability. Decision Terrain is designed around the three questions an approver asks first: where does the data go, can we stop it, and can we prove what it did.

01

Your environment, your models

Runs on your hardware or in your own cloud account, with models inside your boundary or a provider you already use. No connection back to Decision Terrain.

Review deployment options
02

Limits and approvals that are enforced

Deny tools for one agent, a Team, or everyone. Hold outgoing email for review of the exact message, and require approval for exact API writes. Instructions guide agents; these controls enforce boundaries.

Review security and governance
03

Stop it, and see what happened

Where enabled, place a security hold from the console or from your SIEM, released only by an authorized person. Material actions are recorded before they run and forwarded to your security tools.

Request the security review materials

03 / Work your teams can evaluate

Start with a responsibility that returns.

Agents keep instructions, files, and history, so program, technical, and analytical teams get concrete starting points to evaluate.

  • Program reporting from approved status records
  • Technical document review against defined requirements
  • Research and knowledge briefs from approved reference material
Read the defense AI readiness guide

Illustrative workflows to configure and evaluate, not claims of deployed customer results. Human owners remain responsible for the evidence.

An agent's chat reply listing three open audit evidence items, each with an owner, a status, and a source file, followed by a caveat that the sources were not verified.
An actual reply from a demo agent, fictional data. It names owners and sources, and says what it could not verify.

04 / Experience that informs the platform

Mission context. Practical engineering.

Defense and intelligence experience shapes how we approach internal systems, operating boundaries, and the people responsible for the work.

01

Understand the environment

Frame the responsibility with its users, sources, authorities, and maintenance needs.

Meet Decision Terrain
02

Make the work reviewable

Test representative assignments, including failure conditions and human checkpoints, before expanding.

Explore evaluation resources

05 / Build and implement

Your team can build on DT.

Develop capabilities with your own technical team, and add DT expertise where it helps.

01

Develop internal capabilities

Connect APIs and MCP tools, package reusable skills, and use persistent agents from your applications.

Explore developer interfaces
02

Optional DT engineers

Add DT engineers for deployment, integration, and testing in your environment.

Engineering help

Next steps

What will your team build?

Explore the platform around your systems and workflows. Your team can lead implementation, with DT engineering and support available when you need it.