Rust started as a systems language that promised memory safety. Now it's becoming the language that critical infrastructure demands.
The Consortium Became Real
The Safety-Critical Rust Consortium launched in late 2024, but 2025 is the year it stopped being a press release and started being a mandate. Toyota leads it. So do Airbus, Lockheed Martin, and a nuclear energy company I can't name.
The consortium's goal isn't theoretical. It's practical: get Rust certified for DO-178C (avionics), ISO 26262 (automotive), and IEC 61508 (industrial safety). These aren't rubber-stamp processes. They're years of work.
And it's happening.
Toyota's Production Win
Pete LeVasseur, lead of the Safety-Critical Rust Consortium and staff engineer at Woven by Toyota, made an announcement in late 2025: Rust is now in production vehicles at Toyota.
This isn't a research project. It's not a demo. It's running in cars driving on real roads.
Toyota's "Woven" division—yes, they named it that—is the tip of the spear for software-defined vehicles. They're not just using Rust in infotainment. They're pushing it into the safety-critical layer.
The Federal Nudge
Here's what accelerates everything: the U.S. government mandated in late 2024 that critical software systems must move away from C/C++ by 2026 or face increased scrutiny. The Federal Risk and Authorization Management Program (FedRAMP) started requiring memory-safe languages for high-impact systems.
This isn't regulation in the abstract. It's procurement language. When NASA buys software, when the DoD awards contracts, when aerospace companies bid on federal work—Rust is no longer "experimental." It's becoming the expected default.
Why Now?
Three converging forces:
-
Cost of bugs: The average automotive recall costs $500 million. One memory safety vulnerability in a brake-by-wire system is existential. Rust's borrow checker isn't just a developer tool—it's an insurance policy.
-
Tooling maturity: The consortium isn't starting from zero. There's cargo-audit for dependency vulnerability scanning. There's rustfmt and clippy for style and safety checks. The ecosystem has the building blocks for certification workflows.
-
Talent pipeline: Rust developers aren't unicorns anymore. Companies can hire them. The language's popularity means the workforce exists.
What This Means for You
If you're building anything that touches the physical world—robotics, drones, industrial control, medical devices—the writing is on the wall. The same forces that pushed Rust into WebAssembly and Linux system programming are pushing it into safety-critical domains.
The question isn't whether Rust will dominate safety-critical software. It's whether you'll be ready when your industry makes the switch.
Sung.