Question 1

What's the difference between Core RPC API and Dedicated Clusters?

Accepted Answer

Core RPC API is shared, multi-tenant access to full and archive nodes across 80+ chains, billed by usage and ready the moment you create an endpoint. Dedicated Clusters are private, single-tenant nodes with no shared rate limits, predictable latency, and burst capacity to 50K RPS. Start on Core RPC API, then move to Dedicated Clusters when shared infrastructure stops keeping up.

Question 2

What infrastructure does Quicknode offer for Solana?

Accepted Answer

For Solana, Quicknode runs Solana gRPC, which streams validator data, including mempool transactions and account updates, before standard RPC propagation. Pair it with co-located Dedicated Clusters and Jito integration for MEV-protected transaction landing. It is the low-latency path Solana trading teams and bots run production on, available on your existing Quicknode endpoint.

Question 3

What infrastructure does Quicknode offer for Hyperliquid?

Accepted Answer

For Hyperliquid, Quicknode provides HyperCore data access over Streams, gRPC, JSON-RPC, and WebSocket, plus low-latency HyperEVM RPC and dedicated endpoints. Launched in January 2026, it gives HyperEVM teams one data and execution layer instead of stitching providers together. Use Core RPC API for HyperEVM calls and Dedicated Clusters when you need isolated performance.

Question 4

Which chains does Quicknode support?

Accepted Answer

Quicknode Core RPC API covers 80+ chains from one endpoint and one API key, including Ethereum, Solana, Base, Bitcoin, and Hyperliquid HyperEVM, across mainnets and testnets. Dedicated Clusters, IPFS, and Validator as a Service run on the same account. Check the docs for the current per-chain list, since new chains ship regularly.

Question 5

Do I need a separate account for each infrastructure product?

Accepted Answer

No. Every infrastructure product runs on one Quicknode account with one API key and one credit pool. Core RPC API, Dedicated Clusters, IPFS, and Validator as a Service are available on your existing endpoint, so you can add a layer from the dashboard without a new contract or a separate integration. Billing and usage stay in one place.

Question 6

How is infrastructure billed?

Accepted Answer

Quicknode infrastructure is usage-based, metered in API credits from one shared pool. Core RPC API charges credits per request by method and chain. Dedicated Clusters are priced for reserved single-tenant capacity, and Validator as a Service is priced per validator. Start free on your existing account and scale to dedicated infrastructure when you need it. See pricing for the full breakdown.

Question 7

What compliance certifications does Quicknode hold?

Accepted Answer

Quicknode holds SOC 1, SOC 2 Type II, and ISO 27001 certifications. Dedicated Clusters add custom SLAs, custom rate limits, and custom billing, with a support team that answers. It is the infrastructure procurement teams approve, built so security and compliance reviews clear without custom engineering on your side.

Question 8

Can I run validators through Quicknode?

Accepted Answer

Yes. Validator as a Service runs validators for you across major proof-of-stake networks, with key management, monitoring, and uptime SLAs. SOC 2 Type II and ISO 27001 are covered, so you earn staking rewards without the on-call rotation or the slashing risk. It is institutional staking infrastructure, managed end-to-end.

這是所有其他事物所依賴的基礎架構。

每條鏈。每項工具。
一個平台。

通往 Solana

全端開發 Hyperliquid 基礎架構

大多數 RPC 提供者止步於我們起步之處。

所有內容，都匯集在一個帳戶中。
隨時為您服務。

常見問題

想掌握最新動態嗎？

開發者工具

文件與指南

Core RPC API

專用Clusters

驗證器即服務

IPFS