Big Tech companies are increasingly adopting a strategic open-source approach by releasing single-purpose Rust crates and Zig modules under permissive MIT licenses to shape dependency ecosystems before competitors can react. These "loss-leader libraries"—such as Google’s tonic-grpc and Meta’s zstd-safe—are not monetized directly but serve to lock in control over critical parts of the cloud-native software supply chain. According to the source, these two libraries now power 68% of cloud-native observability stacks, illustrating their widespread adoption despite the absence of revenue models around them [https://nonogra.ph/write-some-software-give-it-away-for-free-05-05-2026].
Overview
The strategy reflects a shift in how infrastructure influence is gained: not through market dominance of end products, but through early and deep integration into build pipelines. By open-sourcing foundational tools under MIT licenses, companies ensure that developers adopt them early in project lifecycles, creating long-term dependency. This reduces the likelihood of forking or replacement, especially in environments where stability and compatibility are prioritized over licensing flexibility.
While the article does not specify release dates, version numbers, or exact contributor counts for tonic-grpc or zstd-safe, it emphasizes their technical specificity—each serves a narrow, well-defined function within systems programming and data compression, respectively. Their design in Rust and Zig, systems languages known for safety and performance, aligns with growing industry demand for reliable low-level tooling in cloud infrastructure.
What it does
tonic-grpc: Enables gRPC communication in Rust-based services, commonly used in microservices and distributed systems.zstd-safe: Provides memory-safe bindings for Zstandard compression in Zig, targeting high-performance data processing.
Both libraries are maintained by their respective corporate teams but are consumed widely in open-source and commercial projects without licensing friction. Their permissive licensing allows integration even into proprietary software, accelerating adoption across the ecosystem.
Tradeoffs
The tradeoff for developers and organizations using these libraries lies in dependency centralization. While they benefit from high-quality, well-maintained code, they also become reliant on infrastructure decisions made by Google and Meta. There is no indication in the source that either company plans to withdraw support, but such reliance introduces potential long-term risks if maintenance slows or strategic priorities shift.
Additionally, the success of this model may discourage independent development of competing tools, as the cost of achieving equivalent reliability and integration outweighs the benefits for smaller teams.
When to use it
These libraries are appropriate for cloud-native projects requiring robust gRPC or compression functionality, particularly in Rust or Zig environments. Teams should evaluate them based on technical merit while remaining aware