tonic becomes grpc-rust under official gRPC project, adds xDS support

Rust developers who have been betting on tonic for gRPC now have a different kind of signal to read: the project is moving under the official gRPC umbrella, and the question is no longer whether tonic can survive as a busy community crate, but how far it can go with institutional backing. Over the next week, hyperium/tonic will become grpc/grpc-rust, and a preview release of the new grpc crate is set to follow. The move puts one of Rust’s most widely used RPC stacks inside a project backed by Google, LinkedIn, and Datadog, with the gRPC effort itself sitting under the CNCF and the Linux Foundation.

That matters because tonic had reached the point where its popularity was outrunning its maintenance model. Lucio Franco said the project began in the summer of 2019, shipped its first 0.1 release in the fall of that year, and grew to more than 12,000 GitHub stars. He also said the workload had become hard to sustain as reviewing incoming changes, building new features, and keeping dependencies in shape consumed more time than one maintainer could reliably absorb. Tonic had already shifted into a narrower maintenance mode, concentrating mainly on high-priority bugs and security issues.

The new arrangement formalizes work that the gRPC team had already started on April 3, 2024, when it announced a native Rust implementation in conjunction with Franco. That plan called for a new channel and server implementation to be contributed into the tonic repository, then for tonic to move into the gRPC GitHub organization under the grpc-rust name. It also leaned on the grpc crate name on crates.io, which Stepan Koltsov donated to the project. For Rust teams weighing whether to adopt gRPC in a side project that might later become infrastructure, that shift changes the risk profile: the stack is no longer just a successful community effort, but part of a broader cross-language RPC platform with deeper maintenance support.

The technical stakes are just as important as the organizational ones. The 2024 gRPC plan emphasized connection management, client-side load balancing, and xDS support for proxyless service mesh integration. Tonic’s xDS story has been growing through tonic-xds, whose documentation says it provides an XdsChannel and can serve both gRPC and generic HTTP clients through the same xDS management server. Separate project notes still describe xDS support in Tonic as alpha-stage, which makes the official gRPC backing especially meaningful for users who want service-mesh features without gambling on an orphaned path. The gRPC project’s own continuous multi-language performance tests, which run every few hours against master, add another layer of interoperability discipline that Rust users have not always had outside the core ecosystem.