Multi-modal sensing
Normalize video, thermal, RF, telemetry, access, and operational signals without flattening their provenance.
Sovereign infrastructure
Scutum
Sovereign Infrastructure Defense Operating System.
Research thesis
When infrastructure is under pressure, command cannot fragment.
Scutum is building the accountable command layer between complex infrastructure signals and the people responsible for acting on them.
It brings sensing, decision support, authorization, simulation, and evidence into one sovereign operating layer while keeping authority with accountable human operators.
03Mission-cycle stages
Sense, authorize, validate
06Platform capabilities
Sensing through evidence custody
03Mission environments
Ports, energy, airspace
SINGLETenant model
Designated sovereign boundary
The continuity gap
Critical infrastructure still asks operators to assemble the mission picture while conditions are changing.
Sensors, dashboards, procedures, approvals, and operational context often remain fragmented even though the decision they inform is one decision.
Critical environments still ask operators to piece together fragmented sensors, dashboards, procedures, and approvals while the situation is changing.
Scutum exists to create a shared mission picture, keep authority with accountable humans, and make every important decision inspectable.
The mission cycle
From signal to sanctioned action.
A continuous operating loop gives teams clarity without removing judgment.
Sense and fuse
Fuse video, thermal, RF, telemetry, and operational context into one mission picture while preserving source provenance.
Decide and authorize
Surface candidate courses of action with rationale, confidence, constraints, and policy context while accountable operators retain authority.
Validate and audit
Exercise the proposed response against a mission model and preserve the decision record for review.
ScutumOS
One operating layer. Full mission context.
A shared model carries context from first observation through the authorized decision and into the evidence record.
Mission graph
Connect every observation to the assets, zones, policies, incidents, and people that give it meaning.
Decision support
Rank practical courses of action and show the rationale, confidence, constraints, and likely impact.
Policy authorization
Bind approvals to identity, mission state, delegated authority, and explicit operational rules.
Twin validation
Exercise a proposed response against a mission model before an operator chooses to proceed.
Evidence custody
Preserve a tamper-evident chain across source events, recommendations, approvals, and outcomes.
Sovereignty is architecture
Deployment, identity, data, and evidence remain under designated control.
The sovereign boundary is part of the system design rather than a hosting label applied after deployment.
- Deployment
- Single-tenant
- Identity
- Customer-controlled
- Network
- Isolated
- Evidence
- Local custody
A deployment model intended to remain within the designated sovereign environment.
Identity and delegated authority remain within the customer's designated control boundary.
Network isolation and policy enforcement are designed into the deployment architecture.
Mission evidence remains within the designated evidence-custody boundary.
Mission environments
Built where infrastructure meets national consequence.
The programme distinguishes its primary pilot wedge from broader platform design and supported detection scope.
Ports and maritime continuity
The primary pilot wedge: unify perimeter, vessel, drone, cargo-zone, fuel-area, and access signals around the operating picture that keeps a port moving.
Energy and operational technology
Platform design scope: bring physical security, OT telemetry, work authorization, and safety context together while respecting high-consequence control boundaries.
Airspace and remote borders
Supported detection scope: correlate restricted-airspace observations, perimeter approaches, identity, remote-site readiness, and observe-only counter-UAS metadata into a human-commanded workflow.
Open foundations
Critical primitives should be inspectable.
Inspectability and clear interfaces strengthen trust across the engineering ecosystem.
Open schemas
Expose clear contracts for the mission events, context, and evidence structures that integrators need to inspect.
Policy tooling
Provide inspectable foundations for representing operational rules, delegated authority, and policy gates.
Evidence libraries
Support traceable records across source events, recommendations, approvals, simulations, and outcomes.
SDK and deployment foundations
Give integrators defined interfaces for building against the platform and its sovereign deployment boundary.
Design-partner evaluation
A controlled path from mission question to evidence.
Frame the mission
Define the infrastructure, decision rights, operational thresholds, and acceptable response boundaries.
Connect the signals
Map the available and simulated sources that matter, then preserve their identity and provenance.
Exercise the workflow
Run controlled scenarios through recommendation, authorization, validation, and review.
Preserve the evidence
Package mission evidence so operators and stakeholders can inspect what the controlled workflow recorded.
Research stage
A working lab foundation, prepared for controlled pilot evaluation.
Scutum describes a reproducible hardware-first software MVP spanning mission events, policy, simulation, hardware readiness, audit evidence, SDKs, and sovereign deployment tooling.
The next phase is controlled evaluation with design partners. Production deployment, field validation, certified security controls, and operational use remain outside the present validation scope.