OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Infrastructure

Ar Io Node

Ar Io Node is open-source, TypeScript gateway software for self-hosting access to the Arweave permaweb and its permanent data network. It includes configurable data-serving and indexing functions, and can be paired with an optional Turbo bundler sidecar for accepting and bundling data items.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Ar Io Node — OpenViST project profile in Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Ar Io Node when you need to operate an Arweave gateway under your own infrastructure or configure its data-serving and indexing behavior. Consider the separate bundler setup when the service needs to accept and bundle data items.

Who it is for

  • Infrastructure operators who want to run an Arweave permaweb gateway.
  • Teams serving Arweave-stored data through their own gateway.
  • Operators configuring ANS-104 bundle indexing or a separate data-item bundling service.

Documented uses

  • Run a gateway that serves access to permaweb content stored on Arweave.
  • Configure GraphQL pass-through to another server while serving data through the gateway.
  • Filter ANS-104 bundle data for unbundling and indexing.
  • Pair the gateway with a Turbo bundler sidecar to accept data items and bundle them for submission to Arweave.
Before you choose

Requirements & limits

The repository is public and identifies the software as AGPL-3.0 licensed. Linux and Windows installation instructions are linked from the project README.

  • The project is infrastructure software that operators install and configure, not a hosted browsing app.
  • Docker examples expose the standalone gateway on port 4000 and persist data in a volume.
  • The optional Turbo bundler requires a stringified JWK wallet and uploader access configuration.
  • ANS-104 unbundling and indexing are described as experimental, with possible issues when indexing larger transaction sets.
  • The documented developer workflow uses Yarn and SQLite database migrations.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Run the standalone gateway with Docker

Build and start a standalone ar.io gateway container with persistent data storage.

Before you start

  • Docker
  • A local copy of the ar-io-node repository

Steps

  1. Build the image with the command below.

    Documented command
    docker build . -t ar-io-core:latest

  2. Start the container with the command below.

    Documented command
    docker run -p 4000:4000 -v ar-io-data:/app/data ar-io-core:latest

  3. Direct requests to the published port, 4000.

Expected outcome

A standalone gateway container runs with its data directory stored in the Docker volume `ar-io-data`.

Guide limitations

  • This recipe covers the standalone container path only; it does not configure Envoy or other optional services.
Documentation 1 ↗
Source-based practical guide

Configure GraphQL pass-through in Docker Compose

Proxy GraphQL requests to another server while using the ar.io gateway to serve data.

Before you start

  • Docker Compose
  • The ar-io-node repository

Steps

  1. Add GRAPHQL_HOST=arweave.net and GRAPHQL_PORT=443 to the project-root .env file.

  2. Use the repository's Docker Compose configuration to run the services.

Expected outcome

The gateway is configured to pass GraphQL requests to the specified host while serving data.

Guide limitations

  • The documented example uses arweave.net; other upstream configurations are not detailed here.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
ar-io/ar-io-node · Official homepage title · retained in its source language
How we review sourcesSuggest a correction