I design open, safety-aware software foundations for software-defined vehicles.
This space is about vehicle software that scales: across legacy ECUs, mixed fleets, and long product lifecycles — without locking innovation into proprietary tooling.
- Open vehicle diagnostics & control (SOVD-first)
- Flashing & lifecycle tooling beyond ODX / OTX
- SDV platform architecture (OEM, EV scale)
- Open-core strategies for safety-critical domains
- System-level design at the hardware / software boundary
I focus on architecture, interfaces, and decision clarity — not features.
-
OpenSOVD Flash Client
A modern, diagnostic-first alternative to traditional ECU flashing stacks.
Built for extensibility, mixed ECU landscapes, and open integration. -
SDV Architecture References
C4 models, patterns, and decision records for vehicle software platforms: diagnostics, flashing, lifecycle control, and fleet-scale operations.
Most vehicle tooling today is:
- proprietary
- hard to evolve
- tightly coupled to legacy processes
That slows down software-defined vehicles.
This profile explores how open, composable systems can replace that — without breaking safety, compliance, or operational reality.
- Open by default
- Explicit interfaces over hidden flows
- Architecture before implementation
- Legacy-aware, not legacy-bound
- Scale is a system property, not a feature
- Reference architectures and diagrams
- Focused repositories with clear scope
- Experiments marked as experiments
- Opinions backed by system experience
What you will not find: marketing, buzzwords, or generic samples.