Ferrocene 26.02.0 Automotive Core Certification

Ferrocene 25.02.0 was released at embedded world 2025. Now, a week after we visited embedded world 2026, Ferrous Systems has released Ferrocene 26.02.0, extending the reach of qualified Rust tooling in safety-critical development by adding ISO 26262 ASIL B certification for a certified subset of the Rust core library. The update matters because it pushes certification beyond the compiler toolchain itself and deeper into the library layer that embedded and no_std projects rely on.

Why Ferrocene 26.02.0 matters

Ferrocene is already positioned as a qualified Rust compiler toolchain for automotive, industrial, and medical work, but the latest step is more practical than cosmetic. In safety projects, it is not enough to say that Rust is memory-safe in principle; teams need qualified tools, certified components, and paperwork that can stand up in an audit trail. By moving a larger subset of core into certified territory, Ferrous is giving developers a more realistic way to ship certifiable Rust in embedded systems without having to work around the standard building blocks they actually use.

The company says Ferrocene 26.02.0 rolls in changes from Rust 1.91 and 1.92, alongside expanded certified coverage in core, minimal certified panic hooks, and broader documentation for the certified library subset. The result is a more credible path for Rust in automotive and industrial control systems, where qualification work tends to bog down long before code reaches production.

Ferrocene 26.02.0 and the certified Rust core

The important distinction here is that Ferrocene’s compiler qualification was already in place. Ferrous had previously secured qualification for the toolchain under ISO 26262 ASIL D, IEC 61508, and IEC 62304, and late last year it announced IEC 61508 SIL 2 certification for a first subset of the Rust core library. This new release adds ISO 26262 ASIL B coverage for that library subset and substantially expands the number of certified functions.

That should be read as a steady removal of excuses rather than a single dramatic breakthrough. Safety engineers have long liked Rust’s promise, but qualification has been one of the sticking points. As previously reported by eeNews Europe when eeNews Europe covered Ferrous Systems’ work with TrustInSoft, the broader ecosystem around safety-critical Rust has been filling in around analysis, debugging, and mixed-language deployment. Ferrocene 26.02.0 is another piece of that same puzzle.

Commercial push into embedded markets

Ferrous is also clearly trying to reduce the friction around adoption. The company sells Ferrocene on a per-user subscription basis, which makes it easier for smaller embedded teams to trial a qualified Rust flow without the kind of up-front commercial and process burden that usually comes with safety tooling. That does not make certification easy, but it does make the starting point less forbidding.

For embedded developers, the significance of Ferrocene 26.02.0 is straightforward: it narrows the gap between Rust’s technical advantages and the formal compliance demands of regulated sectors. For Ferrous Systems, it strengthens a claim that Rust is no longer just interesting for safety work, but increasingly usable.