Dedicated RPC nodes

Dedicated RPC nodes are premium-level products of GetBlock. While ordering private RPC nodes, you access the entire server with no need to share computational resources with anyone. This option is highly recommended for scaling dApps and running high-load cryptocurrency applications.

chevron-down

133 of 133 chains

Extra services for dedicated nodes

Available on every dedicated chain below, 8 of them, from $199/mo.

Full documentation
  • Advanced Analytics

    Purpose-built Grafana with per-method, per-key, and per-region breakdowns

  • Automatic RPC Failover

    Automatic fallback to shared RPC if the dedicated node degrades

  • Custom Endpoint URL

    Replace the autogenerated hash with a URL you actually chose.

  • Dedicated ingress proxy

    Your own routing layer, fully isolated from all other traffic.

  • IP Allowlist

    IP whitelisting, CIDR allowlists, scoped keys, and rotation policies for regulated environments.

  • Nonstandard Client Support

    Extra namespaces, private forks, exotic configs, all running on managed infrastructure.

  • Unified Multichain Endpoint

    One URL for every node and chain in your stack.

  • Zero-Hop Node Access

    Connect straight to your node, bypassing the proxy layer entirely.

FAQ

Frequently Asked Questions

  • What is a Dedicated Node?

    plus
  • What is the difference between a Dedicated and a Shared node?

    plus
  • Private dedicated node: What are the advantages?

    plus
  • How to get a private node?

    plus
Dedicated nodes

A node of your own: what changes, and when it is worth it

cube-01

What a dedicated node gives you

Hardware reserved for one team, so throughput stops depending on anyone else’s traffic. Archive mode and nonstandard clients become available per chain, and so do the extra services a pooled endpoint cannot offer — an IP allowlist, an endpoint URL you chose, automatic failover and per-method analytics.

lightning-01

When it is time to move off Shared

Four signals, in the order they usually appear: sustained load that keeps meeting the rate limit rather than spiking into it; queries that need archive depth on every call; a compliance requirement that names IP allowlisting or a fixed endpoint; and methods or namespaces a standard client does not carry.