PRICING
Per-seat pricing on a governance tool has a bad incentive baked into it: the vendor is paid more the more people you put under watch, and the buyer is quietly taxed for growing the team. The guard also does not sit on anybody's machine, so a seat is not even the thing being used.
NUMBERS · WITH THE LAUNCH The shape below is settled; the figures land with the launch, validated with early teams rather than guessed at here.
WHAT IS BOUGHT
Every commit on a connected repository carries a receipt, verified in CI against keys you control. Installs in an afternoon; your developers install nothing. Priced per repository under guard, because that is the unit that generates the work.
The record underneath: what was promised, what was graded, what contradicted. It is one record per company rather than per repo, because the questions worth asking of it cross repositories.
THE LINE
Nobody is charged to look at their own history. A record you have to pay to read is a hostage, and it would make leaving cost more than staying for the wrong reason.
Verification is exactly as faithful at every tier. If a commitment failed, it is recorded as failed whether or not you are paying — the discipline does not come in tiers, and a product that graded its paying customers more kindly would be worth nothing to either of us.
The record leaves in a form you can read without us. Switching cost should come from the record being useful, not from it being trapped.
The guard never receives the rules it enforces, on any plan. That is an architectural property, not a premium feature — see how the receipt is signed.
PLAINLY
The guard asserts one thing: every commit in range carries a valid receipt from the policy you approved. It does not assert that your code is secure, that your standards are good, or that nothing slipped through a rule you never wrote. A tool that let you believe otherwise would be selling comfort.
Where a check could not run, the record says so in its own words rather than defaulting to a pass. Absence is never reported as success — that is the single behaviour the whole product is arranged around.
SOLORA
The guard and the ledger are bought by the person accountable for the codebase. The workspace your engineers actually run agents in is Solora, and it is downstream of this: it writes into the same record, and it is worth nothing without one.