1) Mission-critical production dApps that cannot accept Preview terms
- If contractual SLAs, mature escalation processes, and stability guarantees are required, a preview product poses risk.
2) Use cases requiring enhanced APIs beyond JSON-RPC
- If workloads need trace/debug endpoints, transfer/NFT indexing, or other data-platform features, specialist providers may be more appropriate.
3) Strict regulated environments without written compliance confirmation
- If it is necessary to prove Blockchain RPC is in-scope for specific audits/certifications and it is not publicly documented, adoption may be blocked.
4) High-throughput workloads needing clear paid scaling paths
- The current preview throughput (100 req/sec published) may be insufficient for high-volume consumer apps, and GA scaling terms are not yet transparent.
5) Organizations aiming to minimize centralization risk
- If organizational policy requires decentralization or avoidance of major cloud concentration, a hyperscaler-provided RPC endpoint may not align with those requirements.