> ## Documentation Index
> Fetch the complete documentation index at: https://docs.initia.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently asked questions about Rollytics and migrating from the legacy KV Indexer.

## What Is Rollytics?

Rollytics is Initia's production indexing service that replaces the legacy KV
Indexer. Unlike KV Indexer, which runs inside each RPC node and duplicates index
storage, Rollytics runs as a dedicated external service that indexes chain data
once into a shared Postgres database and serves queries via a KV-compatible HTTP
API.

Key benefits:

* Eliminates duplicate index storage across RPC nodes
* Simplifies operations (reindexing happens in one place)
* Improves RPC node performance by removing indexing overhead

## Can We Keep Using KV Indexer?

Yes, but it is **not recommended**.

KV Indexer:

* Duplicates storage on every RPC node
* Increases operational cost as you scale
* Adds load to RPC nodes
* Is no longer actively maintained

Rollytics is the long-term supported indexing solution for Initia rollups.

## Will Services Break if We Don’t Migrate?

No immediate breakage is expected, but migration is recommended before
production scale.

## Is Rollytics Compatible with Existing KV Indexer Endpoints?

Yes, Rollytics is fully compatible with KV Indexer endpoints.

Rollytics exposes a KV Indexer endpoint-compatible HTTP API, which means:

* Existing tools and services continue to work without modification
* No code changes are required
* Only the base endpoint URL needs to be updated

This allows Rollytics to act as a drop-in replacement, making migration
straightforward and low-risk.

## Can Rollytics Run Alongside KV Indexer?

Yes, and this is the recommended migration approach.

You can:

* Run both in parallel
* Switch consumers incrementally
* Validate correctness
* Disable KV Indexer after confirmation

This approach requires no downtime and allows easy rollback.

## Does Rollytics Require Archival Nodes?

Yes.

The indexer needs access to **historical data from genesis**, which requires:

* Archival RPC
* REST endpoint
* JSON-RPC endpoint for EVM rollups

## What Postgres Version Is Required?

Postgres 15+ is compatible.

## How Many Rollytics Instances Should We Run?

* **Indexer**: one per chain
* **API**: one or more, depending on query load
* **Postgres**: one primary database, with replicas if needed

## What Data Does Rollytics Index?

Rollytics indexes:

* Blocks
* Transactions
* NFTs
* EVM transactions
* Internal EVM transactions (EVM rollups only)

## Which VM Types Are Supported?

Rollytics supports Move, Wasm, and EVM rollups.

## Does Rollytics Support Internal EVM Transactions?

Yes. For EVM rollups, internal transaction indexing is enabled by default.

## Where Is the API Reference?

The API reference is documented separately and mirrors the KV Indexer endpoint
structure.