Bruno

Bruno is an open-source, offline-first API client that stores collections as plain files you can commit to Git. Created by Anoop M.D., it covers REST, GraphQL, gRPC, and WebSocket work on your filesystem using Bru markup and, increasingly, OpenCollection YAML. Pull requests review API definitions the same way they review application code. In 2026 Bruno moved fast. Version 3.0 (January 2026) added workspaces, a redesigned UI, improved Git UI, and YAML/OpenCollection support. Version 4.0.0 (23 July 2026) is the summer headline: BYOK (bring-your-own-key) AI sidebar with OpenAI-compatible providers, help for docs/scripts/tests, Apps for interactive request and collection UIs, secret-manager revamps, collection caching, a major Collection Docs redesign, OpenAPI Sync promoted to GA, richer WebSocket/gRPC/SSE handling, and CLI support for external secrets (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault). macOS code-signing stayed careful through mid-2026 certificate rotations so updates remain trusted by Gatekeeper. Pricing on usebruno.com/pricing (August 2026): Open Source at $0 with the full core client; Pro at $6/user/month billed annually; Ultimate at $11/user/month billed annually; 14-day Ultimate trial without a credit card. Free tier includes HTTP/REST/GraphQL/gRPC client work, testing, scripting, docs, and community support. Paid tiers add deeper Git UI (merge conflict resolution, stash), more workspaces, OpenAPI sync volume, secret-manager integrations, SSO/SCIM (Ultimate), and support SLAs. Golden Edition one-time SKUs were sunset earlier; existing Golden users were grandfathered. Bruno stays offline by default. There is no mandatory cloud sync of collections. Collaboration is Git. That is still why regulated teams and open-source maintainers leave Postman. Competitors in 2026 include Postman (cloud ecosystem), Insomnia, Hoppscotch, and editor-embedded clients. Bruno's bet is developer-native files over SaaS workspaces. On Mac in 2026, prefer the official download or brew install --cask bruno, confirm Gatekeeper and notarization prompts, and grant only the disk access you need for collection folders. On Apple Silicon and macOS Tahoe 26.x, use current arm64 builds. Pin the cask version in team Brewfiles when CI depends on CLI behavior from @usebruno/cli. Re-check pricing and release notes when a major version lands (v3 and v4 both shipped with breaking-change pages). Export or commit collections before upgrades that rewrite on-disk formats, and keep a previous DMG handy for rollback. Store secrets in .env files that stay out of Git, not in shared .bru files. Day-to-day Mac workflow is simple: keep a bruno/ folder next to each service, commit .bru or OpenCollection YAML with the PR that adds the endpoint, and run bru run in CI with @usebruno/cli. The free open-source core already covers REST, GraphQL, gRPC, and WebSocket requests with testing and scripting. Teams typically pay only when they want deeper Git UI (merge conflict resolution and stash), higher OpenAPI sync volume, secret-manager integrations, SSO/SCIM on Ultimate, or a support SLA. That split is why Bruno undercuts Postman seat math for many engineering squads while still offering Pro at $6/user/month annual and Ultimate at $11/user/month annual for orgs that need governance. v3's workspaces matter when one person owns collections across multiple repos: you group them in one dashboard without merging directories. v4's BYOK AI sidebar is optional sugar for docs, scripts, and tests; the sticky reason people migrate remains collections-as-files. Import paths from Postman still work, though complex scripts may need tweaks. If you are upgrading a large team from earlier major versions, read the breaking-changes notes before rolling v4 across every laptop.