Bruno fits a developer or team that wants API collections stored as plain files on disk, shared through Git, with no account or cloud sync. Hoppscotch fits a team that wants an API tool it can open in a browser, on the desktop or in a terminal, with a hosted cloud service or a self-hosted workspace to share from.
Two open source API clients, two very different ideas of where your requests should live. Bruno keeps everything as folders and text files on your own machine. Hoppscotch runs in the browser, on the desktop and on the command line, and gives you a workspace you can use in its cloud or host yourself. If you're leaving a heavier client and want something open source, that difference shapes your week far more than any single feature.
Files in Git or a workspace you host
Bruno's pitch is simple: everything is folders and text files on your filesystem, and your data never leaves your machine. Bruno says there's no cloud sync, no account and no login. That makes Git the sharing method. Your collection sits in the repo next to the code it tests, it's reviewed in the same pull requests, and history comes from your commits. For a team already living in Git, that's a natural fit; for a team that doesn't use Git, it's a new habit to learn before anyone can share a request.
Hoppscotch's docs lead somewhere else. They describe it as open source and available offline, on-prem and in the cloud, with web, desktop and CLI apps. The web client needs no installation, the desktop app covers macOS, Windows and Linux, and you can deploy your own instance on your own infrastructure through a Community Edition or an Enterprise Edition. There's also a cloud service hosted by Hoppscotch. So the sharing model is a workspace, either theirs or one you run.
Neither model is more open than the other; they put the source of truth in different places. One keeps it in your repo, the other in a workspace your team signs into.
Where Bruno fits and where Hoppscotch fits
Bruno fits a developer who wants requests versioned with the code and nothing stored on someone else's server. Its free edition is described as open source and built for the crafty engineer, and it covers HTTP, REST, GraphQL and gRPC. The docs cover a CLI and mock servers that serve realistic responses while you build, so front-end work can carry on before an endpoint is finished. Bruno's homepage cites four million users and more than five hundred contributors.
Hoppscotch fits a team where not everyone wants to install something, or where people switch between laptops and a browser tab. REST testing supports HTTP methods, headers, parameters, body, auth and pre-request scripts, and the CLI runs API tests from your terminal and CI/CD pipelines. Its feature list also includes personal access tokens, history, a Spotlight search, shortcuts, scripts and an importer.
On cost, Bruno's Open Source edition is free and its paid tiers are priced per user per month, billed annually. For Hoppscotch, check its pricing page for how the cloud service and the Enterprise self-host edition are billed. For a wider field, my guide to Postman alternatives sets out other clients worth a look.
Send three real requests through each client
Take one API you use every week and three requests you send often: a simple GET, an authenticated POST and one with a pre-request script or variable. Install Bruno and open Hoppscotch's web client in a browser tab.
In Bruno, build the three requests, then open the folder on disk and look at the files it wrote. Commit them to a branch and ask a colleague to pull and run them. In Hoppscotch, build the same three in the browser, then try the desktop app and the CLI against the same collection. If your team would self-host, read the Community Edition setup guide alongside, so you know what running your own instance involves.
Finally, run one request from a CI step in each, Bruno through its CLI and Hoppscotch through its CLI. Whichever feels closer to the way your team already works is the one to trial for a fortnight. If testing is the bigger job, my guide to API testing tools covers tools built mainly for that.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Do you make API clients and API testing tools? Tool makers can ask to be considered for a featured place on this list.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Can I move my Postman collections into Bruno or Hoppscotch?
Yes, both have an import route, but they're documented differently. Bruno documents exporting from Postman as a Collection v2 or v2.1 JSON file and importing it into Bruno, which covers a collection at a time. Bruno also says bulk import of a full Postman data dump needs its Ultimate edition, so a team with many collections should check which edition it'll need before planning the move. Hoppscotch's feature list includes an Importer. Before you commit, export your largest and messiest collection, the one with environments, variables and scripts, and import it into each tool. Then run a handful of requests and check that auth, variables and pre-request scripts came across. Whatever breaks in that import is your clean-up list for the move.
Does Bruno have a cloud or team workspace?
Bruno says there's no cloud sync, account or login, and that your data never leaves your machine. Collections are folders and text files on your filesystem, which is what makes them easy to keep in Git. So sharing happens through your repository: someone commits a change, others pull it, and the history is your commit log. That suits a team that already reviews code in pull requests, because API changes can be reviewed the same way. It's less suited to a team where some people never touch Git, such as testers or analysts who only need to send a request now and then. If that's your situation, a workspace model, hosted or self-hosted, may sit more comfortably, so it's worth asking who on the team will open the tool each week.
Can I self-host Hoppscotch?
Yes. Hoppscotch's docs describe deploying your own instance on your own infrastructure, with a Community Edition and an Enterprise Edition for self-hosting. There's also a hosted cloud service if you'd rather not run anything yourself. Self-hosting suits a team that wants a shared workspace but needs it inside its own network, often for security or data rules. It also means someone has to look after updates, backups and uptime, so that's time to budget for. A sensible first step is to read the Community Edition getting-started guide and try it on a test server, then decide whether the Enterprise Edition's extras matter to you. Check Hoppscotch's pricing page for how the Enterprise Edition and the cloud service are billed before you plan a rollout.
How do Bruno's paid editions work?
Bruno's Open Source edition is free, and its paid tiers, Pro, Ultimate and Enterprise, are priced per user per month and billed annually. The current figures sit on Bruno's pricing page. You can start a free two-week trial of Bruno Ultimate with no credit card, which is a good way to test the features that sit above the free edition, such as bulk import from Postman. Bruno's site also claims that its Enterprise edition can cut costs for teams moving across from Postman; treat that as the vendor's own framing and work out your own numbers from your headcount. The useful question is simple: which features does your team need that the free edition doesn't include? If the answer is none, the open source edition may cover you; if it's bulk import or team features, price the edition that includes them.
How do Bruno and Hoppscotch run in a CI pipeline?
Both have a command line route, so both can run in CI. Hoppscotch's CLI is described as running API tests from your terminal and CI/CD pipelines. Bruno's docs cover a CLI as well, and because Bruno collections are plain files in your repo, the CI job can run straight from the same checkout as your code, with no separate export step. For Hoppscotch, check how your collection reaches the CI runner, whether it's exported to the repo or fetched from a workspace. The practical test is to write one small job in your own pipeline for each tool: a single request with an assertion that fails when the status code is wrong. Time how long each takes to set up and see which output your team finds easier to read when a build goes red.
Do I need to install anything to use Hoppscotch or Bruno?
Hoppscotch's web client runs in the browser with no installation, and there's also a desktop app for macOS, Windows and Linux plus a CLI for terminals. That makes it easy for someone to open a request on a borrowed laptop or a locked-down work machine. Bruno is an offline-first client that stores collections on disk, so you'll install it on each machine that needs it, and the collections come from your Git repository. Neither approach suits every team. A browser tab helps when people move between devices or can't install software, while an installed client with files on disk helps when you want requests to live in version control next to the code. Think about where your team works day to day and which of those two habits is already in place.


