The Git-native API client
Collections stored as code. Works with Git, your IDE, and your agents.
Open-source, local, and built for developers.

Trusted by organizations that get it
Chosen by teams who prioritize developer efficiency, security, and clear value


























Why Bruno
Everything a platform does,
without the platform
Your collections are plain-text files in your repo. Everything else follows from that.
Developer First
An API client,
not a platform
Bruno is the open-source challenger to bloated, cloud-locked "platforms". A devtool should be extensible and work with the rest of your stack, not against it.

Built on OpenCollection, the open standard for API collections

Collaborate
Collaborate via Git
Everything is folders and text files on your filesystem, co-located with the code they belong to.
Branch, diff, review, and merge your API collections with the exact workflow your team already trusts.
Secure & Local
Your data never leaves your machine
No cloud sync. No account. No login. We have zero visibility into your requests, and we're not training AI models on your data. Share only when you choose, through Git.
Enterprise Ready
Scale without the
security overhead
Bruno runs inside the security perimeter you already have. Whatever your enterprise has configured applies automatically. No cloud tenant. No new admin console. No new attack surface.
Inherited automatically
Built into Bruno
Loved by developers
Don't take our word for it
Take back your API workflow
Your collections in your repo, running on your machine, in under a minute.
Free and open source · macOS, Windows & Linux · No account needed
Frequently asked questions
As a local desktop application, Bruno doesn't have a concept of an 'account' and there is no login. The paid versions of Bruno are activated via license key, which can be validated through an SSO login with your Identity provider.
Since all data is local, there is no user-level RBAC. When sharing collections in Git, RBAC is inherited from your configurations within your Git provider.
For License Administrators:Access to the licensing server for the purposes of assigning license keys can be performed via SSO.



























































































































