NEAR node
A NEAR RPC node of your own. No shared limit between you and the chain.
NEAR's own public endpoint is described in its docs as severely rate limited. A NEAR RPC node is a server that follows the chain and answers your app's calls on a private address, with a backup node running beside it. It keeps recent history, not all of it, and this page says exactly how much.
Updated . Prices checked .
- Full
- $289/mo
- Ready
- 24 h
On this pageNode type
02Node type
What a NEAR RPC node keeps, and what it does not.
NEAR has RPC nodes, archival nodes and validators. We rent the first kind, and the numbers below show why.
Full node
$289/mo
- Does
- Follows NEAR, checks every block and answers JSON-RPC calls from your app
- Keeps
- The last 5 epochs by default, set by the NEAR docs. An epoch is a fixed stretch of blocks. Older data is cleared away
- Disk
- The docs recommend 4 TB of NVMe, with 2.5 TB of SATA SSD as the stated minimum
- Memory
- 32 GB recommended, 16 GB as the minimum, with an 8-core, 16-thread CPU
- Archive
- Not offered. Full history needs about 3 TB of fast disk plus 115 TB of cold storage, per the docs
- Validator
- Not offered. We rent the RPC node only
The one-line test
Do your calls ask about accounts, balances, recent blocks and sending transactions? An RPC node fits. Do they ask about state from months or years ago? That is archival data, and no RPC node keeps it.
03How it works
Inside a NEAR RPC node: one program, five epochs.
NEAR's node software does everything on one server. It joins the network, checks blocks and answers your calls.
Epoch Sync
The node starts from the genesis block without a snapshot and catches up to the chain.
neard
NEAR's node program checks every block as it arrives.
Recent epochs
The last 5 epochs sit on fast NVMe storage. Older ones are cleared.
Your endpoint
Calls reach JSON-RPC at a private address on nodes.herorpc.com, keyed to you.
RPC and archival nodes run the same program. They differ only in how much history they keep.
NEAR docs recommend Epoch Sync for starting a node. It replaces the free snapshots many guides still mention.
The peer port is 24567. If a firewall blocks it inbound, state sync can stall.
04Know the field
RPC against archival, in numbers.
Both are real NEAR nodes. The disk gap between them is the reason we sell only one.
Archival figures are the docs' recommended mainnet setup: a hot database on SSD and a cold one on cheap disk. We do not sell it.
nearcore neard, RPC
- RPC node (what we run)
- 8-core, 16-thread CPU, 32 GB memory (16 GB minimum), 4 TB NVMe (2.5 TB SATA SSD minimum)
Epochs kept
- RPC node (what we run)
- 5 by default, 3 at the lowest. More epochs need more SSD
Archival (we do not sell)
Current release
- RPC node (what we run)
- nearcore 2.14.0 on 26 October 2026, with a database version change
The NEAR docs do not publish a total chain data size, so none is shown here. Figures are from near-nodes.io, updated March 2026.
CPU, memory and network figures for NEAR nodes, from the official docs: see the node requirements index.
05NEAR, specifically
What the NEAR docs warn about before you start.
From the NEAR node docs and troubleshooting pages. Most only matter once a node is live.
Five epochs by default
The setting is gc_num_epochs_to_keep. The default is 5 and the lowest is 3. Raising it costs disk.
Epoch Sync starts it
The docs recommend syncing from genesis with Epoch Sync, with no snapshot to download.
One port to keep open
Peers connect on 24567. The troubleshooting page says a firewall blocking it makes state sync time out.
Slow at epoch start
Cleanup runs when an epoch begins, and a node can miss blocks for a short while. The docs list it as known behaviour.
A CPU that matters
The docs name the needed CPU features: CMPXCHG16B, POPCNT, SSE4.1, SSE4.2, AVX and SHA-NI.
NEAR Lake is gone
The docs say NEAR Lake stopped indexing on 24 March 2026. They point to Neardata and other data services instead.
06Who rents one
Why teams rent one.
People whose app breaks when a public endpoint says no.
Wallets and payment apps
Read accounts, check balances and send transfers without depending on a throttled public address.
Indexers and bots
Teams that used NEAR Lake now need their own block and state reads. Anything older than five epochs still needs archival data.
DeFi and intent apps
When shared provider limits start to bite, a dedicated node has no per-request ceiling but its own hardware.
Teams running other chains
Keep a NEAR endpoint beside your other nodes. Cosmos nodes start from $139 a month.
07Price check
Under half the Allnodes list price.
The Allnodes bar is a fair match: its NEAR full node is the same kind of plan. Allnodes also prices archival NEAR, which we do not sell. RPC Fast quotes clusters from a much higher figure.
Full node
Allnodes: the cheapest dedicated plan on its NEAR pricing page.
RPC Fast
A dedicated NEAR node cluster, with infrastructure costs charged on top. Maintenance is included.
You save each month
$351 full
against the Allnodes list price above
08What you get
Set the term.
Pick the node type and how long to prepay. The price updates as you choose.
Your NEAR node
Term
- A dedicated server sized for NEAR
- neard as an RPC node, one private endpoint
- A backup node, included
- A private endpoint on nodes.herorpc.com
- Your server logins
- No setup fee, ready within 24 hours
$289
a month, full node
Billed monthly
Pay in BTC, ETH, USDT, USDC, BNB, SOL, TRX, LTC, DOGE or XMR.
10Questions
NEAR RPC node questions
Real questions from node operators, answered plainly.
What is a NEAR RPC node?
A server running neard, the NEAR node program, that follows the chain and answers JSON-RPC calls. It keeps recent history only, 5 epochs by default.
Do I need an archival node?
Only if you query state from long ago. An RPC node covers accounts, balances, recent blocks and sending transactions. Archival is a separate setup and we do not rent it.
Why do you not sell NEAR archival?
The docs recommend about 3 TB of fast disk plus 115 TB of cold storage. That is a different product at a very different cost, and we only list what we can run well.
Why not use the public NEAR endpoint?
NEAR's docs call it severely rate limited and point developers to providers or to running their own node.
What are the NEAR RPC node requirements?
The docs recommend an 8-core, 16-thread CPU, 32 GB of memory and 4 TB of NVMe. The stated minimum is 16 GB of memory and a 2.5 TB SATA SSD.
What happened to NEAR Lake?
The NEAR docs say it was deprecated on 24 March 2026 and its buckets stopped indexing. Neardata is named as the replacement, among other data services.
Is there a NEAR validator here?
No. We rent the RPC node only. Validators are a separate role in the NEAR docs.
What does it cost?
The plan is $289 a month, and nothing is charged to start. Paying for 12 months at once lowers that by 25 percent.
How fast is it ready?
The node is yours inside 24 hours of payment. Once it has synced, the endpoint address and your logins show in the dashboard.
A NEAR endpoint nobody else shares.
$289 a month, with a spare node alongside, running inside a day.