Bruno vs Hoppscotch
Which should you use? A side-by-side look at what each one does, who it suits, what it costs, how hard it is to set up, and where each falls short.
Open source · MIT
Free, offline-first desktop app for exploring and testing APIs, storing collections as files.
Open source · MIT
Open-source app for building, sending, and testing API requests in the browser, desktop, or CLI.
The short answer
Choose Bruno if you need…
- Developers who want to test HTTP or GraphQL APIs without an account or cloud sync
- Teams that already keep code in Git and want API collections stored alongside it
- People who want to run API test collections in CI/CD using the Bruno CLI
- Users who care about keeping API data on their own device
Choose Hoppscotch if you need…
- Developers who want to test REST, GraphQL, WebSocket, or other APIs without a heavy desktop client
- Teams that want to share collections and environments across members
- People who prefer an open-source tool they can self-host or run offline
- Developers who want to run API tests from the command line via the Hoppscotch CLI
Side-by-side
| Bruno | Hoppscotch | |
|---|---|---|
| Type | App | App |
| Price | Free and open source | Free and open source |
| Licence | MIT | MIT |
| GitHub stars | 48k | 80.7k |
| Setup difficulty | Beginner | Beginner |
| How you get it | Download the app | Use it in the browser (or self-host) |
| Main language | JavaScript | TypeScript |
| Last code update | 4 days ago | 6 days ago |
What each one is
Bruno
Bruno is a desktop app for sending requests to APIs and checking the responses, similar in purpose to Postman or Insomnia. It saves your request collections as plain-text files in a folder on your computer, so they can be versioned with Git and shared like any other project files. The README states it is offline-only and has no plans for cloud sync.
Hoppscotch
Hoppscotch is an open-source tool for making and testing requests to web APIs. You enter a URL, choose a method such as GET or POST, send the request, and inspect the response. It is offered as a web app, a installable desktop or PWA app, and a command-line interface, and the README positions it as an open-source alternative to Postman and Insomnia.
Best for
Bruno
- Developers who want to test HTTP or GraphQL APIs without an account or cloud sync
- Teams that already keep code in Git and want API collections stored alongside it
- People who want to run API test collections in CI/CD using the Bruno CLI
- Users who care about keeping API data on their own device
Hoppscotch
- Developers who want to test REST, GraphQL, WebSocket, or other APIs without a heavy desktop client
- Teams that want to share collections and environments across members
- People who prefer an open-source tool they can self-host or run offline
- Developers who want to run API tests from the command line via the Hoppscotch CLI
Strengths
Bruno
- Collections are stored as plain files, which works well with Git and other version control
- Works offline and keeps data on the local device, per the README
- Available for Mac, Windows and Linux, with the CLI usable in automated pipelines
Hoppscotch
- Open source under the MIT license with a large community (about 80,700 stars at the time of metadata)
- Supports many protocols beyond basic HTTP, including GraphQL, WebSocket, and MQTT
- Available as a web app, PWA, and CLI, with offline support noted in the README
Not ideal for
Bruno
- Teams that need cloud-synced collections across machines, since the README says Bruno is offline-only and has no plans for cloud sync
- People looking for a hosted service with built-in team dashboards, as the README describes Bruno as a local tool with paid versions for extra features
Hoppscotch
- Users who need features the README does not describe; the README is truncated and feature depth is not fully covered
- People who want a fully managed, closed hosted service with no interest in self-hosting or sync setup
- Non-developers with no need to call APIs
Trade-offs
Bruno
- The README does not describe the full feature set, so specific capabilities need checking in the documentation
- Cloud sync and team hosting are not offered; the README points to paid versions for additional features
- The README is truncated, so details on paid tiers and edge-case behavior are unclear
Hoppscotch
- Some features, such as cloud sync and teams, depend on signing in and may involve a hosted service
- The README is truncated and does not fully document installation for every platform
- The latest release listed has no downloadable binaries, so setup may require building from source or using the web app
Getting started
Bruno
Install on Mac via Homebrew
brew install brunoInstall the Bruno CLI from npm
npm install -g @usebruno/cliHoppscotch
Clone the repository
git clone https://github.com/hoppscotch/hoppscotchFrequently asked questions
What is the difference between Bruno and Hoppscotch?
Bruno: Free, offline-first desktop app for exploring and testing APIs, storing collections as files. Hoppscotch: Open-source app for building, sending, and testing API requests in the browser, desktop, or CLI. Bruno suits developers who want to test http or graphql apis without an account or cloud sync, while Hoppscotch suits developers who want to test rest, graphql, websocket, or other apis without a heavy desktop client.
Are Bruno and Hoppscotch free?
Bruno: Free and open source. Hoppscotch: Free and open source.
Is Bruno or Hoppscotch more popular?
Hoppscotch has more GitHub stars (80.7k) than Bruno (48k). Popularity isn't the same as fit — check which one matches your use case above.
What are other alternatives to Bruno and Hoppscotch?
Other options people compare them with include Scalar, AI Website Cloner, Yaak, Krayin CRM, Vue Admin Better.
Keep comparing
Built from our catalogue entries for both products: open-source details come from each project's README (AI-assisted, refreshed weekly) and GitHub data; AI-tool details are editorial. Spotted something wrong? Let us know from either product's page.