DroneShield: counter-drone hardware and enterprise software
DroneShield combines counter-drone hardware with software and support. Its enterprise software announcement illustrates a move toward managing multiple customer sites.
Counter-drone / Archive
DroneShield combines counter-drone hardware with software and support. Its enterprise software announcement illustrates a move toward managing multiple customer sites.
Epirus develops the Leonidas high-power microwave product family. Its public Army contract evidence separates system delivery, testing, support and potential future programme requirements.
A clean demonstration says little about the effort of reviewing uncertain information or handing work to a colleague. Interface evaluation should connect usability evidence with the staffing and training the customer is buying.
Estonia-headquartered Frankenburg combines interceptor development with regional manufacturing partnerships; a Riga opening and a Colt CZ memorandum show different stages of expansion.
OpenWorks’ catalogue spans optical systems and drone-capture products. Its public history shows why sensing, integration and customer delivery should be assessed separately.
Origin Robotics’ public catalogue identifies BEAK and BLAZE. A June 2026 Latvian ministry statement provides independent institutional evidence that company products form part of support to Ukraine.
A false-alarm claim is only comparable when the buyer knows what was counted, over what period and against which reference record. Percentages and alerts per hour describe different things.
Silentium Defence reports more than 100 employees worldwide. Its business combines passive-radar equipment, space-surveillance data and new US, UK and European operations.
SYPAQ combines Corvo aircraft, engineering services and Bellinger communications. Its public DEF129 plan identifies acquisition, support and named Australian suppliers.
An acceptance report connects the delivered configuration to the agreed purchase. Its most useful pages explain the scope of the evidence, outstanding exceptions and the responsibilities that pass into service.
A large trial dataset can contain surprisingly little independent evidence. Procurement teams need to know what was sampled, how results were grouped and which claims remain outside the record.
Replacing a sensor can preserve a standard interface while changing the information the rest of the system receives. The purchase needs a compatibility scope that covers meaning, application behavior and support ownership.