Bruno

Bruno is an API client for developers who want requests, tests, and automation managed alongside project code. Its Git-based collections are a strong fit for repository-centered teams; the workspace and OpenAPI sync caps on the free plan, and annual billing on paid plans, are the main compromises.

Overview

Bruno stores API collections as plain-text files in a project repository, where teams can version and review changes through Git. Collections, environments, and secrets stay on the user’s device, and Bruno says it does not store user data in the cloud. This model suits teams that treat API work as part of the codebase, but is less suited to those who want a cloud-hosted workspace.

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

Key features

Bruno supports REST, GraphQL, gRPC, and WebSocket APIs. Assertions, test scripting, collection automation, scheduled runs, and CI/CD integration make it useful for repeatable checks as well as manual API exploration. Multiple environments, variables, and pre-request and post-response JavaScript scripts help adapt a collection to different setups.

The desktop client shares its collection format with a CLI, IDE extension, API documentation generator, and mock server. Collections can also become standalone 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. The breadth favors teams that want related API workflows to use one collection format; the free plan’s limited OpenAPI syncs may constrain teams that depend on syncing specifications.

Pricing

Bruno has a free Open Source plan, a 14-day Ultimate trial with no credit card required, and two paid plans billed annually. The annual term matters: the monthly figures below do not mean monthly billing.

Open Source is the practical starting point for individuals or small projects that can work within two workspaces and five monthly syncs. Pro removes the workspace cap, but keeps the same sync limit, so it is a better fit for teams needing more room without frequent specification syncs. Ultimate is the clearest fit for heavier sync use or teams that need unlimited license admins. The 14-day Ultimate trial lets prospective users evaluate that tier before choosing; paid subscriptions carry an annual billing commitment.

Platforms

Bruno offers desktop versions for Windows, macOS, and Linux, alongside an API client, IDE extension, and CLI. The combination supports both interactive desktop use and developer workflows built around the shared collection format.

Who it's for

Bruno is best for developers and teams that keep API definitions and testing work in Git-managed repositories, and want automation, documentation, and mock-server tools tied to those collections. Teams seeking a cloud-centered collaboration model, or users who need more than five monthly OpenAPI syncs without moving to Ultimate, should weigh other options.

Pros and cons

• Pro: Plain-text, Git-versioned collections make API changes reviewable alongside project code.
• Pro: Multiple protocols, scripting, scheduled runs, CI/CD integration, documentation, and mock-server tools cover a broad API workflow.
• Pro: Collections, environments, and secrets remain on the device rather than in Bruno’s cloud.
• Con: Startup license validation sends an IP address, license key, hashed device ID, and version, which may matter to privacy-conscious users.
• Con: Open Source is limited to two workspaces and five OpenAPI syncs per month; Pro raises workspace capacity but not the sync cap.
• Con: Both paid prices are billed annually, which is less flexible for users who prefer a monthly commitment.

Alternatives

Compare API Testing Tools or API clients if you want to survey the category. Choose Apidog if its time-unlimited free plan for four users or its web and self-hosted platforms better match your team. Postman is another freemium API client with web support and Native Git. Consider Hoppscotch for its forever-free plan, personal workspace, and web and self-hosted options. Insomnia may suit teams preferring a free Essentials tier with Git Sync projects for up to three users and a stated mock-server request allowance. Karate is worth considering when API testing needs to sit alongside browser and desktop UI automation. Keploy offers an open-source local record-and-replay core. Kreya may fit individuals who can work with request history limited to the latest request. Pact is an alternative if you want its open-source tooling.

Verdict

Choose Bruno if you want API collections, tests, and supporting tools to live in a Git-managed project rather than a cloud workspace. Its plain-text collections and broad automation workflow are the strongest reasons to pick it; look elsewhere if the startup license check, the free plan’s sync cap, or annual billing conflicts with your requirements.