GetBlock RPC competitor monitor — 2026-11-06
Criterion: Dedicated nodes, self-hosted nodes, bare metal and private endpoint customization (dedicated-node-customization)
Executive result
The cumulative topic brief was rebuilt as a normalized 15-provider matrix. This pass records 2 decision-relevant current product-surface changes and several evidence corrections/refreshes. Page hashes, navigation changes and generic homepage rewrites were not counted as market changes.
Confirmed decision-relevant changes
- Chainstack now explicitly presents Self-Hosted Nodes as user-managed nodes on any infrastructure with automated deployment, self-healing and lifecycle management, alongside Managed Dedicated Nodes with flexible deployment/customization. Source: Chainstack home.
- dRPC now explicitly presents a Self-Hosted Gateway using open-source NodeCore and a NodeHaus RPC management/monitoring surface. This is gateway/orchestration evidence, not proof that dRPC supplies buyer-controlled bare-metal nodes. Sources: dRPC home, dRPC docs.
Evidence corrections and baseline refreshes
- Alchemy: current first-party navigation supports Dedicated Clusters, but the earlier topic row’s self-hosted classification was not supported and was removed. Source: Alchemy home.
- QuickNode: current pages explicitly support private, isolated Dedicated Clusters and custom-RPS enterprise sizing; they do not establish self-hosting, bare metal, region pinning or dedicated-cluster node-mode customization. Sources: home, pricing.
- Ankr: enterprise copy supports dedicated/bespoke infrastructure by request and customizable throughput. It does not establish self-hosted or bare-metal delivery. Source: enterprise.
- NOWNodes: pricing supports dedicated nodes and select regions; its node directory exposes archive, trace and debug modes by chain. Confirm applicability to a quoted dedicated node before sales use. Sources: pricing, nodes.
- Blockdaemon: the current homepage lists Dedicated Nodes, deployment options and Fleet Management. Bare-metal/on-prem and node-mode configuration remain unverified in today’s monitored evidence. Source: home.
- Blast API: the official site continues to say Blast products are deprecated and directs users to Alchemy. Source: official notice.
- Pocket Network / Grove: Grove’s official site says Grove is winding down; Pocket Network continues separately. No dedicated/self-hosted enterprise node product was verified for this criterion. Sources: Grove, Pocket Network.
Noise versus market evidence
- QuickNode, Chainstack, Moralis, dRPC and Blockdaemon returned changed page hashes in parts of the monitored surface. Only explicit, criterion-relevant first-party statements were promoted into the matrix.
- QuickNode blog/chains and Chainstack navigation changes were not independently treated as launches.
- Moralis’s pricing hash changed, but the captured text did not verify managed dedicated, self-hosted or bare-metal nodes. “Bring an RPC endpoint” describes connecting an endpoint to Moralis’s data schema, not Moralis operating that node.
- Lava’s invitation to run an RPC node is provider participation in a decentralized network; it was not classified as a buyer-controlled self-hosted product.
Access and extraction limitations
- QuickNode: changelog path returned 404.
- Alchemy: monitored chains and customer-story paths returned 404; current home navigation still supplied dedicated-cluster evidence.
- NOWNodes: legacy Postman documentation path returned 404.
- Blockdaemon: monitored legacy RPC and pricing paths returned 404; homepage remained usable.
- Tatum: monitored supported-blockchains path returned 404.
- Pocket Network / Grove:
docs.grove.cityfailed DNS resolution; the winding-down notice and Pocket Network site were accessible. - LlamaRPC: public pages returned HTTP 526 and docs/status hosts failed DNS resolution. Every capability cell remains
Not verified in monitored public evidence. - Allnodes: all monitored pages returned HTTP 403. Prior dedicated/bare-metal evidence was preserved as stale and explicitly marked for re-verification; access failure was not converted into a negative product claim.
- Lava Network: two legacy paths returned 404; current home/docs/blog were accessible.
Provider disposition
| Provider | 2026-11-06 disposition |
|---|---|
| QuickNode | Dedicated clusters evidenced; other customization dimensions unverified |
| Alchemy | Dedicated Clusters evidenced; unsupported self-hosted attribution removed |
| Infura | No criterion-specific positive evidence in monitored pages |
| Chainstack | Dedicated, self-hosted, flexible deployment and node add-on/configuration evidence |
| Ankr | Dedicated/bespoke infrastructure and throughput customization evidenced |
| Moralis | No managed-node hosting evidence; bring-your-endpoint wording not promoted |
| NOWNodes | Dedicated nodes, select regions and chain-specific node modes evidenced |
| dRPC | Self-hosted gateway/orchestration evidenced; node hosting boundary still open |
| Blast API | Not applicable: officially deprecated |
| Blockdaemon | Dedicated Nodes and deployment/fleet surface evidenced |
| Tatum | No criterion-specific positive evidence in monitored pages |
| Pocket Network / Grove | Grove winding down; no current positive criterion evidence |
| LlamaRPC | Not verified due to HTTP/DNS access failures |
| Allnodes | Prior evidence retained as stale; current re-verification blocked by 403 |
| Lava Network | Provider node participation not classified as enterprise self-hosting |
Topic-brief update
Updated: /root/getblock-rpc-competitive-research/monitoring/topics/dedicated-node-customization.md
The consolidated matrix now uses five uniform dimensions, covers all 15 tracked providers, attaches direct links to positive claims, distinguishes deprecated/not-applicable status, and places this dated audit trail below the current comparison.
Agentic-routing paper
The pre-run updater returned ok: true, paper_updated: true, and published the refreshed paper at Agentic Routing for RPC. Its candidate evidence focused on QuickNode latency, uptime/SLA, RPS and product-surface signals. Those routing-paper updates are recorded separately and do not by themselves establish dedicated-node customization.
Research priorities
- Re-verify Allnodes via an accessible first-party source.
- Obtain explicit bare-metal/on-prem and private-network evidence from active vendors.
- Verify dedicated-offering scope for archive/debug modes, client choice, plugins/gRPC, region pinning and private connectivity.
- Distinguish dRPC gateway deployment from upstream node ownership and operations.
- Confirm exact tenancy boundaries and configuration options for QuickNode and Alchemy dedicated clusters.