Default
Full node
- Workload
- Read + write. Recent state
- Storage
- Pruned
- History
- Recent state only
Built for
- dApp backends
- Wallet RPC
- Bot signing
99.95% uptime, fully managed
Deploy and manage blockchain nodes without running them yourself. We handle monitoring, updates, and incident response.
What looks like one endpoint is a stack of independent layers, each built so a failure in one does not cascade to the next.
L1 · Edge
The load balancer routes every request to the closest healthy region. DDoS mitigation, TLS termination, and per-key rate limits run here, before any request reaches a node.
Edge
The load balancer routes every request to the closest healthy region. DDoS mitigation, TLS termination, and per-key rate limits run here, before any request reaches a node.
Auth
API key validation, origin and IP allowlists, method allowlists, and per-key quota counters. The auth plane runs apart from the node fleet, so a rejected key never reaches client code.
Routing
Reads go to the nearest node on the canonical tip. For read-after-write consistency, the X-Instanodes-Sticky header pins your requests to one node. Archive methods route to the archive cluster automatically.
Nodes
Where a chain ships more than one production client, the pool runs a mix (on Ethereum: Geth, Erigon, Reth, Nethermind), so one client's bug does not take every node down. Pre-synced replicas join the pool within minutes.
Health
Every node is probed continuously against the canonical tip. A node that falls behind is drained from the pool automatically. After a reorg, reads go to nodes on the canonical tip.
Observability
Latency histograms by method, error breakdowns, request distribution, mempool depth. Your own dashboard, plus a push stream to your Grafana, Datadog, or PagerDuty.
EVM and non-EVM, mainnet and testnet, full and archive. Every supported chain ships with the same monitoring, the same SLA, and the same authentication layer. A sample, grouped by stack:
Same JSON-RPC surface, one API key
7 shown
Rollups and their settlement layers
8 shown
Each chain's own RPC methods and tooling
9 shown
UTXO chains with indexer modules
4 shown
Not on the list? We add chains based on customer demand. Shared RPC Endpoints run on every network here: full nodes, archive nodes, and indexer modules where the protocol supports them. Dedicated Node is self-serve on 28+ of these chains.
Full, archive, trace, and validator nodes are priced separately because they cost meaningfully different amounts to operate. Choose by read pattern: how far back you query, and which methods you call.
Default
Built for
Deep history
Built for
Debug
Built for
Stake
Built for
Node type is what the node does. Deployment mode is who else is on it. Pick both independently.
Pooled capacity
Your traffic runs on pooled infrastructure alongside other customers. This is the RPC Endpoint product, priced by request volume rather than by node. The right default for most workloads.
Isolated capacity
One node, one chain, reserved entirely for you. Higher throughput and no noisy neighbours. Buy and configure a dedicated node directly from the dashboard, with no sales call and no quote.
Dedicated Node · selected chains
A selection of the 28+ chains you can buy a Dedicated Node on. The panel lists the full set with live per-chain pricing.
Pre-synced nodes go live in under 5 minutes. You skip the initial chain sync.
Both environments on every chain that has a public testnet. Switch between them from the dashboard.
Capacity scales up with traffic and back down when it drops, within your tier's burst limit.
Indexing
Archive nodes with trace support for indexers, analytics platforms, and on-chain monitoring services.
Create an Instanodes account. Sign-up takes no card — you choose the chain, node type, and term before anything is charged.
Pick from 28+ chains. Ethereum, Solana, Bitcoin, BSC, Polygon, Cosmos, and more. Mainnet, testnet, or both.
Full, archive, or trace node, shared or dedicated. The dashboard shows live pricing for each chain and term.
An authenticated RPC Endpoint, a monitoring dashboard, and configurable alerts. Live in under 5 minutes.
Need something specific? Talk to an engineer.
Node as a Service (NaaS) is a managed offering where Instanodes operates blockchain nodes on your behalf. You consume an RPC Endpoint; we handle the hardware, syncing, monitoring, protocol upgrades, failover, and incident response. The output is a stable RPC URL with contractual SLAs.
Shared RPC Endpoints cover 50+ networks, including Ethereum, Solana, Bitcoin, BSC, Polygon, Cosmos, Avalanche, Base, Arbitrum, Optimism, TON, Tron, Polkadot, Tezos, Celo, Mantle, and Fantom, EVM and non-EVM, mainnet and testnet. You can buy a Dedicated Node on 28+ of them.
Running your own node means buying hardware, paying for bandwidth, hiring on-call engineers, patching every protocol release, and absorbing every outage. NaaS replaces all of that with a flat-rate or usage-based subscription and a contractual uptime SLA. You stop staffing node on-call and paying for spare hardware.
Shared nodes serve multiple customers from the same node cluster with per-customer rate limits. They are the most cost-efficient option. A Dedicated Node is reserved for you alone, so all of its throughput and resources are yours. Pick dedicated for sustained high-volume production traffic or for latency-sensitive work like liquidations or arbitrage.
Yes, on every chain that has an archive node type. Archive nodes maintain full historical state, which is required for `eth_getBalance` on old blocks, `debug_traceTransaction`, contract state reads at arbitrary block heights, and most indexing workloads.
p99 under 100ms globally for read operations on shared nodes, and under 80ms on dedicated capacity. We run regions in North America, Europe, Asia-Pacific, and Latin America, and requests route to the nearest healthy node automatically.
We apply protocol upgrades (Ethereum hardforks, Solana cluster updates, Cosmos chain upgrades, etc.) ahead of the upgrade block, on a coordinated schedule. You don't need to do anything. Your RPC Endpoint stays live through the upgrade.
Yes, on dedicated and enterprise tiers. You can specify the execution and consensus clients and their versions (for example Erigon or Reth for traces, Lighthouse on the beacon side), indexer modules, and custom RPC method allowlists. We deploy and operate to your spec.
Auto-scaling absorbs spikes within your tier's burst limit. If you regularly need higher throughput, the dashboard suggests a tier upgrade and you switch from there. Your endpoint stays the same.
Not for nodes. The Free tier is an RPC Endpoint plan — 600K requests per month on shared infrastructure across 50+ chains, no card required. A Dedicated Node is a separate purchase, priced per chain and per term in the dashboard. Build against the RPC free tier, then move to a Dedicated Node when you need isolated capacity.
Pre-synced nodes across 28+ chains, multi-region by default, under a contractual uptime SLA. Pick your chain and term in the dashboard, which shows live pricing.