Bruno vs Hoppscotch
| Attribute | Bruno | Hoppscotch |
|---|---|---|
| Where it runs | Desktop app for Mac, Windows, and Linux, offline only | Browser or PWA, desktop apps, or self-hosted |
| Where collections live | Plain-text files in a folder you can keep in Git | Its workspace, with import and export |
| Importing from Postman | Collections and environments | Collections (v2.0 and v2.1) and environments |
| Protocols | REST, GraphQL, gRPC, WebSocket, SOAP, and SSE | REST, GraphQL, WebSocket, SSE, MQTT, and Socket.IO |
| Purpose | An API client that stores collections as files. | An API client that runs in the browser. |
| Documented capabilities | Git-friendly collections, Offline desktop app, No account required | HTTP and GraphQL requests, Browser client, Self-host option |
| Best-fit workflow | API teams that want requests stored in the same repo as the service. | Developers who want an API client without a heavy desktop install. |
| Check before choosing | It is a local client, not a hosted collaboration workspace. | Check whether your team needs the offline collections and governance a desktop client provides. |
| Deployment options | Desktop | Docker, Web |
| GitHub stars | 48,432 | 80,842 |
| License | MIT | MIT |
| Self-hosted | Yes | Yes |
| Docker noted | Not recorded | Yes |
| Cloud / hosted | Not recorded | Yes |
| Primary language | JavaScript | TypeScript |
| Last commit | 2026-11-17 | 2026-11-05 |
| Difficulty | Easy | Easy |
| Content source | Editorial catalog entry | Editorial catalog entry |
| Metadata checked | 2026-11-18 | 2026-11-18 |
| Forks | 3.1k | 6.2k |
| Star growth | +1134 (2026-10-01 to 2026-11-18) | +284 (2026-10-01 to 2026-11-18) |
| Alternative to | Postman | Postman |
This comparison uses recorded capabilities, not hands-on performance tests. A capability missing from one record does not mean that product lacks it. Confirm edition, version and current pricing in the official documentation.
Bruno or Hoppscotch?
Both are MIT-licensed Postman alternatives that import Postman collections and environments. Pick Bruno when you want collections in Git: it is an offline-only desktop app that saves requests as plain-text files in a folder on your disk, has a CLI for CI runs, and has no plans for cloud sync.
Pick Hoppscotch when you want an API client in the browser that your team can also self-host: it runs as a web app or installable PWA, with desktop apps and a CLI, and supports REST, GraphQL, WebSocket, Server-Sent Events, MQTT, and Socket.IO. Single sign-on is an Enterprise edition feature.
When to consider Bruno
API teams that want requests stored in the same repo as the service.
It is a local client, not a hosted collaboration workspace.
Bruno documentation and sourceWhen to consider Hoppscotch
Developers who want an API client without a heavy desktop install.
Check whether your team needs the offline collections and governance a desktop client provides.
Hoppscotch documentation and sourceBruno vs Hoppscotch questions
- Bruno vs Postman vs Hoppscotch: which should I use?
- If you want to keep collections in Git with no cloud sync, pick Bruno. If you want a browser-based client your team can self-host, pick Hoppscotch. Both import Postman collections and environments.
- What is Bruno?
- An API client that stores collections as files.
- What is Hoppscotch?
- An API client that runs in the browser.
- Can you self-host Bruno and Hoppscotch?
- Both can be self-hosted.
- What licenses do Bruno and Hoppscotch use?
- Bruno uses the MIT license. Hoppscotch uses the MIT license.
- Which has more GitHub stars, Bruno or Hoppscotch?
- Hoppscotch has 81k stars and Bruno has 48k. Stars show attention; check recent commits and releases for maintenance.
- What languages are Bruno and Hoppscotch written in?
- Bruno is mainly written in JavaScript. Hoppscotch is mainly written in TypeScript.