Dedicated NEAR RPC Node & NEAR RPC Endpoint | RedSwitches
// dedicated near rpc node

Private NEAR RPC Endpoints on a Dedicated Node

A private NEAR RPC endpoint on single-tenant NVMe bare metal. Full, archive, or validator nodes serving NEAR native JSON-RPC, with zero rate limits and no compute units.

Get a QuoteStart Live Chat
  • Private Endpoint, Zero Rate Limits
  • No Compute Units, Unlimited Requests
  • Full, Archive & Validator Builds
  • NEAR Native JSON-RPC
  • NVMe IOPS Tuned For State Reads
  • 20+ Global Tier III Locations
deploy.shlive

$ rs deploy near --type full --region fra

allocating single-tenant bare metal

restoring neard snapshot

syncing chunks to chain tip

serving near json-rpc

attaching ddos shield + ip allowlist

private endpoint live · near json-rpc

region Frankfurt · Nightshade PoS · ~1.2s finality

  • UnlimitedRequests
  • ZeroRate Limits
  • 100%Isolation
// why redswitches

Why Teams Run NEAR Nodes With RedSwitches

A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.

Unlimited RPS & Responses

One node, unlimited requests and responses. No compute units, no rate caps, no overage bills. A flat monthly price, run as hard as the hardware allows.

Dedicated Account Manager

A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.

Direct Engineering Access

Talk to the engineers who run the metal. nearcore (neard) config, AVX-ready compute, archival hot/cold storage layouts, and state-read IOPS tuning, handled by people who run NEAR nodes daily.

20+ Global Data Centers

Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.

Pay In Crypto

Settle in crypto or fiat, NEAR included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.

Tailored Load Balancing

Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.

// request your endpoint

Configure Your NEAR Node

Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.

1 Dedicated Node = Unlimited RequestsNo Compute Units$0 Overages, Guaranteed

NEAR Full Node

For dApps, wallets, bots & backend APIs

CPU
8–16 cores (AVX required)
RAM
24–64 GB
Storage
1–2 TB NVMe (4 TB recommended)
Network
100 Mbps+ on a 10/25 Gbps port
Clients
nearcore (neard) + full config access
Best for
  • Current-state reads for wallets and dApps
  • View calls and high parallel reads
  • Private JSON-RPC for backend APIs
Included with every node
  • Unlimited RPS, no rate limits
  • HTTPS & WebSocket (WSS)
  • 99.99% uptime SLA
  • Multi-region endpoints
  • Private networking + IP allowlisting
  • 24/7 Web3 engineering support
From$199/moflat, no compute units

Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.

Node specs above are based on the official NEAR documentation.

View official NEAR node docs →

Inquiring about: NEAR · Full Node

Fastest channel for quick deploys

Replies in ~5 minA RedSwitches Web3 engineer specs your private endpoint

No compute units, no rate limits. From $199/mo, flat.

Prefer to talk it through first? Start Live Chat

// why dedicated

Stop Fighting For Bandwidth On Shared NEAR RPC

Shared NEAR RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated NEAR node is your own private backbone: flat-priced, uncapped, and yours alone.

CapabilityShared RPC PoolRedSwitches Dedicated
Request limitsHard rate caps and compute-unit quotas throttle your NEAR calls the moment traffic spikesZero rate limits, your NEAR node serves unlimited requests up to what the hardware can push
ResourcesA noisy-neighbor pool where another tenant's mint or airdrop steals the throughput you paid for100% single-tenant CPU, RAM, and NVMe, reserved for your NEAR workload alone
BillingPer-compute-unit metering with surprise overage bills at the end of the monthOne flat monthly price for the whole node, $0 overages and no usage math
NetworkShared, throttled bandwidth you can neither see nor controlA dedicated 10 / 25 Gbps port, metered or unmetered, that is yours alone
PrivacyA public, pooled endpoint with a wide, shared attack surfaceA private NEAR endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull NEAR archive with custom RAM and disk, sized to your query depth
ControlNo server access, the provider picks the client, version, and configFull root, KVM, and IPMI, run the NEAR client and tuning you choose
// network details

NEAR Node Specifications

The networks, node software, data interfaces, and execution model your dedicated NEAR node ships with. NEAR serves its own native JSON-RPC over HTTP, not Ethereum eth_* namespaces.

Chain Parameters

Networks
Mainnet, Testnet
Native token
NEAR
Consensus
Nightshade sharding · Doomslug Proof of Stake
Block time
~600 ms
Finality
~1.2 s (Nightshade)
Execution
Sharded chunks · WebAssembly (Wasm)
Accounts
Human-readable account IDs
Smart contracts
Rust, JavaScript
Archive
Full history via archival node
Explorer
nearblocks.io

Supported Clients

Node software
  • nearcore (neard)
Data interfaces
  • NEAR JSON-RPC (HTTP)
Official SDKs
  • near-api-js
  • near-sdk-rs

Keep your endpoint private behind IP allowlisting and firewall rules. NEAR exposes a native JSON-RPC over HTTP (query, block, chunk, tx, send_tx, status), not Ethereum eth_* namespaces, so backends call it with near-api-js or near-sdk-rs against your dedicated node.

// use cases

What Teams Build On NEAR Nodes

Where a private, uncapped endpoint beats a shared RPC pool.

Wallet State Reads

Wallets need fast NEAR RPC reads for balances, access keys, and account state. A dedicated node keeps responses consistent during login spikes and airdrops, so users never see stalled screens and backends stop retrying.

Indexer Backfill Jobs

Indexers scan blocks and receipts at scale, then replay data for analytics and ETL. Dedicated capacity prevents queue buildup during long runs; pair with a NEAR archival node for deep-history backfills.

Explorer Search Traffic

Explorers face nonstop read pressure for blocks, transactions, receipts, and contract pages. A dedicated node keeps your explorer APIs responsive during high-attention events, so results load reliably instead of returning partial failures.

Historical Audit Queries

Audit and research workflows need old receipts, contract state changes, and long-range data. A NEAR archival node gives dependable deep-history access for compliance checks and forensic traces without slowing production RPC traffic.

Exchange Deposit APIs

Exchanges and custody systems monitor deposits, withdrawals, and confirmations constantly. Dedicated NEAR RPC cuts missed events from throttling, so your platform tracks activity with steadier reads, fewer retries, and cleaner downstream reconciliation.

Bot And Automation

Automation breaks when response times spike and requests queue. Dedicated resources keep bot reads consistent and lower missed execution windows, supporting trading bots, treasury automation, liquidation triggers, and alert systems that depend on timely NEAR RPC calls.

// how it works

From NEAR To Private Endpoint In 3 Steps

Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.

  1. 01

    Pick Your NEAR Node

    Choose full, archive, or validator. Full nodes serve current-state reads, archive keeps full history; tell us the region closest to your users.

  2. 02

    We Provision Bare Metal

    Your single-tenant nearcore (neard) node deploys on AVX-ready NVMe, snapshot-restored, so you skip the long chunk sync from genesis.

  3. 03

    Get Your Private Endpoint

    Receive a dedicated NEAR JSON-RPC endpoint with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.

// latency & locations

Put Your Node Where Milliseconds Are Won

RPC latency is mostly a function of distance. A dedicated node lets you choose the exact region, so you sit next to the traffic that matters instead of fighting for routing on a shared, far-away endpoint.

Place It Where Your Users Are

Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your NEAR node in the region your traffic actually comes from, not wherever a shared pool happens to route you.

Cut The Round Trips

RPC latency is mostly physical distance. Running in the same region as your users and the NEAR network's peers shaves the round-trips a far-away, shared endpoint can never give back, which is what high-frequency reads and transaction submission live or die on.

Multi-Region By Design

Run a primary node plus regional read replicas for fast reads everywhere and built-in redundancy. Split public read endpoints from private admin, debug, and trace endpoints.

Need a node within a target latency budget of a specific region or venue? Tell us the endpoint and we'll recommend the closest facility.

// supported chains

One Backbone For Every Major Chain

Run validators, RPC, and archive nodes across the chains your stack depends on, all on the same dedicated bare metal, with the same isolation, speed, and control.

// customer reviews

Trusted To Run Production Nodes

Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.

  • 4.8/525Gbps Bare Metal
    Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
    Felix MartinsenDenmark
  • 5.0/5VPN Operations
    Network has been rock solid. They’ve got Tier 1 carriers like Arelion, GTT, and TATA… We just ping them on Telegram and they sort things out quickly.
    TomasNetherlands
  • 4.8/5Validators
    Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
    Peppe TerranovaSouth Korea
  • 5.0/5Full Root Access
    As a sysadmin, I care more about control than flashy dashboards. RedSwitches gives me root access, IPMI, and actual hardware specs I can configure. Good for serious users.
    Eun-Woo GimSouth Korea
  • 5.0/5Enterprise Uptime
    We were searching for a truly reliable and stable hosting provider with maximum uptime and a powerful network infrastructure to ensure the lowest possible latency. RedSwitches not only met but exceeded our expectations.
    AppsLabGermany
  • 5.0/5Cloud Exit
    RedSwitches gave us full control over our infrastructure without the vendor lock-in we kept running into with cloud hosts. Customizable builds, fast provisioning, and actual humans handling support tickets. It’s refreshing.
    Princeton OttUnited States
  • 5.0/599.99% Uptime
    My website works smoothly, thanks to their 99.99% uptime guarantee. The support team is another plus for me, as I always have been able to get help whenever I needed it in just 5 minutes on average.
  • 5.0/5ETH & BTC Nodes
    Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
    Ervin KaruGermany
  • 5.0/510Gbps RPC
    They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
    Atri MukherjeeIndia
  • 5.0/5Streaming
    I am using their 10gbps streaming server for last 6 months and I have no complaints. Extremely quick live chat support and I love that they accept crypto.
    Tarun GhoshIndia
  • 5.0/5Bare Metal
    A really great hosting provider - what stands out the most is the stability of the network connection and the wide selection of bare metal servers. We’re very satisfied, and RedSwitches covers all of our needs.
    Борис ВербицкийPoland
  • 5.0/5AI Workloads
    Pros: Extremely reliable hardware, low-latency network, transparent billing… Great choice if you need raw power without cloud complexity. Works well for our dev environment and some AI workloads.
    Henry HarrisonUnited States
  • 5.0/5Switched Provider
    I have worked with OVH and Contabo in the past, but RedSwitches hit a better balance of price vs. support. Not the cheapest, but I get better performance and faster help.
    Samual SuttonUnited Kingdom
  • 5.0/5Game Servers
    Been using RedSwitches for 6 months now for my small game server biz. Uptime has been great, and I haven’t run into any hidden charges.
    Jerold PerkinsUnited States
  • 5.0/5AI Storage
    Using the storage servers to archive logs and snapshots from our AI pipeline… I also love that I could pick the datacenter closest to our team.
    Eino KoppelEstonia
  • 4.8/5Support
    Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
    Boniface LeandreUnited States
  • 5.0/5Instant Delivery
    They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
    Daniel StuartSri Lanka
  • 5.0/5Fast Provisioning
    A dedicated server has been installed within 30 minutes. Thirty minutes. It takes DAYS for some famous providers out there, but these guys do their work right.
    Ярослав СавенковNetherlands
  • 5.0/55+ Years
    I have been using their services for over 5+ years… Uptime: 10/10, Network: 10/10, Hardware Quality: 10/10, Customer Support: 20/10 (No, That’s Not A Typo).
  • 5.0/51 to 14 Servers
    They offer top quality hardware, excellent uptime and very responsive support… They helped us scale our business exponentially and we went from 1 server to 14 dedicated servers in less than a year.
    Sandip PanditIndia
  • 5.0/5Reliability
    Great hardware, non congested network and excellent service. Already using them for over a year and would definitely recommend Redswitches if you are looking for a reliable hosting provider.
    CandiceUnited States
  • 4.8/5Global Locations
    With servers available in numerous strategic locations, RedSwitches offers exceptional versatility and performance for our company’s diverse hosting needs. Plus, their no setup fee policy really helps keep costs down.
    Tiberiu RomanUnited States
  • 5.0/5Exam Platform
    "Your server is ready" - I read this message within 30 mins of starting the chat with their Sales Team… Excellent DELL Hardware and 100% Uptime.
    Mridul MehtaIndia
  • 5.0/5Bare Metal Cloud
    The dedicated server I got from RedSwitches has been incredibly reliable and fast. Their bare metal cloud solutions offer excellent performance, and the cloud VPS options are perfect for scaling. Highly recommended!
  • 5.0/5Zero Downtime
    I have been using their dedicated server from 9 months now. Starting from pre-sales till today I have not experienced downtime or lack of support.
    Amit BhatiaIndia
  • 5.0/524/7 Support
    First of all, all services work as expected - secondly - support is outstanding, no matter when you start the conversation with colleagues at support they have knowledge to help you out.
    LukaSlovenia
  • 5.0/5Since 2021
    We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
    Eitan WaisgerberIsrael
  • 5.0/5Easy Onboarding
    Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
    Birk SpillumNorway
  • 5.0/5Bare Metal
    Very good experience using their bare metal servers. Their customer service is one of the finest I have experienced - always prompt at resolving troubles. Highly recommend.
// faqs

Frequently Asked Questions

Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.

What do you get with Dedicated NEAR RPC Node Servers compared to shared NEAR RPC endpoints?

Shared endpoints batch you with other users. When traffic spikes, you compete for CPU, RAM, and disk IOPS. That leads to throttling, higher latency, and inconsistent responses. With dedicated NEAR RPC node servers, your endpoint runs on single-tenant resources. You get predictable throughput, stable reads, and cleaner send reliability. You also control server access, upgrade timing, and how you expose the endpoint.

When do I need a NEAR archival node instead of a standard Dedicated NEAR RPC Node?

Use a standard dedicated NEAR RPC node when your app mainly needs current state. That fits wallets, dApps, bots, and most backend APIs. Choose a NEAR archival node when you must query deep history for analytics, investigations, compliance, or long-range backfills. Archival is the right choice when recent state is not enough and you cannot accept missing older receipts or historical data.

How do you size CPU, RAM, and NVMe for my workload?

We size for your request pattern first, not generic tiers. Tell us what you run: wallet reads, explorer traffic, indexer backfills, or automation bots. Then we map that to dedicated resources. For NEAR RPC, disk speed matters a lot, so we prioritize NVMe for state reads. We scale RAM for cache headroom and concurrency, and we scale CPU cores when you need more parallel request handling. If you expect sustained high load, we plan a scale path instead of waiting for incidents.

What is included in managed vs unmanaged Dedicated NEAR RPC Node service?

Unmanaged means we deliver the dedicated infrastructure and you run node operations. You get root access, full control, and you manage installs, upgrades, and monitoring. Managed means we handle core node operations with you. That includes nearcore setup, service health checks, upgrade assistance, and incident escalation through 24/7 technical support. Managed is built for teams that want reliability without full-time on-call.

How do you secure the endpoint (firewall rules, IP allowlisting, auth, DDoS protection)?

Security starts at the network edge. We support firewall controls so you can restrict who can reach your NEAR RPC endpoint. Many teams keep RPC private and allow only backend IPs. We include DDoS protection to reduce downtime risk from volumetric floods. For access control, you can add an allowlist model at the server and network level. If you need stricter patterns, we can align the deployment around your security policy.

How do NEARcore upgrades work, and how do you avoid downtime during updates?

Nearcore upgrades should be planned, not rushed. With managed service, we schedule upgrades, validate service health, and follow a controlled rollout approach. With unmanaged, we can still advise on safe upgrade timing and operational practices. If you need uptime guarantees during upgrades, use a NEAR dedicated node cluster approach so you can upgrade one node while the other continues serving traffic.

What is your expected sync time for a fresh node, and what options reduce time-to-ready?

Sync time depends on current network conditions, your hardware profile, and whether you run NEAR RPC or a NEAR archival node. A dedicated server helps because you are not sharing disk and CPU during catch-up. We set expectations based on your target height and workload. If you want faster time-to-ready, the best lever is sizing storage and memory correctly from day one so the node does not hit I/O bottlenecks during catch-up.

For archival nodes, do you support split hot/cold storage layouts to control storage growth?

Yes. Archival history grows, and storing everything on premium NVMe is expensive. Split storage is a practical approach: keep hot data on faster disks, and push older history to colder storage. This keeps performance where it matters while controlling long-term storage cost for a NEAR archival node.

Do you charge per request or per compute unit?

No. Unlike shared RPC providers that bill per "compute unit" and throttle you past a quota, a dedicated node is a flat monthly price with unlimited requests and zero overages. One node equals all the throughput your hardware can serve. That makes budgeting predictable and removes the surprise bills that come with usage-based RPC pricing.

How is this different from a shared RPC endpoint?

Shared RPC pools serve thousands of customers from pooled infrastructure, so you inherit rate limits, noisy-neighbor latency, and compute-unit billing. A RedSwitches node runs on single-tenant bare metal that is yours alone: reserved CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.

Do I have to sync the node myself, or wait days for it?

No. We provision from current snapshots so your node is live in hours rather than syncing from genesis for days. You can run it yourself with full root access, or choose our fully managed option where our engineers handle the sync, updates, and monitoring. Either way you receive a working private endpoint, not an empty server.

Can I deploy close to a specific region or sequencer?

Yes. With 20+ Tier III locations across the US, EU, Asia, and Australia you can place your node in the same region as your users or a chain's sequencer to cut round-trip latency. Tell us your target region and we will recommend the closest facility. You can also run multi-region nodes for redundancy and split read and write endpoints.

// developer resources

NEAR Developer Resources

Official NEAR resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.

// launch your node

Launch Your Private NEAR Node

From $199/mo flat, sized to your chain's node specs and typically 30-40% below other providers. Snapshot-ready provisioning, zero setup fees, 24/7 Web3 engineers, no compute units, no rate limits.

Get a QuoteStart Live Chat