AttestorianEvidence anyone can check. Offline. For free.
Trust should not depend on the vendor. Attestorian evidence can be verified by auditors, regulators, customers, or courts on their own machines, with networking switched off, without an account or contacting us.
Pick the one that fits the reviewer.
Command-line verifier
For auditors' and regulators' own machines. Returns a clear pass or fail with the exact reason.
Embeddable TypeScript verifier
Build verification into your own portals, review tools, and workflows.
Browser Forensic Studio
A single file that runs in any modern browser with the network switched off, ideal for live demonstrations.
How an external reviewer checks evidence.
- Receive the evidence package, which may be a redacted copy.
- Obtain the signer's public key through an agreed, trusted channel.
- Run a free verifier offline on your own machine.
- Read the result: valid, or the exact point where the record fails.
- Review visible fields, policy checks, and approvals. Hidden fields are confirmed present and unaltered.
No lock-in on your history.
- Evidence created today remains checkable years from now
- Verification does not depend on Attestorian being online
- Independent implementations must agree on a shared conformance corpus
- Bounded parsing resists malformed or malicious packages
Trust the key, then trust the result. A verifier confirms a package matches a public key. Reviewers should obtain that key through a trusted channel agreed with the evidence producer, just as with any digital signature.
Frequently asked questions
What happens to our historical evidence packages if we stop using Attestorian?
Historical evidence packages remain independently verifiable forever. Because Attestorian Verify is free, open source, and implemented in standard Python, Go, Rust, and TypeScript with zero vendor phone-home calls, you can verify archived .attpkg files offline on any machine using your pinned public keys.
What checks does the offline verifier perform on an evidence package?
Attestorian Verify executes four fail-closed checks: (1) archive schema and manifest structure validation, (2) sequential step-by-step SHA-256 hash chain continuity, (3) cryptographic signature verification against the pinned KMS/HSM public key, and (4) salted commitment verification for any selectively redacted fields.
Verify evidence packages on your own offline machine.
Download the open verifiers and run them on sample packages with Wi-Fi switched off. Or start a 30-day pilot on your workflow.
Last updated: