Bruno has grown into a large open-source project with thousands of issues, discussions and contributions from developers around the world.
This document explains how the project is governed, how product decisions are made, how community contributions fit into that process, and what contributors can expect when participating in the project.
Our goal is to be transparent about how we work, set clear expectations, and provide clarity on how the project is built.
Bruno is, at its core, an open-source-first company.
More than 95% of our work happens in the open. The open-source project is not a funnel. It is the product. Our commercial offerings are designed to extend value, not limit or gate it.
We believe in open source for two key reasons.
-
First, it is the best way to build developer tooling. Open source enables a global community to contribute, fix bugs, suggest improvements, and build new features. The quality and volume of feedback from developers is unmatched.
-
Second, we see open source as a counterbalance to the extremes of capitalism. It ensures that anyone, anywhere in the world, has access to Bruno. It is also our way of giving something back to the future, just as we have benefited from the work of countless open-source contributors before us.
We're not chasing ideological purity of FOSS. We are product people first. Our goal is to build the best possible product.
We feel fortunate to be working at the intersection of developer tooling and open source, an ecosystem we deeply admire, are grateful for, and are proud to contribute to in our own small way.
While Bruno is open source, Bruno is not a community-governed project.
Product direction, architecture, user experience, roadmap prioritization, and release management are primarily driven by the core Bruno team.
We believe great products require strong product judgment, clear design principles, and long-term architectural consistency. For this reason, Bruno operates as a maintainer-led project.
Community feedback plays an important role in shaping Bruno, but final product decisions remain the responsibility of the maintainers. This approach allows us to move quickly while preserving a coherent product experience.
We welcome bug reports, feature requests, discussions and pull requests from the community.
Our issue tracker serves as the central place where ideas, bugs and improvements are collected and discussed. Every issue remains valuable, even if we are not able to work on it immediately.
To help us keep things organised, please use the appropriate channel for each type of conversation:
| Channel | Best used for |
|---|---|
| GitHub Issues | Bug reports and feature requests. |
| GitHub Discussions | Questions, how-to discussions, and technical topics that don't fit as bugs or feature requests. |
| Discord | Real-time discussion, brainstorming, and informal community chat. |
| Support | Account, licensing, billing, and customer support enquiries. |
We keep GitHub Discussions open because they provide a valuable place for technical questions and longer-form conversations that don't naturally belong in the issue tracker. Discord is a great option if you prefer real-time, chat-based conversations with the community.
If a discussion uncovers a bug or feature request, we'll ask that it be moved to GitHub Issues so it can be tracked and prioritised properly.
Bruno has a very large backlog of feature requests, bugs and community ideas.
To keep the project focused, the product team maintains a rolling three-month roadmap, which is reviewed and updated every month.
The roadmap represents the work we currently expect to deliver over the next three months. Everything else remains in the backlog until it is selected during a future planning cycle.
Because of the size of the backlog, we generally cannot provide delivery estimates or commit to work beyond the published roadmap.
The current roadmap is available on our website.
Community feedback plays an important role in roadmap planning.
Useful signals include:
- Upvoting existing issues instead of creating duplicates
- Adding new information, use cases or technical details
- Commenting when requirements or urgency have changed
Recent, meaningful activity helps us better understand which problems matter most to the community.
We welcome pull requests and greatly appreciate the time people invest in improving Bruno.
Submitting a pull request does not guarantee that it will be reviewed or merged immediately.
Due to our large volume of pull requests, we generally perform a full review when the underlying work has been prioritised into our three-month roadmap. This allows us to review contributions in the appropriate product and architectural context rather than on a purely first-come, first-served basis.
Ahead of that, maintainers may provide high-level feedback or request changes where possible, but we generally cannot commit to a review or merge timeline.
To make our issue tracker more transparent, every issue and pull request is assigned a status badge. Please note that we are rolling this out gradually to every issue.
These statuses are intended to communicate where an issue currently stands in our product planning process. They are not guarantees of delivery, but they help set expectations.
| Status | Meaning |
|---|---|
| Done | The work has been completed and is available in Bruno. |
| Planned | The issue is part of our current three-month roadmap. |
| Tracking | We agree the issue is valid and are tracking it, but it is not currently scheduled for development. |
| Discovery | We're still evaluating whether this belongs in Bruno. Additional use cases, discussion and community feedback help inform that decision. |
Issues may move between these states as new information becomes available.
If you'd like to influence prioritisation, the most helpful things you can do are:
- Upvote existing issues rather than creating duplicates.
- Add new use cases or technical context.
- Explain the impact on your workflow or organisation.
- Share related discussions or community feedback.
Bruno is maintained by the team at Bruno Software Inc, led by its creator, Anoop, who serves as the project's lead maintainer.
Open-source product planning is shared across five product managers, each responsible for different areas of Bruno:
Development is supported by a dedicated engineering team at Bruno, with additional contributions from the open-source community.
Building Bruno is a long-term commitment.
We're here to build a great product, work with our community, make thoughtful decisions, and continue improving Bruno year after year. Whether you've reported a bug, opened a pull request, suggested a feature, or simply use Bruno every day, thank you. The project is better because of you ❤️