Security
Trust built into the architecture, not bolted onto the policy.
EdgeLance runs where an adversary can jam, spoof, capture, and impersonate. Every layer assumes it, from who can join the mission to which sensor report the tracker will believe.
Defense in depth
Every layer fails closed.
Identity and access
Every service entry point checks role and mission. Unknown roles are denied, not defaulted. Operators check in by biometric, badge, or session, and access ends when the mission does.
Least privilege between components
Each mission block gets its own credentials and may publish and subscribe only to the topics it needs. A compromised camera feed cannot issue a task.
Signed orders
Plan tasks are signed when approved and bound to their mission. Execution accepts only signed requests, so a forged or replayed directive is refused.
Trusted inputs
The tracker validates every observation against the mission schema and rejects untrusted, foreign, backdated, and downgrading reports. A spoofed sensor cannot take over an established track.
Device trust
Devices are enrolled and approved before they join the mission mesh. Posture is tracked, and any node can be revoked at once.
Model trust
Only approved models run. Each answer records which model produced it and on what sources, and policy decides what runs on which device at which classification.
Complete control of intelligence
Own it, use it, destroy it, and prove all three.
The government owns the data
Mission data, models, prompts, outputs, and the record stay with the customer. Nothing phones home.
Provable deletion
When a mission ends, the burn destroys the encryption keys and everything under them, including data derived from it for AI search. A signed receipt proves what was destroyed and when.
The record survives the burn
The signed after-action record outlives the mission data. Together they show when intelligence was created, what grounded it, who saw it, and when it was destroyed.
Every decision attributed
Approvals, overrides, dispatches, and AI recommendations are logged to a person and a time in an append-only record.
Delivery and accreditation
Ready for the networks you actually run.
Air-gapped install
EdgeLance installs into disconnected Kubernetes environments from one signed package. Each mission block is an optional component, so a deployment carries only what the mission needs.
Hardened runtime
Containers run with read-only root filesystems and per-component broker credentials drawn from a single managed secret.
Accreditation artifacts
Each release produces its software bill of materials, control mapping, and provenance attestation from the same build that produces the software.
Works with your process
EdgeLance fits existing ATO, STIG, and customer security processes rather than working around them.
Security review
Bring your security team.
We walk your reviewers through the architecture, the package, and the controls.