FluxRPC Engineering
Solana RPC Pricing: FluxRPC vs Helius vs Triton
What monthly plans, request mix and mainnet Yellowstone access mean for your RPC bill.
By FluxRPC | Pricing reference: 14 October 2026
Regular monthly prices are used throughout. Introductory promotions, annual discounts and negotiated rates are excluded.
FluxRPC and Helius both sell monthly Solana RPC plans with included usage. Triton charges usage against a prepaid balance. The difference is what that starting allowance buys, how additional usage is charged and whether the plan includes the streaming your application needs.
For developers who need RPC reads and mainnet Yellowstone gRPC together, FluxRPC Developer includes both for $38 per month, with 250 GB of bandwidth and 100 RPC requests per second. Helius mainnet LaserStream starts on its $499 Business plan. Those are different bundles, but the entry-price difference matters before the first stream is opened.
Request volume tells another part of the story. Using the production request mix in this article, 10 million monthly JSON-RPC requests works out to an estimated $38 on FluxRPC Developer, $58.75 on Helius Developer and $106.38 of Triton usage. The two Developer figures include their base plan fees. These are modelled charges, not invoices.
Here is how the plans, streaming charges and request mix produce those numbers.
How do FluxRPC, Helius and Triton charge for RPC?
FluxRPC starts with a plan. Each plan includes bandwidth and its associated limits and features. Requests use that allowance first. Once it is consumed, you can purchase additional bandwidth at $6 per 100 GB or upgrade to a larger plan. The $0.06-per-GB rate is an additional-bandwidth rate, not a substitute for the monthly fee.
Helius also starts with a plan. Its allowance is measured in credits. Standard RPC calls use 1 credit and standard getProgramAccounts calls use 10 credits. Additional credits are listed at $5 per million. Streaming and enhanced APIs have their own credit rules.
Triton starts with prepaid usage credit. Its published standard-RPC rate is $10 per million calls plus $0.08 per GB. Streaming is charged by bandwidth separately. The initial $125 deposit is prepaid credit, not a recurring $125 monthly subscription.
What do the monthly Solana RPC plans include?
The paid tiers below show the regular monthly fee, starting allowance, RPC request-rate limit and mainnet gRPC eligibility. The bundles are not identical.
FluxRPC: bandwidth and mainnet Yellowstone included
| Plan | Monthly fee | Included bandwidth | RPC req/s | Mainnet gRPC |
|---|---|---|---|---|
| Developer | $38 | 250 GB | 100 | Yellowstone included |
| Scale | $349 | 3 TB | 300 | Yellowstone included |
| Pro | $849 | 15 TB | 750 | Yellowstone included |
Helius: credits, with mainnet gRPC from Business
| Plan | Monthly fee | Included credits | RPC req/s | Mainnet gRPC |
|---|---|---|---|---|
| Developer | $49 | 10 million | 50 | No; Devnet gRPC only |
| Business | $499 | 100 million | 200 | LaserStream included |
| Professional | $999 | 200 million | 500 | LaserStream included; data add-ons available |
Mainnet Yellowstone gRPC: what does it cost to get started?
FluxRPC includes mainnet Yellowstone gRPC on its $38 Developer plan. Helius mainnet LaserStream begins at $499 on Business. That is a $461 difference in the eligible monthly subscription, or a 92.4% lower entry price on FluxRPC.
Helius Business includes a larger credit allowance and other services. The subscription difference is not a claim that the products are identical or that every equal-volume stream costs 92.4% less.
Included access is not unlimited streaming. FluxRPC RPC responses and streaming draw on the applicable plan bandwidth. Budget for their combined consumption. Buying more bandwidth does not increase the plan’s request-rate limit.
How is the streaming data charged?
FluxRPC uses included plan bandwidth first, followed by additional bandwidth at $6 per 100 GB or a plan upgrade. Helius LaserStream uses 2 credits per 0.1 MB of uncompressed data; Professional plans also offer data add-ons. Triton charges $0.08 per streaming GB without adding its standard-RPC per-call charge.
At large volumes, the package matters. Helius lists a Professional data add-on of $6,000 for 100 TB, equivalent to $0.06 per decimal GB before the base subscription. Equal GB labels also need not mean identical billable data: Helius explicitly meters uncompressed data.
Against Triton, FluxRPC’s additional-bandwidth rate is 25% lower per GB, but that is not the same as a 25% lower total bill. For example, 250 billable GB of Triton streaming represents $20 of usage, while FluxRPC Developer costs $38 and includes 250 GB. Triton still requires the $125 prepaid deposit.
For an application using both RPC and streaming, compare the combined bill. Triton charges standard RPC calls as well as bandwidth; FluxRPC uses its applicable bandwidth allowance for both. The JSON-RPC estimates below do not measure gRPC stream volume.
What would 10 million or 100 million RPC requests cost?
For the request mix in our sample, one million JSON-RPC requests represents approximately 7.98 GB of egress or 1.195 million Helius credits. Applying the published rates gives the following monthly estimates.
| Monthly requests | FluxRPC Developer Base fee + usage | Helius Developer Base fee + usage | Triton Usage from prepaid credit |
|---|---|---|---|
| 10 million | $38.00 | $58.75 | $106.38 |
| 100 million | $70.88 | $596.50 | $1,063.84 |
Estimated monthly charges for this sample, not provider invoices. JSON-RPC only; no streaming. Assumes traffic stays within each plan’s overall and method-specific limits and additional usage is charged proportionally. Taxes, purchase increments, promotions and negotiated discounts are excluded. These are selected-plan scenarios, not every provider’s lowest possible quote. Triton requires an initial deposit of at least $125.
At 10 million requests, the modelled traffic fits within FluxRPC Developer’s included bandwidth. Helius Developer consumes its included credits and then additional credits. Triton deducts both the request charge and bandwidth charge from its balance.
The 100-million-request calculation
FluxRPC: $38 + (798 GB − 250 GB included) × $0.06 = $70.88.
Helius: $49 + (119.5M credits − 10M included) × $5/M = $596.50.
Triton: (100M calls ÷ 1M) × $10 + 798 GB × $0.08 = $1,063.84.
Both Developer scenarios retain the same plan. A different traffic pattern may require an upgrade: additional usage does not raise the plan’s request-rate limit.
What does another million requests cost above the allowance?
Once the relevant allowance is exhausted, one million more requests with this mix has an estimated additional-usage value of $0.48 on FluxRPC or $5.98 on Helius. Triton’s standard usage charge for the same modelled traffic is about $10.64. These figures exclude FluxRPC and Helius base plan fees.
With bandwidth still available in a FluxRPC plan, those requests consume the allowance instead. $0.48 is not the cost of a FluxRPC subscription. Base fees and purchase rules still apply.
Why does the RPC method mix change the bill?
In FluxRPC’s sampled Amsterdam workload, about 2% of requests accounted for 68% of recorded outbound data through getProgramAccounts. Meanwhile, getMultipleAccounts generated about 60% of requests and 16% of outbound data.
| RPC method | Approx. request share | Approx. egress share |
|---|---|---|
| getMultipleAccounts | 60% | 16% |
| getAccountInfo | 18% | 3.4% |
| getProgramAccounts | 2% | 68% |
| getBlock | 0.02% | 6.5% |
Selected methods from the September 19–October 5, 2026 sample. Rounded estimates from sampled rates, not all Solana traffic. Rows do not sum to 100%; full detail is in the methodology below.
That is why a request count alone is not enough to compare prices. Method mix determines credit and per-call charges; response size determines bandwidth consumption. A million small account reads and a million large responses do not consume the same amount of data.
How far do the included allowances go?
Using the same 7.98 GB or 1.195 million Helius credits per million requests, each plan’s full allowance translates to these estimated request volumes:
| Plan | Monthly fee | Estimated requests within allowance, using this sample |
|---|---|---|
| FluxRPC Developer | $38 | 31.3 million |
| Helius Developer | $49 | 8.4 million |
| FluxRPC Scale | $349 | 376 million |
| Helius Business | $499 | 83.7 million |
| FluxRPC Pro | $849 | 1.88 billion |
| Helius Professional | $999 | 167 million |
Allowance-only estimates using published plans, not guaranteed monthly request counts. Request-rate limits and bursts still apply. The entire allowance is allocated to JSON-RPC, with none allocated to streaming.
For this sample, FluxRPC Developer’s included bandwidth covers about 31.3 million requests within its $38 plan, compared with 8.4 million within Helius Developer’s $49 plan. Small, repeated responses stretch the bandwidth allowance further. Different response sizes change that result.
When can a credit-based provider cost less?
Bandwidth is not always cheaper. In this sample, getBlock responses average an estimated 2.62 MB. At the published additional-usage rates, 1,000 such calls have a bandwidth value of about $0.157 on FluxRPC, compared with $0.005 at Helius’s documented 1-credit getBlock rate. That is a method-level illustration, not a comparison of complete monthly bills.
Provider-specific APIs can also change the calculation. Helius lists standard getProgramAccounts at 10 credits and its paginated getProgramAccountsV2 at 1 credit per request. One paginated request is not necessarily equivalent to a complete standard-GPA result. This article prices the standard methods in the sampled workload; it does not model an application redesigned around provider-specific APIs.
Choose the plan around the application, not the billing unit
For developers making frequent, small account-state reads and needing mainnet streaming, FluxRPC brings two relevant advantages together: an included bandwidth allowance that can cover substantial request volume, and mainnet Yellowstone on the $38 Developer plan. When usage grows, purchase additional bandwidth or move to a larger plan.
The comparison starts with what your application actually requests, the data those requests return and the streaming it needs. Add the plan fee, apply the included allowance, then calculate additional usage. That is a more useful buying decision than comparing “250 GB” with “10 million credits” in isolation.
Frequently asked questions
Is FluxRPC pay-as-you-go like Triton?
No. FluxRPC starts with a plan that includes bandwidth, limits and features. Use the allowance first, then purchase additional bandwidth or upgrade. Triton’s shared-service pricing deducts usage from prepaid credit.
Does FluxRPC’s $38 plan include mainnet Yellowstone gRPC?
Yes. Developer includes mainnet Yellowstone gRPC, 250 GB of bandwidth and 100 RPC requests per second. Streaming consumes the applicable bandwidth allowance; it is not unlimited.
Does Helius Developer include mainnet LaserStream gRPC?
No. The $49 Developer plan lists Devnet gRPC. Mainnet LaserStream gRPC starts on Business at $499 per month. WebSocket eligibility is separate.
Is Triton’s $125 deposit a monthly subscription?
No. It is prepaid, non-refundable usage credit valid for 12 months, not a recurring $125 monthly subscription.
Is FluxRPC cheaper than Helius for account-state reads?
For the small, repeated account-state reads in this sample, FluxRPC’s included bandwidth and additional-bandwidth rate are favourable. Different response sizes, product requirements or APIs can change the result. The monthly examples above include the selected base plans.
Methodology and sources
The cost estimates use FluxRPC Solana mainnet traffic from Amsterdam between September 19 and October 5, 2026. The exports contain 759 timestamps at 30-minute intervals, using five-minute request-rate and egress-rate windows. These are estimates from sampled rates, not individual response logs or provider invoices.
Observed workload detail
| RPC method | Requests | Egress | Est. bytes / request |
|---|---|---|---|
| getMultipleAccounts | 60.20% | 16.38% | 2.02 KB |
| getAccountInfo | 18.45% | 3.40% | 1.37 KB |
| getTokenLargestAccounts | 9.96% | 2.32% | 1.73 KB |
| getTokenAccountsCount | 7.10% | 0.08% | 78 B |
| getProgramAccounts | 2.01% | 68.32% | 252 KB |
| getSignaturesForAddress | 0.56% | 0.33% | 4.38 KB |
| getTransaction | 0.37% | 1.51% | 29.9 KB |
| getTokenAccountsByOwner | 0.28% | 0.95% | 25.2 KB |
| getBlock | 0.018% | 6.50% | 2.62 MB |
The pricing subset excludes provider-specific or non-portable methods and unknown labels. It retains approximately 92.9% of sampled requests and 99.8% of egress. Request shares determine credit and per-call costs; response volumes determine bandwidth costs. No weighted score is used.
For one million requests: FluxRPC = 7.98 GB × $0.06; Helius = 1.195 million credits × $5 per million; Triton = $10 + (7.98 GB × $0.08). Calculations use decimal billing units and rounded model inputs. Helius getProgramAccounts is charged at 10 credits; other modelled standard methods use 1 credit under its credit reference.
The model assumes comparable responses across providers. Compression, metering definitions, purchase increments, product-specific charges and plan limits may change actual bills. JSON-RPC telemetry does not establish gRPC data volume. Streaming prices are a separate comparison.
Helius source note
The Helius pricing-page FAQ describes archival calls as 10 credits, while its detailed credit reference lists getBlock and getTransaction at 1 credit. This article retains the lower, method-specific rates from that credit reference. The paginated getProgramAccountsV2 alternative is noted separately and is not substituted into the existing workload model.
Sources
- https://fluxrpc.com/pricing
- https://www.helius.dev/pricing
- https://triton.one/pricing
- https://solana.com/docs/rpc/http
- https://www.helius.dev/docs/billing/credits
- https://www.helius.dev/docs/laserstream
Pricing reference: 14 October 2026. Published by FluxRPC using its own production sample. Regular monthly prices exclude introductory promotions, annual discounts and negotiated rates.