🔗 Ecosystem

Ecosystem: Bruno doesn't ask you to throw away tools you already use — it plugs into them. Think of it like moving house with a removals company rather than starting from an empt

Bruno doesn't ask you to throw away tools you already use — it plugs into them. Think of it like moving house with a removals company rather than starting from an empty flat: your furniture comes with you, it just ends up in a building you own instead of one you rent. Already have 200 requests in Postman? Import them in one step. Have an OpenAPI/Swagger spec? Generate a whole collection from it. Live in VS Code all day? There's an extension so you barely have to leave it. But why should a tool's ecosystem weigh into your decision at all — surely the tool that tests best wins? Because in practice nobody adopts a tool in isolation; they adopt it into a team that already has 200 requests, a Swagger spec, a CI pipeline and a Jira board. A tool with no import path is not "a different choice", it is a migration project — and migration projects get postponed forever. The ecosystem is what decides whether adopting something takes an afternoon or a quarter. The comparison worth making is with Selenium and Playwright: neither won on raw browser control alone. They won because they fit into Maven/npm, into Jenkins, into the reporting tools teams already ran. Bruno's story is the same shape one layer up — it fits into Git, and therefore into every review and CI process built on Git. For a QA engineer the payoff is concrete: you can adopt it for one service without a big-bang migration, keep Postman running for the collections nobody has moved yet, and still have your new API tests gated in the pipeline this sprint.

Migrating From Postman or OpenAPI

Export your Postman collection

In Bruno: Import Collection

Bruno converts requests to .bru files

Or skip Postman entirely

Beyond REST — Other Protocols

VS Code Extension & Bruno Cloud

Bruno Ecosystem — What Plugs Into What

The VS Code extension lets you view and lightly edit .bru files with syntax highlighting right inside your editor — handy when you're already there fixing a backend bug and want to peek at the related test. Bruno Cloud is an entirely optional paid layer for teams that want some cloud convenience (shared secrets, team sync) without giving up the local-first, Git-based core — it sits on top of the same .bru files, it doesn't replace them.

🎬 No Wi-Fi on the Plane: Offline-First Architecture in Action

A QA engineer is on a flight, no internet, but still needs to run this morning's API regression.

Step 1 — Bruno opens: the .bru files are already on disk, no cloud connection required. The collection loads instantly.

Step 2 — the local API server (localhost:3000, a mock/test server that runs fine on the plane too) is targeted. The request needs no internet, it just loops on the same machine.