Nearly half of all companies now use Rust in production.

Let that sink in. Not "interested in." Not "evaluating." In production. Serving real users. Handling real traffic. Paying real salaries.

I remember when Rust was the language everyone talked about but nobody used. "Great, but won't it slow us down?" "Can we even hire for it?" "What about the learning curve?"

Those questions didn't disappear. But something changed.

The Numbers

The 2026 Rust survey (covered in This Week in Rust #641) found that 48.7% of responding organizations have Rust running in production. Of those already using Rust:

These aren't early adopters patting themselves on the back. These are companies with budget reviews, security audits, and ops teams. They chose Rust because it delivered — not because it was trendy.

What Changed

The inflection point wasn't a single thing. It was a stack of things happening at once.

The ecosystem matured. Serde, tokio, actix, reqwest — these aren't experimental libraries anymore. They're stable, well-documented, and have years of production hardening. When I built my first Rust CLI tool in 2023, I reached for crates that had already survived the "will this still exist in two years?" test. Now that list is much longer.

The hiring fear faded. "We can't find Rust developers" used to be the default objection. But developers learned Rust on personal projects, on wasm experiments, on side projects. Companies started hiring smart people and letting them learn Rust on the job. The supply problem solved itself because the language was worth learning.

Memory safety became non-negotiable. After years of buffer overflows, use-after-frees, and log4j-style catastrophes, security teams started demanding memory-safe languages. Rust wasn't just "nice to have" — it became the answer to "how do we stop getting pwned?" C and C++ started feeling reckless, not performant.

Linux embraced it. The kernel now has Rust modules. Android is Rust-first for new code. Fedora and Debian ship Rust by default. When the operating system backs your language, the "is this production-ready?" question answers itself.

The Shift No One Noticed

What's striking is how quiet the transition has been.

There's no "Rust revolution" moment. No dramatic defenestration of Python or Java. Instead, Rust crept in through the back door:

Companies don't announce "we switched to Rust." They announce "we rewrote this one service in Rust" and quietly never go back.

What This Means for You

If you've been on the fence about Rust — about investing time, about proposing it at work, about building something in it — the fence is gone.

The question isn't "is Rust ready for production?" It's "what part of your stack is still running on something that can leak?"

I picked Rust because I wanted to understand systems programming. I stayed because it made me a better engineer. Now the industry is catching up to what a lot of us already knew: this is how software should be built.

48% is just the beginning.