We shipped 78 releases, completed the v1 to v2 transition, and doubled down on what makes Bruno different: fast, local-first, and Git-native API Client that cares about the developer community.
We're honored to have the opportunity of building a product alongside millions of passionate developers and appreciate every request you send through Bruno.
2025 was a turning point for Bruno.
We grew from 6 to 23 people globally across engineering, design, product, and GTM. That growth allowed us to ship faster, respond to feedback more quickly, and take on larger improvements without losing the focus that made Bruno what it is.
We also opened a new headquarters in Bangalore, giving the team a shared space to collaborate day to day. Bruno has always been global, but having a fresh home base has noticeably improved how we plan, build, and ship together.
A snapshot of what we shipped in 2025:
That pace was intentional. The goal wasn't just to ship for the sake of speed to volume; the aim with each release was to steadily remove friction and make Bruno feel better with every update.
We've highlighted a number of features below, but a few of the areas we had (and continue to have) focus on for incremental continuous improvements were: onboarding/migration from Postman, working with different authentication methods, and advancing the capabilities of our CLI for automation.
Shipping is only half the story. The other half is how many developers showed up and stuck around.
That kind of adoption only happens when a tool fits into real workflows. Git-native, offline-first, and fast still resonates.
In March, we rebuilt OAuth 2.0 based directly on community feedback. We removed the need for separate authorization and resource requests, added automatic token injection, and made OAuth feel like a natural part of the request workflow instead of a separate setup step.
We added WebSocket support with the same principles as the rest of Bruno. Local-first, Git-friendly, and reviewable in a pull request. Real-time API testing should not require a different tool or a hosted dashboard.
After months in beta, gRPC became generally available with server reflection, import paths, and smoother integration with existing collections. Teams working across REST and gRPC can now keep everything in one place.
We launched 14-day trials of our commercial product. This marked an important step toward building a sustainable business while keeping Bruno open-source and developer-first. This lets us invest more into the product without changing what Bruno stands for.
We added native support for request and response examples so API collections can double as living documentation. This reduces duplication and makes collections easier to understand for new team members.
We brought browser-style debugging into Bruno with network logs, request metadata, and response analysis. When something breaks in an API flow, you should be able to see exactly why.
Throughout the year, we invested heavily in the collection runner. Parallel execution, CSV iterations, test filtering, and a redesigned UI all landed in 2025. It is one of the most used parts of Bruno, and we treated it as a core product, not an afterthought.
We realize that nearly all of you are coming from different tools, and Postman is the most common. We spent a lot of time in 2025 working on making the process smoother to simply import your collections and get on with your work in Bruno. This won't stop in 2026 and the end goal is for it to be as automatic/"automagic" :) as possible.
Bruno continues to be shaped by a few core beliefs:
Every feature we shipped this year ties back to these ideas.
2025 confirmed what we believed going in. Developers want simpler, faster, more transparent API tooling.
We shipped 78 releases, grew the team, and Bruno is now used by hundreds of thousands of developers. The foundation is strong, and the direction is clear.
We’re closing the year with v2.15.1, and we’re already gearing up for our v3 release on January 5th, 2026.
You can try our v3 early preview today that includes major new capabilities that change how people structure and use Bruno: workspaces for multi-project workflows, native YAML support alongside Bru, and an inbuilt terminal for running CLI tasks without leaving the app. These features are part of a broader push to make Bruno feel more like a complete development environment while staying fast, local, and Git-centric.
2026 is about building on that momentum, continuing to ship with discipline, and making Bruno better without making it heavier.
2026, here we come.