All-in-One Deployment

Run the entire OpenScan.AI stack — database, indexer, API, and frontend — inside a single container. This method is meant for evaluation, demos, and development environments. It is not recommended for production.

When to Use It

• Trying OpenScan.AI against a local or testnet node
• Demos and screenshots
• Development against the API

For anything user-facing, use the containerized deployment or a source build instead.

Run It

docker run -d \
  --name openscan-aio \
  -p 3000:3000 -p 4000:4000 \
  -e ETHEREUM_JSONRPC_HTTP_URL=http://your-chain-node:8545 \
  -e ETHEREUM_JSONRPC_TRACE_URL=http://your-chain-node:8545 \
  -e CHAIN_ID=50 \
  -v openscan-data:/data \
  ghcr.io/openscanai/all-in-one:latest

The container initializes its own database and starts indexing immediately. Logs:

docker logs -f openscan-aio

Limitations

• All state lives in one container filesystem (or the -v volume) — no service isolation.
• A crash of any component takes down the whole explorer.
• Not tuned for large backfills or production query loads.

Verify

curl "http://localhost:4000/api/v2/blocks"

Open http://localhost:3000 in a browser to see the UI.