Decentralized Architecture
Decentralized architecture spreads data and processing across many nodes — removing single points of failure and improving privacy, security and resilience.
Decentralized Protection
Secure your dApps with privacy-first bot protection
What is Decentralized Architecture?
A decentralised architecture distributes work and data across independent nodes rather than concentrating them in one operator's systems. No single party holds everything, and no single failure stops the service.
The word is used loosely. A geographically distributed CDN run by one company is distributed but not decentralised — one operator still controls it. Decentralisation is about who holds authority, not where the servers are.
What it changes
| Property | Centralised | Decentralised |
|---|---|---|
| Single point of failure | The operator | No single node is load-bearing |
| Who sees the data | One party, in full | Each node sees a share |
| Who you must trust | The operator's policies and jurisdiction | The protocol, and the economics keeping nodes honest |
| Censorship and takedown | One place to apply pressure | No single place |
| Operational complexity | Lower | Considerably higher |
The last row is the honest cost, and it is why decentralisation is a deliberate trade rather than a free improvement. Consistency, upgrades and incident response are all harder when no one party is in charge.
Why it matters for a CAPTCHA
A CAPTCHA sees every visitor to every site that deploys it. Centralised, that is a view of a large share of web traffic held by one company — and several widely used CAPTCHAs are operated by advertising businesses, which is the detail privacy reviews tend to catch.
Distributing verification across independent providers changes what any one of them can observe. No single operator holds the full picture of who visited where, which addresses the concentration problem directly rather than asking users to trust a policy document.
How Prosopo uses it
Procaptcha runs verification across independent provider nodes rather than a single central service. A site's verification requests are distributed, so no one node observes the whole of a site's traffic, and the system keeps working when individual nodes do not.
Two things worth being straight about. First, decentralisation here is about distributing what is observed and removing single points of failure — it is not a claim that no data is processed, because a verification decision requires signals. Second, it is a means rather than an end: the reason it is worth the operational cost is the privacy position it makes possible, and that is what we would ask you to judge it on.