Proof. Request demo

Request demo

See Proof on
a real repository.

We spend forty minutes in a live map, one finding and the gate.Then we size your first component with you.

  • A live map of a real repository.

    We open the public map of buger/jsonparser and walk it end to end. You see each promise, the code that carries it, and the tests behind it.

    The map runs on proof-demo (on our probelabs/jsonparser fork, not on buger/jsonparser), our showcase branch. The open findings on it are seeded demonstration entries; the fixed records are the real ones. We list that as a limitation.

  • One finding, promise to failing test.

    We take KI-3, a real finding on that repository, and run its witness in front of you. KI-3 is pinned the second way: its test asserted the broken output while the bug was live, and flipped when the fix landed. The record says which mode each finding uses.

  • The gate stops a merge.

    We break a promise on purpose. The gate blocks the merge and names the promise that broke.

  • What your first component takes.

    We size one component with you on the call. You leave with the number of weeks, and the hours your engineers must give.

A person validates every finding before it reaches you.

Leonid Bugaev · founder
runs every demo himself

Ask for a demo

Leonid reads each request. He replies in two working days.

Private early access: we take on a small number of engagements at a time. Leonid onboards each team himself. Private code stays private. We countersign your NDA before we read a line of your code.

Do you prefer a call first? 20 minutes with Leonid →