MACHINERY REGULATION

(EU) 2023/1230

Is your documentation really ready for January 20, 2027?

Ready for the new Machinery Regulation?

From 2027 you can deliver machinery documentation digitally. QRcube® supports the management and retention of this documentation, with version traceability and the paper version always available when needed.

Contact us

SDS – Safety Data Sheets

Delivering the sheet to the customer isn't enough: every revision under Article 31(9) must be sent without delay to recipients supplied in the previous 12 months. Missing an update: administrative fines up to €60,000.

Distribute SDS with no risk

With SDS Manager you send sheets to your customers, propagate updates to those who received them and keep proof of every transmission. Fully tracked, supporting compliance.

Contact us
All industries →
PlansCertiblogSecurityAboutPartnerContact
Start free

Decentralized cloud: what it is, how it works and why it changes document management

· by Gianluigi Michelotto

Share:

A traditional cloud stores files on centralized servers, usually concentrated in one or a few data centers. A decentralized cloud does the opposite: it encrypts each file, splits it into fragments and distributes them across a large network of storage nodes, none of which holds the whole document. It is not a variant of the cloud you already know: it is a different architecture, designed to reduce the single point of attack where most ransomware and data breach damage is concentrated.

How Certiblok®'s decentralized architecture works

In Certiblok® every document is encrypted with AES-256 and split into 80 fragments, distributed across a global network of 26,000 storage nodes. No single node holds the complete file: rebuilding it requires several fragments, not just one. European customers are assigned only to nodes located in the European Union, to comply with the GDPR.

On top of this infrastructure, a smart contract on the Ethereum blockchain controls how the cloud and the node network operate: it manages how fragments are distributed and retrieved, not the individual documents. This distinction matters because you often read the opposite: Certiblok®'s blockchain does not notarize or timestamp documents. The benefit for documents comes from a different mechanism, versioning: every update creates a new version, previous versions remain stored and restorable at any time, and the whole archive can be exported whenever needed.

Why it reduces risk in case of attack

A centralized cloud has a precise target: the data center or server where the files are stored. An infrastructure fragmented across thousands of nodes does not offer the same target. But the most concrete benefit against ransomware comes from versioning: if ransomware encrypts a file on your computer and the encrypted version reaches Certiblok®, the previous one remains stored and restorable. The attack can still reach its destination; when it does, it does not remove the possibility of going back.

Data sovereignty: where your documents really end up

With a traditional centralized cloud, knowing where data physically resides, and under which jurisdiction, is not always straightforward. With a distributed node architecture the question changes shape: what counts is not the single server but the rule by which fragments are assigned. For European customers, that rule is the contractual constraint that assigns them only to nodes in the European Union. This is relevant for anyone assessing non-EU cloud providers precisely because of the risk of access by third-country authorities.

Decentralized cloud vs traditional cloud: the differences that matter

Traditional cloud (centralized)Decentralized cloud (Certiblok®)
Where files areOne or a few data centersFragmented across thousands of nodes
Target in case of attackThe data center itselfNo node holds the complete file
Recovery after ransomwareDepends on a separate backupPrevious versions already stored and restorable
Control over where data residesVariable, often not transparentExplicit geographic assignment rule for EU customers

The most common mistakes in cloud document storage

Companies moving to a decentralized cloud almost always come from concrete problems, not from a theoretical interest in technology: shared folders with no control over who can access what, no version history, a single backup that turns out to be useless exactly when it is needed, because it was hit together with everything else. These are structural flaws of a centralized architecture, not carelessness.

An architecture that is becoming the standard

Five years ago the decentralized cloud was a niche topic. Today the same reasons that pushed companies towards the cloud, resilience, remote access, lower infrastructure costs, are pushing some of them beyond the centralized cloud: towards architectures that distribute risk instead of concentrating it in a single point.

Further reading: DORA 2025 and the decentralized cloud, Certiblok® ServerBackup: business backup on a decentralized cloud, QRCube®: smart sharing and cloud sync

Key takeaways

  • Every document is encrypted with AES-256 and split into 80 fragments distributed across the network: no node holds the whole file.
  • The network has 26,000 storage nodes worldwide; European customers are assigned only to nodes in the European Union, by contractual constraint.
  • A smart contract on the Ethereum blockchain controls the cloud and the node network, not individual documents: Certiblok® does not notarize or timestamp files.
  • The concrete defense against ransomware is versioning: previous versions remain stored and restorable.
  • The whole archive, with versions and history, can be exported at any time.

FAQ

What is a decentralized cloud?
It is a storage architecture that encrypts files and splits them into fragments distributed across a network of nodes, instead of storing them whole on one or a few central servers. No single node holds the complete document.
Is a decentralized cloud more secure than a traditional cloud?
It reduces the risk of having a single target, because data is fragmented across many nodes instead of concentrated in one data center. In Certiblok® the main benefit against ransomware comes from versioning: previous versions of a document remain stored and restorable even if a newer version is compromised.
What role does the blockchain play in Certiblok®'s decentralized cloud?
A smart contract on the Ethereum blockchain controls how the storage infrastructure and the node network operate, not individual documents. Certiblok® does not notarize or timestamp files on the blockchain: document versioning is a separate function, independent of the blockchain.
Where is data physically stored in a decentralized cloud?
It depends on the provider. In Certiblok® European customers are assigned exclusively to storage nodes located in the European Union, by contractual constraint, in order to comply with the GDPR.
What happens to documents if ransomware hits the company?
If ransomware encrypts a file on the computer and the encrypted version reaches Certiblok®, the previous version of the document remains stored and can be restored. The protection mechanism is versioning, not being impossible to hit.
Can a single storage node access a whole document?
No. Every file is encrypted and split into 80 fragments distributed across different nodes of the network: no single node stores or can rebuild the complete document on its own.

Text generated with AI assistance and reviewed by a human.