Which version is running where — and who approved it?
DiagStudio gives you one verified, auditable answer — for every component and every baseline, from engineering to the field. Built for diagnostics and E/E teams at OEMs and Tier-1s, and for defence programmes with decades of service life.
Built for software-defined vehicles & defence · proven in serial production
One platform, many components, thousands of version combinations — the web DiagStudio keeps track of, so your team doesn't have to.
01 · Why it matters now
"Does it work?" is no longer the hard question.
As vehicles and defence platforms become software-defined, the hard question is no longer "does it work?" but "what exactly is running, where, in which version — and who approved it?" These platforms stay in service for decades, draw on long supplier chains, and must remain in a known-good, approved state to stay available and secure. Spreadsheets and tribal knowledge do not survive that.
DiagStudio doesn't replace your existing tools — it connects them, gathering what's scattered across them into one verified picture of what's running where.
02 · Four core capabilities
Design it. Deliver it. Verify it. Keep it available.
01 · Platform design
One model of the platform
Define and maintain the hierarchical structure of your platform: every component, version, attribute, dependency and relationship, in one model.
02 · Software delivery
Traceable and controlled
Move component versions and platform baselines through configurable stages (for example Engineering → Validation → Release), with formal approval workflows and a tamper-evident audit log at every transition. A baseline is the formal record of exactly what is running where.
03 · Supplier chain
Verified network
Track the governance and compliance profile of the companies in your supply and partner network. (Emerging capability — currently a proof of concept developed with NVR.)
04 · System availability
Secure and known-good
Catch compatibility problems early through automated impact analysis, hold verified baselines of what is deployed, and ensure that only approved configurations progress through the lifecycle.
03 · How it works
Baselines, stages, impacts — and a provable audit trail.
Components are versioned with semantic versioning and organised by type. A baseline snapshots exactly which versions are installed across a platform. Stage changes advance components and baselines only through deliberate, recorded human approval. Impacts automatically flag downstream effects of any change and force a review decision before it can progress. Role-based access control and a complete audit trail mean every action — who did what, when — is captured and provable.
Before DiagStudio
A fix is released — and the questions begin. Which dependencies? Which individuals? Did I miss anything?
After DiagStudio
Open it up, see every affected relation and individual, and run the update with confidence.
04 · Built for two worlds
Defence and software-defined vehicles ask the same question.
Defence
Platforms that must stay ready and secure for decades, with sovereign control of the supply chain and a provable record of every software state. It speaks directly to the resilience and software-defined-platform themes shaping the sector today.
Automotive / SDV
As the vehicle becomes defined by its software, "which version is in which car, and is it approved?" turns into a daily, safety- and security-critical question. DiagStudio answers it.
Software-defined platforms live or die on a simple question: do you know, and can you prove, exactly what is running where?
— Viktor Eliasson · CEO, Diadrom
05 · Proven in proof of value
Land-systems organisations are already evaluating it.
A European tracked combat-vehicle programme evaluated DiagStudio in a proof of value — applying traceable, baseline-controlled software delivery to a complex, multi-supplier platform.
A European developer of unmanned ground vehicles (UGVs) evaluated DiagStudio in a proof of value — managing and verifying software baselines across an autonomous land platform.
Customer identities withheld at the programmes' request — a deliberate choice that reflects the sensitivity of the work. References available to qualified parties under NDA. Book a demo to go deeper.
06 · From heritage to platform
Two decades of keeping mission-critical systems diagnosable.
From RBS 70 NG lifecycle diagnostics to the FMV fleet communication box, Diadrom has spent more than two decades keeping mission-critical systems diagnosable and maintainable. DiagStudio is where that discipline becomes a product — platform design, traceable delivery and verified availability in one place.
