ENRU
Get a free endpoint

Dedicated nodes

A node of your own.
No neighbours in the queue.

Isolated capacity with your own limits, archive data and a pinned region. Teams move here when the shared endpoint stops being enough — because of load or because of infrastructure requirements.

Discuss a setup Compare with shared RPC
$1,000
Price · month
2 h
Support response
99.99%
Uptime · 30 days
9
Placement regions

Dedicated node

Ethereum mainnet

live
Your backendPrivate endpoint Dedicated nodeNetwork
Rate limit
set to your load
Latency · p50
18 ms
Block height
21,384,902
Archive
from genesis

What you get

A separate node, not a bigger quota

The difference from a shared endpoint is not in the plan numbers: it is who you share the capacity with and who decides its configuration.

  • Isolated capacity

    The node serves your traffic only — someone else's spike never shows up in your latency.

  • Your own limits

    Request rate and batch size follow your load instead of a pricing tier.

  • Archive data

    Full state history for indexing and reconciliation, with no depth limit.

  • Pinned region

    The node sits where your backend sits, so the route drops the whole trip to someone else's data centre.

  • Private endpoint

    Your own address and key. Request body and response shape stay the same as on shared RPC — no code changes.

  • 24/7 support

    Two-hour response time and a dedicated manager over email and chat.

How it rolls out

Four steps from the first call to production

We run and maintain the infrastructure; on your side one address in the config changes.

  1. 01

    Pick the network

    Bitcoin, Ethereum, Solana or Tron. Testnets follow the same shape — only the network segment changes.

  2. 02

    Bring the node up

    Configuration follows your load: sync profile, archive depth, disk requirements.

  3. 03

    Hand over the private address

    A separate endpoint and key. The rest of the integration stays as it is.

  4. 04

    Put it under monitoring

    Availability, response time and block-height lag are visible in the dashboard and on the status page.

Shared or dedicated

The shared endpoint stays right there — it is the easy place to start and to test.

Both run on the same API and the same key, so you can keep part of the traffic on the shared pool and move only the critical part to your own node.

Capacity

01
Shared RPC
Shared pool, scaled by us
Dedicated nodes
Reserved node, yours alone

Noisy neighbours

02
Shared RPC
Fair queue per key
Dedicated nodes
None — single tenant

Rate limits

03
Shared RPC
Per plan, burst-friendly
Dedicated nodes
Whatever the node can serve

Archive

04
Shared RPC
Included
Dedicated nodes
Included, custom retention

Placement

05
Shared RPC
Nearest healthy region
Dedicated nodes
Pinned to your region

Setup

06
Shared RPC
Instant
Dedicated nodes
Provisioned within a day

Best for

07
Shared RPC
Wallets, apps, bursty traffic
Dedicated nodes
Exchanges, indexers, steady load
See plansShared RPC endpoints

Who needs this

When traffic cannot wait in a shared queue

Dedicated nodes go to products where a predictable answer is part of what they promise their own users.

Price

One node, one network

The price covers running the node, monitoring and support. Each network gets a node of its own.

$1,000/ month

The exact setup depends on the network and the load profile — we quote it after a call.

Discuss a setup

What it covers

  • An isolated node in the region you pick
  • A private endpoint and a separate key
  • Archive data and usage stats in the dashboard
  • 24/7 support with a two-hour response

Questions

What teams usually ask

Infrastructure shouldn't be the thing slowing you down.

Free to start. No credit card required.

Get a free endpoint Talk to an expert