Dedicated nodes are single-tenant: the whole server answers to you, with no compute shared with anyone. This is how teams scale a dApp or run high-load workloads. Available in Frankfurt, US East and Singapore, in full or archive mode.
Add-ons
124 of 127 chains
Available on every dedicated chain below, 8 of them, from $199/mo.
Purpose-built Grafana with per-method, per-key, and per-region breakdowns
Automatic fallback to shared RPC if the dedicated node degrades
Replace the autogenerated hash with a URL you actually chose.
Your own routing layer, fully isolated from all other traffic.
IP whitelisting, CIDR allowlists, scoped keys, and rotation policies for regulated environments.
Extra namespaces, private forks, exotic configs, all running on managed infrastructure.
One URL for every node and chain in your stack.
Connect straight to your node, bypassing the proxy layer entirely.
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.
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.
