Contract Hub
One record of the contract
that both parties can trust.
Contract Hub keeps the working record of a commercial agreement: every notice, request, approval, work order step, register change, incident and invoice, in one append-only, hash-chained ledger that neither party can quietly edit.
For two organisations running a long-term software or services agreement, who need to know what was served, when the clock started and what was deemed agreed — without arguing over e-mail threads.
Capabilities
Every step of the agreement, on the record.
Each event is recorded once, linked to the clause it relies on, and chained to the entry before it. Both parties sign in to the same hub and see the same record.
Hash-chained record
Every entry carries the hash of the one before it. The database itself refuses updates and deletions.
Business-Day clocks
Bank holidays, a daily cut-off, deemed receipt on the next Business Day, reminders and deemed outcomes.
Formal notices
A notice composer; the e-mail as sent — body, time and recipients — is stored in the record.
Work orders and change requests
Proposals, counter-offers, approvals, versions with a field-level diff, delivery, acceptance and disputes.
Registers
Data classification, tools and AI, environments, third-party recipients, IP addenda and security incidents.
Signed mirror
The record is pushed to the other party's read-only mirror as signed bundles, with replay and fork protection.
01 — Integrity
A record that proves itself.
The point of the hub is that nobody has to take the other side's word for what happened. The record can be checked by either party at any time.
Corrections, never edits
A mistake is fixed by a new entry that references the original. The original stays visible.
Verification on demand
A verification page and a command-line check walk the whole hash chain and report the first break, if any.
Encrypted export
The full record exports to one encrypted file that restores into a fresh installation, plus a daily off-site backup.
Roles and redaction
Administrators and users for each party, plus scoped observers. Pricing is redacted on the server for observers.
How it works
- 01
Load the agreement
The clause register holds the full text, so every event can point at the clause it relies on.
- 02
Work in the hub
Both parties serve notices, raise requests and approve work orders in one place.
- 03
Verify and mirror
The record is checked, signed and copied to the mirror at least daily.
Built on
Run your agreement on a record both sides trust.
Ask for a walkthrough with a filled demonstration record, or talk to us about adapting the hub to your own agreement.
Request a demoDownload brochure (PDF)