Bruno.

About Bruno

Bruno is an open-source, Git-native API client for building, testing, documenting, and automating API workflows. Instead of storing collections in a cloud workspace or a proprietary database, Bruno keeps requests and related configuration as plain-text files inside a project directory. This makes API collections easy to inspect, version, branch, review, and share alongside application code. Bruno supports REST, GraphQL, gRPC, and WebSocket workflows through a desktop application, command-line tools, and editor integrations. Developers can organize requests into folders, define environments and variables, add authentication settings, run scripts, inspect responses, and create assertions for automated checks. Collections can be used interactively during development or executed in CI/CD pipelines. The local-first approach keeps requests, responses, environments, and credentials under the team’s control. Developers can work without an account or cloud synchronization, and collaboration can happen through the Git provider and repository workflow they already use. This can be useful for teams that want API work to follow the same review, branching, and access controls as source code. Bruno’s collection format is designed to be human-readable and diff-friendly. Requests can be reviewed in pull requests, updated as APIs evolve, and kept close to the code or documentation they describe. The same collections can support local API exploration, automated testing, generated documentation, and mock-server workflows, reducing duplication between development and testing tools. The client includes support for request scripting, response assertions, environment variables, API authentication, OpenAPI-related workflows, and integrations for handling secrets. Its CLI can run collections and tests from automation systems, while editor extensions let developers work with API requests without leaving their coding environment. Bruno is a strong fit for developers and teams that want an open-source API client with local storage, Git integration, offline-friendly workflows, and support for multiple API protocols. It may be less suited to organizations that specifically need a centralized hosted workspace with extensive built-in collaboration and governance, although enterprise capabilities and support options are available. Teams should review the current license, pricing, and feature details before standardizing on it.