About
We build checks you can believe.
Software teams now write and review code faster than ever, much of it with AI. The number of rules that must never break stays the same.
Why Bracel exists
A refund cannot exceed what was charged. An admin route cannot answer a stranger. Rules like these should be executed on every change, and the answer should be stated exactly.
What we make
A check that runs the rule, not a comment that reads about it.
Bracel runs approved business rules against your application on every pull request, before merge, and tells you what happened: what was expected, what was observed, and why the verdict follows. If it cannot establish the result, it says so.
The rules are approved by your team and read from the base commit, so a change cannot rewrite the rules that judge it. The check runs in your own GitHub Actions, and every result shows the release and the code it came from.
How we work
Four things we will not do.
We hold ourselves to the standard of the product. The full list is on the principles page.
- 01
Call something a pass that was not executed
If Bracel cannot establish the result, the verdict is UNKNOWN, with the reason.
- 02
Hide what was not checked
Every result names the rule, the scenario and the limits of what it proves.
- 03
Publish a number we cannot back
Claims go on this site only when we can show the evidence. Examples are labelled as examples.
- 04
Stop checking quietly
Verify does not stop at a quota. A missing check is never presented as a passing one.
The name
Bracel. Say it BRAY-sel.
One word, capital B. Not “bracelet”, and not an acronym. Logo files and colours are on the brand page.
BRAY-sel