A defined Bundle or a usage bill
The useful question is how much data your application requests and streams. Supanode publishes Bundle prices with explicit quotas. Triton currently bills standard RPC calls and bandwidth, and bills streaming by bandwidth. A lightly filtered stream and a full-block indexer can produce very different bills on the same provider.
Terms checked on 21 October 2026. USD prices below retain the provider's billing units. Triton's deposit is prepaid balance, not a monthly subscription price.
Compare the same interfaces
| Workload or term | Supanode | Triton PAYG |
|---|---|---|
| Standard RPC | STARTER $40 / 30 days; 15 RPS, 5 TPS | $10 / million calls + $0.08 / GB |
| Filtered mainnet gRPC | FOCUS $99 / 30 days; one subscription, 100 watched addresses | Dragon's Mouth streaming: $0.08 / GB |
| Budget model | Bundle price within stated quotas | Usage deducted from prepaid balance |
| Initial funding | See selected Bundle and trial instructions | Minimum $125 deposit; non-refundable; valid 12 months |
| Capacity | FOCUS 25 RPC RPS, 10 TPS; BUILD 200 RPS, 30 TPS | Flexible rate and connection limits; confirm for the workload |
Triton rates and deposit conditions: Triton pricing. Standard RPC and streaming have different charge formulas.
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.
Estimate the bill from actual bytes
Triton's bandwidth documentation says gRPC is billed on compressed bytes sent. HTTP JSON-RPC uses the uncompressed response size, while WebSocket traffic is billed as transmitted without compression. Your network monitor and invoice can therefore measure different byte totals. Triton bandwidth accounting explains the accounting.
Illustrative calculation, not a quote: 1,000 billed GB of gRPC at $0.08/GB gives $80 of streaming usage. One million standard RPC calls plus 1,000 billed GB gives $10 + $80 = $90. Do not add the RPC per-call charge to a pure streaming feed. These examples exclude other services and assume the published base rates.
Supanode FOCUS is a useful candidate if your filters fit its one-subscription and 100-address limits. Triton PAYG is worth modeling when traffic varies or a broader feed makes byte-based billing attractive. Neither example demonstrates identical throughput, filtering scope or recovery capability.
Client and recovery considerations
Dragon's Mouth is Triton's Geyser-fed Yellowstone interface for accounts, transactions, slots and blocks. Its documentation notes that protobuf definitions can change and the client should match the current interface. Treat a migration as a tested configuration change plus a review of filters, decoding and recovery. Triton Dragon's Mouth documentation.
For a full-block feed, test bandwidth, consumer CPU and persistence together. Compression changes both transfer volume and processing cost. Keep persistent checkpoints and verify available replay before retiring a backfill path.
Migration checklist
- Export one representative day of RPC counts, method mix, stream filters and billed or compressed bytes. Include a busy period.
- Calculate RPC and streaming independently. For Triton, confirm the deposit, rate/connection limits and byte accounting before funding.
- Match the Yellowstone protobuf/client version and check x-token authentication. Start with a narrow account or transaction filter.
- Validate slot continuity, commitment handling, duplicates and reconnect behavior with both providers reading the same workload.
- Move traffic gradually and review the actual usage dashboard against your estimate. Keep an independent backfill and rollback plan.