Bruno

Bruno is a Git-native API client for exploring and testing APIs. It supports REST, GraphQL, gRPC and WebSocket, with assertions, test scripting, collection automation and CI/CD integration. Collections are plain-text files kept in project repositories for Git versioning and review. Users can set up multiple environments, switch between them, use variables and run JavaScript before requests or after responses. Bruno includes a desktop client, CLI, IDE extension, API documentation generator and mock server using the same collection format. Collections can also be published as interactive HTML documentation with code samples and a live playground. Collections, environments and secrets are stored on the user's device, and Bruno says project data is not sent to the cloud. However, the startup license check sends an IP address, license key, hashed device ID and Bruno version. The free Open Source plan includes two workspaces and five OpenAPI syncs per month. Pro is $6 a month billed annually; a 14-day Ultimate trial is available without a credit card.

Bruno centers API work on versionable local collections and offers several client and automation tools. Consider the free plan's workspace and sync limits, as well as the startup license check's transmitted details.

Bruno may suit developers who want API collections stored and reviewed with Git. Its desktop, CLI and IDE options serve workflows that use testing, automation or CI/CD.

Bruno is an API client and testing toolkit built around collections saved as plain-text files in a project repository. It is best suited to developers who want API requests and tests managed alongside code. Its Git-centered workflow is a strong reason to choose it, while the free plan’s sync cap and annual billing on paid plans call for a careful fit check.

Overview

Bruno’s collections can be versioned and reviewed through Git, making it a natural choice for teams whose API work belongs in the same repositories as their projects. Collections, environments, and secrets stay on the user’s device; Bruno says it does not store user data in the cloud. That model will appeal to teams prioritizing local files, but is less suited to those who want cloud storage at the center of their collaboration.

Local storage does not mean zero outbound traffic: Bruno makes an HTTPS license-validation call at startup that sends the IP address, license key, hashed device ID, and Bruno version. Bruno says project data is not sent in that call. The company states that it is SOC 2 Type I certified and independently audited against AICPA Trust Services Criteria, and describes internal role-based access, multi-factor authentication, code reviews, dependency audits, and an incident response plan.

Key features

Bruno supports REST, GraphQL, gRPC, and WebSocket APIs. Assertions, test scripts, collection automation, scheduled runs, and CI/CD integration give teams ways to make collections part of repeatable testing rather than just manual request exploration. Multiple environments, variables, and pre-request and post-response JavaScript scripts help adapt that work across setups.

The same collection format extends across Bruno’s desktop client, CLI, IDE extension, documentation generator, and mock server. Collections can also become interactive HTML documentation with code samples and a live playground. Integrations include Git providers and secret managers such as Vault, Azure Key Vault, and AWS. This breadth is useful for teams that want one collection to support development, testing, and documentation, though the value depends on adopting Bruno’s repository-based format.

Pricing

The Open Source plan costs nothing and includes two workspaces, five OpenAPI syncs per month, and community support. It is a sensible way to start, but the workspace limit can constrain teams with multiple projects, and five monthly syncs may be restrictive for frequent OpenAPI updates.

Pro costs $6 a month (billed annually) and adds unlimited workspaces while retaining the five-sync monthly cap. It fits users who need more room for projects but not more sync capacity. Ultimate costs $11 a month (billed annually) and includes unlimited workspaces, unlimited OpenAPI syncs, and unlimited license admins; it is the clearer fit for teams that need sync capacity or more license administrators. Both paid plans use annual billing. Bruno offers a 14-day Ultimate trial with no credit card required.

Platforms

Bruno lists desktop versions for Windows, macOS, and Linux, along with an IDE extension and API access. Its desktop client and CLI provide distinct ways to work with the same collections.

Who it's for

Bruno is a strong fit for developers and teams that want API requests, tests, and documentation kept in versionable project files, especially when CI/CD and automation matter. It is less compelling for teams that prefer cloud-centered shared collections, or whose workspaces and OpenAPI sync needs exceed the free plan’s caps without justifying a paid annual subscription.

Pros and cons

• Pro: Plain-text collections in project repositories make API changes versionable and reviewable through Git.
• Pro: REST, GraphQL, gRPC, and WebSocket support, plus automation and CI/CD integration, covers a broad API testing workflow.
• Pro: Local storage keeps collections, environments, and secrets on the user’s device rather than in Bruno’s cloud.
• Con: The free plan allows only two workspaces and five OpenAPI syncs per month, which can limit broader or fast-moving projects.
• Con: Pro and Ultimate are billed annually, and Pro keeps the same five-sync monthly cap as the free plan.
• Con: Startup license validation sends the IP address, license key, hashed device ID, and Bruno version over HTTPS.

Alternatives

For a different API workflow, consider Parasoft SOAtest, which offers tailored pricing based on business needs and a free trial. Apidog is another freemium option, with a time-unlimited free plan for four users. Insomnia may suit users who want a free Essentials tier with Git Sync projects for three users and 1,000 mock-server requests per month. Karate offers a free, MIT-licensed framework for API testing as well as browser and desktop UI automation and Gatling performance testing.

Kreya is a freemium option for individuals whose request history limit is acceptable. Pact is worth considering for those seeking open-source tooling. Postman offers a free tier with an API client, core tools, specs, mock servers, Native Git, and Collection Runner. Yaak is another freemium desktop option. Browse more API Testing Tools or API clients.

Verdict

Choose Bruno if you want API collections to live as reviewable, version-controlled files and need testing and automation built around them. Its protocol coverage and local-first model are compelling for repository-centered development. Look elsewhere if cloud-centered collaboration is essential, or if the free plan’s workspace and sync limits are too tight and annual paid billing is not a fit.