Bruno stores and tests API requests as local files that can be versioned with Git.

The main limitation: Git collaboration features require a paid edition

Bruno keeps collections on your computer rather than synchronizing them through a shared cloud workspace. That supports offline work and local control, but it also means there is no built-in real-time collaboration. In the free Open Source edition, Git push, branching, and merging inside the app are not available; those operations and some team features are reserved for Pro and Ultimate.

For developers who prefer requests alongside source code, Bruno saves each collection as plain text files in a folder you choose. Putting that folder in a project’s Git repository lets teams review and version API requests using their existing repository workflow, without creating an account or syncing collection data to a vendor cloud.

Working with requests and collections

The client supports HTTP, REST, GraphQL, and gRPC requests. Environments and variables help organize values used across requests, while secret management provides a way to handle sensitive values within the collection workflow. These features make it possible to keep related API definitions together rather than treating each request as a separate document.

Bruno also supports JavaScript pre-request and post-response scripts, along with assertions for checking responses. A collection runner can execute requests as a group, which is useful when validating a sequence or rerunning a set of checks after an API change. The Open Source edition includes an unlimited collection runner, as well as code generation.

Moving existing API work into Bruno

Collections can be imported from Postman and Insomnia, and Bruno can also import OpenAPI specifications. This provides a route for bringing existing request definitions into a local-file workflow. After import, collections can be kept in a chosen folder and committed to a repository like other project files.

For a new collection, the practical setup is to create or open one on first launch and select its storage folder. Choosing a folder inside the relevant Git repository keeps API work close to the code it supports. Because the application does not require an account, setup does not depend on establishing a cloud workspace.

Edition and platform details

The Open Source edition is released under the MIT License. It includes request types, environments, secret management, scripting, tests, code generation, and collection execution. Pro and Ultimate add full Git operations within the application, unlimited workspaces, data-driven runs, report generation, and enterprise features such as SSO. The free edition is limited to two workspaces.

Bruno runs on Windows (x64 and ARM64), macOS, and Linux. Its local-first design is suited to individual developers and teams comfortable managing collection files through Git. Teams that need real-time cloud sharing or in-app Git operations in the free edition will encounter the main trade-offs of this approach.

Leave a Comment