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.