Catch sensor drift before the next test run.
Kaltreon runs an always-on agent fleet that watches the RF and radar sensors on autonomous-vehicle test platforms the way a maintenance crew watches a power plant — every shift, every run — flagging drift between formal calibrations, recalibrating in minutes, and pushing regulator-ready reports around the clock.
- Fleet watch
- 24/7
- Telemetry round-trip
- <2 ms
- Median to recal
- 6 min
- Native buses
- CAN + 77 GHz
Live telemetry
The fleet feed is streaming right now.
The same synthetic 77 GHz feed the demo dashboard renders is on the home page — polled every 15 seconds so the site never feels like a brochure.
- AV perception teams
- Tier-1 sensor suppliers
- Test-fleet operators
- Calibration labs
Capabilities
The four jobs the agent fleet runs on every test platform.
Conventional CMMS tools leave sensor drift blind spots in AV operations; edge-case classifiers flag anomalies but can't recalibrate or close the compliance loop. Kaltreon is the wedge between them.
Ingest
/01- CAN-FD
- 1000BASE-T1
- 4D radar 76–81 GHz
- ROS2 bridge
Detect
/02- Beam-pointing ±0.05°
- Phase drift 3σ
- Range-bin migration
- Thermal envelope
Act
/03- Boresight rerun
- Cavity sweep
- Timing-skew fix
- Phantom-target recheck
Report
/04- Signed PDF + JSON
- ECE / NHTSA templates
- Audit trail
- API egress
The three pillars
What every test-fleet operator gets on day one.
Drift detection without compliance leaves you auditing in panic mode; compliance without drift detection leaves you filing yesterday's report. Kaltreon runs the three jobs the test fleet actually needs in parallel.
Pillar 01
- 24/7 watch on every node
- <2 ms round-trip latency
- 76–81 GHz + CAN-FD native
Pillar 02
- Signed PDF + JSON
- ECE / ISO / NHTSA templates
- Immutable audit trail
Pillar 03
- Cross-platform telemetry
- Per-sensor health rollups
- Channel-level diagnostics
How it works
From a live sensor bus to a signed compliance packet.
The agents run continuously. The on-call team sees drift within milliseconds of the event, the regulator sees a signed packet hours later — without anyone dropping a quarterly calibration audit.
Book an architecture walkthrough- 01
Telemetry in, every shift, every run
Agents wire onto the sensor buses your test fleet already produces and watch for hundreds of metrics per node — without waiting on a quarterly audit.
- 02
Drift flagged within two milliseconds
Comparison runs against the last formal calibration; deltas above threshold trip the alert channel your on-call engineer already monitors.
- 03
Targeted recal on the affected channel
The agent narrows the recal to the channel that drifted instead of taking the whole sensor offline — median six minutes from alert to verified fix.
- 04
Compliance packet out the door
A signed report — drift event, what ran, verification result — lands in the inbox (or the API) your certification team hands to the regulator.
Foundation
Built by an RF design engineer who saw what drifted in field test.
One of our founding leads designs phased-array radar for self-driving sensors at Aptiv — so the agents ship wired for CAN bus synchronization, phased-array radar, and the drift signatures perception teams actually see in the field.
Wedge
Stance
Posture
Pilot
Drop the agents on one platform. We'll have a drift packet in your inbox by the next shift.
Pilots start with a single test bench and a single sensor. Real training, real alerts, real compliance archive — without taking your perception stack offline.