How ROOTKey compares
Short answer
ROOTKey seals a fingerprint of every version of your files, tables and records in an independent public registry, shows what changed - who, when and where - and restores only what was altered to the last version proven valid. It works on top of the tools you already use, without replacing them. Backup, a SIEM and immutable storage each answer a different question, so ROOTKey complements them rather than competing with them.
Three comparisons
Each comparison sets out what the category does and what ROOTKey does, side by side, when you need each and how they work together.
| Category | The question it answers | The question ROOTKey answers | Comparison |
|---|---|---|---|
| Backup | Can we get our systems and data back? | Can the restored data be trusted? | ROOTKey vs backup |
| SIEM | What is happening across our systems, and is any of it suspicious? | Which data can still be trusted after an alert? | ROOTKey vs SIEM |
| Immutable storageWORM · object lock | Can this record be changed? | Can I prove to a third party that it wasn't? | ROOTKey vs immutable storage |
What ROOTKey adds in each case
Comparing hashes answers one question: did it change? Not what, who, when or where - and not which version to trust. ROOTKey answers all of them, in three steps.
- Anchor
- Every version of every file, table or record gets a unique fingerprint, sealed in an independent public registry with a timestamp.
- Detect
- ROOTKey continuously compares your data with the sealed record. Any change is caught and explained: what, who, when and where.
- Recover
- Restore the last version proven valid, down to one file or one row. Only what was altered returns to the sealed original, cryptographically verified. Every critical action produces an independent proof that external auditors can verify without access to the original data.
The full explanation: how ROOTKey works.
On top of your infrastructure, not instead of it
ROOTKey doesn't replace existing systems. It adds a layer of cryptographic verification via API - no migrations, no vendor lock-in.
- Connectors
- SharePoint · OneDrive · Amazon S3 · Cloudflare R2 · REST API and webhooks
- Deployment
- SaaS · Private cloud · On-premise
Frequently asked questions
Does ROOTKey replace my SOC, SIEM or backup solution?
No - it complements them. Your SIEM detects events; ROOTKey answers which data can still be trusted after an alert. Backup restores systems; ROOTKey verifies that the restored data is clean. They answer different questions and work best together.
Which systems can ROOTKey connect to?
ROOTKey connects through direct connectors to SharePoint, OneDrive, Amazon S3 and Cloudflare R2, and through a documented REST API with webhooks for every other system. It works on top of the tools you already use, without replacing them.