GetBlock RPC competitor monitor — 2026-07-22

Source: /root/getblock-rpc-competitive-research/monitoring/daily/2026-07-22.md

GetBlock RPC competitor monitor — 2026-07-22

Criterion of the day: Dedicated node customization: regions, methods, binaries, archive/debug, private networking (dedicated-node-customization; query hint: "dedicated nodes custom regions archive debug private networking").

Summary

What really changed / new signals

QuickNode changed most monitored pages (home, pricing, enterprise, blog, chains). The visible delta is mostly nav/campaign refresh, but the nav continues to expose Dedicated Clusters / Dedicated backends as a first-class infrastructure product. Source: [QuickNode home](https://www.quicknode.com/), [pricing](https://www.quicknode.com/pricing), [enterprise](https://www.quicknode.com/enterprise).
Alchemy has the clearest newly verified dedicated-cluster customization page for today’s criterion. [Dedicated Clusters](https://www.alchemy.com/dedicated-clusters) says dedicated RPC + WebSocket infrastructure is built to specs; use cases include custom tracers/binaries, deployment in specific regions beyond standard footprint, single-tenant isolation, custom hardware configuration, hybrid Dedicated + Shared setup, and failover to Alchemy RPC.
Chainstack changed all public marketing pages in the monitored set except docs (home, pricing, protocols, enterprise, blog). It is pushing a broad control story: Managed Dedicated Nodes, new Self-Hosted Nodes, Archive Data, Yellowstone/gRPC and “any infrastructure” deployment. Source: [Chainstack home](https://chainstack.com/), [Dedicated Nodes](https://chainstack.com/dedicated-nodes/), [Self-Hosted](https://chainstack.com/self-hosted/), [Archive Data](https://chainstack.com/archive-data/).
Infura pages were unchanged, but pricing remains relevant to the criterion: Free/Core includes full archive data; Developer ($50/mo) adds Debug / Trace API and Settings Override; Enterprise adds auto-scaling, enhanced support and SLA. Source: [Infura pricing](https://www.infura.io/pricing).
Ankr pages were unchanged, but enterprise copy explicitly supports customization: low-latency geo-distribution across 24 metros, custom throughput over 25,000 RPS, dedicated Slack/Telegram support, and “dedicated and bespoke infrastructure by request.” Source: [Ankr enterprise](https://www.ankr.com/enterprise/).
Moralis pages were unchanged and remain data-platform first: RPC Nodes are in navigation, but captured pages emphasize Data APIs, Streams, Datashare, Data Feeds, SOC 2 Type II and enterprise SLAs more than dedicated-node customization.

Unchanged / no strong change

Alchemy core home, pricing, enterprise hashes were unchanged; blog changed only as part of recent content rotation. Dedicated Cluster page was supplemental, not in the pre-run monitored set.
Infura, Ankr, Moralis monitored pages were unchanged vs last run.
No reliable public evidence found today for competitor changes to actual price levels beyond previously captured plan/package terms.

Blocked / limited

No generic web-search tool was available. Supplemental checks used direct HTTP fetches of known/likely pages.
QuickNode /changelog returned 404; guessed https://www.quicknode.com/dedicated-clusters returned 404, while the product remains visible in nav.
Alchemy blog URL guessed for “introducing dedicated clusters” returned 404; public product page resolved.
Moralis https://moralis.com/rpc-nodes/ returned 403; Moralis RPC detail is limited to monitored pages and docs overview.
Alchemy docs_chains and /customer-stories returned 404 in pre-run.

Competitor notes

QuickNode

Sources: [home](https://www.quicknode.com/), [pricing](https://www.quicknode.com/pricing), [enterprise](https://www.quicknode.com/enterprise), [blog](https://www.quicknode.com/blog), [chains](https://www.quicknode.com/chains), [Dedicated Nodes blog](https://www.quicknode.com/blog/dedicated-nodes).

Positioning/features delta: Multiple monitored pages changed. Product nav continues to classify Dedicated Clusters under Infrastructure as “Dedicated backends,” alongside Core RPC API and Validator as a Service.
Dedicated/customization signal: Public monitored text confirms the dedicated product category, but not detailed customization levers. A direct /dedicated-clusters product URL returned 404; the older dedicated-nodes blog resolves but extraction mainly surfaced site navigation. Treat detailed QuickNode customization evidence as limited today.
Enterprise packaging: Enterprise page unchanged in substance: contractual 99.99% uptime SLAs, high-throughput data access, “no rate limits on supported methods,” volume discounts, compliance reports on request, named solutions architect and 24/7 on-call engineering.
Archive/debug/private networking: Not enough public extracted evidence today to claim custom binaries/private networking/debug packages on dedicated nodes.
Assessment: QuickNode is visibly packaging dedicated backends, but today’s public extraction gives less detail than Alchemy/Chainstack. Sales should ask prospects exactly which QuickNode dedicated levers were offered: region, client binary, trace/debug, archive, isolation, failover and network path.

Alchemy

Sources: [home](https://www.alchemy.com/), [pricing](https://www.alchemy.com/pricing), [enterprise](https://www.alchemy.com/enterprise), [blog](https://www.alchemy.com/blog), [Dedicated Clusters](https://www.alchemy.com/dedicated-clusters).

Dedicated-cluster positioning: “Dedicated clusters, customized your way”; dedicated RPC and WebSocket infrastructure “built to your specs” and secured to enterprise standards.
Customization levers found: custom tracers and binaries; deploy in any/specific region beyond standard footprint; single-tenant isolation with no shared traffic/compute; custom hardware configuration benchmarked against traffic patterns; fully managed provisioning, upgrades, monitoring, redundancy and failover; hybrid Dedicated + Shared setup; optional automatic failover to Alchemy RPC if traffic exceeds cluster capacity.
Use cases named: security/forensics with simulation and debug_trace-heavy workloads; financial institutions with compliance/audit needs; Trading/DeFi deployments near sequencers/validators; oracles; analytics/indexing/backfills with unlimited getLogs ranges; exchanges/in-house operators replacing self-managed nodes.
Pricing/packaging: Public pricing page unchanged: Free 25 RPS/30M CU monthly; PAYG from 300 RPS; Enterprise from 1000 RPS. Dedicated Clusters appear sales-led rather than self-serve priced.
Assessment: Alchemy is the strongest public competitor for the exact criterion today. Its dedicated-cluster page directly names the buyer objections GetBlock must answer: custom binaries/tracers, regional compliance, single-tenant isolation, hardware sizing, debug_trace, getLogs, failover and hybrid shared/dedicated operations.

Infura

Sources: [home](https://www.infura.io/), [pricing](https://www.infura.io/pricing), [networks](https://www.infura.io/networks), [blog](https://www.infura.io/blog), [docs](https://docs.infura.io/).

Snapshot status: All monitored pages unchanged vs last run.
Relevant package signals: Pricing page explicitly packages Full archive data in Core/Free, Debug / Trace API and Settings Override in Developer ($50/mo), higher throughput/prioritized support in Team ($225/mo), and Auto-scaling / Enhanced Support / SLA in Enterprise.
Customization/private infra: Captured public pages emphasize managed API access and plan-based features, not custom regions, binaries, single-tenant dedicated nodes or private networking. Enterprise customization may exist via sales, but it was not visible in today’s extraction.
Assessment: Infura’s visible wedge for this criterion is archive + debug/trace as packaged features, not bespoke dedicated-node control. GetBlock can contrast dedicated-node flexibility if supported.

Chainstack

Positioning delta: Home/pricing/protocols/enterprise/blog all changed. New/current nav heavily exposes Managed Dedicated Nodes, Self-Hosted Nodes, Archive Data, gRPC Data Streaming, Ultra-fast Transactions, Unlimited Node and use cases such as Trading & MEV.
Dedicated/customization signal: Managed Dedicated Nodes are described as fully managed RPC nodes with flexible deployment and customization options. Trader Nodes adds custom region/cloud-provider selection for latency-sensitive trading.
Self-hosted control signal: Self-Hosted page says user-managed nodes run on infrastructure customers control, with automated deployment, self-healing and lifecycle management; supported deployment targets include cloud VPS, virtual machines, bare-metal servers and local environments. This is a strong “your infrastructure, your data” counter to hosted-only providers.
Archive/debug/method controls: Archive Data page explains full archive nodes for historical state and debugging; it mentions Solana archive nodes, Ethereum archive nodes, node-client matching, and configuration for heavy eth_call, larger eth_getLogs and eth_newFilter ranges.
Assessment: Chainstack is the broadest control-oriented competitor: managed dedicated, self-hosted, archive, custom node config and trader-region packaging. GetBlock should decide whether to counter with fully managed simplicity, dedicated flexibility, or a hybrid/self-hosted roadmap.

Ankr

Sources: [home](https://www.ankr.com/), [RPC](https://www.ankr.com/rpc/), [enterprise](https://www.ankr.com/enterprise/), [blog](https://www.ankr.com/blog/), [docs](https://www.ankr.com/docs/).

Snapshot status: All monitored pages unchanged vs last run.
Customization signal: Enterprise page says customers can access 30+ blockchains, tap low-latency geo-distribution across 24 metros, customize throughput requirements above 25,000 RPS, engage dedicated Slack/Telegram engineering support, and design dedicated and bespoke infrastructure by request.
Related infrastructure: Home/enterprise also point to Scaling Services / AppChains: dedicated blockchain solutions with customized chain launch, higher transaction speed, scalability and enterprise-grade infrastructure.
Archive/debug/private networking: No strong public extracted evidence today for custom binaries, trace/debug packages or private networking in Ankr RPC dedicated infra.
Assessment: Ankr competes on enterprise “bespoke by request” and scale/throughput rather than transparent menu-style node customization.

Moralis

Sources: [home](https://moralis.com/), [pricing](https://moralis.com/pricing/), [chains](https://moralis.com/chains/), [enterprise](https://moralis.com/enterprise/), [blog](https://moralis.com/blog/), [docs](https://docs.moralis.com/).

Snapshot status: All monitored pages unchanged vs last run.
Positioning: Enterprise-grade onchain data platform: Wallet API, Token API, NFT API, Price API, DeFi API, Blockchain API, Streams, Datashare, Data Feeds, RPC Nodes and Cortex API.
Customization signal: Captured pages emphasize enterprise data delivery, 100% data delivery guarantee for Streams, full historical coverage, audit-grade data, SOC 2 Type II and enterprise SLAs. They do not visibly sell custom dedicated-node regions, binaries, archive/debug or private networking in the captured text.
Limit: Direct moralis.com/rpc-nodes/ fetch returned 403, so RPC-node product detail could not be verified today.
Assessment: Moralis is less of a direct dedicated-node customization threat than Alchemy/Chainstack; it is a threat for enterprise data feeds and managed historical/enriched data.

GetBlock implications

Sales

Build a dedicated-node customization discovery checklist for competitive calls: required regions, cloud/provider, single-tenant isolation, private networking/VPC/peering, node client/binary, custom tracers, debug/trace, archive/full-history, getLogs ranges, heavy eth_call, WebSocket/gRPC, failover, SLA and support channel.
Prepare competitor objection cards: Alchemy = custom tracers/binaries + region + isolation + hardware + failover; Chainstack = managed dedicated + self-hosted + archive/config controls; Infura = packaged archive/debug; Ankr = bespoke infra + 24 metros + 25k RPS.
If GetBlock supports dedicated/private nodes today, make reps ask for exact competitor quotes and translate them into GetBlock equivalents rather than generic “dedicated node” language.

Product marketing

Create or refresh a GetBlock page for Dedicated RPC nodes / private nodes with a table of customization levers: regions, protocols, archive mode, debug/trace, WebSocket/gRPC, client/version, request-limit policy, support/SLA and security/networking.
Add public proof for archive/debug: supported chains, method availability (debug_trace*, trace_*, eth_getLogs ranges), archive-node definitions and ideal use cases (indexers, tax/compliance, analytics, simulations, trading).
If private networking or single-tenant isolation is supported, say it plainly; if not, define a roadmap/enterprise FAQ because Alchemy is already using this language.

Content

Publish Dedicated blockchain nodes: shared vs dedicated vs self-hosted RPC comparing Alchemy Dedicated Clusters, Chainstack Dedicated/Self-Hosted, Infura archive/debug packages and GetBlock.
Publish Archive nodes vs full nodes: when you need historical state, debug/trace and getLogs at scale with GetBlock product tie-ins.
Create SEO comparison pages for GetBlock vs Alchemy Dedicated Clusters and GetBlock vs Chainstack Dedicated Nodes focused on concrete customization dimensions, not generic “reliable RPC.”

Opportunities

High priority: Ship a dedicated-node customization matrix for GetBlock public site and sales: regions, archive/debug, allowed methods, binary/client/version, single-tenant/private networking, failover and SLA.
High priority: Build comparison/objection assets specifically against Alchemy Dedicated Clusters and Chainstack Dedicated/Self-Hosted Nodes.
Medium priority: Add archive/debug method documentation and content around debug_trace, trace_*, eth_getLogs ranges and historical state use cases.

Tomorrow seed

state.json shows used criteria ai-agent-tooling, solana-trading-latency, and dedicated-node-customization, but no upcoming criterion queue. Next criterion is not inferable from current state; tomorrow's pre-run JSON should supply it.