grpc

grpc-go: Build Go Services with gRPC over HTTP/2

grpc-go is the Go implementation of gRPC, an open-source RPC framework built around HTTP/2 with mobile and HTTP/2 as priorities. It gives Go teams a framework for building and connecting services through remote procedure calls.

ActiveGoApache-2.0GolangLibraryNetworking
Stars
23.1k
Forks
4.8k
Stars, last 30 days
+30
Last commit
1 day ago
Contributors
100+

Our take

Activeregular commits and releases

Health score

68/100

How it is scored
Activity
79
Community
91
Issues
58
Pull requests
43

+30 stars in the last 30 days

  • More contributors than 78% of the projects we track
  • Slower to merge pull requests than 83% of the projects we track

grpc-go is an actively maintained Go implementation of gRPC, with frequent commits and releases and contributions spread across many people.

Good fit if

  • Your services are written in Go and you want to use gRPC over HTTP/2.
  • You want an established project with recent releases and active development.
  • Apache-2.0 licensing works for your project.

Look elsewhere if

  • Your application does not need RPC or HTTP/2-based service communication.
  • You need a library for a language other than Go.
All health signals
Last commit2026-10-23 (1 day ago)
Commits, last 90 days100+
Releases, last 12 months19 (latest v1.84.0, 2026-09-17)
Contributors100+ (top contributor: 22% of commits)
Issues closed, last 90 days8+ (typically closed in 4 days)
Pull requests merged, last 90 days36 (typically merged in 3 days)
Project age11 years

Checked on 2026-10-25 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

23,120

Forks

4,825

Change since Nov 17, 2026: +6 stars·+3 forks

Overview

grpc-go is the Go implementation of gRPC, an open-source RPC framework built around HTTP/2. It is designed for high-performance service communication, with mobile and HTTP/2 as priorities.

The project is for Go developers building services that need to call one another through RPCs. The official Go gRPC documentation provides a quick start and API reference; this repository also includes technical documentation and examples.

Key Features

  • Implements the gRPC framework for Go.
  • Uses HTTP/2 as the foundation for RPC communication.
  • Supports Go module installation through the google.golang.org/grpc import path.
  • Includes examples and low-level technical documentation in the repository.
  • Provides a public Go API reference and quick-start documentation.
  • Offers configurable logging through environment variables.

Use Cases

  • Go teams building services that communicate through remote procedure calls.
  • Developers connecting mobile clients to backend services using gRPC.
  • Service owners who need HTTP/2-based communication between Go components.
  • Go developers evaluating an established RPC framework for a microservices architecture.

What you need

Detected in the repository

  • Go 1.26.0 or newer (from go.mod)
  • A test suite and automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Import the package in your Go code:

import "google.golang.org/grpc"

Go build tools can fetch the dependency automatically. See the README and quick start for setup and usage details.

Considerations

  • The project requires Go; the supplied repository metadata identifies Go 1.26.0 as its runtime requirement.
  • The README recommends using one of the two latest major Go releases, so check compatibility with your toolchain before adopting a specific version.
  • Some environments may not be able to access the golang.org domain, which can prevent fetching the module. The README describes a module replacement workaround, including for transitive dependencies.
  • A client-side Unavailable error can result from server shutdown, handshake failures, disrupted connections, or keepalive settings. Diagnosing it may require logging on both client and server.

Found this useful?

Share it with someone who would like grpc-go.