ar.io Gateways

What are Gateways?

Ar.io gateways are infrastructure nodes that make Arweave data easy to access from web apps, APIs, and users. They retrieve data from Arweave, cache and index it, resolve ArNS names, and expose standard HTTP interfaces for the permaweb.

Gateways do not replace Arweave. Arweave provides permanent storage and data availability guarantees; gateways make that data fast, discoverable, and practical to use.

Core Responsibilities

Data Access

Retrieve permanent data from Arweave, peer gateways, local cache, or chunk-level sources
Serve content over HTTP using familiar web patterns
Optimize delivery through caching, streaming, and source selection

Indexing and Discovery

Index transactions and bundled data items so apps can search and retrieve content efficiently
Resolve ArNS names into the data records and routes they point to
Expose gateway metadata so users and applications can discover available infrastructure

Network Participation

Register in the Gateway Address Registry to become discoverable as an ar.io network gateway
Stake ARIO to participate in network incentives and signal operational commitment
Participate in OIP by being observed, reporting observations when selected, and earning rewards for reliable service

What Gateways Are Not

Not Storage Providers

They do not create Arweave permanence: permanence comes from Arweave itself
They do not need to store everything: operators choose what to cache, index, and serve
They do not control user data: data ownership remains with the original publisher and underlying protocols

Not Application Compute

They do not run protocol logic: ar.io protocol state, staking, ArNS, and incentives are coordinated by Solana programs
They do not process arbitrary app logic: gateways focus on data access, indexing, routing, and delivery

Not a Single Service

Anyone can run one: the gateway network is open to independent operators
Apps can choose among gateways: routing can consider availability, geography, performance, policy, and payment requirements
Operators can specialize: gateways may differ in scale, indexing choices, moderation policy, payment setup, and extensions