Rekord Kloud. Proof, on demand.
Rekord Kloud anchors your records append-only and versioned. The Proof Console gives depositors, auditors and regulators read-only access to the same evidence operators see. Rekord Kloud and the Proof Console are built by Rekord AG in Zug, Switzerland.
From record to proof.
Push records through one API
Send files and structured records from your existing stack. Each one lands in a catalog, and every catalog owns its own chronological list of versions.
Hash and batch
Rekord computes a SHA-256 hash for every record and folds the hashes of a version into one Merkle root.
Anchor the root
The root is written on-chain, to VeChain by default or to Litecoin or BSV. Your documents stay with you.
Verify on the Proof Console
Depositors, auditors and regulators open any version, read-only, and check your records against its anchored proofs.
The Proof Console and the cryptography under it
Rekord Kloud uses 4 primitives: SHA-256 file hashes, canonical JSON for structured records, deterministic Merkle roots and append-only on-chain anchors. The full architecture walkthrough shows where each one sits across the Rekord stack.
SHA-256 per file, hashed verbatim
Every file gets its own SHA-256 hash, computed over the exact bytes you submitted. Rekord doesn't reorder, trim or normalize anything before hashing.
To verify a file later, you submit exactly the same bytes. If re-saving a PDF or re-exporting a spreadsheet changes even 1 byte, the hash changes too, so any edit to the file shows up.
Canonical JSON for structured records
Structured records that Rekord produces, such as briefs, evidence revision manifests and underwriting configuration, are serialized as canonical JSON before hashing. Object keys are sorted recursively, whitespace is removed and the text is encoded as UTF-8.
Anyone who holds the same data computes the same hash, whatever order their system happened to write the fields in.
Deterministic Merkle batch roots
The hashes of a version become the leaves of a Merkle tree, built the same way every time:
- each leaf hash is trimmed, lowercased and stripped of any
0xprefix, and empty values are dropped; - duplicate hashes are removed and the remaining leaves are sorted in ascending order;
- consecutive nodes are paired, and a trailing odd node pairs with itself;
- each pair is sorted, hex-decoded, concatenated and hashed with SHA-256, level by level, until one root remains.
Frozen golden test vectors keep every root byte-identical across releases, so a root anchored today still recomputes the same way after the next deployment.
The trees are recursive: a child version's root becomes a leaf of its parent. Each record stays provable on its own with an inclusion proof, the short list of sibling hashes that links it to the anchored root.
Append-only on-chain anchoring
Only the Merkle root goes on-chain. Rekord Kloud anchors to VeChain by default, and to
Litecoin and BSV, where the root is written into an OP_RETURN output.
Each anchor records its confirmations and the anchored Merkle hash. When you verify, the version service re-checks every anchor live against the chain, and the Proof Console links each anchor to a public explorer: explore.vechain.org for VeChain, a Litecoin explorer, and whatsonchain.com for BSV.
An update appends a new version with its own root. Earlier versions and their anchors stay in place, which gives you immutability by design: history is append-only, and any edit to an anchored record is tamper-detectable.
What you see in the Proof Console
- Catalogs. Every catalog, each with its own detail view.
- Version history. Every version of a catalog, newest first.
- Proof view. The anchors behind a version, with confirmations, the anchored Merkle hash and an explorer link.
- Verify data. Open a specific version, submit your files, and the console checks them against that version's proofs, showing the SHA-256 of each file.
- Role-based access. Operators write records; depositors, auditors and regulators get read-only access to the same evidence.
To check a data room's files against its manifest before you open the console, use the SHA-256 dataroom verifier.
A live example: the 9SicUSDC vault
The 9Summits Short Duration Institutional Credit vault, powered by Rekord (USDC), carries
the symbol 9SicUSDC. It's an ERC-7540 vault on Lagoon, deployed on Ethereum Mainnet at
0x6a39fe461278376f61acbbb6759550e24a78a7b2.
9Summits curates it, Rekord Capital Markets operates it, and its listed proof layer is the Rekord AG Trust Layer. The vault's own on-chain state is public on Ethereum: you can read it on Etherscan without an account. See the full vault card on Rekord Vaults.
Proof as a byproduct.
Immutability by design
Records are append-only and each version keeps its own anchored root, so a changed record no longer matches its proof.
Your documents stay with you
A 32-byte Merkle root is all that touches the chain. It holds none of the content of the files behind it.
Role-based access
Decide who writes records and who gets read-only audit access.
Proofs that recompute
Golden test vectors pin the Merkle procedure, so a root from any release recomputes byte for byte.
3 anchoring chains
VeChain by default, plus Litecoin and BSV, each with a public explorer link per anchor.
One API
Hashing, versioning, anchoring and verification behind a single API surface, including a verify call that checks data against any version's Merkle tree.
Evidence records for EU product and ESG regulation
EU product and sustainability rules ask you to keep records that a third party can check years later. Rekord Kloud hashes, versions and anchors those records, so you can show which version existed on which date and that it hasn't changed since.
Rekord provides the infrastructure. The obligation under each regulation, and the content of every record, stays with you.
- ESPR, Regulation (EU) 2024/1781. The Ecodesign for Sustainable Products Regulation introduces the Digital Product Passport. Rekord Kloud anchors the product data you keep as evidence for each passport, one version per update.
- Battery Regulation, Regulation (EU) 2023/1542. The battery passport applies from 18 February 2027 for LMT batteries, industrial batteries above 2 kWh and EV batteries. You keep the passport records; Kloud gives each revision an anchored root.
- CBAM, Regulation (EU) 2023/956. The Carbon Border Adjustment Mechanism entered its definitive period on 1 January 2026. Kloud anchors the emissions data and supplier records you keep as evidence for your declarations.
- CSRD, Directive (EU) 2022/2464. The Corporate Sustainability Reporting Directive calls for sustainability reporting that can be assured. Kloud versions and anchors the source records behind your reported figures.
- EUDR, Regulation (EU) 2023/1115. The deforestation regulation requires due-diligence statements with geolocation data. Kloud anchors the plot data and supplier documents you keep as evidence for each statement.
Product passports nest: a component has its own records inside the record of the product that contains it. Recursive Merkle trees follow the same shape, with each child version's root sitting as a leaf in its parent.
Rekord validated a wind turbine lifecycle DPP with the Advanced Manufacturing Research Centre (AMRC), modelling thousands of recursive nested components that require simultaneous ESPR and CRMA passports.
How the evidence compares
Most teams prove a record today with a quarterly PDF attestation or with logs kept in a cloud account. Here's how those approaches compare with Rekord Kloud and the Proof Console on the questions an auditor asks.
| Criterion | Quarterly PDF Attestations | Centralized Cloud Logs | Rekord Kloud + Proof Console |
|---|---|---|---|
| Verification Frequency | Once per reporting period, on the attestor's schedule | Whenever the log owner grants access | On demand, against any anchored version |
| Tamper Detection | Depends on comparing the PDF with the attestor's own copy | Administrators can edit or delete entries; detection relies on the provider's own controls | Any change to a record's bytes changes its SHA-256 hash and breaks its match with the anchored Merkle root |
| Independent Third-Party Verification | Relies on trust in the attestor's signature | Relies on trust in the log owner and cloud provider | Anyone with the bytes can re-hash them and compare the root with the transaction in a public explorer |
| Data Exposure | Figures and supporting detail are shared in the document | Raw entries are readable by everyone with account access | Only the Merkle root goes on-chain; documents stay with you |
| Version History | One snapshot per period | Retention and overwrite rules set by the account owner | Append-only versions per catalog, newest first, each with its own anchor |
| Regulatory Evidence | A point-in-time statement | Entries whose history depends on the provider's retention | Hashed, versioned and anchored records you keep as evidence for ESPR, the battery passport, CBAM, CSRD and EUDR |
| Time to Verify | Wait for the next report or request a new engagement | Request access, then reconcile exports by hand | Re-hash the bytes and check membership in the version's Merkle tree |
For everyone who verifies.
The Proof Console gives the same evidence to everyone who needs to check it, each with the access that fits their role.
Auditors
Verify any record on your own schedule.
Regulators
Open any earlier version from the history, with its anchors.
Depositors
Check the records behind your position.
Operators
Make proof a byproduct of doing business.
Developers
One API for hashing, anchoring and verification, with no chain plumbing to build.
Part of the Rekord stack.
Rekord AI hashes each evidence revision manifest as canonical JSON and anchors it as a proof through the same trust layer. Rekord Vaults lists the Rekord AG Trust Layer as the proof layer for its live vault.
Learn the fundamentals.
Plain-English guides from the Rekord Education Hub on the concepts behind this page.
Frequently asked questions
What is Rekord Kloud?
Rekord Kloud is the proof layer built by Rekord AG in Zug, Switzerland. It hashes your records with SHA-256, batches the hashes into a Merkle tree and anchors the root on-chain in an append-only, versioned sequence. The Proof Console gives depositors, auditors and regulators read-only access to the same evidence operators see.
How do SHA-256 and Merkle verification work?
Each file is hashed with SHA-256 exactly as it was submitted, byte for byte. The hashes of a version are sorted, paired and hashed again until one Merkle root remains, and that root is anchored on-chain. To verify, you submit the same bytes to a specific version; the service checks that the hash belongs to that version's Merkle tree, and you can compare the root with the anchoring transaction in a public explorer.
Does my data go on-chain?
Only the Merkle root goes on-chain. A root is a 32-byte SHA-256 value that holds none of the document content, and the documents themselves stay with you.
Which blockchains does Rekord Kloud anchor to?
Rekord Kloud anchors to VeChain by default, and to Litecoin and BSV. Each anchor records its confirmations and the anchored Merkle hash, and the Proof Console links every anchor to a public explorer for that chain.
Is Rekord Kloud a proof of reserves product?
Rekord Kloud gives you the anchored, verifiable evidence layer underneath a reserves claim. The reserve figures themselves come from the operator and custodian records you choose to anchor, such as wallet attestations or custody statements. Kloud shows that those records exist in a given version and have stayed byte-identical since they were anchored; the accuracy of the figures stays with whoever produced them.
Can Rekord Kloud hold evidence for the EU Digital Product Passport or the battery passport?
Rekord Kloud hashes, versions and anchors the records you keep as evidence for ESPR (EU) 2024/1781 and for the battery passport under Regulation (EU) 2023/1542, which applies from 18 February 2027. Rekord provides the infrastructure. The regulatory obligation, and the content of each passport, stays with you.
How is it different from cloud storage or a normal database?
A database or bucket lets an administrator edit a record and leaves no outside trace of the earlier value. Rekord Kloud appends every change as a new version with its own anchored Merkle root, so any later change to a record is detectable by anyone holding the original bytes.
Who can verify records?
Through the Proof Console, auditors, regulators, depositors and operators each get role-based, read-only access to check any record against any anchored version themselves.