Repository Evidence Review
The free tool tells you what your evidence shows. A Repository Evidence Review is us doing it with you, on one repository and one named decision: agreed scope, a supervised scan in your own environment, the pinned report and certificate, a review session, a readout, and a two-page decision memo you can hand to whoever has to sign.
The engagement
C$7,500 · PRICE-LIST-VERSION: 2026-09-21.1Fixed fee, one repository, one named decision. Canadian dollars, plus applicable taxes. Includes agreed decision scope and pinned inputs; a supervised local scan in your own environment; an evidence-and-limitations review; the pinned report, certificate, and binding attestation; one reproducibility rerun on identical pinned inputs; a 60-minute evidence-review session; a 60-minute readout; and a two-page decision memo.
You pay half up front. The rest is due only if the readout gives you a decision you can act on. “Do not accept this revision yet” counts. A finding you dislike still counts. Not being able to decide does not.
Excludes remediation engineering, compilation or runtime testing, penetration testing, exhaustive defect coverage, legal or regulatory certification, and any representation that the software is safe or defect-free.
Yes, you are paying for a certificate about your own work
That is how credit ratings went wrong, and it is not what happens here. A rating is an opinion only the agency can produce, so whoever pays can shop for it. A Cejel certificate is deterministic: your customer runs the same command against the same version and compares the result character for character. You can pay for it precisely because you cannot influence it.
It has already been used without us in the room
Thirteen outside engineers have run Cejel on their own code without us in the room.
Count as of the last internal traction review; verify against a refreshed count before treating this page as current.
Start a Repository Evidence Review
Tell us the repository and the decision that depends on it. We agree scope, pinned inputs, and the stop conditions before anything else happens. You retain your code and artifacts in your own environment throughout.