Passive optical sensing
USB camera input feeds a trained single-class drone detector running on NVIDIA Jetson Orin Nano edge hardware.
Platform // System architecture
Lamassu begins with passive optical observations at the edge. The platform direction is to correlate those observations across sensors, preserve their provenance, and produce useful track data for existing operator workflows.
The stack
We distinguish what has been demonstrated from what is being developed. That boundary matters in a system intended for consequential environments.
USB camera input feeds a trained single-class drone detector running on NVIDIA Jetson Orin Nano edge hardware.
The prototype classifies candidates, maintains visual identity over time, and can command a calibrated pan-and-tilt optical mount.
A common observation model is intended to correlate optical, RF, radar, and acoustic inputs as those integrations mature.
Structured track output for operator interfaces and command-and-control systems is planned, but is not currently available.
End-to-end direction
The sensor does not need to know the whole air picture. It reports what it observed; the system decides how those observations relate.
Camera nodes create timestamped detections. Remote ID and other sensor adapters are planned as separate inputs.
Local inference reduces raw video movement, maintains visual tracks, and preserves sensor context.
Planned multi-camera triangulation and modality-agnostic fusion build confidence without hiding provenance.
The intended output is a coherent track that can flow into an operator view or standards-based C2 interface.
Current prototype
A trained YOLO detector runs against live camera input on Jetson edge hardware with an engineering HUD for timing and confidence.
DemonstratedByteTrack-based tooling maintains target identity over video and exposes per-track motion information.
DemonstratedClosed-loop proportional control drives a calibrated two-axis mount to keep the selected detection centered.
DemonstratedA subscriber confirms alerts when multiple nodes observe activity within a time window, with deduplication and heartbeat monitoring.
DemonstratedFusion core
The fusion core is in development. Its design preserves the sensors that contributed to a track, their health, and the confidence behind each update.
Sensors report what they saw rather than independently declaring a complete track.
Every fused track is intended to retain which sensors contributed and how.
Silent or degraded nodes should affect confidence instead of disappearing from operator context.
Optical, RF, radar, and acoustic observations can enter through explicit adapters as integrations mature.
The same observation stream should produce the same track history for analysis and testing.
Track data is intended to support existing workflows rather than force a new closed ecosystem.
Evaluate the fit
We will map your environment against the demonstrated prototype and make the maturity boundary explicit before proposing a next step.
Discuss your environment