Author: Qorix Communications
Date: August 2026 ·
Reading Time: 5 min
July was a shipping month for Qorix. Qorix Developer reached a meaningful milestone: its first Bootloader configuration for a Tier-1 development program, followed by a second. Not a pilot, not a demo, but a production deployment. Our CTO also published a new thought-leadership piece on the true cost of fragmented SDV toolchains. And Eclipse S-CORE reached version 0.8, with our contribution centered on release governance and integration confidence. Here is what happened.
🔧 CUSTOMER
Qorix Developer Now Configures Bootloader for a Tier-1 Development Program
Qorix Developer is our configuration workspace for the SDV stack: one environment, one YAML-based source of truth, with AI Assist and Auto Assist support across configuration work, instead of a patchwork of tool specific formats and licenses.
For this program, that approach was put to the test on Bootloader configuration. All six configuration views, covering everything from application and communication to machine, platform, execution, and deployment, were built through the same YAML-based workflow, supported by AI Assist and Auto Assist, just like every other Qorix Developer module. A second delivery on the same Bootloader configuration followed, with the same result. That is how we approach Bootloader configuration in a real Tier-1 development program, not as a one-off exception.
“This is exactly the kind of proof point we mean when we talk about production readiness,” says Paula Herzog, Head of Product Program Management at Qorix. “Getting the configuration right the first time, twice, in a real Tier-1 development program, that’s what systematic hardening looks like in practice, not in a whitepaper”
CORE MESSAGE
Bootloader configuration now runs through the same YAML-based, AI Assist supported workflow as the rest of Qorix Developer, proven twice now in a Tier-1 development program, where there is no room to patch it later.
Product
Qorix Developer: The Hidden Cost of Fragmented SDV Toolchains – and What It Looks Like Fixed
In a new thought-leadership piece, Qorix CTO Nico Hartmann breaks down a cost most automotive teams have stopped questioning: managing three, four, or five separate configuration tools across the SDV stack, each with its own license, file format, and training curve. The result – rework at integration, days lost reconstructing ASPICE traceability from files that can’t be diffed, and slow onboarding for every new engineer.
CORE MESSAGE
Binary configuration files cannot be reviewed in a Pull Request. The entire discipline of modern software engineering – review, traceability, collaboration – stops at the boundary of the configuration tool.
Want to see what the alternative looks like in practice? A configuration task that takes roughly 60 lines of manual ARXML authoring runs to about 11 lines in Qorix Developer, completed in seconds with AI Assist grounded in a curated know-how database, not a generic assistant guessing at values. And because every change is tracked like code, two engineers editing the same interface get flagged the moment their changes collide, not at the end of a sprint when it is expensive to unwind.
◆ OPEN SOURCE
Eclipse S-CORE · July 20, 2026
Eclipse S-CORE 0.8: Process You Can Actually Plan a Program Around
On July 20, the Eclipse S-CORE community released version 0.8 of its open-source middleware stack for software-defined vehicles. Most releases are measured by what got added. This one is measured by what got fixed: the decision-making process behind platform-wide changes, and the way independently developed modules are proven together before every release.
Qorix focused its contributions on two areas:
- Governance Maturity. Platform-wide changes now go through a structured review with a named owner and a fixed, time-boxed community sign-off window. No more decisions drifting indefinitely in a chat thread. For OEMs and Tier-1 suppliers, this means: when S-CORE says something is scoped or decided, there is now an actual mechanism behind that statement.
- Release Confidence. Every release candidate is now built and tested as one coherent whole, with each module re-checked against everything it ships alongside and, hence, not assembled from independent modules at the last minute. This is the precondition for any certification claim: you cannot certify a moving target.
QORIX FOCUS
Governance Maturity: A structured, time-boxed process for every platform-wide decision – enforceable, not aspirational.
Release Confidence: Every release proven together as a whole before it ships – the foundation for certifiability.
Ready to accelerate your SDV program?
