I use Bruno at work and at home for APIs I call more than once in a while with curl. I like having a history, editable params and variables, and the ability to undo if I mess up. I love keeping everything local and versioned with git. The tests are really great, and I like visualizing responses as tables with some JS magic. I also appreciate the password and secret management and machine-readable config formats: I can keep secrets out of my workspace and easily bulk-change requests. Setup was very easy; I imported my Postman collection, and it converted my requests and tests with few changes needed. With four workspaces open, CMD-K search is very fast, and Bruno runs better for me than Postman ever did. I recommend Bruno all the time. Review collected by and hosted on G2.com.

Git proxy support was a problem, but Bruno fixed it recently. It can also run a little slow when I have a dozen larger workspaces open; searching for a specific request with CMD-K takes a bit to show results. With four workspaces open, it’s very fast. Review collected by and hosted on G2.com.

Bruno is very user-friendly and makes working with APIs simple and efficient. I especially like how easy it is to set and manage environment constants, which makes switching between different environments much more convenient. It also supports multiple request/response formats, giving a lot of flexibility depending on the use case.

The overall interface is clean and intuitive, and it’s easy to get started without a steep learning curve. It’s a great lightweight alternative for API testing and development. Review collected by and hosted on G2.com.

I don’t have any major complaints so far. Bruno has been simple and easy to use for my day-to-day API testing. Review collected by and hosted on G2.com.

I've been using Bruno for a few months as an alternative to Postman, and overall I've been pleasantly surprised.

The biggest selling point for me is that Bruno stores collections directly as files on disk instead of hiding everything behind a cloud account. It feels much more developer-friendly, especially when working with teams that already use Git for version control. Being able to review API request changes in a pull request is something that just makes sense, and I wish more API tools worked this way.

Performance is another area where Bruno stands out. The application starts quickly, uses fewer system resources than some of the larger API clients, and doesn't constantly push cloud features in your face. If you've ever been frustrated by slow startup times or being forced to log in just to access your own collections, Bruno feels refreshing.

The user interface is clean and functional, but occasionally feels rough around the edges. There were a few moments where I had to dig through documentation to figure out how certain features worked. Nothing deal-breaking, but it's clear that the product is still evolving.

What I appreciate most is that Bruno seems focused on solving a specific problem well rather than trying to become an all-in-one platform. It respects local-first workflows, works well with Git, and stays out of the way when you're trying to get work done. Review collected by and hosted on G2.com.

While it covers most day-to-day API testing needs, some of the more advanced features available in Postman are either missing or not as mature. The ecosystem is also much smaller, which means fewer community resources, templates, and integrations. If your team relies heavily on advanced collaboration features, extensive automation, or a large plugin ecosystem, you may find Bruno a bit limiting. Review collected by and hosted on G2.com.

What I like most is how simple and lightweight it is. Being able to store collections directly in Git makes collaboration much easier, and it means I don’t have to rely on cloud-based workspaces to manage my APIs. Review collected by and hosted on G2.com.

The main drawback is that it doesn’t offer as many advanced features as some larger API testing tools. For my day-to-day work, it’s great and gets the job done, but when workflows get more complex in a team setting, I sometimes miss having stronger collaboration and automation capabilities. Review collected by and hosted on G2.com.

What makes Bruno exceptional is its offline-first, Git-friendly philosophy, which directly challenges bloated, cloud-centric API platforms.

Rather than locking your data away on proprietary cloud servers or requiring mandatory account logins, Bruno stores your API collections as plain-text .bru files right on your local filesystem. This design lets you treat API documentation just like source code: you can keep collections alongside your project repository and manage collaboration smoothly through your existing Git workflows, including branches and pull requests. Overall, it’s an incredibly fast, lightweight, open-source tool that brings back data privacy and developer-centric simplicity. Review collected by and hosted on G2.com.

Bruno’s main drawback is that it’s still relatively immature and doesn’t yet offer the same level of advanced enterprise features as more established tools like Postman. Since it’s newer, the ecosystem is still evolving, which can mean fewer third-party integrations, less comprehensive documentation, and a smaller community to rely on for troubleshooting. More advanced workflows—such as complex, multi-step request chaining, sophisticated performance testing, and detailed mock server configurations—are either not available or tend to require significantly more manual scripting. Review collected by and hosted on G2.com.

Simple and intuitive to use, great performance Review collected by and hosted on G2.com.

Nothing really that I can think of right now Review collected by and hosted on G2.com.

I like Bruno for API testing, especially because of its user experience, which minimizes problems and makes the tool easy to use. I appreciate how it organizes calls and its structure, and the UI feels very smooth. It's lightweight, allowing me to organize folders according to my convenience. The initial setup is pretty easy, and even a beginner can set it up. Review collected by and hosted on G2.com.

NA Review collected by and hosted on G2.com.

Simple syntax – Requests are easy to read and edit. Bruno stores API collections as plain text files on your filesystem instead of inside a cloud workspace. Review collected by and hosted on G2.com.

Bruno is powerful, but: Less community content (templates, tutorials, public collections) Review collected by and hosted on G2.com.

Bruno is open source; my company uses it for hitting API endpoints in different environments. It's easy to use and pick up. It's a great free alternative to Postman. It's relatively light on memory usage. You can bring your Postman Collections and OpenAPI collections to Bruno without any translation required. Review collected by and hosted on G2.com.

I don't like that you can't move the position of tabs in Bruno, so you constantly need to click on the left and right arrow buttons to navigate between tabs. There's also a slight problem that you can't search for variables in your environment - you need to manually scan a list to find your variable of choice. I also do not like the fact that Bruno collections often fail to get imported Review collected by and hosted on G2.com.

Bruno is simple, intuitive, ideal for developers and testers. Review collected by and hosted on G2.com.

Bruno is an excellent choice. No points to improve Review collected by and hosted on G2.com.