Infrastructure that stays boring under load.

Iteradian provides managed RPC infrastructure built for sustained load and consistent behaviour, so your application stays stable when traffic does not.

12

Networks in catalog

7-day

Free Trial

JSON-RPC 2.0

Unified API

The Problem We Solve

Public RPC endpoints are rate-limited and unreliable when demand spikes. Self-hosted nodes require constant maintenance, monitoring, and tuning. In decentralized networks, infrastructure instability costs real money — lost rewards, missed trades, and degraded user experiences.

Rate-limited public endpoints
High node maintenance overhead
Revenue loss from downtime

Our Approach

We built a full-stack managed RPC platform starting with Bittensor and expanding across 12 blockchain networks. Plans run from shared node access to nodes reserved for a single organization, with per-request analytics on every tier. We do not publish an uptime percentage or a service level agreement, because we do not have a measurement we could stand behind.

What Drives Us

Enforced, not advertised

Every limit we publish is one the gateway applies before your request reaches a node. A field in a database is not a feature.

Reliability

A ranked candidate list per network, fall-forward to the next healthy node when one stops answering, and eviction of the node that failed so other requests do not repeat the timeout.

Honest analytics

Every chart is drawn from recorded requests. Where there is no data behind a metric, the dashboard shows an empty series and says why, rather than drawing plausible noise.

Multi-chain

Bittensor, Lightchain AI and 10 more networks behind one JSON-RPC 2.0 interface and one API key.

Technology Stack

Built for production reliability at every layer.

Gateway

NestJS + JSON-RPC 2.0 Proxy

Database

PostgreSQL + Redis

Dashboard

Next.js + React

Rate Limiting

Sliding 1-second window + concurrency limit

Monitoring

Real-time metrics + Alerting

Failover

Automatic node health checks

Iteradian at a glance

Verified against the Iteradian control plane on .

Iteradian is a multi-chain RPC gateway and node control plane. Customers get an API key, point JSON-RPC 2.0 traffic at an Iteradian endpoint, and each request is routed to a pool of managed nodes with failover, rate limiting and per-request usage analytics.

As of

Iteradian's supported network catalog lists 12 networks: Arbitrum One, Avalanche, Base, Bittensor, BNB Smart Chain, Ethereum, Lightchain AI, Optimism, Polygon, Solana, Ethereum Sepolia, Polygon Amoy. Current availability is published by the gateway at GET /rpc/v1/networks.

As of

Iteradian plans are Free RPC at no cost, Developer RPC at $39 per month, Professional RPC at $169 per month, Dedicated RPC priced per contract, billed monthly in USD, or annually where the plan offers it. Prices and overage rates exclude applicable VAT and sales tax, which is calculated at checkout based on the billing location.

As of

Each plan includes a monthly request allowance: Free RPC includes 3,000,000 requests per month; Developer RPC includes 25,000,000 requests per month (overage $0.005 per 1,000 requests, capped at $150 per billing period); Professional RPC includes 80,000,000 requests per month (overage $0.003 per 1,000 requests, capped at $350 per billing period). Once the overage cap is reached, requests receive HTTP 429 with a JSON-RPC error body.

As of

Iteradian includes a 7-day free trial. New organizations start on the Developer RPC plan in trialing status and can issue API keys immediately.

As of

Iteradian publishes SDKs for TypeScript / JavaScript, Python, C# / .NET (npm: @iteradian-rpc/sdk, PyPI: iteradian, NuGet: Iteradian). They cover the management API and RPC calls through the gateway; any HTTP client or existing Web3 library also works with an X-Api-Key header.

As of

Iteradian authenticates gateway requests to `POST /rpc/v1/{network}` with an `X-Api-Key` header, or an `Authorization: Bearer` header. Requests over the plan's per-second rate or concurrency ceiling receive HTTP 429 with JSON-RPC error code -32005; requests past the monthly allowance and overage cap receive HTTP 429 with -32006 or -32007.

As of

Iteradian organizations use owner, admin, developer and viewer roles backed by a 28-permission catalog, and every organization-scoped API route checks membership before the handler runs.

As of

Our Journey

2024 Q3

Founded

Started with a focus on Bittensor RPC infrastructure.

2024 Q4

Multi-Chain Expansion

Added support for Ethereum, Polygon, Arbitrum, and more.

2025 Q1

Enterprise Launch

Introduced dedicated plans with custom SLAs and priority support.

2025 Q2

Automatic Failover

Read requests fail over across up to three nodes automatically; transaction submissions go to one node and are never replayed.

Global Presence

Caesarea, Israel • Lima, Peru

Ready to Get Started?

Join developers and teams who rely on Iteradian for their blockchain infrastructure needs.