PULSAR Platform
The AI-native platform for teams integrating software-defined vehicles — the whole system, or the part you own. PULSAR reconstructs how each software version actually behaves, from the runtime data you already record.
PULSAR / Overview
software 7.4 ▾ 96 runs last 24 h Ask PULSARin one software state of one program
Where we built it
We start in automotive integration. It is the domain we have lived in. How we came here →
Robotics and medical devices are next — same problem, different domain. PULSAR reads logs, not vehicles.
Why automotive is the hard case
Our first target complex industry — and where the problem hurts most.
150+
control units in one car, from different suppliers.
100M
lines of code across them. Nobody holds the whole picture.
Strong IP protection: across every company boundary, software arrives as a black box — in both directions.
The platform
One figure, assembled as you scroll. Five chapters: your runs go in and the model builds itself, then three modules read it.
PULSAR / Overview
software 7.4 ▾ 96 runs Ask PULSAR Upload runsPULSAR Engine · before any module can answer anything
One screen, one continuous action: as the upload progresses, components appear one by one on the canvas below — and once it completes, the finished model is ready, with behavior fully reconstructed.
Inside the engineAnomaly Detection · an integration engineer, on release day
Every run is measured against a baseline PULSAR learned from your program’s own history. Two things go wrong on a propagation path: steps happen in the wrong order, or a step takes too long to transition. Both are marked on the path.
How normal is learnedRoot-Cause Analysis · whoever is on the hook for the escalation
Describe the symptom in your own words. PULSAR traces the same paths backwards to the component where the chain breaks — and shows exactly why.
Root-Cause AnalysisChange Detection · a release lead, two weeks after a green build
Two states of the same program, held side by side. It’s a diff of what the system did, not of the code that changed — and every difference tells you where it happened and what kind it is: message order, transition time, or a measurement that moved.
Ask PULSAR · the same platform, in your own words
Everything the screens show, you can also just ask for — and more. Bring your own case and explore it in your own words, against your own model.
What we are building next
In development · not in production
Agent Builder
Turn a question your team asks every week into a reusable agent, grounded in the same model the existing modules use.
An invitation
Your custom module
If your program asks a question the existing modules do not answer, the model already has the answer. Just tell us what it is.
Discuss it with us →A model per software state
Every release is a combination of component versions that has never run together before. PULSAR does not keep only one model and update it — it re-derives the model from runtime for each system version you run.
model rebuilt · state 41 · current
Get started
We build a model of your system. You pick the modules your team needs.
You bring
Recorded runs from the benches you already have — a full vehicle, one domain, or a single component
Whatever they emit, in whatever format. Plus part-time access to one engineer who knows the program. No new tooling on your benches, and you write nothing.
We build
4–6 weeks
any format
From your runs to your first answer
Whatever your benches emit, we write the adapter for your format.
