1. Toxic Workload Suite
RPC Cost Profiler plus dedicated SLO/SKUs for eth_getLogs, archive/backfill, websockets and stream/webhook alternatives.
Leverage 5/5Evidence Med-High
5/5
Toxic workload fragility
Generic RPC/CU pricing cracks around eth_getLogs, archive, websocket, polling and backfill workloads.
4/5
Single-provider fragility
Production apps increasingly need endpoint health, failover, method-level SLOs and RCA, not one opaque “fast” endpoint.
4/5
Bundling risk
L2/appchain/agent growth can be captured by RaaS, indexing/data and agent platforms before standalone RPC is chosen.
Three strategic moves
2. Failure-containment layer
Method-level status, private health API, diagnostics, incident RCA, synthetic monitoring and optional multi-provider routing.
Leverage 5/5Evidence Medium
3. Appchain/agent migration layer
New Chain RPC Launch Kit, sequencer/RPC divergence monitoring, archive/indexing bundles and agent-safe keys/limits.
Leverage 4/5Evidence Low-Med
What changed vs the old site
- The old site was a quick-scan competitor hub. It now needs to be a strategy lab around attack surfaces.
- Keep daily competitor monitoring, but route its evidence into three product/sales decisions: toxic workload monetization, failure containment, and appchain/agent migration.
- Add credibility labels: vendor pages are useful for positioning, not independent proof; GitHub operational artifacts are narrow but stronger evidence.
New strategy pages
Base 12-month GetBlock strategy
Operating plan based on churn, commodity perception, $350k new MRR/month target, ABM, customer success, and public proof.
Competitor-updated strategy
The base plan upgraded with competitor analysis from QuickNode, Alchemy, Infura, Chainstack, Ankr, Moralis, and the site’s attack-surface research.