See what it does in an afternoon. No integration, nothing leaves your machine.
A pilot does not need a data-sharing agreement or a core-system change to be worth an hour. Download the on-prem bander, take one of two worked sample corridor tables, band a price locally, and verify the signed verdict offline. Everything below runs on your laptop; the only thing that would ever reach an operator is an opaque commitment, and in this pilot you run the operator’s logic in your own browser too.
Get the bander — the only thing that ever sees a raw value
A single, dependency-free binary whose sha256 is its identity. It seals its own network access, reads the
corridor secret from a file (never the command line), and now folds received verdicts into a signed evidence
pack with casepack. Generate a real 256-bit corridor secret first.
Take a worked corridor table
Two illustrative tables so you have something to band against immediately — a metals corridor and an
electronics corridor with a one-band tolerance. Each carries its derived corridor_id
(SHA-256 over the sorted edges), so two banks that hold the same edges reach the same id with no negotiation.
The bands are a sample, not a market quote — in a real corridor the parties ratify and cite them.
Band a price locally, and watch what leaves the building
Put a price-per-unit in a CSV and band it against the sample edges. The raw value stays on your machine; the bander emits only salted commitments. Or skip the file entirely and drag a dial on the live pages — the same kernel runs in your browser and shows exactly what the operator would receive.
Verify a signed verdict offline — the examiner’s view
The output a supervisor cares about is a single ES256-signed verdict you check with the network unplugged. The pack re-verifies every signature in your browser, and a conformant verifier refuses a record that carries a filing decision or a risk score, even when it is validly signed — so the cannot-list is something the examiner checks, not the operator’s word.
Check the claims yourself
Every refusal on the cannot-list is a test. The whole suite runs with one command, and the sha256 of every test file it executes is published — so you can confirm you ran the whole suite, not a subset chosen to pass. Read the honest limits alongside the wins.
Choose a table before you have a counterparty
Start from the template for your goods, then try two or three candidate tables on your own multi-leg shipments. Shadow mode runs the operator’s own kernel inside the bank and submits nothing: per table, how many shipments would reconcile, diverge or stay undetermined, and how wide a mispricing each table can hide. Counts only — no figure from your book appears in the report, and no table is ranked for you.
What never leaves your machine
This is a pilot you can run before any legal review, precisely because there is nothing to review on the way in:
- ×the price, quantity, amount, or counterparty name — the bander emits only a salted hash of the band
- ×the corridor secret — generated locally, written owner-only, never printed to a terminal
- ×your data to us — the console’s only network call is to the operator, and this pilot can run the operator’s logic in-browser with none at all
When you are ready to reconcile against a real counterparty, the same bander and a table you both ratify is the whole of it. Enquiries are taken by direct introduction while the contact address is being set up — the security page says how to reach a person in the meantime.