How we build
Every Ceradon product applies the same thesis: put the capability in software, run it at the edge, and make it work on commodity hardware the operator already owns.
Four design rules
Data is computed where it’s collected: a laptop on the tactical network, embedded compute on the platform. Nothing depends on connectivity, and nothing transits infrastructure the operator doesn’t control.
Demonstrated in
The capability lives in the software, so the hardware can be cheap, replaceable and already in inventory.
Demonstrated in
Emitting reveals position. Where the physics supports it, read signals already present rather than adding new ones.
Demonstrated in
Autonomy handles volume; the human holds judgement. Systems surface, rank and recommend, and a person validates before anything consequential happens.
Demonstrated in
Where the research is going
None of this is a product yet.
In development
RAPTOR: detection on a small edge computer that the operator can correct and retrain. Not working end to end yet.
In development
VANTAGE: presence sensing from radio signals already in a building. An early prototype with no performance figures.
Applied research
What fits on a laptop, a Jetson or a phone, with no connection: models, retrieval and tooling small teams can own.
Research partnerships
New builds
One short note per release, with the download link. Reply to stop.