ChainsEthereumSolanaBSCBaseBrowse all chainsFull index (1,000+)
SolutionsTrading bots & MEVIndexers & analyticsExchanges & paymentsChain teams & validatorsBring your own hardware
ResourcesWhat is a dedicated RPC node?LocationsFAQAbout
PricingContact
For indexers & analytics

Backfill the whole chain.
The bill stays the same.

Indexing is the workload metered plans punish hardest: millions of archive reads, trace calls on every block, and a credit budget that dies on day two of a backfill. On a dedicated archive node, a full historical crawl costs exactly what an idle month costs.

Built for heavy reads

What your node is tuned for.

Node type
Archive · full history where the chain offers it
Heavy methods
trace_ · debug_ · getBlock, unmetered
Tuning
Indexing profile: throughput and read concurrency
Client choice
Pick the client whose storage model fits your queries
Connections
Run as many workers as the pipeline wants
Cost
Archive band: flat $799/mo, any chain
The honest argument

Do the math on your last backfill.

Take the request count from your last historical sync and price it on any metered plan. Then compare a flat month of the Archive band. For most indexers the crossover happened long before they switched; they were paying a per-request tax on data they could have owned the pipe to.

There is a second cost metered plans hide: retry logic. Rate-limited pipelines spend engineering time on backoff, batching around caps, and partial-failure recovery. A node with no caps deletes that whole class of code.

Reorgs, resyncs and client upgrades are on us; your pipeline just reads. Live p50/p99 in the dashboard tells you when the bottleneck is your code, not the node.

Bring the chain. Bring the query shape.

We spec the archive node, the client and the city. Firm quote within the hour.

Get a quote in an hour