The operating layer for physical security.
Spyder unifies every sensor and data stream on your site: cameras, radar, RF, acoustic, access systems, network traffic, third-party APIs, anything with a documented interface. One operating picture. Multi-object detection across ground and airspace, on the hardware you already own.
Tripwire
Know when drones enter your airspace. Automatically.
Remote ID receiver powered by solar or Power over Ethernet. Detects compliant drones up to twelve kilometres. Installs in under ten minutes. Mount it, point it at the sky, done. No radar, no cameras, no IT department.
Software and sensors. One operating picture.
Tripwire
Sensor · available nowAutomatic alerts the moment a Remote ID drone enters your airspace. Solar or PoE power, cellular, ten-minute install.
Buy Tripwire →Spyder
Platform · in pilotsThe integration layer as software. Cameras, radar, RF, acoustic, access systems, network feeds, anything with an interface, fused into one operating picture.
Explore →The stack is fragmented by input.
Every sensor lands in its own console. Today the integration layer is human coordination. Mosaic replaces it with one picture from every input. Access is by invite only while we build it with launch partners.
Simplify with Spyder, see what matters.
Detected Person on runway 27 during an active landing clearance Detected Tailgate into Server Rm B — 2 people, one badge Detected Unregistered craft in the berth exclusion zone — no AIS
Help shape Mosaic before it ships.
We're working with a small group of invited teams ahead of launch. If you're one of these three kinds of team, request access.
Request access- Pilot sites Airports, bases, prisons, and critical infrastructure ready to deploy.
- Sites with sensors Already running cameras, radar, RF, acoustic, access control, network sensors, anything? Bring it.
- Sensor makers Building hardware? Give its data a home in the operating picture.
Multi-source fusion
Any sensor, any vendor, any modality. If it has an interface, Mosaic speaks to it.
Cross-sensor identity
One person past three cameras is one contact. One drone across RF and optics is one track.
Operator-defined
Zones, rules, severities drawn on shift. SOP changes, the system changes the same day.
Open at every layer
Models swappable. Sensors swappable. Outputs feed anything you run. No lock-in.
Spyder replaces the human integration layer with software.
One map, one alert stream, one set of rules the operator wrote themselves, across every sensor on site. Built ground-up for fusion, not bolted onto a single sensor type.
Cameras over ONVIF · radar and RF over published APIs · access control over OSDP · acoustic, third-party feeds, anything with a documented interface.
A.1People, vehicles, drones, wildlife, unknown. Persistent identity across sensors, one track per object, not three.
B.1Zones, rules, and severities drawn by the operator on the same map they work from every day. SOP changes, system changes, same day.
C.1Severity-tiered, routed by operator logic, propagated cross-site. Webhook, dashboard, syslog, whatever your operations already use.
D.1Unify every sensor.
The sensor fusion and unified-picture layer. In active development. Invite only, request access to join.
Predict what's next.
Pattern recognition across sites and time. Anomaly detection before alarm thresholds trigger. Incident probability by zone, by shift, by season.
Close the loop.
Operator-defined automated response. Routing, escalation, dispatch, counter-action. Always under human authority. Signal to outcome, end to end.
We started at the integration layer.
Most platforms in physical security started as a single sensor type and bolted on integrations later. We didn't.
Built ground-up for fusion.
Spyder isn't a VMS with extra inputs. It isn't a drone-detection tool that learned to read cameras. The unified picture is the architecture, not a feature. That's why we can swap models, swap sensors, and add new modalities without rebuilding the product.
Operator-defined, not vendor-defined.
The people on shift configure zones, rules, severities, and routing, not a services team in a different time zone. We measure how fast the platform absorbs the operator's intent, because that's the metric that determines whether the platform gets used at two a.m.
Defense-credible. Commercially deployable.
Finalist in the DIU and NORTHCOM low-cost drone sensing challenge. The system has to work in environments where the cost of getting it wrong is measured in lives or in millions. It's the same product that runs on a corporate campus.
Tripwire for your home
Know when a drone is over your home, and where the pilot is. Alerts on your phone, a dated record you can keep. Works with drones that broadcast Remote ID. No camera, no microphone.
Tell us what you need.
Pick the path that fits.
Rather talk than type? Book a 15-minute call →