Dedicated NEAR RPC node. A private NEAR RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.
NEAR is a sharded proof-of-stake layer-1 with roughly 1 to 2 second finality and low fees, running WebAssembly smart contracts.
NEAR RPC endpoint and network details.
| Network | NEAR mainnet |
| Currency | NEAR |
| Testnet pages | NEAR Protocol Testnet |
| Interfaces | JSON-RPC |
| Dedicated endpoint | Your own NEAR RPC endpoint, from $509/mo → |
Public endpoints are listed in NEAR's official documentation (docs.near.org). They are shared and rate limited. Facts from NEAR's official documentation.
Order a dedicated NEAR 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 NEAR 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 connections, no per-plan cap
- Your own domain and an IP allowlist you control
- 99.99% SLA in writing, with service credits
- 24/7 support answered by engineers
NEAR node requirements, and what we build.
Chain facts from NEAR's official documentation (docs.near.org). Where it is silent, the row says so.
| Node software | nearcore |
| Interfaces | JSON-RPC |
| Full node | Yes, from $509/mo |
| Archive node | Yes, quoted per setup |
| Validator | Public validator role; quoted per setup |
| Gas token | NEAR |
| Official hardware guidance | RPC node, mainnet recommended: 8-Core (16-Thread) Intel i7/Xeon or equivalent, 32GB DDR4, 4TB NVMe SSD (minimal: 16GB DDR4, 2.5TB SATA3 SSD at 15k IOPS / 800 MiBps); archival node mainnet recommended: same CPU, 32GB DDR4, 3 TB SSD hot + 115 TB non-SSD cold storage (https://near-nodes.io/archival/hardware-archival). source ↗ |
| 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. |
What changed on NEAR recently
- Archival node spec (3 TB SSD hot + 115 TB cold) is far heavier than a normal RPC box; archive offers should be priced/scoped separately.
- FastNEAR became the sole snapshot provider from 1 Jan 2025 and its free snapshot service was deprecated 1 June 2025; official guidance is to use Epoch Sync where possible. source ↗
- NEAR Lake (AWS S3 indexer) stopped indexing on 24 March 2026; alternatives are Neardata, FastNear/NearBlocks data APIs or the nearcore indexer. source ↗
- nearcore 2.11.0 carried protocol version 83 (vote 13 Apr 2026) and a further upgrade to protocol 84 was scheduled for 1 June 2026; testnet and mainnet releases run ~5 weeks apart. source ↗
Sources: docs.near.org/api/rpc/introduction · near-nodes.io/archival · near-nodes.io/validator · near-nodes.io/rpc/hardware-rpc
Dedicated NEAR RPC node: the questions buyers ask.
What is a NEAR RPC node?
A server running NEAR's node software (nearcore) 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 NEAR RPC node?
A NEAR 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 NEAR 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 NEAR RPC endpoint?
An RPC endpoint that only your applications use. It sits on a dedicated NEAR 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 NEAR node is live?
As soon as it has synced with the NEAR network, and we tell you the moment it is ready. Sync time depends on the node type (an archive node replays the full history, so it takes longest), 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 $509/mo for my NEAR 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 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 NEAR node run on?
A machine that meets NEAR'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.
Does Argusnodes run NEAR archive nodes?
Yes. NEAR's documentation describes full-history operation; we run NEAR archive nodes, quoted per setup, with historical queries unmetered.
Can I run a NEAR validator with Argusnodes?
Yes. NEAR 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 NEAR endpoint from another provider?
Yes. A dedicated NEAR node speaks the same JSON-RPC interface 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 NEAR 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 NEAR 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 NEAR RPC URL?
The public NEAR RPC URLs are listed in NEAR's official documentation (docs.near.org). 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 NEAR RPC URL of your own, on your domain if you want, that nobody else uses.
Is NEAR RPC free?
Public NEAR endpoints are free and listed in NEAR's official documentation (docs.near.org). They are shared and rate limited, which is fine for a wallet or a test. A dedicated NEAR node is the paid option for an app, bot or indexer, at one fixed monthly price.
What is the best NEAR 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.