Counter-UAS Command and Control
SkyNet is site-level counter-UAS (counter-unmanned aircraft systems — defense against drones) command and control software, developed to detect, classify, track, and direct the response against unmanned aerial threats — protecting military installations and critical infrastructure with the commander setting the rules of engagement.
In Plain Language
A military base or a power plant usually has several systems watching the sky — a radar, some cameras, maybe a microphone array and a radio detector. Each one was bought separately, each sends its own alerts, and none of them talk to each other. A crew in a control room has to look at all of it and decide, in seconds, whether what they're seeing is a threat.
SkyNet is the software that does that reconciling. It takes the feeds from whatever equipment is already installed, combines them into one picture, works out which objects are actually dangerous and which are a news helicopter or a hobbyist, ranks them by what they're threatening, and recommends how to respond. The commander decides the rules in advance; the software works inside them and shows its reasoning.
We don't make the radars and we don't make the drones. We make the part in the middle that turns a pile of separate alerts into one decision.
Persistent Threat Detection
SkyNet's multi-sensor architecture continuously monitors protected airspace, identifying unmanned aerial threats at extended range — day or night, in contested environments.
Core Capabilities
SkyNet connects to existing equipment through published industry standards rather than a proprietary system, so a customer isn't locked into one vendor.
Intelligent Threat Classification
SkyNet autonomously classifies detected targets by type, size, and behavior — distinguishing hostile small drones from friendly or neutral aircraft.
Coordinated Intercept
SkyNet directs available interceptors against confirmed threats — selecting the right effector, sequencing the engagement, and returning assets to station under the engagement authority the commander has set.
Resilient Communications
SkyNet operates under full-spectrum electronic warfare conditions, maintaining command and control between SkyNet components through contested, jammed, and GPS-denied environments.
Command and Control Integration
SkyNet is tactical C2 at the site. It subordinates to the command system above it.
Counter-UAS command and control is not settled. FAAD C2 is the fielded joint interim standard for counter-small-UAS. IBCS is the Army's program of record and will absorb legacy air and missile defense command and control over the next decade. Fire control modernization is moving on a separate track. Services and combatant commands are operating across more than one of these today and will be for years.
SkyNet does not assume a winner and does not ask a customer to choose one.
Where SkyNet sits. SkyNet performs sensor fusion, classification, assessment, and engagement sequencing at the protected site. It publishes a prioritized, explainable air picture upward to the service or theater command system and accepts engagement authority downward from it. SkyNet does not replace FAAD C2, IBCS, or any successor. It gives them a cleaner, already-correlated picture to act on.
One site, multiple command systems. A single SkyNet installation can publish to more than one command system at the same time. Where an Army element and a Marine element operate different battle command systems over shared airspace, SkyNet feeds both from one fused track picture, with engagement authority held by the designated controlling node. Adding, changing, or retiring a command system is a configuration change at the interface, not a redesign.
Published standards, documented interface. Track and status data are published over Cursor-on-Target and ASTERIX; unmanned asset control uses STANAG 4586 and MAVLink. An interface control document is available under NDA.
When the link to higher drops. SkyNet's internal networking carries traffic between SkyNet components, not into the customer's command system. If the link to higher C2 is severed by terrain, electronic attack, or node loss, SkyNet continues operating inside the commander's pre-established rules of engagement and reconciles state when the link is restored.
Program Status
SkyNet is at Technology Readiness Level 3 — the stage at which a concept has been proven in software and simulation, before integration with hardware [Status]
Graduated Response
SkyNet is designed so that commanders and operators exercise appropriate levels of human judgment over the use of force, consistent with DoD Directive 3000.09. The commander sets the rules of engagement; the software works inside them and shows its reasoning.
1) Detect and assess
Fuse, track, classify. Most contacts are resolved here and never become engagements.
2) Warn and hand off
A prioritized, explainable picture is pushed over standard interfaces to the existing command systems — one or several, simultaneously.
3) Soft-kill first
Where the threat is susceptible and authority permits, non-kinetic defeat is the preferred answer.
4) Kinetic only when nothing else will work
Reserved for threats that cannot be stopped otherwise — RF-silent and fiber-optic-guided types — under the engagement authority the commander has set.
Mitigation authority in the United States is limited by statute to specific federal departments. SkyNet is built so the detection and assessment layer delivers value wherever it is installed, and defeat actions remain subject to the authority held by the operating organization.
Terms Used on This Page
UAS / UxS — Unmanned Aircraft System, or more broadly Unmanned Systems. A drone and the equipment used to control it.
C-UAS — Counter-UAS. Technology for detecting, identifying and defending against drones.
C2 (Command and Control) — The system that takes in information, decides what matters, and directs a response. SkyNet is a tactical C2 platform at the site level, operating beneath the service or theater command system.
Group 1–3 — The Department of Defense size classification for drones. Group 1 is small and hand-launched; Group 3 can weigh up to roughly 1,300 pounds. These are the sizes SkyNet is built to address.
TRL (Technology Readiness Level) — A 1-to-9 scale the government uses to describe how mature a technology is. TRL 1 is a basic idea; TRL 9 is proven in operational use. SkyNet is at TRL 3 — proven in software and simulation, not yet integrated with hardware.
Hardware-in-the-loop simulation — Testing where real software runs against a physics-accurate simulation of the hardware, so behavior can be validated before anything is built or flown.
Sensor fusion — Combining data from several different sensors into one picture, so a radar track, a camera image and a radio signal are recognized as the same object rather than three separate ones.
Soft-kill / Non-kinetic defeat — Stopping a drone without destroying it, typically by disrupting its control link or navigation.
Kinetic — Physically intercepting or destroying a drone.
Electronic warfare (EW) — Attacking or interfering with an opponent's use of the radio spectrum, including jamming radio links and GPS.
GPS-denied — Operating where GPS is jammed or spoofed and position has to be determined another way.
Cursor-on-Target, STANAG 4586, MAVLink, ASTERIX — Published standards that let equipment from different manufacturers exchange information. Building to them is what lets SkyNet work with a customer's existing systems.
Edge compute — Processing done on the equipment at the site rather than sent to a remote server, so decisions don't depend on a network connection.
DoD Directive 3000.09 — The Department of Defense policy governing autonomy in weapon systems. It requires that commanders and operators retain appropriate human judgment over the use of force.
SDVOSB — Service-Disabled Veteran-Owned Small Business. A federal contracting designation.
CAGE / UEI — Identifier codes assigned to organizations registered to do business with the U.S. government.
Ready to Learn More?
Inquiries are welcome from qualified defense primes, government agencies, and accredited investors. All conversations are subject to NDA prior to any technical disclosure.