Company // Mission & principles

A guardian at the threshold.

The Lamassu stood watch over important gateways. We are building the modern sensing layer for another threshold: the low-altitude airspace above sites that cannot afford ambiguity.

Company stage // Early & engineering-led Product scope // Detection & tracking

Why we exist

Make the air picture clearer before the decision gets harder.

Small drones have made low-altitude awareness a software and sensing problem, not only a radar problem.

Lamassu Systems is building from the sensor edge outward: first make optical detection and tracking work on real hardware, then combine observations into a coherent picture that can support existing operator systems.

We are early. The prototype is real, the fusion roadmap is ambitious, and the distinction between those two appears everywhere in how we communicate.

Responsible by design

Detection without hidden escalation.

Lamassu is a sensing company. We do not build jammers, weapons, autonomous interdiction, or other mitigation systems.

01 // Passive-first

Observe without transmitting

Camera-first sensing can contribute awareness without requiring an active RF emission from the detector or target.

02 // Human-led

Information before action

The system is intended to surface observations and confidence for human review, not make autonomous response decisions.

03 // Detection-only

A deliberate boundary

Mitigation stays outside the Lamassu product boundary and must remain with appropriately authorized systems and operators.

How we build

Evidence over theater.

Counter-UAS has enough dramatic language. We prefer demonstrated behavior, explicit constraints, and engineering work that survives contact with hardware.

01Principle

Real hardware early

Prototype on the edge computer, camera, motors, and network behavior that expose actual constraints.

02Principle

Bound the claim

Validation metrics are not field guarantees, a roadmap is not a deployment, and a planned integration is not a partnership.

03Principle

Design for the operator

Sensor provenance, health, confidence, and clear failure states matter as much as a detection box.

04Principle

Integrate, do not isolate

The intended product produces useful track data for existing systems rather than demanding another closed console.

05Principle

Prefer passive signals

Optical detection remains useful when a drone is not broadcasting Remote ID or another cooperative RF signal.

06Principle

Build the learning loop

Replayable observations, explicit tests, and field data should continuously sharpen the system's behavior.

Operators, partners, builders

Help us test the system against a real problem.

We are interested in technically serious conversations with site operators, sensing partners, integrators, and people building the counter-UAS ecosystem.

Start the conversation