Contact · CaseAnchor

Talk to the team behind the anchoring layer

About CaseAnchor · Agreements with tamper-evident anchoring

CaseAnchor turns an agreement into a record you can check later. Once finalised it is fingerprinted and sealed, so any later change is detectable rather than a matter of trust.

Fingerprint
Commitment
Issued per case
Verifiable
Recognition
Checkable later
3
Root hashes
Per agreement
External
Key custody
Held outside the app
Core Principles

What the platform is built around

Four principles, each traceable to a specification file

Each value below maps to a rule that is written down in the spec files rather than asserted in marketing copy.

Detectable alteration

A fingerprint on a finalised agreement means a later change can be detected rather than assumed away.

FingerprintPer case

Open specification

The handling rules live in a published specification that can be reviewed independently of any marketing claim.

Reviewed inThe specification

Keys outside the application

Agreement content is encrypted before it is stored, and the key is held outside the application.

Key custodyExternal

Least data in the register

What is registered is a fingerprint, not the agreement itself.

Register storesA fingerprint
Contact

Get in touch

Tell us what you are trying to run, and we will tell you honestly whether CaseAnchor fits. The specification files answer most technical questions faster than we can.

Deployments
Volume and topology
How many cases, participants and files you expect to anchor.
Integrations
Your existing stack
What CaseAnchor needs to talk to in your environment.
Data handling
Residency and keys
Where the payload lives and how the encryption keys are held.

Send a message

Fields marked with an asterisk are required.