What the record says
A fingerprint of the record’s content. Change a single character and the fingerprint no longer matches.
Nobody can quietly rewrite the past.
Every protected write is sealed and linked to the one before it. If a record is altered, removed or slipped in outside the proper path, verification shows which record and what happened to it.
Sealed at the moment of writing
Ghostables wraps the database writes you already make. Your query runs unchanged, and each protected write leaves evidence behind it. The integrity layer is available today as an SDK for PostgreSQL and MySQL.
Which record, which version
The content is bound to the record it belongs to and its version, so a valid record cannot be passed off as a different one or an older one.
Where it sits in history
Each event is linked to the event before it, so removing or inserting history breaks the chain. Once a batch is anchored outside your systems, the break cannot be hidden by rewriting the chain.
Who can change it
A change made outside the protected path does not produce matching evidence, so it shows up at verification. Anchoring, now being rolled out, extends that to someone with full database access.
Checked continuously, explained plainly
Verification compares live records with their seals and walks the chain of events behind them. Every result is specific to a single record, so an investigation starts with the record that changed.
Verified
The record matches its seal and its history is intact.
Altered
The stored content no longer matches what was sealed.
Removed without authority
A sealed record is missing and no protected deletion explains it.
History broken
An event has been removed from, or inserted into, the record’s history.
Awaiting independent proof
The record is verified locally and its batch is waiting to be anchored.
See tampering detected
Alter or delete a payment the way an intruder would, then run verification.
Payments ledger
Loading the ledger.
| Reference | Payee | Amount | Fingerprint | Status |
|---|
Changes made here go straight to the stored records and bypass the application, the way an intruder or a rogue administrator with database access would. The fingerprints are computed live in your browser.
Evidence an auditor can take away
Writes are gathered into batches, and each batch is reduced to a single compact proof. For any record, Ghostables can assemble a self-contained evidence pack: the verification result, the proof that the record belongs to its batch and, where anchoring is enabled, the independent receipt for that batch.
Once a batch is anchored, the pack can be checked without access to your systems and without trusting the people who run them.
Continue exploring the platform
Zero-knowledge encryption
Data is sealed on the user’s side, so your infrastructure stores it without ever being able to read it.
Ghost Tables
Stored data that gives anyone studying it nothing to work with.
Access governance
Many people working on the same sealed records, each with exactly the access they were given.
Independent proof
Integrity evidence built to be checked outside your organisation.
Deployment
Runs inside your applications and databases, in your cloud and your region.
Find out where sealed data fits in your systems
Our engineers will map your sensitive data and show you which protections apply, before you commit to anything.