These are not two products of the same kind. INKAS® Aerospace & Defense (INKAS Defense) builds armored vehicles, unmanned platforms and security systems, and offers counter-UAS as one of its capabilities. Its C-UAS page describes “Fully integrated drone defense systems for end-to-end threat protection”: detection by “active radar and passive RF sensing”, an EO/IR camera that provides “continuous visual tracking” once a drone is detected, and neutralization by jamming or “a remote weapon system”. INKAS says each component “can be deployed as a standalone capability or combined into a complete multi-layered defense solution”, and that the architecture “supports fixed installation on armored vehicles”. GOTEAM covers one part of that chain. It detects and identifies drones passively, with thermal sensors and on-edge AI, and hands the track to whatever system acts on it.
INKAS presents itself as an integrator as well as a manufacturer. Its Ecosystem and Integration page says “Best-in-class third-party solutions are sourced and integrated seamlessly”, and lists “Client-supplied weapon stations and sensors” and “EO/IR cameras and thermal imaging systems” among typical vehicle integrations. Its About page says “Defense solutions are developed and manufactured in-house”. The C-UAS page does not name the radar, RF sensor, camera, jammer or weapon station, or who makes them, so this page does not say which parts are INKAS’s own. It compares the sensor chain INKAS describes with GOTEAM’s.
The main difference is where thermal sits in the chain. INKAS says its detection layer “requires no thermal imaging for detection”: radar and RF find the drone, then the EO/IR camera is brought onto it to confirm. In GOTEAM the thermal sensor is the detector. Fixed wide-field nodes search every frame for targets and need no cue from another sensor.
Every claim about INKAS on this page is quoted from INKAS’s own website, linked in the sources at the bottom and checked on 6 October 2026. INKAS publishes no datasheet on those pages, and we have not tested any INKAS product. Every claim about GOTEAM is published on this site or in /llms.txt.
Most of this table follows from one choice: GOTEAM detects with a passive thermal sensor that watches its whole field all the time. INKAS detects with radar and RF, and uses its camera afterwards. Neither choice is wrong. They put the thermal layer in different places.
| Capability | GOTEAM — passive thermal detection layer | INKAS C-UAS — radar/RF detect, EO/IR confirm |
|---|---|---|
| The thermal camera is a detector, not only a confirmation sensor | ✓neural detection on every 16-bit thermal frame | ✗“requires no thermal imaging for detection”; the EO/IR camera tracks “Once a drone is detected” |
| The optical layer needs no cue from another sensor to find a target | ✓fixed wide-field stare; the whole scene is searched every frame | ✗the camera follows a detection from radar or RF; INKAS describes it keeping UAVs “centered” |
| Every target in the optical field is imaged on every frame | ✓“one drone or twenty, at the same latency” | —how many targets the EO/IR camera can image at once is not stated |
| Nothing in the detection chain transmits | ✓passive EO/IR; no spectrum licence required | ◐the RF sensing is passive; the radar is “active” |
| An annotated clip of every confirmed track, kept for later review | ✓annotated clip and zoom-crop thumbnails per track in the GOTEAM Hub | ◐live “positive target confirmation” through EO/IR; recording and review not described |
| Open C2 output over SAPIENT (BSI Flex 335 v2) | ✓azimuth, elevation and range handed to third-party C2 and effectors | —“Integrates seamlessly with the C2 system”; we found no named interface standard on the pages reviewed |
| Detection engine licensable as software onto a third party’s thermal core | ✓camera-agnostic; licensed to OEMs, integrators, and platform and vehicle integrators | — |
Both detect drones, both cover drones that do not transmit, both use AI, and both can ride on a vehicle. The mechanisms differ, and so do the conditions in which each one fails.
| GOTEAM does it by… | INKAS does it by… | |
|---|---|---|
| Finding the drone | Looking at it. Full 16-bit thermal frames, sky and cloud suppression, a neural detector trained on tens of thousands of hand-verified thermal drone frames, then a tracker that confirms a target only once it persists and moves consistently. | Radar and radio. “active radar and passive RF sensing”, with “low false alarm rates via data fusion”. INKAS says the system “Operates fully automatically with AI support”. |
| Seeing the radio-silent drone | Heat and shape. Fibre-optic, pre-programmed and fully autonomous drones look the same to a thermal camera as radio-controlled ones. | The radar layer. “Radars detect various UAV classes, including commercial, military, autonomous, and dark drones”. The RF layer covers “commercial, DIY and FPV drones using radio control”, so a silent drone falls to the radar. |
| Telling drone from bird | On the detecting sensor. On-edge neural classification, flight-behaviour cues that down-weight birds, and track confirmation before a target is declared. | A second look. Radar and RF “detect, classify, and localize”, and the EO/IR camera “Supports UAV-type classification through visual and thermal cues” and “Enables positive target confirmation before neutralization actions commence”. |
| Stating range | Target- and scenario-dependent. GOTEAM optimises for confident, multi-target detection inside the envelope where a small drone can actually be engaged. | Long stated ranges, with a caveat. “RF >5 km and radar >10 km, depending on drone type and conditions”, with “360° x 90° coverage”. We have not tested these figures. |
| Riding on a vehicle | A node that mounts on someone else’s vehicle. Vehicle-mounted, tripod or rooftop, on vehicle DC, mains or solar with battery backup; a sealed IP67 edge box; passive detection that travels with a convoy. | Building the vehicle. “fixed installation on armored vehicles”. INKAS lists “Layered Counter-UAS (C-UAS) Integration” and a “Counter-UAS-Capable Remote Controlled Weapon Station (RCWS)” among Sentry APC options. |
| Acting on the track | Handing it off. No jamming, no spoofing, no kinetic action. Tracks go out over SAPIENT (BSI Flex 335 v2) to the C2 and effectors already on site. | Its own effectors. Directional jamming “up to 6 km”, omni-directional jamming “for swarm neutralization (up to 3 km)”, and a remote weapon system with “30×113 mm ammunition”. |
Where GOTEAM is stronger. The thermal layer does the searching. Every bearing in a node’s field is watched on every frame, a drone that sends no radio signal is seen by its heat and shape, and nothing in the detection chain transmits, so a node needs no spectrum licence and gives away nothing on a convoy that must stay quiet. Every confirmed track comes with an annotated clip an operator can review afterwards, and goes out over SAPIENT to whatever C2 and effectors are already there. The engine can also be licensed as software onto another company’s camera and compute.
Where INKAS is stronger. Everything after detection, and reach. INKAS offers soft-kill jamming and hard-kill engagement, locates the pilot as well as the drone (“Detects and geolocates drone operators, including Remote ID-equipped drones”), and states detection ranges far beyond what an uncooled thermal node is built for. Radar and RF also work without the line of sight and clear air a camera needs. INKAS builds the armored vehicle as well, so one supplier delivers the platform, the sensors and the effectors. GOTEAM does not jam, shoot or find the pilot, and it does not build vehicles.
The two can work together. INKAS lists “Client-supplied weapon stations and sensors” and “EO/IR cameras and thermal imaging systems” among the systems it integrates into its vehicles, and GOTEAM licenses its engine to platform and vehicle integrators and reports over SAPIENT. A staring thermal layer could sit alongside radar and RF on such a vehicle: it would watch for the close-in drone the other sensors miss and cue the camera and effectors onto it. No partnership exists between the two companies, and buyers should judge both against their own threat, range and platform.
Sources (all accessed 6 October 2026). INKAS® Aerospace & Defense, “Counter-unmanned aerial systems” page — “Fully integrated drone defense systems for end-to-end threat protection”, “active radar and passive RF sensing”, “requires no thermal imaging for detection”, RF and radar ranges, “360° x 90° coverage”, operator geolocation, EO/IR tracking and confirmation, jamming ranges, remote weapon system and “fixed installation on armored vehicles”: inkasdefense.com/c-uas/. INKAS, Ecosystem and Integration page — “Best-in-class third-party solutions are sourced and integrated seamlessly”, typical vehicle integrations including “Client-supplied weapon stations and sensors” and “EO/IR cameras and thermal imaging systems”: inkasdefense.com/ecosystem-and-integration/. INKAS, About Us page — “Defense solutions are developed and manufactured in-house”: inkasdefense.com/about-us-2/. INKAS, Sentry APC page — “Layered Counter-UAS (C-UAS) Integration” and “Counter-UAS-Capable Remote Controlled Weapon Station (RCWS)” options: inkasdefense.com/armored-vehicles/inkas-sentry-apc/. GOTEAM claims: this site and /llms.txt.
Independent comparison by GOTEAM. GOTEAM is not affiliated with or endorsed by INKAS. INKAS® and Sentry are names used by INKAS® Aerospace & Defense. INKAS capabilities and figures are quoted from INKAS’s own website and have not been independently tested; INKAS may have revised them since the access date. INKAS does not name the makers of its C-UAS sensors and effectors on the pages reviewed, and this page makes no claim about them. ◐ = partial — present but narrower than the other column. — = not documented publicly: it marks something INKAS’s published material does not address, not a claim that the capability is absent. GOTEAM marks reflect capability published on this site and in /llms.txt; specifications beyond that are shared under NDA after vetting.
Upload a clip to FlyBox and a GOTEAM field device processes it on real hardware, streaming back an annotated result with per-frame detections and range and bearing — your footage, our engine, no NDA required to start.