Plans and billing
Shared or dedicated infrastructure, pay-as-you-go or invoiced billing, and how requests and bandwidth are measured.
Current rates are on the pricing page. This page explains how billing works.
Shared or dedicated
Locations
8 cities on 3 continents, routed to the nearest
One location of your choice
Services
Every service on every network
One network per node. Solana: the monthly price of a standard node includes Dragon's Mouth gRPC streaming. JSON-RPC and WebSocket run on shared infrastructure and are billed as shared usage. Fumarole is billed separately, per usage. Sui: see the Sui dedicated nodes page. Monad: dedicated nodes are not offered. Custom setups on request
Latency
Low: routed to the nearest region
Low: in the data centre you choose
Capacity
Shared with other customers
Fixed gRPC streaming capacity for your traffic only. WebSocket runs on shared servers by default. If your node goes down, traffic fails over to shared backup nodes by default
Rate limits
Flexible, adjustable on request. Rate limits do not affect pricing
Can be customized for your workload. Contact support to review them
Billing
Per request and per GB, pay-as-you-go or invoiced
Fixed monthly price per node, invoiced. On Solana it covers Dragon's Mouth gRPC streaming. On Sui it covers gRPC streaming, and unary gRPC, archival gRPC, Walrus and Seal are billed per usage. On Solana, WebSocket, Fumarole and JSON-RPC are billed separately, per usage
Shared fits most workloads, including trading bots and market makers.
Riptide gRPC on shared infrastructure performs comparably to a dedicated node.
Choose dedicated for high-volume gRPC streaming, when metered streaming would cost more than a node's fixed monthly price on the pricing page.
Choose dedicated for a workload that needs isolated gRPC streaming capacity.
Pay-as-you-go or invoiced
Payment
USDC, through Buy credits in the customer dashboard
Card, ACH, USDC, or wire
How you're charged
Usage is deducted from your prepaid balance
Invoiced on the 1st of each month for the coming month
Minimum
A minimum prepaid deposit, valid for 12 months
A minimum monthly invoice
Going over
Not possible. Service stops when your balance reaches zero. The last debit can be larger than what was left; your balance stops at zero and the difference isn't taken from your next deposit
Billed at the same rates on the next invoice, without interruption
Coverage
Every service and network
Every service and network
Cancellation
Set by the pay-as-you-go terms you accept at signup. Unused balance is not refunded
One calendar month's notice
The minimum deposit is on the pricing page.
Sales sets your minimum monthly invoice when you switch to invoicing.
Deposits are non-refundable, under the terms you accept at signup.
Devnet and testnet are free on every subscription and don't use your balance.
Teams with steady production traffic usually switch to invoicing:
Overages at the same rates. Usage above your estimate is added to your next monthly invoice, with no service interruption.
Predictable bills. The same line items each month, sized on the previous month's usage.
To switch, open the chat in your customer dashboard or contact sales.
Top-ups, alerts, and usage
Top up: customer dashboard → Billing → Buy credits.
Low-balance alert: in Billing, turn on Low balance notifications, set a threshold in USD, and click Save. Every user on the account gets the email.
Zero balance: service stops and you get a balance-depleted email. Topping up reactivates it.
Usage: Billing shows your requests and GB, with a breakdown by service.
How usage is billed
Two meters:
Requests: each call, billed per million.
Bandwidth: data sent to you, billed per GB (1 GB = 1,024³ bytes). Data you send isn't counted.
Standard RPC, unary gRPC calls, Cloudbreak accounts, Superbank historical queries
Requests + bandwidth
Metaplex DAS API
Requests + bandwidth
Streams: Yellowstone gRPC, Deshred, Fumarole, Riptide and WebSocket
Bandwidth
Titan Swap API
Bandwidth
Shred Streaming
Per IP and data centre: by the minute at the 15-minute rate, or monthly on invoiced plans
Preconfirmations (Jito BAM, Harmonic)
Per covered slot or per message, whichever is greater
GraphQL, unary gRPC, archival gRPC, Seal, Walrus
Requests + bandwidth
gRPC streaming
Bandwidth
JSON-RPC
Requests + bandwidth
WebSocket
Bandwidth
Streams are recorded when they close. A long-lived stream appears in your usage all at once, and a stream still open at the end of a month is billed in the next month.
How bandwidth is measured
gRPC streams, such as Yellowstone gRPC and Riptide
Compressed bytes sent
Yes. zstd or gzip lowers it, at a CPU and latency cost
JSON-RPC and other HTTP calls, including Superbank, Cloudbreak, and DAS
Uncompressed response size
No. gzip speeds up transfer but doesn't change the bill
WebSocket (listed as Whirligig on usage pages and invoices)
Bytes sent (frames aren't compressed)
No
Filtering what you request or subscribe to is the most effective way to cut bandwidth.
On Solana,
base64+zstdaccount encoding anddataSliceshrink the response itself, so they do lower the bill.If your bandwidth is higher than you expect, contact support and we'll go through it with you.
Errors and disconnects
Requests rejected with HTTP 403, 429, 500, or 503
Not billed
A JSON-RPC or other HTTP response that Triton's load balancer cuts off before it completes. It ends with HTTP 500.
Not billed
Other error responses, such as 400, 404, 502, and 504
Counted as requests
A request your client cancels or times out before the response completes
Counted as requests
A gRPC or WebSocket stream that Triton's load balancer closes after sending data, for example when a server goes down or traffic fails over
Billed for the data already delivered, if it's over 1,000 bytes
What's next
Contact support by clicking the chat icon in your customer dashboard Sales questions? Contact us AI agent? Read llms.txt Follow updates: Blog · X · YouTube · Telegram · GitHub
Last updated