Priced by vendors monitored. Never by internal seats.

It feeds them cleanly. Compliance platforms track whether a vendor review happened; Bastion Ledger executes the actual supplier evidence harvest, sub-processor diffing, and deterministic rule evaluation, then pushes the signed decision packet and certificate expiry dates directly into Vanta, Drata, Jira, or ServiceNow.

Two engineering choices remove supplier friction: first, we never force vendor engineers to create a password or configure TOTP just to upload a PDF—sessions use cryptographic domain-bound verification codes. Second, public trust-center artifacts pre-fill ~78% of baseline controls, leaving an average of 11 specific delta questions instead of 240 boilerplate rows.

Language models never assign risk tiers in Bastion Ledger. Extraction models only locate candidate clauses inside uploaded attestations and must attach an exact document hash, page number, and verbatim quote. Actual tier classification runs on a deterministic, version-pinned boolean and weighted rule engine that produces identical outputs every run.

Never. Every customer workspace runs with isolated envelope encryption keys in Frankfurt (eu-central-1) or Zurich (eu-central-2), with optional customer-managed KMS keys on Sovereign plans. Zero customer documents, prompts, or vendor responses are ever retained by or used to train foundation models.

At 30 reviews per year, teams typically burn 240+ senior security engineer hours chasing attachments and tracking renewal spreadsheets—roughly six full engineering weeks annually. Our Foundation tier ($232/mo billed annually) deploys in under an afternoon and pays back its annual subscription on the third completed vendor review.