Tools / Bruno

Bruno Review

An offline-first API client that stores collections as plain-text files you can commit to Git

Last reviewed: October 2026

TL;DR

Bruno is an MIT-licensed API client positioned directly against Postman. It saves collections as plain files in a folder using its Bru markup, so teams collaborate through Git rather than a vendor cloud, and its README states there are no plans to add cloud sync, ever. A free open-source edition covers HTTP, REST, GraphQL, gRPC, testing, scripting, and docs, while paid tiers add Git and governance features.

License

MIT (core); Pro and Ultimate are commercial plans

Self-hosted

Yes

Cloud option

None

GitHub stars

47.7K★

Checked October 2026

Category

Developer Tools & API Testing

Pricing

Open Source free; Pro $6 and Ultimate $11 per user per month, billed annually

What is Bruno?

The README describes Bruno as a new and innovative API client aimed at changing the status quo set by Postman and similar tools. It stores collections directly in a folder on your filesystem using a plain-text markup language, Bru, so you use Git or any version control to collaborate. Bruno is explicitly offline-only, and the README says there are no plans to add cloud sync because data privacy should remain on your device. A CLI lets you run collections in automation. The pricing page lists the Open Source edition as free with the core API client (HTTP, REST, GraphQL, gRPC), testing, documentation, scripting, code generation, history, unlimited collection runs, two workspaces, and public Git providers, with the majority of features free and open source. Paid plans fund the project: Pro adds unlimited workspaces, private Git repositories, OpenAPI sync, and a 48-hour support SLA; Ultimate adds secret manager integration, data-driven testing, report generation, audit logs, SSO, SCIM, AI governance, and a 24-hour SLA.

Installation & self-hosting

Bruno is available as a binary download for macOS, Windows, and Linux, and through package managers: Homebrew, Chocolatey, Scoop, winget, Snap, Flatpak, the AUR, and an apt repository with a signing key. A separate Bruno CLI runs collections from a terminal or CI. No account is needed to use the free edition. We did not install it for this review.

User experience

The interface is a desktop request builder with collection folders on the left and request and response panels, similar in layout to other API clients. Because requests are files, Git diffs show exactly what changed. This is drawn from the README and pricing page.

Key features

  • Collections stored as plain-text Bru files in your filesystem
  • Git-based collaboration with no vendor cloud
  • REST, GraphQL, and gRPC support
  • Scripting, tests, docs, and code generation
  • Bruno CLI for CI
  • Optional paid Git, secrets, SSO, SCIM, and audit features

What Bruno does well

  • Privacy-first and offline by design
  • Files in Git make API collections reviewable and portable
  • Free edition covers most solo and small-team needs
  • Very popular: about 47,700 stars and daily commits

Where Bruno falls short

  • No cloud sync means teams must adopt Git workflows
  • Private Git repositories and unlimited workspaces need the paid Pro plan
  • The pricing table was ambiguous on exactly which features split Pro from Ultimate
  • Smaller ecosystem than Postman, particularly for hosted mock servers and monitors

Pricing

Open Source is $0. Pro is $6 per user per month billed annually (unlimited workspaces, private Git repos, unlimited OpenAPI syncs, up to 2 license admins, 48-hour support). Ultimate is $11 per user per month billed annually (secret managers, data-driven testing, reports, audit logs, SSO, SCIM, AI governance, 24-hour support, invoicing). A 14-day Ultimate trial is offered without a credit card.

Bruno vs Postman

Postman is a cloud-centric API platform with collaboration, monitors, mock servers, and workspaces on its servers. Bruno takes the opposite approach with local files and Git, and a lower price for teams, but without hosted monitoring or a vendor-run collaboration cloud.

See all Postman alternatives

Best for

  • Developers and teams already working in Git
  • Privacy-conscious teams that do not want API data in a vendor cloud
  • Anyone looking to cut API-client subscription costs

Not ideal for

  • Teams that rely on Postman's hosted monitors and mock servers
  • Non-technical collaborators who need a shared cloud workspace
  • Organizations that need one vendor-managed system of record

Alternatives

PostmanHoppscotchInsomniaYaak
Compare them all

Final verdict

Bruno is the most compelling Git-native Postman alternative. If your team already lives in Git, the file-based model is a real improvement; if it relies on Postman's cloud features, evaluate the gaps first.

Sources