gRPC Studio
github.com
- Free plan
- Linux
- Web
- Self-hosted
What gRPC Studio is
gRPC Studio is a free, open-source web interface for exploring and invoking gRPC services. It uses gRPC server reflection v1 and v1alpha to discover available services, so the target server must provide reflection. The interface supports unary, server-streaming, client-streaming, and bidirectional-streaming calls. It builds request forms from protobuf definitions, including nested and repeated fields, maps, oneofs, enums, bytes, timestamps, and wrapper types. A single self-hosted instance can connect to multiple targets and switch between them. Each target can use TLS or mTLS, while authentication plugins provide outbound metadata. The web UI can optionally use Microsoft Entra ID. Users can edit request headers, review per-method history, and create shareable request links. The backend exposes Prometheus metrics, and Docker images support Docker Compose and Kubernetes deployment. The repository uses the BSD-3-Clause license.
Who it suits
It suits developers and teams exploring or calling reflection-enabled gRPC services. Self-hosted Linux or web deployments fit teams managing their own environment.
Good to know, and what to watch
- Supports all four listed gRPC RPC patterns
- Dynamic forms cover complex protobuf field types
- Connects to multiple targets in one instance
- TLS and mTLS configurable per target
- Prometheus metrics and container deployment documentation
- Requires server reflection for service discovery
- Binary -bin request headers are unsupported
- No free trial is listed
The verdict
gRPC Studio brings service discovery, request building, security settings, and history into one self-hosted interface. Its reflection requirement and unsupported binary headers are important fit checks.
What the maker publishes
- Authentication
- The backend supports authentication plugins for outbound metadata, and the web UI can optionally use Microsoft Entra ID authentication. source
- Authentication
- The backend supports outbound metadata auth plugins, and the web UI can optionally use Microsoft Entra ID authentication. source
- Compatibility limit
- The target gRPC server must support reflection for gRPC Studio to discover services. source
- Connection security
- Outbound gRPC connections can use TLS or mTLS, configured per target. source
- Deployment
- The project provides Docker images and documentation for Docker Compose and Kubernetes deployment. source
- Deployment
- The project documents Docker Compose, prebuilt GitHub Container Registry images, and Kubernetes deployment. source
- Deployment security
- The Docker deployment guide says both images run as non-root users and recommends read-only config mounts; it also describes TLS/mTLS support for backend gRPC connections. source
- Intended users
- The project is for people exploring and invoking gRPC services; its quick start recommends connecting it to a reflection-enabled server. source
- License
- The repository is licensed under BSD-3-Clause. source
- License
- The repository identifies the project as BSD-3-Clause licensed. source
- Multiple targets
- One instance can connect to multiple gRPC targets and switch between them in the UI. source
- Multiple targets
- One instance can connect to multiple gRPC targets and switch between them in the UI. source
- Observability
- The backend exposes Prometheus metrics for HTTP requests, gRPC calls, WebSocket connections, caches, and Node.js process metrics. source
- Observability
- The backend exposes Prometheus metrics, and its deployment guide describes optional OpenTelemetry tracing. source
- Prerequisite
- The target gRPC server must support server reflection for service discovery. source
- Protobuf forms
- It renders dynamic protobuf request forms, including nested messages, maps, oneofs, enums, bytes, timestamps, and wrapper types. source
- Purpose
- gRPC Studio is a reflection-based UI for exploring and calling gRPC services. source
- Purpose
- gRPC Studio is a reflection-based UI for exploring and calling gRPC services. source
- Request forms
- It renders dynamic protobuf request forms, including nested messages, repeated fields, maps, oneofs, enums, bytes, timestamps, and wrapper types. source
- Request history
- It supports per-method request history and shareable request links. source
- Request history and sharing
- It provides per-method request history and shareable request links. source
- Request metadata
- Users can edit custom gRPC headers per request; binary -bin keys are not supported, and configured auth-plugin and trusted user headers take precedence over user-supplied metadata. source
- RPC support
- It supports unary, server-streaming, client-streaming, and bidirectional-streaming RPCs. source
- RPC support
- It supports unary, server-streaming, client-streaming, and bidirectional-streaming RPCs. source
Checked against the maker's pages on 7 Oct 2026.