Most net stars, last 30 days
trpc/trpc🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
+112
18% of the net stars of this Tag
Tags / Backend and APIs /
A framework for remote procedure calls between services, such as gRPC or Thrift.
The 29repositories with this Tag gained +624 net stars in the last 30 days, 49% less than the 30 days before.
0 created in the last 90 days · 10 published a release in the last 30 days · 338K stars in total
Oct 5, 2026Nov 3, 2026
Most net stars, last 30 days
trpc/trpc🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
+112
18% of the net stars of this Tag
Largest Pace, last 30 days
No other repository gained 2 or more times the net stars of the 30 days before.
Most stars, created in the last 90 days
No other repository with this Tag was created in the last 90 days.
Net stars gained each week. The repositories that gained the most have their own color.
GetBindu/Bindu gained 52% of the net stars of this Tag in the last 13 weeks.
29 repositories with this Tag. Select a column name to change the order.
| # | Repository | Stars | Gained, 90 days | Pace | |
|---|---|---|---|---|---|
| 1 | GetBindu/Bindu Bindu: The identity, communication, and payments layer for AI agents. | 10K | +2,199 | 0.7× | |
| 2 | trpc/trpc 🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy. | 41K | +385 | 0.8× | |
| 3 | grpc/grpc C++ based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) | 45K | +323 | 0.5× | |
| 4 | zeromicro/go-zero A cloud-native Go microservices framework with cli tool for productivity. | 33K | +260 | 0.7× | |
| 5 | grpc/grpc-rust A native gRPC client & server implementation with async/await support. | 13K | +159 | 0.4× | |
| 6 | grpc/grpc-go The Go language implementation of gRPC. HTTP/2 based RPC | 23K | +145 | – | |
| 7 | apache/dubbo The java implementation of Apache Dubbo. An RPC and microservice framework. | 42K | +138 | – | |
| 8 | capnproto/capnproto Cap'n Proto serialization/RPC system - core tools and C++ library | 13K | +119 | – | |
| 9 | apache/brpc brpc is an Industrial-grade RPC framework using C++ Language, which is often used in high performance system such as Search, Storage, Machine learning, Advertisement, Recommendation etc. "brpc" means "better RPC". | 18K | +98 | – | |
| 10 | cloudwego/kitex Go RPC framework with high-performance and strong-extensibility for building micro-services. | 8.1K | +75 | – | |
| 11 | apache/thrift Apache Thrift | 11K | +59 | – | |
| 12 | goadesign/goa Design-first Go framework that generates API code, documentation, and clients. Define once in an elegant DSL, deploy as HTTP and gRPC services with zero drift between code and docs. | 6.1K | +41 | – | |
| 13 | grpc/grpc-java The Java gRPC implementation. HTTP/2 based RPC | 12K | +38 | – | |
| 14 | Cysharp/MagicOnion Unified Realtime/API framework for .NET platform and Unity. | 4.5K | +30 | – | |
| 15 | TarsCloud/Tars Tars is a high-performance RPC framework based on name service and Tars protocol, also integrated administration platform, and implemented hosting-service via flexible schedule. | 10K | +26 | – | |
| 16 | square/wire gRPC and protocol buffers for Android, Kotlin, Swift and Java. | 4.4K | +25 | – | |
| 17 | smallnest/rpcx TranslatedBest microservices framework in Go, like alibaba Dubbo, but with more features, Scale easily. Try it. Test it. If you feel it's better, use it! Java has dubbo, Golang has rpcx! build for cloud! | 8.3K | +23 | – | |
| 18 | grpc/grpc-dotnet gRPC for .NET | 4.5K | +21 | – | |
| 19 | zeroc-ice/ice All-in-one solution for creating networked applications with RPC, pub/sub, server deployment, and more. | 2.2K | +16 | – | |
| 20 | meta/fbthrift Meta's Thrift implementation: cross-language serialization and high-performance async RPC | 2.7K | +14 | – |
Net stars of the last 30 days are 2 or more times those of the 30 days before.
No repository with this Tag meets this rule now.
Net stars of the last 30 days are 50% or less of those of the 30 days before.
Created on GitHub in the last 90 days.
No repository with this Tag meets this rule now.
Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.
The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.
All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.
For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.
The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.
The chart at the top adds up the net stars of all the repositories with the Tag. The darker area is the part from the Seed Dataset; the rest is from rising Admissions. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time. The repositories of the Seed Dataset are a set that does not change.
The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.