--- title: gRPC-Rust Roadmap | daily.dev description: The gRPC-Rust team outlines its roadmap following the client-side preview release. The server API is the top priority, alongside health checking, message... canonical: https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: gRPC-Rust Roadmap | daily.dev og:description: The gRPC-Rust team outlines its roadmap following the client-side preview release. The server API is the top priority, alongside health checking, message... og:url: https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu og:image: https://api.daily.dev/og/posts/JhGIAf4vu.png og:image:alt: gRPC-Rust Roadmap og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # gRPC-Rust Roadmap **[gRPC Blog](https://daily.dev/sources/grpc-blog)** · 3 min read · 69 upvotes · 6 comments ## Summary The gRPC-Rust team outlines its roadmap following the client-side preview release. The server API is the top priority, alongside health checking, message compression, and completing the full gRPC interop test suite for production readiness. Longer-term plans include retries, binary logging, channelz debugging, keepalive, authorization, full xDS/Envoy support for proxyless service mesh and Google Cloud direct connectivity, a shared Rust status type pending stabilization of the Try trait, and performance tuning around memory usage and zero-copy HTTP/2. The team also announces gRPConf 2026 at the Computer History Museum on September 3rd with an open CFP. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Is there a server-side API for gRPC-Rust yet? Not yet as a released feature; it is under active development as the biggest priority following the client-side preview release. It will be built as a natural extension of the client API, sharing types where possible, with another preview announcement planned once it is ready. _Rust developers building RPC services can follow gRPC-Rust's progress toward a server API on daily.dev._ ### What Google Cloud use cases does xDS support enable for gRPC-Rust? Full xDS support, built on Envoy, enables both proxyless service mesh (PSM) use cases and direct connectivity for Google Cloud services. This is described as a longer-term goal the gRPC-Rust team plans to focus heavily on over the following several months, alongside significant features like retries, binary logging, Channelz debugging, keepalive, and authorization. _Engineers evaluating service mesh options for Rust services can track xDS and Envoy developments via daily.dev._ ### Why hasn't gRPC-Rust adopted Abseil's Status type directly? gRPC-Rust intends to standardize on a shared Rust RPC status type rather than reuse Abseil's Status directly, because minor internal differences between the C++ gRPC status type and absl::Status have caused pain despite their similarity. The team is waiting for stabilization of Rust's Try trait, which will let the new type ergonomically support useful features. _Rust API designers weighing error-handling tradeoffs can keep up with Try trait stabilization news on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@pdfopsdev** · 8 upvotes > kind of wild the official [grpc.io](http://grpc.io) rust bindings are still client-preview when tonic's had a solid server impl for years. is anyone here actually planning to migrate off tonic once this stabilizes, or is this more for shops that need the canonical C-core semantics (auth, xDS, channelz) tonic doesn't chase? **@pedropietro** · 0 upvotes >  **@nicoyide** · 0 upvotes > Welcome Toni 🙌 **@rizzdev** · 0 upvotes > Production-worthy is the interop suite. Memory, zero-copy, and lower-level HTTP/2 wait behind retries, channelz, keepalive, authz, and xDS **@lezli01** · 0 upvotes > Why did I thought gRPC for rust was basically naturally already out there... ## Similar posts on daily.dev - [gRPC deep dive: from service definition to wire format](https://daily.dev/posts/grpc-deep-dive-from-service-definition-to-wire-format-mykdq3gjn) · Hacker News · 0 upvotes · 0 comments - [Project goals update — December 2025](https://daily.dev/posts/project-goals-update-december-2025-lsuqsummh) · Rust · 20 upvotes · 9 comments - [Infrastructure Team 2025 Q3 Recap and Q4 Plan](https://daily.dev/posts/infrastructure-team-2025-q3-recap-and-q4-plan-efz6gjlfl) · Inside Rust Blog · 3 upvotes · 0 comments - [Rust/C\+\+ Interop Initiative: Progress Update, September 2026](https://daily.dev/posts/rust-c-interop-initiative-progress-update-september-2026-j7c1j8xac) · Rust Foundation · 1 upvotes · 0 comments --- Tags: [#backend](https://daily.dev/tags/backend), [#rust](https://daily.dev/tags/rust), [#grpc](https://daily.dev/tags/grpc) [View this post on daily.dev](https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"gRPC-Rust Roadmap","url":"https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu"},"datePublished":"2026-08-23T07:20:22.481Z","dateModified":"2026-09-13T19:20:59.529Z","description":"The gRPC-Rust team outlines its roadmap following the client-side preview release. The server API is the top priority, alongside health checking, message...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/10aae04dfd3ba4523d83e4087201877a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/10aae04dfd3ba4523d83e4087201877a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"gRPC Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"gRPC Blog","logo":"https://media.daily.dev/image/upload/s--asedGCAx--/f_auto,q_auto/v1787469607/logos/grpc-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/grpc-blog"},"commentCount":6,"discussionUrl":"https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":69},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":6}],"keywords":"backend,rust,grpc","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"gRPC Blog","item":"https://daily.dev/sources/grpc-blog"},{"@type":"ListItem","position":3,"name":"gRPC-Rust Roadmap"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu","comment":[{"@type":"Comment","text":"kind of wild the official grpc.io rust bindings are still client-preview when tonic’s had a solid server impl for years. is anyone here actually planning to migrate off tonic once this stabilizes, or is this more for shops that need the canonical C-core semantics (auth, xDS, channelz) tonic doesn’t chase?","datePublished":"2026-08-23T18:02:47.493Z","url":"https://daily.dev/posts/JhGIAf4vu#c-V8LGfDLM7","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":8}},{"@type":"Comment","text":"","datePublished":"2026-08-25T02:15:15.841Z","url":"https://daily.dev/posts/JhGIAf4vu#c-N8IIdJRT6","author":{"@type":"Person","name":"Pedro Pietroluongo","url":"https://daily.dev/pedropietro","image":"https://avatars.githubusercontent.com/u/1533471?v=4"}},{"@type":"Comment","text":"Welcome Toni 🙌","datePublished":"2026-08-25T03:18:40.060Z","url":"https://daily.dev/posts/JhGIAf4vu#c-KJ8DngQXI","author":{"@type":"Person","name":"Niko","url":"https://daily.dev/nicoyide","image":"https://avatars.githubusercontent.com/u/138998603?v=4"}},{"@type":"Comment","text":"Production-worthy is the interop suite. Memory, zero-copy, and lower-level HTTP/2 wait behind retries, channelz, keepalive, authz, and xDS","datePublished":"2026-08-25T03:56:09.926Z","url":"https://daily.dev/posts/JhGIAf4vu#c-Zl0UB7eTt","author":{"@type":"Person","name":"Andrew","url":"https://daily.dev/rizzdev","image":"https://media.daily.dev/image/upload/s--35vRfXAA--/f_auto/v1785413727/avatars/avatar_fQ7ttCKtPuu6tDvcgQXv5?_a=BAMAMicg0"}},{"@type":"Comment","text":"Why did I thought gRPC for rust was basically naturally already out there…","datePublished":"2026-08-25T07:04:58.007Z","url":"https://daily.dev/posts/JhGIAf4vu#c-aCRJptYII","author":{"@type":"Person","name":"László Szabó","url":"https://daily.dev/lezli01","image":"https://lh3.googleusercontent.com/a/ACg8ocKj3v7EFYJoXUUuro6ALF9fD3RTRATiBpBOVcOzqro4fy6bWqMm=s96-c"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/grpc-rust-roadmap-jhgiaf4vu#faq","mainEntity":[{"@type":"Question","name":"Is there a server-side API for gRPC-Rust yet?","acceptedAnswer":{"@type":"Answer","text":"Not yet as a released feature; it is under active development as the biggest priority following the client-side preview release. It will be built as a natural extension of the client API, sharing types where possible, with another preview announcement planned once it is ready. Rust developers building RPC services can follow gRPC-Rust's progress toward a server API on daily.dev."}},{"@type":"Question","name":"What Google Cloud use cases does xDS support enable for gRPC-Rust?","acceptedAnswer":{"@type":"Answer","text":"Full xDS support, built on Envoy, enables both proxyless service mesh (PSM) use cases and direct connectivity for Google Cloud services. This is described as a longer-term goal the gRPC-Rust team plans to focus heavily on over the following several months, alongside significant features like retries, binary logging, Channelz debugging, keepalive, and authorization. Engineers evaluating service mesh options for Rust services can track xDS and Envoy developments via daily.dev."}},{"@type":"Question","name":"Why hasn't gRPC-Rust adopted Abseil's Status type directly?","acceptedAnswer":{"@type":"Answer","text":"gRPC-Rust intends to standardize on a shared Rust RPC status type rather than reuse Abseil's Status directly, because minor internal differences between the C++ gRPC status type and absl::Status have caused pain despite their similarity. The team is waiting for stabilization of Rust's Try trait, which will let the new type ergonomically support useful features. Rust API designers weighing error-handling tradeoffs can keep up with Try trait stabilization news on daily.dev."}}]} ```