Hey Product Hunt! 👋 I’m Kamil Mościszko (Raezil), and I’m introducing gRPC–GraphQL Gateway from Protocol Lattice. Your backend speaks gRPC. Your frontend wants GraphQL. You shouldn’t have to maintain a second set of API definitions to connect them. The gateway generates a typed GraphQL API from your annotated protobuf descriptors and routes requests to your existing gRPC services. Your service definitions stay at the center—without a handwritten resolver layer. Here’s what you can build: Queries and mutations from your RPCs. Annotate your methods to expose read and write operations through GraphQL. Real-time experiences from server streams. Turn server-streaming RPCs into GraphQL subscriptions delivered over WebSocket. A connected graph across services. Use Apollo Federation v2 to bring your gRPC-backed APIs into a supergraph, with DataLoader batching for entity resolution. Beyond schema generation, the gateway includes response caching, persisted queries, query depth and complexity limits, Prometheus metrics, and OpenTelemetry tracing. It’s written in Rust and released under the MIT license. This is for teams that want to keep their gRPC services while giving web and application developers a GraphQL interface. I’d love to hear where this fits into your stack—and what would make it easier to adopt. Which gRPC service would you expose through GraphQL first? 🚀

gRPC Graphql Gateway

api, grpc, graphql

api, grpc, graphql