Dedicated Solana RPC node. A private Solana RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.
Solana is a globally distributed layer-1 blockchain kept running permissionlessly by validators around the world, with SOL as its native token.
Solana RPC endpoint and network details.
| Network | Solana mainnet |
| Currency | SOL |
| Interfaces | JSON-RPC · WebSocket · Geyser plugin |
| Dedicated endpoint | Your own Solana RPC endpoint, from $2,359/mo → |
Public endpoints are listed in Solana's official documentation (solana.com). They are shared and rate limited. Facts from Solana's official documentation.
Order a dedicated Solana RPC node.
Pick the node and the city. Where a city shows a price, pay in crypto and we start building; anywhere else, you get a firm quote within the hour.
What every dedicated Solana node includes.
- Fully managed at no additional cost: we set it up, sync it, monitor it 24/7, apply every upgrade and fix it if anything breaks
- Monitoring at no additional cost: live node and server metrics for your node in your dashboard
- No rate limits: the hardware is the only ceiling
- Every RPC method on, heavy queries included
- Unlimited WebSocket connections
- Your own domain and an IP allowlist you control
- 99.99% SLA in writing, with service credits
- 24/7 support answered by engineers
Solana node requirements, and what we build.
Chain facts from Solana's official documentation (solana.com). Where it is silent, the row says so.
| Node software | Agave, Firedancer (Frankendancer) |
| Interfaces | JSON-RPC, WebSocket, Geyser plugin |
| Full node | Yes, from $2,359/mo |
| Archive node | Not documented by the chain; historical access scoped per use case |
| Validator | Public validator role; quoted per setup |
| Gas token | SOL |
| Consensus | Proof of stake with Proof of History and Tower BFT |
| Block time | ~400ms slots (400 to 600ms) |
| Finality | Finalized after ~32 slots (about 13 seconds) |
| Official hardware guidance | Anza's requirements page lists a validator at 12 cores / 24 threads or more (2.8GHz+ base clock, AVX2), 256GB or more RAM (512GB motherboard capacity suggested, ECC), and three PCIe Gen3 x4 NVMe drives (accounts 1TB+, ledger 1TB+, snapshots 500GB+); an RPC node needs 16 cores / 32 threads or more and 512GB or more RAM for all account indexes, with accounts and ledger on separate disks and a larger ledger disk if longer history is required. source ↗ |
| Operator note | Anza recommends 12+ cores, 512GB RAM with all account indexes, and separate NVMe drives for accounts and ledger; nodes run with --limit-ledger-size and serve deep history from Bigtable. |
| Argusnodes build | Meets the official guidance above with headroom on top, never at the minimum. Ask and we tell you the exact CPU, RAM and NVMe; root access on request. |
| Argusnodes extras | Yellowstone gRPC streaming, Jito ShredStream and staked transaction sending (SWQoS), built into your quote on request. |
What changed on Solana recently
- Agave 4.0 (full mainnet rollout targeted May 2026) removed UDP transaction ingestion: QUIC is the only way to submit transactions to the validator; getSignaturesForAddress now returns error -32020 when before/until signatures are not found. source ↗
- Agave 4.2 is the recommended mainnet release for August 2026 with feature activations beginning the week of August 17, 2026: a 90% rent reduction, larger (4096-byte, v1 format) transactions, and slot times stepping from 400ms to 200ms; indexers decoding raw transaction bytes must handle the v1 layout. source ↗
- Full Firedancer remains unreleased for production as of the official README; Frankendancer is the only Firedancer build on mainnet-beta. source ↗
Sources: solana.com/docs/rpc · docs.anza.xyz/operations/setup-an-rpc-node · solana.com/validators · docs.anza.xyz/operations/requirements
Dedicated Solana RPC node: the questions buyers ask.
What is a Solana RPC node?
A server running Solana's node software (Agave, Firedancer (Frankendancer)) that answers RPC requests: reading balances and state, and sending transactions. It can be public and free, shared by a provider's customers, or dedicated to one client.
What is a dedicated Solana RPC node?
A Solana node on a bare-metal server that runs for one client only, with its own private RPC endpoint. Nobody else's traffic shares the machine, so there is no rate limit and no noisy neighbour, and every method the client exposes is on. Argusnodes builds, syncs, monitors and upgrades it for you at one fixed monthly price.
Is my Solana node managed and monitored, and what does that cost?
Yes, and so is monitoring, both at no additional cost. We set up and sync the node, watch it 24/7 with live node and server metrics in your dashboard, apply every network upgrade and client update, and fix it when something breaks. If you need help around the node, such as connecting it to your app, moving off another provider or setting up an indexer, our engineers help with that too, at the same monthly price.
What is a private Solana RPC endpoint?
An RPC endpoint that only your applications use. It sits on a dedicated Solana node that is yours alone, on your own domain if you want one, and answers only the IP addresses you allowlist. No other customer's traffic shares the machine, so nobody else's burst becomes your latency, and there is no rate limit to hit.
How long until my Solana node is live?
As soon as it has synced with the Solana network, and we tell you the moment it is ready. Sync time depends on the node type and the client you pick (Agave, Firedancer (Frankendancer)), so your quote carries an estimate for your exact setup rather than a number that is sometimes wrong. The quote itself lands within the hour, around the clock.
What is included in the from $2,359/mo for my Solana node?
Everything the node can do, with the premium add-ons other providers bill separately included free: unlimited RPS, every RPC method including heavy queries, unlimited WebSocket connections, your own domain with an IP allowlist, 18 cities to choose from, a 99.99% SLA with credits, 24/7 engineer support and live p50/p99 in your dashboard. There is no add-on price list because nothing is an add-on.
What hardware will my Solana node run on?
A machine that meets Solana's official hardware guidance (quoted in the spec sheet on this page) with headroom on top, on a dedicated bare-metal server. We never build at the minimum, because a node sized to the minimum becomes the bottleneck the day the chain grows. Ask before you order and we tell you the exact CPU, RAM and NVMe; the delivery email names the server, and root access is yours if you want it.
Do you offer Yellowstone gRPC streaming, Jito ShredStream and staked transaction sending (SWQoS) on Solana?
Yes, all of them. Tell us which you need when you order and they are built into your Solana quote, alongside every method and interface the client exposes.
Which Solana client should I choose?
Agave: Anza's validator client (agave-validator) and the one used in the official RPC node guide; run with --no-voting and --full-rpc-api for an RPC node, and with account indexes for getProgramAccounts / token lookups. Firedancer (Frankendancer): Jump's from-scratch C client built for performance; the full Firedancer validator 'is not ready for test or production use and has no releases', while the Frankendancer hybrid (Firedancer networking on Agave runtime/consensus) is available on testnet and mainnet-beta.
Does Argusnodes run Solana archive nodes?
Solana's official documentation does not describe an on-node archive mode, so we do not sell one. Heavy methods the client does expose are on by default; historical access is scoped per use case in your quote.
Can I run a Solana validator with Argusnodes?
Yes. Solana has a public validator role, and we operate validators under the same monitoring and support as RPC nodes, quoted per setup. Pick "Validator" in the configurator and describe the stake setup.
Can I move my Solana endpoint from another provider?
Yes. A dedicated Solana node speaks the same JSON-RPC and WebSocket and Geyser plugin interfaces as the shared endpoint you use today, so migration is pointing your application at your own endpoint. Billing is monthly with no lock-in on our side, and support engineers are on the channels 24/7 during cutover.
Are there rate limits or connection caps on a dedicated Solana node?
No artificial ones: unlimited RPS and no connection cap. The machine is yours alone, so the hardware is the only ceiling: if it can serve the request, you can send it. There is no per-plan connection cap because there is no plan tier.
How do I pay for my Solana node, and can I cancel?
In crypto, with no KYC and no setup fee. Pay monthly, or save 5% quarterly and 10% annually, and your price is locked for as long as your node runs. Cancel at the end of any term; the node is provisioned for you alone, so there is no meter to escape and no exit fee.
What is the Solana RPC URL?
The public Solana RPC URLs are listed in Solana's official documentation (solana.com). They are shared, rate limited and run by third parties, so they are fine for a wallet and not for an application. A dedicated node gives you a private Solana RPC URL of your own, on your domain if you want, that nobody else uses.
Is Solana RPC free?
Public Solana endpoints are free and listed in Solana's official documentation (solana.com). They are shared and rate limited, which is fine for a wallet or a test. A dedicated Solana node is the paid option for an app, bot or indexer, at one fixed monthly price.
What is the best Solana RPC provider?
It depends on the workload. Check four things: whether the node is single-tenant or shared, whether there are rate limits or credits, whether archive, trace and debug are included, and who answers when it breaks. For a wallet, a free public endpoint is enough. For an app, bot or indexer, a dedicated node with no rate limits avoids the throttling of shared plans. Our comparison pages (argusnodes.com/vs) set us against other providers, with sources.