Dedicated nodes, self-hosted nodes, bare metal and private endpoint customization

Comparison updated: 2026-11-06

Coverage: 8/15 providers have at least one evidenced comparison dimension; 2/15 have evidence in every applicable dimension. No provider has current monitored evidence for an explicitly bare-metal buyer deployment.

> Evidence semantics: “Publicly evidenced” means a direct vendor source explicitly supports the narrowly worded cell. “Not verified in monitored public evidence” means the monitored/direct sources are insufficient; it does not mean the provider lacks the capability. Dedicated clusters, API keys, archive access, validators, and high request limits are not treated as self-hosted or bare-metal nodes without explicit evidence. Scope and availability are volatile; verify before sales use.

Product definitions

  • Managed dedicated: vendor-operated, isolated or dedicated node/cluster infrastructure rather than a shared API plan.
  • Self-hosted / user-managed: software or lifecycle tooling explicitly offered for nodes running on buyer-controlled infrastructure.
  • Bare metal / on-prem: an explicit buyer deployment target; “dedicated” alone does not qualify.
  • Custom deployment / region: explicit flexible deployment, bespoke infrastructure, selectable region, or equivalent customization.
  • Node modes / configuration: explicit archive, debug/trace, client/plugin, or similar node-surface customization associated with the vendor’s node offering. Generic archive access on a shared API is not enough.
ProviderManaged dedicatedSelf-hosted / user-managedBare metal / on-premCustom deployment / regionNode modes / configurationDirect sourcesCoverage
QuickNodePublicly evidenced — private, isolated dedicated clustersNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified for dedicated-cluster customizationhome; pricing1/5
AlchemyPublicly evidenced — Dedicated Clusters are listed as a scale productNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified for dedicated-cluster customizationhome1/5
InfuraNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencepricing0/5
ChainstackPublicly evidenced — Managed Dedicated NodesPublicly evidenced — user-managed nodes on any infrastructureNot verified in monitored public evidencePublicly evidenced — flexible deployment and customization optionsPublicly evidenced — dedicated-node docs expose monitoring, hybrid hosting and add-ons including Yellowstone gRPC/Geyserhome; docs4/5
AnkrPublicly evidenced — dedicated infrastructure by requestNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced — bespoke infrastructure and customizable throughputNot verified in monitored public evidenceenterprise2/5
MoralisNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencehome0/5
NOWNodesPublicly evidenced — dedicated-node plansNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced — select regions on custom plansPublicly evidenced — node directory exposes archive, trace and debug modes by chainpricing; nodes3/5
dRPCNot verified in monitored public evidencePublicly evidenced — open-source self-hosted NodeCore gatewayNot verified in monitored public evidencePublicly evidenced — self-hosted gateway plus NodeHaus RPC management surfaceNot verified in monitored public evidencehome; docs2/5
Blast APINot applicable — official site says Blast products are deprecatedNot applicable — deprecatedNot applicable — deprecatedNot applicable — deprecatedNot applicable — deprecateddeprecation noticeN/A
BlockdaemonPublicly evidenced — Dedicated Nodes infrastructure serviceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced — deployment options and multi-network Fleet Management are listedNot verified in monitored public evidencehome2/5
TatumNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencehome0/5
Pocket Network / GroveNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceGrove winding-down notice; Pocket Network0/5
LlamaRPCNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidence—0/5
AllnodesPublicly evidenced in the prior consolidated review; current pages were inaccessible to the monitorNot verified in monitored public evidencePublicly evidenced in the prior consolidated review; current pages were inaccessible to the monitorNot verified in monitored public evidenceNot verified in monitored public evidencehome; pricing2/5, stale
Lava NetworkNot verified in monitored public evidenceNot verified as a buyer-controlled node productNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencehome0/5

Cross-provider readout

  • Breadth: 8 of 15 tracked providers have at least one positive, directly linked signal in the current matrix, including stale carried-forward Allnodes evidence; Blast API is marked not applicable because its official site says the product is deprecated.
  • Completeness: Chainstack and Blast API have no unresolved cells, but Blast is complete only because every dimension is not applicable. No active provider has evidence across all five dimensions.
  • Most evidenced: managed dedicated infrastructure (6 active providers) and custom deployment/region (5 active providers, including dRPC’s self-hosted management surface).
  • Least evidenced: explicit bare-metal/on-prem deployment. The only carried-forward signal is stale Allnodes evidence, and its pages returned access protection during this pass.
  • No positive topic evidence in the monitored surface: Infura, Moralis, Tatum, Pocket Network / Grove, LlamaRPC, and Lava Network.
  • Important distinction: Lava’s “run an RPC node” is provider participation in a decentralized network, not evidence of a managed self-hosted product for enterprise buyers. Moralis’s “bring an RPC endpoint” connects an endpoint to its data schema; it is not evidence that Moralis deploys or manages that node.

Buyer guidance

  1. Specify whether the requirement is an isolated managed cluster, a buyer-operated node, bare metal/on-prem, or merely a private URL/API key; vendors use “dedicated” inconsistently.
  2. Ask who owns the cloud account, operating system, node keys, snapshots and incident response, and whether the node is single tenant at compute, storage and network layers.
  3. Put chain, client, pruning/archive depth, debug/trace methods, plugins/gRPC, genesis backfill, region, RPS and failover topology into the quote request.
  4. Require contractual language for region pinning, maintenance windows, upgrades, recovery point/time objectives, SLA measurement and service credits.
  5. Verify whether archive/debug capabilities apply to the dedicated deployment rather than only to a shared API pool.

Direct-source ledger

  • QuickNode: home and pricing — checked 2026-11-06.
  • Alchemy: home — checked 2026-11-06.
  • Infura: pricing — checked 2026-11-06; shared managed API evidence only for this criterion.
  • Chainstack: home and docs — checked 2026-11-06.
  • Ankr: enterprise — checked 2026-11-06.
  • Moralis: home — checked 2026-11-06; “bring an RPC endpoint” not classified as node hosting.
  • NOWNodes: pricing and nodes — checked 2026-11-06.
  • dRPC: home and docs — checked 2026-11-06.
  • Blast API: official deprecation notice — checked 2026-11-06.
  • Blockdaemon: home — checked 2026-11-06.
  • Tatum: home — checked 2026-11-06.
  • Pocket Network / Grove: Grove notice and Pocket Network — checked 2026-11-06.
  • Allnodes: home and pricing — prior evidence carried forward; HTTP 403 in the 2026-11-06 collector, so re-verification is required.
  • Lava Network: home — checked 2026-11-06.

Research priorities

  1. Obtain explicit bare-metal/on-prem and private-network evidence; do not infer either from “dedicated.”
  2. Re-verify Allnodes through an accessible first-party source or assisted browser session.
  3. Find product-level Alchemy Dedicated Clusters documentation and determine supported regions, tenancy boundary and configurable node modes.
  4. Confirm whether QuickNode Dedicated Clusters permit region pinning, client selection, archive/debug configuration and private connectivity.
  5. Separate dRPC NodeCore gateway orchestration from actual node hosting and document where upstream nodes run.

Research log

Audit trail — 2026-11-06 consolidation
  • Refreshed the fixed five-dimension matrix across all 15 tracked providers.
  • Added current direct evidence for QuickNode and Alchemy dedicated clusters; Chainstack managed dedicated and self-hosted nodes; Ankr bespoke dedicated infrastructure; NOWNodes dedicated nodes/select regions/node modes; dRPC’s self-hosted NodeCore gateway; and Blockdaemon Dedicated Nodes/deployment options.
  • Removed the prior Alchemy self-hosted classification because the monitored source did not support it.
  • Preserved prior Allnodes dedicated/bare-metal evidence as stale rather than converting collector access failure into a negative product claim.
  • Treated broad page hash changes and navigation refreshes as collection noise unless the extracted first-party text supported a buyer-relevant cell.
  • Daily evidence record: 2026-11-06.