Blockchain RPC endpoints,
ready in minutes.
Reliable, low-latency RPC access across five ecosystems. Standard JSON-RPC, WebSocket, and gRPC interfaces — connect your dApp, trading bot, or analytics pipeline without rewriting code.
vs best-effort public endpoints
sol · hl · pm · mon · bnb — one provider
push instead of polling — WS in every Solana plan
NTT FRA2 on DE-CIX — adjacent to validator clusters
◆ TRY IT FIRST
48-hour free trial at full speed, no card. Measure your workload in staging — what you see is what production gets.
◆ STANDARD JSON-RPC
web3.js · solana-web3.js · ethers · viem. Swap the URL — keep your code.
◆ ENGINEERS IN TELEGRAM
Not a ticket queue — engineers who can see your endpoint.
Wallets connect. Balances load. Users stay.
Wallet connections, transaction signing, and balance queries answer fast — without timeout errors that turn users away. Streaming keeps the UI live without a polling tax.
Every tier states its limits openly.
RPS and TPS are published for every Solana Bundle, so the hardware behind them is never oversold. You know exactly what you buy — and when you outgrow the ladder, dedicated picks up with no caps.
What is included in a Supanode Bundle plan?
Each Bundle pairs Solana JSON-RPC with Yellowstone gRPC under one IP-allowlisted subscription. STARTER is RPC-only; FOCUS and above add gRPC. RPS scales by tier from 15 to 500, TPS from 5 to 100, and gRPC concurrent connections from 1 to 50, measured over a 10-second sliding window.
Which chains does shared RPC cover?
The Bundle plans are Solana: JSON-RPC plus Yellowstone gRPC from one Frankfurt edge. Other ecosystems run their own products — Hyperliquid WebSocket streaming and indexer, Monad native gRPC, a Polymarket indexer, and BNB Chain dedicated nodes — while Ethereum, Base, Arbitrum, and other chains are available as dedicated nodes on request.
How fast is shared RPC?
The shared edge runs in Frankfurt — NTT FRA2 on DE-CIX — with nodes adjacent to major validator clusters, so in-region reads return in single-digit milliseconds and gRPC streams at a 3.8 ms p99. Uptime over the trailing 30 days is 99.9%.
How is shared RPC authenticated and rate-limited?
By IP allowlist — one IP per Bundle subscription, no x-token header on RPC. The RPS budget is shared between RPC HTTP calls and gRPC subscribe updates and measured over a 10-second sliding window. Most methods cost 1 RPS unit; heavier ones cost more (getProgramAccounts is 30).
How do I integrate shared RPC into my app?
Swap the endpoint URL. The Bundle speaks standard Solana JSON-RPC — every method, all three commitment levels — and the gRPC side is Triton/Yellowstone-compatible, so existing clients keep their code. Your endpoint and IP allowlist are provisioned over Telegram.
How is shared RPC priced?
Each tier is a flat monthly subscription, crypto-only and prepaid, with no per-request metering — only the caps (RPS, TPS, gRPC connections) change between tiers. Every tier carries an up-to-48-hour free trial, no card. Rates live on the Solana pricing page.
Can I change tiers later?
Yes. Upgrades and downgrades are arranged over Telegram and prorated against the time left on the current subscription. When PROFESSIONAL gets tight, the next step is a dedicated node with no shared budget at all.
When should I move from shared to dedicated?
When you need unlimited RPS/TPS, a private endpoint with no shared budget, or a custom region and hardware. Shared Bundles cover development and moderate production; dedicated nodes are single-tenant and built to your spec. See the Dedicated RPC solution.
Ready to connect?
Pick your chain, message us, get endpoints. Provisioning runs over Telegram with an engineer.