Overview
Learn more about extra services specifically for GetBlock dedicated nodes
A GetBlock dedicated node gives you isolated compute for one workload. These extra services extend that node. Each service solves one specific problem that a standard node cannot solve on its own.
The extra services are for Dedicated Nodes and available to all blockchains. The one exception is Solana Shreds Streaming, which is Solana-specific and is also offered as a standalone, credit-based service without a node.
Extra Services for Dedicated Nodes at a glance
These prices are temporary
All prices are preliminary and per month. They add to your dedicated node subscription. They do not replace it.
What each service gives you
1. Advanced Analytics
A private Grafana workspace that records every request your node handles and turns it into time-series charts: request volume, latency as percentiles (p50, p95, p99), and error rate — sliced by RPC method, by access key, and by region. You can trace a latency spike to the exact method behind it, attribute cost to a team or customer, size capacity from measured traffic, and spot a key that starts behaving abnormally.
2. Automatic RPC Failover
Health-checks your node at set intervals and treats it as degraded when it lags the chain head, its error rate rises, or its latency crosses a limit. Degraded traffic moves to GetBlock's shared RPC pool automatically and moves back once the node recovers — the endpoint URL never changes, so your application never notices the switch. Client upgrades and maintenance windows stop being downtime.
3. Custom Endpoint URL
Serves your node from a domain you own — rpc.yourapp.com via a CNAME record — instead of the autogenerated address with a random access token in the path. Authentication moves to a header such as x-access-token, so the secret no longer travels inside the URL, where it tends to end up in server logs and browser history. The URL also survives token rotation.
4. Dedicated Ingress Proxy
A dedicated node isolates the compute, but every request still passes through a shared ingress layer that terminates TLS, checks authentication, applies rate limits, and routes the request. This service gives you a proxy fleet that serves only your traffic: no other customer's surge can slow your gateway, the added latency stays predictable, and the rate-limit and routing rules become yours to configure.
Use it when you run at high request rates and the shared gateway has become the limit, or your compliance rules require an isolated traffic path end to end. Skip it when your traffic is moderate and the shared gateway keeps up — it isolates the routing layer, not the node's compute.
5. IP Allowlist
Restricts your endpoint by source IP: only requests from addresses you approved reach the node; everything else is rejected at the gateway with 403 Forbidden, before it consumes node capacity or quota. Entries can be single addresses or CIDR subnets, IPv4 and IPv6. A token authenticates who is calling; the allowlist controls where the call comes from — so a leaked token alone is no longer enough.
6. Nonstandard Client Support
Runs what a default node deliberately leaves off: the debug, trace, txpool, or admin namespaces; a specific client version, patched build, or private fork; custom flags or a custom tracer. You describe what you need, and GetBlock deploys and operates it — upgrades, monitoring, and incidents included — so you get the exotic setup without owning its operations.
7. Solana Shreds Streaming
Delivers raw block fragments (shreds) straight from validators over UDP, before the block is assembled — roughly 100 to 500 milliseconds before a standard commitment-based feed reports the same activity. You decode the shreds into transaction intent as the leader is packing it: signatures, accounts, instructions, and slot numbers. It comes in two modes: attached to your Solana dedicated node, or as a standalone credit-based service with no node at all.
8. Unified Multichain Endpoint
Collapses your per-chain endpoints into one URL and one credential. You keep your dedicated nodes but reach them all through a single unified endpoint, selecting the target chain with a subdomain, a path, or a chain-id parameter. Rate limits and the IP allowlist are set once and apply to every chain behind it, so adding a network no longer adds another endpoint and key to configure, rotate, and keep in sync.
9. Zero-Hop Node Access
Removes the gateway and load balancer from the path and connects your application straight to your node. Those layers each add a small amount of time and, worse for trading, a small amount of variance; a fixed direct route removes both. Because you always reach the same node, you also keep a consistent view of the mempool and chain state. Pair it with a node in the region closest to your systems for the largest gain.
Zero-Hop Node Access and Automatic RPC Failover pull in opposite directions by design: one removes the routing layer, the other depends on it. Choose the one that fits the workload rather than enabling both.
How to choose
Set up a dedicated node from your account dashboard. It covers most workloads on its own.
Add a capability only when you have the problem it solves.
Read the "When you can skip it" section on each page before you buy.
For blockchain-specific capabilities — Beacon API, Blockbook, ERC-4337, Overlay Methods, MEV Protection, Yellowstone gRPC — see the Add-ons section instead.
How to enable an add-on
To add any of these to your dedicated node, use the configurator setting of Dedicated Nodes or contact the support team for assistance.
Last updated
Was this helpful?