At DePIN Day Buenos Aires, William Kempster (known in the ecosystem as Kemp), Ecosystem Lead at ar.io, addressed a problem that many decentralized infrastructure projects quietly struggle with: data may be stored in a decentralized way, but access to that data often is not.
As DePIN networks grow into a multi-billion-dollar sector, this architectural gap becomes increasingly risky. Kemp framed ar.io as an attempt to close that gap by decentralizing not just storage itself, but the indexing, routing, and access layer that sits on top of it.
The Hidden Centralization in DePIN Data Stacks
By the end of this year, DePIN is expected to represent a $32B market. Yet, according to Kemp, an estimated 90% of DePIN networks still rely on centralized infrastructure somewhere in their stack — most critically at the data access layer.
Even networks that store data on decentralized storage protocols often depend on a single gateway or endpoint to retrieve it. If that gateway goes down, access to “permanent” data disappears. In that scenario, decentralization at the storage layer loses much of its value.
This is the problem ar.io was designed to solve.
What ar.io Is Building on Arweave
ar.io positions itself as the first permanent cloud network, built on top of Arweave. While Arweave already guarantees permanent data storage, ar.io adds a decentralized layer for indexing, routing, and access.
The architecture consists of three core layers:
- Permanent storage on Arweave
- Smart contracts and compute on AO
- A decentralized gateway network operated by independent node operators
Together, these layers transform Arweave from a storage protocol into a permissionless, production-grade data platform.
Turbo, Gateways, and Wayfinder: Making Access Decentralized
Kemp walked through the main components that power the ar.io network. Turbo provides a high-availability upload service that allows data to be written quickly, with flexible payment options and immediate availability. Final settlement onchain happens in the background, abstracting complexity for developers and devices.
The Gateway Network is made up of hundreds of independently operated gateways that index Arweave data and serve it to users. These gateways communicate with each other, creating a resilient “hot cache” layer that dramatically improves reliability and performance.
Wayfinder solves one of the hardest problems in decentralized storage: how users find their data. Instead of hard-coding a gateway URL, users provide a transaction ID or name, and Wayfinder dynamically routes requests to an available gateway based on configurable strategies such as stake, latency, or redundancy.
Human-Readable Names for Permanent Data
To make permanent data usable at scale, ar.io also introduced the Arweave Name System (RNS). RNS allows developers to map human-readable names to immutable data stored on Arweave.
These names can be resolved across all gateways in the network, creating a resilient alternative to traditional domain systems. In practice, RNS is increasingly used not just for websites, but as a decentralized GET API pointing to permanent data objects.
Decentralizing Access
Kemp described decentralized access as the “final boss” of decentralized storage. Even if data is stored permanently and immutably, reliance on a single access point undermines the entire system.
ar.io’s gateway network addresses this by ensuring that data can always be retrieved — even if individual gateways, cloud providers, or centralized services fail. This architecture becomes especially relevant in scenarios where major infrastructure providers experience outages.
The result is a system where no single actor controls access to data, while still allowing teams to optimize performance for enterprise use cases.
How ar.io Fits into DePIN Architectures
Most DePIN networks follow a familiar pattern: devices collect data, centralized services process and store it, and protocols verify and monetize it. ar.io proposes replacing much of that centralized middle layer.
Devices can upload data permissionlessly into ar.io, where it is indexed, verified, and made permanently available. Protocols then build economic logic on top, rewarding contributors and selling access to enterprise customers.
For teams that require guaranteed quality of service, ar.io supports a hybrid model: running dedicated gateways for performance-critical traffic, with automatic failover to the decentralized network when needed.
Why Permanent Data Matters for the Machine Economy
Kemp emphasized that in a world of AI agents and autonomous systems, subscription-based storage models are fragile. Machines need the ability to write data once and rely on it indefinitely, without worrying about renewals, permissions, or billing failures.
Arweave’s pay-once, store-forever model enables this. Combined with cryptographic verification, it allows DePIN networks to build systems where data integrity, provenance, and availability are guaranteed long-term.
This makes ar.io particularly well-suited for machine-to-machine coordination and autonomous economic activity.
The Road Ahead: Monetized Data and Machine-Native Payments
Looking forward, ar.io is focused on enabling machine-native access and payments through standards like X402. The long-term vision is a network where gateways are rewarded directly by protocols for providing storage, indexing, and access services.
As more DePIN networks begin monetizing data itself, ar.io aims to push those revenue flows deeper into the decentralized stack, gradually replacing centralized components as they mature.
Building the Permanent Data Layer for DePIN
ar.io’s core thesis is simple but ambitious: decentralized infrastructure cannot be considered complete unless data access itself is decentralized.
By solving indexing, routing, naming, and access in a permissionless way, ar.io provides DePIN networks with a foundation for permanent, resilient, and machine-native data coordination — unlocking use cases that centralized systems struggle to support.
