Passive Multi-Modal C-UAS Detection & Persistent Track
Commercial referenceDEF-026
Quote DEF-026 when requesting information, licensing, technical review, or acquisition discussion.
Who this is for
Passive C-UAS program managers and force-protection leads needing persistent-track evidence without active emission.
The problem you already have
A drone going radio-silent shouldn't make it disappear from the display
A small UAS can stop transmitting its control-link signal — autonomously, pre-programmed, or deliberately, specifically to evade RF-based detection. A system that treats loss of RF as loss of the track drops custody at exactly the moment the threat is trying hardest to avoid it.
Passing behind a building shouldn't count as evidence the track is gone
When a track enters a known visual occlusion region, a system that only trusts continuous positive detections reads the resulting gap as a negative signal — instead of recognizing that no detection was possible there in the first place.
This works from detection logs, not live sensor-emission control
Never requested, and structurally rejected if submitted: live sensor-emission control, classified sensor-network placement, or defeat-system access.
Real-World Operational Scenario: The Drone That Went Silent and Didn't Disappear
Scenario: A small UAS being tracked via RF, acoustic, and EO/IR sensors cuts its control-link signal mid-approach.
The RF emission that was helping localize the drone simply stops — a common evasion tactic against RF-centric detection.
WITHOUT this check: A system built around RF as the primary modality treats the loss of signal as the track disappearing. The operator watches the threat vanish from the display at exactly the moment it went stealthy — the worst possible moment to lose custody.
WITH this check: RF modality state is explicitly marked as unsupported rather than declaring the whole track lost. Acoustic and EO/IR observations continue updating the same persistent track, so the drone stays tracked through the exact tactic that was supposed to defeat detection.
What you provide
Redacted passive-sensor detection and track-confidence logs already produced by your C-UAS sensor network.
What BivectorAI Provides
Losing One Modality Doesn't Mean Losing the Track
When RF, acoustic, or visual support drops out, that specific modality is marked unsupported — the track itself continues on whatever modalities remain, rather than being declared lost.
A Predictable Gap Isn't Treated as Negative Evidence
Terrain occlusion and known coverage gaps are distinguished from a genuine loss of detection — the track coasts through a predictable gap and reacquires within an expected region rather than resetting from zero.
Sensor Cells Hand Off Tracks Without Sharing Raw Data
As a drone moves between coverage areas, one sensor cell can pass a compact track summary to the next without exporting raw RF signal or full-resolution imagery.
Hash-Sealed Certificates for Post-Event Review
Every track-confidence and modality-support classification traces back to the exact detection evidence that justified it at the time.
Redacted passive-sensor detection and track-confidence logs already produced by your C-UAS sensor network.
What BivectorAI actually hands you
Evidence package
- track-confidence classification
- handoff and uncertainty evidence
- emission-constraint compliance records
- reviewable tracking certificates
Integration package
Customer-safe input/output contract, local/private integration boundary, validation fixtures and reviewable evidence artifacts.
Deployment model
Qualified local, private or on-premise integration. No public Defense API and no uncontrolled public execution surface.
Technical disclosure
Customer-visible behavior and evidence are disclosed. Confidential implementation details, protected core methods and internal technical data are not published.
What we will never ask you for
Never requested, and structurally rejected if submitted: live sensor-emission control, classified sensor-network placement, or defeat-system access, or your system's core design data. Every submission is checked against this rejection list before any evidence logic runs — a malformed or over-broad submission is blocked and reported back to you, not silently processed.
How it actually runs
Engagement path & current acquisition terms
DEF-026 · Tier C — Strategic Sensing / Infrastructure
Secures a defined diligence and exclusive-negotiation period. Any option credit is agreed in writing as part of the signed commercial terms.
Starting integration engineering, customer-safe adaptation, local/private deployment work, validation and acceptance evidence for the agreed environment.
Scope-dependent consideration for negotiated exclusivity in a defined field, program, platform class, territory and rights scope.
Engineering support, update access, security maintenance, evidence infrastructure and agreed sustainment services.
Applied to attributable net program revenue under the definitive agreement, subject to negotiated exclusions and accounting rules.
Commercial boundary. These are indicative starting terms, not a binding offer. Final price depends on exclusivity scope, field of use, territory, sublicensing, technical-data rights, integration obligations, export-control review, support requirements and definitive agreement.
IP boundary. Exclusive FOU does not automatically transfer ownership of BivectorAI Background IP. Worldwide/all-defense rights, sublicensing, source-level technical-data rights or assignment require separate negotiated consideration.
Technology licensing only
No public API is represented for this technology.
Engagement begins through NDA, technical diligence and a negotiated controlled-access or licensing structure.
Rights structure
Exclusive rights are defined by field of use, program scope, territory, term, sublicensing and technical-data rights. Underlying BivectorAI Background IP remains owned by BivectorAI unless expressly assigned.
Annual sustainment
May include updates, integration support, security maintenance, evidence infrastructure, validation support and agreed engineering services.
Revenue participation
Applied to attributable net program revenue under a definitive agreement with negotiated exclusions, reporting and audit terms.
Scope the DEF-026 diligence and integration boundary
Request DEF-026 Acquisition Discussion →Email fallback: contact@bivectorai.com
Defense technology is integrated through qualified local/private engagement. No public Defense API and no automated Defense checkout are provided.