Skip to main content
Research6 min read

Instanodes RPC Plans for Every Stage of Growth

A plan-by-plan guide to Instanodes RPC pricing: what Free, Build, Basic and Advanced include, how to read the quotas against real traffic, and when to move up.

Instanodes RPC Plans for Every Stage of Growth

By Instanodes Team

Share

This guide walks through the pricing page: what each plan includes, how to read the quotas against real traffic, and the signals that tell a team it is time to move up. Prefer to skip the reading? Deploy a free endpoint or talk to an engineer.

The Four Plans at a Glance

Every shared plan covers 50+ blockchain networks, a real-time dashboard and the same 99.95% uptime SLA. What changes as you move up is request volume, burst capacity, endpoint count, archive access and how close you sit to the engineers.

PlanPrice per monthRequests per dayRequests per monthRequests per secondEndpointsArchive access
Free$020K600K401No
Build$2960K1.8M602No
Basic$79500K15M1804Yes
Advanced$1691.6M48M2206Yes
PlanSupportBuilt for
FreeDeveloper communityResearch and POCs
BuildEmail, 24h responseEarly-stage protocols
BasicPriority, 4h response SLAGrowing protocols
AdvancedDedicated engineering Slack channelProduction and institutional

Advanced also adds dedicated IP addresses and custom rate limits and throughput. Prices shown are monthly billing. A 6-month term saves 12% and an annual term saves 20%.

Reading the Quotas Against Real Traffic

The daily quota sets your sustained load; the per-second limit sets how hard you can burst. Spread evenly over 24 hours, even the Advanced quota averages under 20 requests a second, so most teams hit the daily cap long before the burst ceiling.

Quotas are counted in plain requests. The number on the page is the number you budget against.

PlanAverage sustained requests per secondBurst ceiling, requests per secondCost per 1M requests
Free0.2340$0
Build0.6960$16.11
Basic5.8180$5.27
Advanced18.5220$3.52

The sustained figure is the daily quota divided by 86,400 seconds. Per-request cost drops by roughly 4.5x between Build and Advanced on monthly billing, before any term discount.

When to Move Up

Each upgrade tends to follow a specific limit you can point to. These are the signals to watch at each step.

Free: prove it works

Free is for hackathon builds, contract testing, research scripts and side-by-side benchmarks against a current provider. It has no time limit and needs no credit card. One endpoint and 600K requests a month cover a single developer comfortably.

Move on when a second environment appears or real users start hitting the endpoint.

Build: first users, two environments

At $29 a month, Build gives you two endpoints, which maps cleanly to staging and production. Email support with a 24h response covers teams that can tolerate a next-day answer.

Move on when any of these show up:

  • Daily requests regularly pass 60K, or rate-limit errors start appearing during launches and mints
  • An indexer, subgraph backfill or analytics job needs historical state
  • A next-day support answer is no longer acceptable

Basic: archive data and a 4h response

Basic is the first plan with archive node access. That matters as soon as you query state older than the recent window most full nodes keep: eth_getLogs across wide historical block ranges, eth_call or eth_getBalance at an old block number, or rebuilding a database from genesis.

It also raises the daily quota roughly 8x over Build, to 500K, and adds a 4h priority response SLA and four endpoints. This is the plan we recommend for most teams with live mainnet traffic.

Advanced: production at institutional standards

Advanced is for teams where the RPC layer sits on the critical path for user funds. It adds:

  • A dedicated engineering Slack channel, so incidents go straight to the people running the nodes
  • Dedicated IP addresses, useful when partners, exchanges or custodians allowlist traffic by IP
  • Custom rate limits and throughput tuned to your traffic pattern
  • 1.6M requests a day, 220 requests per second and six endpoints

If you are past Advanced, the next section covers what comes after.

Beyond the Shared Plans

Three paths open up once a team outgrows Advanced or needs isolation from shared infrastructure.

OptionWhat you getHow it is pricedHow you buy it
Custom planHigher rate limits and SLA terms on top of the shared fleetPriced against your real peak trafficRequest a quote
Dedicated NodeOne node, one chain, reserved for you. More throughput and isolation than shared plansPer chain. Base price and term discount vary by network. Terms of 1, 3, 6 or 12 monthsSelf-serve in the dashboard
Dedicated ClustersMulti-chain, multi-region, single-tenant capacity with a custom SLAScoped and quotedWith our team

For a custom quote, send three things: your peak requests per second, the chains you run, and the SLA terms you need. You get a plan sized to that traffic instead of a tier you have to grow into.

Dedicated Nodes are available on 28+ chains across mainnet and testnet. Every chain is priced individually, and current rates for each term are shown in the dashboard before you pay.

What Every Plan Gets

Some things do not change with the price tag.

  • The SLA is in writing on every plan, Free included. 99.95% uptime, contractual, backed by multi-region automatic failover and 24/7 monitoring.
  • The prices are on the page. Each plan lists its price, request limits and endpoint count. On a 6-month or annual term, the undiscounted price and the exact saving sit next to what you pay.
  • Plans change from the dashboard. Upgrade, downgrade or cancel at any time, with no penalty and no minimum term.
  • Nodes go live in under 5 minutes. Pick a chain, configure the endpoint, get a live RPC URL. The node arrives synced to the chain tip, so there is no hardware to set up and no sync to wait for.

Switching to Instanodes

For most teams, migration is a single URL change in the app config. Endpoints are drop-in compatible with standard EVM and non-EVM RPC interfaces.

The low-risk path is to test your own workload on the Free tier first, then swap the URL and pick the plan your traffic needs. The onboarding team provides a migration checklist, endpoint mapping and a parallel-run period, and migrations that involve dedicated nodes get direct engineering support throughout. The migration playbook covers the steps in detail.

FAQ

Is there a free plan?

Yes. Free gives you one RPC endpoint, 600K requests a month across 50+ networks, and the same 99.95% uptime SLA as paid plans. No credit card, no time limit.

Which plans include archive node access?

Basic ($79/month) and Advanced ($169/month). Free and Build do not.

Does the SLA change between plans?

No. Every plan carries a contractual 99.95% uptime SLA. Teams that need different terms, such as higher availability or dedicated incident response, can agree to them as part of a custom plan.

What if we need more than 220 requests per second?

Ask for a custom quote with your peak requests per second, chains and SLA requirements. If you need single-tenant capacity on one chain, a Dedicated Node is self-serve from the dashboard.

Can we change plans at any time?

Yes. Upgrade, downgrade or cancel from the dashboard with no penalty and no minimum term.

How do the longer billing terms work?

A 6-month term saves 12% and an annual term saves 20%. The pricing page shows the undiscounted price and the exact saving next to what you pay.

What is the difference between a Dedicated Node and Dedicated Clusters?

A Dedicated Node is one node on one chain, bought and configured self-serve. Dedicated Clusters are multi-chain, multi-region, single-tenant deployments with a custom SLA, scoped with our team.

Which chains are covered?

Shared plans cover 50+ networks across EVM and non-EVM ecosystems, including Ethereum, Base, Avalanche, BNB Chain, Bitcoin, Cosmos, TON, TRON, Polkadot and more. Dedicated Nodes are available on 28+ chains. The chains page has the full list.

Start on Free

Start on Free and upgrade when your traffic does.

Deploy a free endpoint Talk to an engineer

Written by

SP

Shivam Pandiya

Product Owner

Content specialist with 5+ years of experience across diverse niches, currently focused on Web3 infrastructure, nodes, rollups, and appchains.