Supanode vs Helius

Compare Solana RPC and mainnet gRPC plans, credit billing, replay windows and migration checks before choosing Supanode or Helius.

Choose the workload before the plan

A wallet reading account balances and a backend streaming program transactions need different infrastructure. For a small RPC workload, compare STARTER with Helius RPC plans. For a live Yellowstone feed, compare FOCUS or BUILD with LaserStream Mainnet. The $499 Helius Business plan is a mainnet streaming entry point, not the entry price for every Helius service.

Terms checked on 21 October 2026. Prices below are USD. Supanode uses 30-day Bundle periods; Helius lists monthly subscriptions. These plans have different capacities.

RPC and streaming, side by side

Workload or termSupanodeHelius
RPC entrySTARTER $40 / 30 days; 15 RPS, 5 TPSFree $0 / month; 1M credits, 10 RPS
Paid RPC exampleBUILD $159 / 30 days; 200 RPS, 30 TPSDeveloper $49 / month; 10M credits, 50 RPS
Mainnet gRPC entryFOCUS $99 / 30 days; RPC + WebSocket + gRPCBusiness $499 / month; 100M credits, 200 RPC RPS
Streaming billingIncluded within Bundle quotasLaserStream consumes 2 credits per 0.1 MB
gRPC recovery window100 slotsUp to 48 hours; historical semantics vary with age
Trying the serviceProduct trial up to 24 hours via portal instructionsFree RPC tier; mainnet LaserStream requires an eligible paid plan

Helius pricing supplies the Helius prices and credits; Helius historical replay describes recovery behavior.

What the Supanode plans include

STARTER is $40 per 30 days for RPC and WebSocket. Mainnet gRPC begins with FOCUS at $99 per 30 days: 25 RPC requests/s, 10 transactions/s, one gRPC subscription and up to 100 watched addresses. BUILD is $159 per 30 days with 200 RPC requests/s, 30 transactions/s, 10 gRPC subscriptions and 5,000 watched addresses in total. Owner/program filter limits also apply.

Supanode gRPC replay covers 100 slots. RPC replay covers two days. These are separate interfaces and windows; neither is a promise of arbitrary historical access. A higher plan buys stated capacity. It does not establish a latency advantage.

For a trial of up to 24 hours, enter the portal, open Free trial and follow the instructions there. The trial duration and setup follow those instructions. See Free trial and the full plan matrix.

Where the choice changes

Supanode can fit a defined filtered feed when its subscription and watched-address quotas cover the workload and you want a stated Bundle price. Measure the account list and bursts first: one connection in your code does not imply an unlimited subscription scope.

Helius documents Yellowstone compatibility and multi-node aggregation. Its longer documented replay window can matter when your recovery target exceeds 100 slots. For historical LaserStream replays older than roughly 20 minutes, Helius says data comes from finalized history; this can differ from the live processed stream. Helius LaserStream documentation and Helius historical replay explain those terms.

For credit budgeting, record the RPC method mix and stream bytes separately. The Business credit allowance also serves billed usage; a listed monthly price does not by itself establish the bill for a full-chain feed. No performance ranking is implied by these plan prices.

Migration checklist

  1. Inventory standard JSON-RPC, WebSocket subscriptions and any Helius-specific APIs or filters. Keep provider-specific calls behind an adapter until their replacement is verified.
  2. Pin the Yellowstone client and protobuf version. Configure the destination endpoint and authentication using its own documentation; test every subscription filter.
  3. Rehearse a disconnect from a saved slot. Keep your own durable checkpoints and deduplicate repeated events. Recovery must fit the destination window.
  4. Run both read paths against the same accounts and commitment level. Compare missing events, slot lag, errors and local processing time without sending duplicate transactions.
  5. Move a small share of traffic, inspect quota and credit usage, then expand. Keep a rollback endpoint and retain the old credentials until recovery is proven.

Sources

Continue reading