head to head · open source
Bruno vs grpc-gateway
Bruno has 47,992 GitHub stars, 3,068 forks, 1,831 open issues and last shipped yesterday. grpc-gateway has 20,012 stars, 2,415 forks, 149 open issues and last shipped yesterday. Bruno leads on adoption by 140% (47,992 vs 20,012 stars). Bruno is written in JavaScript under MIT; grpc-gateway is written in Go under BSD-3-Clause. Bruno has attracted 6% as many forks as stars, grpc-gateway 12%. Bruno was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (openapi, rest-api), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Bruno | grpc-gateway | |
|---|---|---|
| GitHub stars | ★ 48K | ★ 20K |
| License | MIT | BSD-3-Clause |
| Written in | JavaScript | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 3.1K | ⑂ 2.4K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Bruno if
- You weight community size — 48K stars and counting
- You want the MIT license terms
- Your stack matches JavaScript
- You value the larger contributor base for long-term maintenance
pick grpc-gateway if
- You want the grpc-gateway feature set and don't need the biggest community
- You prefer the BSD-3-Clause license terms
- Your stack matches Go
- You evaluated both and grpc-gateway fits your workflow better
About Bruno
Bruno Opensource IDE for exploring and testing APIs. English Українська Русский Türkçe Deutsch Français Português (BR) 한국어 বাংলা Español Italiano Română Polski 简体中文 正體中文 العربية 日本語 ქართული Nederlands فارسی Bruno is a new and innovative API client, aimed at revolutionizing the status quo represented by Postman and similar tools out there. Bruno stores your collections directly in a folder on your filesystem. We use a plain text markup language, Bru, to save information about API requests. You can use Git or any version control of your choice to collaborate over your API collections. Bruno is offline only. There…
read the full Bruno overview →
About grpc-gateway
gRPC Gateway gRPC to JSON proxy generator following the gRPC HTTP spec About The gRPC Gateway is a plugin of the Google protocol buffers compiler protoc. It reads protobuf service definitions and generates a reverse proxy server which translates a RESTful HTTP API into gRPC. This server is generated according to the google.api.http annotations in your service definitions. This helps you provide your APIs in both gRPC and RESTful style at the same time. Docs You can read our docs at: Testimonials We use the gRPC Gateway to serve millions of API requests per day, and have been since 2018 and through all of that…
read the full grpc-gateway overview →
More in Developer Tools
Related comparisons
More API Development & Testing projects
Compare either of these against the rest of the API Development & Testing field.
Frequently asked questions
Is Bruno or grpc-gateway more popular?
Bruno has 47,992 GitHub stars and grpc-gateway has 20,012. Bruno has the larger community by that measure.
Are Bruno and grpc-gateway free?
Both are open source. Bruno is licensed under MIT and grpc-gateway under BSD-3-Clause. Neither carries a licence fee.
What is the difference between Bruno and grpc-gateway?
Bruno is written in JavaScript and grpc-gateway in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Bruno or grpc-gateway?
Choose Bruno if you want the larger community (47,992 stars) or its MIT licence terms. Choose grpc-gateway if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.