One address, and a plain account of what happens next.
Broka has no public issue tracker and no forum. Reports, questions and feature requests reach us two ways — an account in the portal, or one inbox — and this page says what to put in them and what to expect — including the parts that are not a promise.
- The version, from Settings → About, or the image tag you pulled.
- Which broker and which version of it — the platform matters more than the console does.
- What you did, what happened, and what you expected instead.
- The trace id, if the console showed you one. Every error response carries one.
There is no response-time undertaking, no support tier and no bug bounty. Both doors are read by the people who build Broka, which is why there is one team and not a queue — and also why we do not print a number of days.
Where to write
info@broka.dev — for a defect, a question, or a feature you want. One inbox covers all three because one team answers all three. It needs no account, and it is what to use if you cannot sign in.
Or register a free account at portal.broka.dev/register and raise it there. The difference is that a request in the portal keeps its own thread: you can see what state it is in and read the reply in the same place you wrote it. When a request is answered, the portal emails you a link back to it — the answer itself stays in the thread. The account costs nothing and unlocks nothing: the images are public either way.
A security finding
Same address, and please say security in the subject so it is read first. Do not post it anywhere public first — not because a disclosure policy forbids it, but because there is nowhere public to post it and the delay only helps whoever finds it next. Each repository ships a SECURITY.md with its own scope; between them they cover the product, the vendor service that holds customer records, and this site. What is out of scope is named there too: the brokers themselves, your own deployment, and third-party dependencies.
A feature you want
Write what you are trying to do rather than the control you imagine — the useful half of a feature request is the operation, not the button. Where the product is heading is in the product direction section of the change data capture page.
There is nothing to fork
The source is closed and there is no public repository, so there is no pull request to open. That is a decision rather than a gap — it is why this page is an address instead of a contributor guide, and what you may do with what you run is the licence agreement, not a repository policy.