Tessellate RPC JSON-RPC for EVM Chains

Tessellate RPC serves reads, writes and subscriptions across six EVM chains at launch. Every region publishes its availability, latency and head lag against targets on a public status page.

Why Use Tessellate RPC

Standard Methods

Standard JSON-RPC, so existing clients and libraries work without changes.

Published Limits

Block ranges, batch sizes and result caps are documented per plan.

Honest Reporting

Availability and latency are published against targets, including the months we miss.

One Endpoint

Start on a shared tier and move to dedicated nodes without changing your code.

Built for Diversity

Client diversity and N+2 node pools per chain, per region, monitored to a stated standard.

RPC

Requests pass through an Envoy gateway to a Rust router that classifies each method and picks a backend by head lag, error rate and latency. Immutable data is cached by block hash; latest and pending are never cached beyond one block time.

Launch chains:

More Planned

How RPC Works

How Archive Works

Archive and Trace

A Reth archive tier on local NVMe serves historical state and the debug_ and trace_ namespaces. Archive reads are weighted on shared plans and unmetered on Dedicated. Mainnet archive state is of the order of 3 TB.

Launch chains:

More Planned

Built for Developers
by Engineers

Tessellate RPC keeps integrations simple:

Meet with us

Bring reliable infrastructure to your organisation

Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to ourPrivacy Policy, which details how we collect and use your information.