GetBlock RPC competitor monitor — 2026-07-23

GetBlock RPC competitor monitor — 2026-07-23

Criterion of the day: Enterprise security/compliance proof: SOC 2, ISO, SSO, RBAC, SLAs, support channels (enterprise-security-compliance; query hint: "SOC 2 ISO SSO RBAC SLA support").

Summary

What really changed / new signals

1. QuickNode changed home, pricing, blog, and chains; enterprise stayed unchanged. The visible enterprise/security story is now very complete across public pages: SOC 1 Type 2, SOC 2 Type 2, ISO 27001 reports on request, SSO/SAML 2.0, RBAC/custom roles, committed SLAs, dedicated clusters, dedicated support and 24/7 on-call engineering. Sources: QuickNode enterprise, pricing, home.
2. Alchemy changed home and blog; pricing/enterprise were unchanged. It has strong enterprise security packaging: SSO, KMS, TLS, SOC II-certified cloud partners, 24/7 account/engineering access, 99.99% uptime, signed SLAs, RBAC, account activity logs and advanced security in pricing. Sources: Alchemy enterprise, pricing, home.
3. Chainstack pages were largely unchanged today, but its enterprise proof is broad and very explicit. Public text includes SOC 2 Type II on home, SOC2 certification on enterprise, SSO, MFA, granular permissions, TLS, KMS references, private networking, custom uptime SLAs, 24/7 priority support/direct engineer access, and SLA/support links. Sources: Chainstack home, enterprise, pricing.
4. Moralis pricing changed and remains clearly enterprise-data/compliance led. Captured pages repeatedly state SOC 2 Type II compliant APIs / Data Feeds and enterprise SLAs, with audit-grade data positioning. The extraction did not expose SSO/RBAC/private support-channel details today. Sources: Moralis enterprise, pricing, docs.
5. Infura and Ankr monitored pages were unchanged. Infura’s enterprise proof is mostly packaging around 24/7 engineering support, dedicated account team, committed SLAs, auto-scaling and enhanced support. Ankr’s enterprise proof is strongest on dedicated Slack/Telegram engineering support and bespoke infrastructure, but public captured text did not show SOC/ISO/SSO/RBAC. Sources: Infura pricing, Ankr enterprise.

Unchanged / no strong change

• Infura, Chainstack, Ankr: all monitored hashes unchanged vs previous run.
• QuickNode enterprise remained unchanged; today’s QuickNode changes were home/pricing/blog/chains and appear to include nav/campaign/content refresh plus security proof surfaced in pricing/home.
• Alchemy pricing and enterprise remained unchanged; only home/blog changed.
• Moralis pricing changed; other monitored Moralis pages unchanged.

Blocked / limited

• No generic web-search tool was available. Supplemental criterion check used local raw snapshots and direct HTTP fetches of known pages.
• Direct HTTP fetches from the runtime returned 403 for QuickNode/Alchemy/Chainstack/Moralis marketing pages, but pre-run snapshots for those pages are available and used as primary evidence.
• QuickNode /changelog returned 404; Alchemy docs_chains and /customer-stories returned 404.
• Public evidence for formal compliance depth varies: some vendors claim certification/reports; the monitor did not access trust centers or downloadable reports requiring login/NDA.

Competitor notes

QuickNode

Sources: home, pricing, enterprise, blog, chains.

• Snapshot status: home, pricing, blog, and chains changed; enterprise unchanged; /changelog still 404.
• Enterprise proof: Enterprise page states contractual uptime SLAs, SOC 1 Type 2 / SOC 2 Type 2 / ISO 27001 reports on request, named solutions architect, 24/7 on-call engineering, 99.99% uptime and service credits if missed.
• Security/compliance controls: Pricing page exposes SSO (SAML 2.0), SOC1 & SOC2 Type 2, RBAC / role-based access control, custom roles, dedicated support, enhanced analytics, custom RPS, dedicated clusters and committed SLAs.
• Public proof: Footer on home/pricing/chains says SOC 2 Type II Certified + ISO 27001. Enterprise page adds “security overview” and compliance reports available on request.
• Positioning implication: QuickNode is one of the strongest public enterprise-proof competitors: not just SLA/support claims, but security/compliance controls in plan comparison.

Alchemy

Sources: home, pricing, enterprise, blog.

• Snapshot status: home and blog changed; pricing and enterprise unchanged; docs chains and customer-stories URLs still 404.
• Enterprise proof: Enterprise page says enterprise-grade security with SSO and KMS for authentication, TLS for request privacy, and partnerships with SOC II-certified cloud providers. It also promises 24/7 access to account team and engineers and 99.99% uptime.
• Pricing/security controls: Pricing page has an “Advanced security, SLAs, and compliance controls” section: IP/domain allowlisting, Google OAuth, SAML SSO, account activity logs, RBAC, premium support packages, signed SLAs, advanced security and increased eth_getLogs() ranges for Enterprise.
• Support proof: Home page includes customer-proof-style quotes around exceptional support, near-perfect availability and 30k RPS peak/zero downtime.
• Gap/nuance: Captured public text cites SOC II-certified cloud providers, not Alchemy’s own SOC 2 certification; avoid claiming Alchemy itself is SOC 2 certified unless a trust-center source verifies it.

Infura

Sources: home, pricing, networks, blog, docs.

• Snapshot status: all monitored pages unchanged.
• Enterprise proof: Pricing page: Enterprise adds auto-scaling, enhanced support and SLA. FAQ says Enterprise is for 24/7 engineering support, dedicated account team, committed SLAs and substantial/custom throughput usage.
• Support packaging: Developer plan includes ticketed support; Team includes prioritized ticket support; Enterprise moves to enhanced support/SLA.
• Security/compliance evidence limit: Captured public pages did not surface SOC 2/ISO/SSO/RBAC. Infura may have deeper Consensys trust/security resources, but they were not verified in today’s monitored extraction.
• Positioning implication: Infura’s visible enterprise proof is weaker than QuickNode/Alchemy/Chainstack on compliance controls, but it still has credible enterprise support/SLA packaging.

Chainstack

Sources: home, pricing, protocols, enterprise, blog, docs.

• Snapshot status: all monitored pages unchanged vs last run.
• Enterprise proof: Home claims SOC 2 Type II, Security Scorecard and 99.99%+ uptime. Enterprise page states Chainstack is SOC2 certified and emphasizes secure/compliant/reliable infrastructure for enterprises.
• Security controls: Enterprise page lists SSO, MFA, granular permissions control, TLS for in-transit customer data/API calls, and KMS / cloud-native secret management references.
• SLA/support packaging: Pricing says Enterprise includes custom uptime SLAs, 24/7 priority support and direct engineer access; home says Enterprise is for bespoke SLAs, custom throughput and unlimited nodes.
• Additional enterprise differentiator: Private Networking is positioned as a way to remove extra layers between app and nodes, lower latency and improve response times for apps running on AWS.
• Positioning implication: Chainstack has the most detailed public security-control vocabulary after QuickNode/Alchemy, and adds private networking as both security and latency proof.

Ankr

Sources: home, RPC, enterprise, blog, docs.

• Snapshot status: all monitored pages unchanged.
• Enterprise proof: Enterprise page says customers can engage a fast-response engineering support team through a dedicated Slack or Telegram channel, customize throughput over 25,000 RPS, and design dedicated/bespoke infrastructure by request.
• Reliability proof: Home claims 99.99% uptime for Web3 API, 56 ms average response time and 70+ blockchains.
• Compliance/security evidence limit: Docs navigation includes “Trust & compliance,” but captured text did not verify SOC 2/ISO/SSO/RBAC or formal report availability. Treat formal compliance proof as limited today.
• Positioning implication: Ankr is credible on enterprise support-channel immediacy (Slack/Telegram) and bespoke infra, but less publicly complete on compliance controls than QuickNode/Alchemy/Chainstack/Moralis.

Moralis

Sources: home, pricing, chains, enterprise, blog, docs.

• Snapshot status: pricing changed; home/chains/enterprise/blog/docs unchanged.
• Enterprise proof: Home/pricing/chains/enterprise/blog repeatedly state Data Feeds are built for institutions/teams that need audit-grade data, are SOC 2 Type II compliant, and include enterprise SLAs.
• Positioning: Moralis leads with enterprise-grade onchain data, compliance/AI/next-gen finance use cases, Data APIs, Streams, Datashare, Data Feeds and RPC Nodes.
• Security/control evidence limit: Captured public text did not expose SSO, RBAC, MFA, dedicated Slack/Telegram or named engineering support. It may exist in sales materials, but not verified today.
• Positioning implication: Moralis is a strong compliance-proof competitor for data/API buyers, but weaker than infrastructure-first vendors on publicly visible access-control/support-channel detail.

GetBlock implications

Sales

1. Add a mandatory enterprise proof checklist to competitive discovery: SOC 2 Type II, ISO 27001, SSO/SAML, RBAC/custom roles, audit/activity logs, IP/domain allowlisting, TLS/KMS/secrets, private networking, SLA/service credits, named SA/TAM, 24/7 engineering and Slack/Telegram/Discord channels.
2. Build quick objection cards by competitor: QuickNode = SOC1/SOC2/ISO + SAML/RBAC + 24/7 engineering; Alchemy = SSO/KMS/TLS + RBAC/logs/signed SLAs; Chainstack = SOC2 + SSO/MFA/granular permissions/TLS/KMS/private networking; Moralis = SOC2 Type II + audit-grade data/enterprise SLAs; Ankr = dedicated Slack/Telegram support; Infura = committed SLA + 24/7 engineering/dedicated account team.
3. In enterprise deals, ask prospects whether compliance evidence must be public, report-on-request, NDA trust-center access, or contract-only. Competitors use all four patterns.

Product marketing

1. Create/refresh a GetBlock Enterprise security & compliance page with a table of verifiable controls: certifications, SSO, RBAC, audit logs, allowlists, TLS/KMS, SLA/service credits, support channels, dedicated/private nodes and report access process.
2. Add plan-table rows for enterprise controls if supported. QuickNode and Alchemy make SSO/RBAC/logs/SLA visible directly in pricing, which helps buyers self-qualify.
3. Publish a one-page PDF/security brief sales can send under NDA: uptime SLA terms, incident/support process, named roles, data handling, network security and compliance report availability.

Content

1. Publish SOC 2, ISO 27001 and SLAs for blockchain RPC: what enterprise buyers should ask with a vendor-neutral checklist and GetBlock CTA.
2. Publish RPC provider security checklist: SSO, RBAC, audit logs, allowlists and private networking to capture compliance/search intent.
3. Add comparison sections to GetBlock vs QuickNode / Alchemy / Chainstack pages focused on enterprise proof, not just chains and pricing.

Opportunities

• High priority: Ship a public GetBlock enterprise security/compliance matrix covering SOC/ISO status, SSO/SAML, RBAC, audit logs, allowlists, TLS/KMS, private networking, SLA/service credits, support channels and compliance-report process.
• High priority: Add enterprise-proof rows to pricing/plan comparison if product supports them; competitors are exposing SSO/RBAC/SLA controls in pricing pages.
• Medium priority: Create sales-ready competitor objection cards for QuickNode, Alchemy and Chainstack security/compliance claims.

Tomorrow seed

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