Site icon Chainstack

Best Sui RPC providers for production in 2026

Alex Usachev
Sui logo

Sui has emerged as a serious non-EVM Layer-1 in 2026. The launch of USDsui and CME cash-settled futures confirm it has crossed from developer experiment to institutional-grade network, with on-chain stablecoin transfers crossing $1 trillion cumulatively by early 2026.

The defining constraint for Sui builders in 2026 is a hard deadline: JSON-RPC public endpoints shut down the week of July 6 (testnet) and July 20 (mainnet), with full protocol-level deactivation on July 31, 2026, replaced by gRPC and GraphQL.

This guide covers the leading Sui RPC providers for production workloads in 2026, with specific focus on gRPC depth, object version retention, archive access, pricing predictability, and operational reliability under real traffic.

💡 Already using Chainstack? Jump straight to the Sui tooling docs for SDK examples across TypeScript, Go, Python, and cURL — or deploy your endpoint in minutes.

Why Sui RPC provider choice matters for production

In development, Sui’s public endpoints are sufficient. They’re free, easily accessible, and have no setup overhead. In production — where a gaming backend processes thousands of object mutations per second, where a DeFi protocol tracks checkpoint sequences for liquidation monitoring, or where an indexer backfills historical object states across months of chain history — the gap between providers becomes operationally decisive.

The API migration is the single most important constraint shaping provider selection in 2026. JSON-RPC, the legacy default that most Sui developers started with, has now been deprecated. Providers that hadn’t implemented gRPC in time forced migrations onto their customers at the worst possible moment — mid-growth, when infrastructure changes carry maximum risk. But beyond the protocol question, Sui’s object model means that standard EVM tooling assumptions simply don’t apply. There are no eth_getLogs-style calls, no account-based state lookups, no block-based event scans. Your provider needs to understand and support Sui’s actual data model — objects, checkpoints, Move events, dynamic fields — not just expose a URL that proxies requests to a Sui node.

The key factors separating production-grade Sui RPC providers from basic public options:

Sui RPC providers comparison table (2026)

The table below summarizes public positioning as of August 2026. Enterprise-only details are noted where applicable.

ProviderPricing modelFree tierDedicated nodesgRPC supportObject versions stored
ChainstackRequest-based (RU)3M RU/month, 25 RPSYes (paid plans)Yes (x-token auth required)51.3M (6.76%)
UniblockCompute-unit based, unified across chainsYes, free tierNot documented for SuiNot documented for SuiNot documented for Sui
OnFinalityResponse-unit based, unified tiersPublic 5 RPS; Free plan 40 RPSYes (Dedicated/Enterprise Nodes)Yes (gRPC primary; JSON-RPC legacy)Not benchmarked
DwellirFlat 1:1 (1 response = 1 credit)Free public endpoints (no SLA)Yes (dedicated clusters)Yes (auth required)14.0M (1.85%)
AnkrAPI credit200M credits/monthPremium private endpointsYes (bare-metal)Not benchmarked
AlchemyCU-based (method-weighted)30M CUs/monthNo standard dedicated tierYes (auth required) 7.4M (0.97%)
QuicknodeCredit-based (method-weighted)Trial only (30-day)Yes (dedicated clusters)Yes (auth required)13.5M (1.78%)

📖 What “object versions stored” means: Sui’s data model is object-centric — every time an object changes (a token transfer, an NFT update, a contract state mutation), a new version is created. Providers retain a limited window of these historical versions before pruning. More versions stored means your app can query deeper historical object state via sui_tryGetPastObject — critical for DeFi protocols replaying collateral history, indexers backfilling NFT provenance, and analytics pipelines auditing past on-chain state. All providers support full checkpoint and transaction history from genesis; object version retention is a separate, finer-grained capability.

How to choose a Sui RPC provider

1. API protocol support is the first filter

Unlike EVM chains where JSON-RPC remains stable indefinitely, Sui is mid-migration. JSON-RPC public endpoints begin shutting down in July 2026 — testnet the week of July 6, mainnet the week of July 20 — with full protocol-level deactivation July 31. Any provider without confirmed gRPC support creates a forced migration during your application’s growth phase. Before evaluating pricing, latency, or feature depth — confirm that the provider supports gRPC today and has a public roadmap for GraphQL. This single criterion eliminates providers from consideration for new production Sui deployments.

2. When dedicated infrastructure starts to matter

In a development or low-traffic context, shared RPC infrastructure is usually sufficient. The threshold for dedicated infrastructure arrives quickly on Sui, typically in three scenarios: gaming applications with concurrent object mutations during peak player sessions, where shared endpoint noise introduces jitter into user-visible transaction flows; DeFi bots and keeper networks that depend on consistent checkpoint polling latency to hit liquidation windows; and indexers running long checkpoint backfills where shared endpoint throttling corrupts the consistency of historical data pipelines. Once any of these apply, shared RPC becomes a liability even if average metrics still look acceptable.

3. Archive and historical checkpoint access

Sui’s full nodes retain only the last 14 epochs by default. Queries for older checkpoint data must route to archive infrastructure. For indexers, analytics pipelines, compliance tooling, and any workload that replays historical object states, your provider must explicitly support archive access — not just current chain state. Some providers handle this transparently through automatic routing from the same endpoint; others require separate archive endpoints, paid plan upgrades, or manual configuration. Know which category your provider falls into before you need it in production.

4. Latency consistency versus average benchmarks

Sui’s sub-second finality creates user experience expectations that average latency figures won’t reveal. What breaks real-time workloads — wallets displaying stale object state, games lagging on transaction confirmations, DeFi bots missing checkpoint windows — is p95 and p99 latency under sustained load, not median response times from a quiet endpoint. Sui isn’t currently one of the chains tracked on Chainstack’s public performance dashboard, so before committing to a provider, benchmark endpoint latency yourself against your actual Sui method mix under representative load — a simple curl loop or k6 script is enough. A provider that averages 40ms but spikes to 800ms under concurrent subscriptions is not production-ready, regardless of what its marketing page says.

5. Enterprise support for regulated and institutional workloads

Institutional DeFi protocols, gaming studios with large player bases, and infrastructure integrators all face the same reality: at some point, a performant endpoint isn’t enough. They need a contractual SLA, verifiable security certifications (SOC 2, ISO 27001), dedicated or isolated infrastructure options, multi-region resilience, and support quality that doesn’t require a public Discord thread to escalate a P1 incident. At this level, your Sui RPC provider becomes part of your operational risk model and needs to pass internal procurement reviews.

Choose the right Sui RPC provider by use case

For gaming and NFT applications

Sui has emerged as a serious gaming platform, driven by the object-centric Move model where in-game assets are native on-chain objects with direct ownership semantics — not entries in a contract mapping. This architectural choice makes Sui genuinely compelling for gaming: NFT transfers happen without global consensus, parallel execution handles concurrent player actions, and the object model maps naturally to game state. Projects like EVE Frontier migrating to Sui reflect real developer conviction, not ecosystem marketing. But this architecture also creates specific RPC demands: high-frequency object state reads, real-time Move event subscriptions for in-game actions, and transaction submission pipelines that must stay responsive during concurrent player sessions without introducing visible lag.

For gaming workloads, the critical provider attributes are gRPC support for streaming, WebSocket connection stability under sustained concurrent subscriptions, and consistent low latency during peak periods. Jitter or connection drops in a game loop are immediately user-visible failures that erode retention. Chainstack offers predictable request-unit pricing and a direct upgrade path to dedicated Sui infrastructure — practical for studios that need to model infrastructure costs as player counts and session concurrency scale. Quicknode’s gRPC depth and globally distributed infrastructure make it a strong alternative for gaming apps where archive access and the broadest API surface matter. Dwellir’s 1:1 pricing model eliminates billing surprises that are particularly costly for gaming workloads with unpredictable method mixes.

Explore gaming infrastructure on Chainstack →

For DeFi protocols and stablecoin infrastructure

DeFi on Sui has matured significantly in 2026. DeepBook provides institutional-grade order book infrastructure, Suilend has become a cornerstone lending platform, and the launch of USDsui creates new stablecoin liquidity and payment rails on the network. Each of these protocols creates demanding RPC patterns: real-time object state reads for price feeds and collateral tracking, checkpoint sequence monitoring for liquidation triggers, Move event indexing for on-chain activity feeds, historical backfill for analytics and audit trails, and transaction submission pipelines that must stay fast during market volatility spikes.

For DeFi workloads, gRPC is not optional — it’s the only protocol with a reliable future on Sui after July 2026, and providers without it will force migrations during exactly the windows when your protocol is most stressed and your team has the least capacity for infrastructure changes. Chainstack has the clearest upgrade path from shared RPC to dedicated Sui infrastructure, with transparent request-unit pricing that’s easier to model than method-weighted credits when your workload mixes archive queries, checkpoint reads, and real-time subscriptions in variable proportions. Quicknode’s archive auto-routing via a single gRPC endpoint removes the friction of managing separate endpoints — a material advantage for analytics-heavy DeFi stacks. Alchemy brings strong developer tooling and a generous free tier, well-suited to teams with predictable, well-characterized method mixes.

Explore dedicated Sui node infrastructure on Chainstack →

For indexers, analytics, and enterprise deployments

Indexers and analytics pipelines stress a Sui RPC provider differently from transactional workloads. The concern here is not single-request latency — it’s whether the provider can sustain historical checkpoint reads across months of data, run long-duration object backfills without throttling, and deliver continuous Move event streams without gaps that corrupt downstream data pipelines. Enterprise deployments add compliance and SLA requirements: SOC 2 certifications for vendor procurement, contractual uptime guarantees for regulated products, and dedicated infrastructure so that a noisy neighbor on shared infrastructure can’t introduce data inconsistency into your indexing jobs.

For this workload category, the realistic production options narrow to Chainstack and Quicknode — both support gRPC with archive access and hold enterprise-grade security certifications. For enterprise deployments specifically, Chainstack’s SOC 2 Type II and ISO 27001, dedicated Sui node options, and transparent request-unit pricing provide a compliance-ready path that doesn’t require complex procurement negotiation just to get meaningful throughput. Quicknode’s dual SOC 2 + ISO 27001 certifications and archive auto-routing make it the strongest option for organizations where both compliance breadth and indexing infrastructure depth are required simultaneously.

Explore enterprise blockchain infrastructure on Chainstack →

Sui RPC providers: breakdown by provider

Chainstack

Chainstack supports Sui with Global Nodes offering HTTP, WebSocket, and gRPC access — covering the full protocol stack required for production applications in 2026. Per Chainstack’s own Sui gRPC developer guide, checkpoint depth on gRPC currently reaches back roughly 64.8 million checkpoints from the chain tip. Chainstack gRPC access requires authentication via an x-token header, passed with every call. The Sui tooling documentation covers TypeScript, Python, Go, Rust, and cURL with full gRPC examples.

Pricing & throughput: Developer plan is free (3M RU/month, 25 RPS). Growth: $49/month (20M RU, 250 RPS). Pro: $199/month (80M RU, 400 RPS). Business: $499/month (200M RU, 600 RPS). Enterprise: $990/month (400M RU, unlimited RPS). Overage rates scale down from $20/1M RU on Developer to $5/1M RU on Enterprise. The Unlimited Node add-on converts any node to flat-fee unlimited requests within a fixed RPS tier (25–500 RPS), removing per-request billing entirely. Dedicated Nodes are available for teams that need isolated, guaranteed throughput.

Limitations: Chainstack’s Sui-specific marketplace add-ons and streaming product surface are narrower than Quicknode’s. Teams needing a fully integrated AI agent data layer or advanced analytics dashboards alongside RPC may find Quicknode’s platform depth more compelling. GraphQL for Sui is not yet supported — it is an open feature request, not a shipped capability.

Fit by workload:

Uniblock

Uniblock is a unified RPC aggregation platform rather than a node operator — it routes requests to upstream providers behind a single API and a single invoice across 300+ chains, including Sui. For teams juggling multiple chains, Uniblock’s value is consolidation: one API shape and one bill instead of separate integrations per provider, plus its higher-level Unified APIs (token, NFT, market data) layered on top of raw RPC.

Limitations: Uniblock is not a Sui-specific infrastructure provider — it aggregates upstream providers rather than running dedicated Sui nodes, and Sui-specific details (gRPC support, archive depth, dedicated node options) are not clearly documented on its own site. Confirm current Sui coverage directly before committing to a production workload.

Fit by workload:

OnFinality

OnFinality runs production Sui Mainnet infrastructure with gRPC as the primary API (querying checkpoints, transactions, objects, and balances, with streaming support) and legacy JSON-RPC maintained for existing applications during migration. Plans run from a public endpoint (5 RPS) and a Free plan (40 RPS with usage insights) up to a Growth plan (500 RPS, priority support), with Dedicated and Enterprise Nodes available for high-performance, scalable deployments.

Limitations: No SLA published on the free/public tiers; Sui-specific archive retention depth wasn’t independently confirmed and should be checked directly before a production commitment.

Fit by workload:

Dwellir

Dwellir operates Sui infrastructure on bare-metal servers with a 1:1 pricing model — every method costs the same credit regardless of complexity. Benchmark testing shows 14.0 million object versions retained (1.85% coverage, ~1 epoch) and gRPC checkpoint depth of 4.9 million — comparable to Quicknode, but roughly 13x shallower than Chainstack. Dwellir’s gRPC runs on port 443 and requires authentication. All standard Sui RPC methods are supported. The platform covers 150+ networks under a single API key, making it practical for multi-chain teams adding Sui without managing separate billing.

Pricing & throughput: Flat 1:1 pricing (1 response = 1 credit, no method multipliers). Paid tiers from $49/month. Free public endpoints available without SLA. Dedicated clusters available with direct technical support.

Limitations: Security certifications (SOC 2, ISO 27001) are not prominently published, requiring direct engagement for enterprise procurement. No public SLA for standard plans. GraphQL RPC for Sui is not documented. Object version history at 14.0M is 3.7x shallower than Chainstack.

Fit by workload:

Ankr

Ankr operates Sui infrastructure on bare-metal servers with private fiber networking — a differentiated architecture compared to cloud-virtualized approaches, aimed at reducing the abstraction overhead between your requests and the underlying Sui node. The platform handles over 8 billion daily requests across its multi-chain network, supports gRPC for Sui as part of the new data stack endorsed by the Sui Foundation, and provides archive access on Premium tier. SOC 2 Type 2 certification was achieved in 2025, making Ankr a viable option for organizations with baseline compliance requirements. The 200M free API credits/month after sign-in is the most generous free tier in this comparison, giving teams substantial runway for pre-production development and testing without committing to a paid plan.

Pricing & throughput: Freemium model with 200M API credits/month after account creation. Premium and Enterprise tiers available for higher throughput and dedicated options. The effective per-request cost on mid-tier plans can run approximately $20/1M actual requests — a figure that requires careful modeling at production volume before committing, particularly for workloads that lean heavily on archive access.

Limitations: Dedicated Sui node offerings are less clearly positioned in Ankr’s public materials than Chainstack or Quicknode. For teams needing a formal dedicated Sui node with a defined SLA, the upgrade path requires direct engagement with Ankr’s sales team rather than self-service. At production scale, the effective per-request cost also requires careful modeling against the headline credit figures, as the advertised volume can be misleading for workloads with heavier Sui methods.

Fit by workload:

Alchemy

Alchemy supports Sui with HTTP, WebSocket, and full gRPC access — all 7 services (LedgerService, StateService, MovePackageService, NameService, SubscriptionService, TransactionExecutionService, SignatureVerificationService) are documented and available. The free tier — 30M CUs/month (~1.2M Sui calls at average consumption) — is the most generous in this comparison by raw volume. The platform brings its established developer tooling to Sui: analytics dashboards, WebSocket subscriptions, and the familiar SDK experience for teams already using Alchemy on EVM chains. The key gap from the March 2026 benchmark: Alchemy retains only 7.4 million object versions (0.97% coverage) — the lowest in the comparison, 6.9x less than Chainstack — and gRPC checkpoint depth was not measured.

Pricing & throughput: CU-based pricing (method-weighted). Free tier: 30M CUs/month. PAYG and higher tiers available. No standard dedicated node tier for Sui — enterprise infrastructure requires direct engagement.

Limitations: At 7.4M object versions retained, Alchemy has the shallowest historical object state coverage tested — a real constraint for DeFi protocols and indexers that depend on historical object queries. No GraphQL support for Sui. No dedicated node tier means limited isolation options for latency-sensitive workloads.

Fit by workload:

Quicknode

Quicknode offers a comprehensive Sui API stack with gRPC, GraphQL (beta), and WebSocket support. Benchmark testing shows 13.5 million object versions retained (1.78% coverage, ~1 epoch) and gRPC checkpoint depth of 4.9 million — solid, but roughly 13x shallower than Chainstack. Unlike Chainstack, Quicknode’s gRPC requires authentication credentials. All standard RPC methods are supported, and the platform explicitly documents gRPC in Go, Python, TypeScript, and grpcurl. For indexers, Quicknode’s archive auto-routing is convenient — queries for data older than 14 epochs route automatically to archive nodes without client-side configuration changes.

Pricing & throughput: Credit-based pricing where different methods consume credits at different rates. Build tier starts at $49/month (80M credits, up to 50 RPS). No permanent free plan — only a 30-day limited trial. The credit model requires method-mix modeling to forecast costs for mixed Sui workloads, adding overhead compared to flat or request-unit pricing.

Limitations: No permanent free tier makes early-stage development more costly. Credit-weighted billing is unpredictable for workloads with variable method mixes. Object version history at 13.5M (1.78%) is 3.8x shallower than Chainstack — relevant for DeFi protocols and indexers needing deep historical object state.

Fit by workload:

Getting started with Sui on Chainstack

  1. Log in to your Chainstack account or create a free account
  2. Create a new project or select an existing one
  3. Choose Sui Mainnet or Sui Testnet
  4. Deploy a Sui RPC node on Chainstack — Global Node for geo-balanced access or Dedicated Node for isolated, SLA-backed infrastructure
  5. Open Access/Credentials and copy your HTTP, WebSocket, or gRPC endpoint

Quick connectivity check — get the latest Sui checkpoint:

curl --request POST \
  --url YOUR_CHAINSTACK_ENDPOINT \
  --header 'Content-Type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sui_getLatestCheckpointSequenceNumber",
    "params": []
  }'

TypeScript (using @mysten/sui):

import { SuiJsonRpcClient } from '@mysten/sui/jsonRpc';

const client = new SuiJsonRpcClient({ url: 'YOUR_CHAINSTACK_ENDPOINT' });
const checkpoint = await client.getLatestCheckpointSequenceNumber();
console.log('Latest checkpoint:', checkpoint);

For gRPC access, Chainstack Sui mainnet nodes are reachable at sui-mainnet.core.chainstack.com:443. Your gRPC endpoint and x-token credentials appear in the console under your node’s Access and credentials panel. The Sui tooling documentation includes full gRPC examples in Go, Rust, and Python alongside the TypeScript and cURL examples above.

🤖 You can also access Chainstack Sui RPC directly from Claude, Cursor, Codex, Windsurf, Gemini CLI, GitHub Copilot, Antigravity, Claude.ai, or ChatGPT using Chainstack MCP. See the Chainstack Agents page for the fuller agent stack.

⚠️ Migration note: If you haven’t already, move to gRPC now — the JSON-RPC deadline has passed. The @mysten/sui SDK, Rust SDK (sui-sdk), Python pysui, and Go SDK all support gRPC, and the transition from JSON-RPC is straightforward with your existing codebase once your provider endpoint is configured.

Conclusion

All seven providers in this comparison support Sui in some form, though gRPC-specific depth varies — the July 31, 2026 JSON-RPC deadline is no longer the filter. The differentiation is now benchmark depth: object version retention, gRPC checkpoint history, GraphQL availability, and pricing predictability under mixed workloads.

Provider recommendation by use case:

Deploy your Sui RPC endpoint on Chainstack →

FAQ

What is the difference between gRPC and JSON-RPC on Sui?

gRPC is Sui’s future API — binary protocol, lower latency, native streaming. JSON-RPC public endpoints shut down in stages — testnet the week of July 6, mainnet the week of July 20 — with full protocol-level deactivation July 31, 2026. Any app still on JSON-RPC after that date stops working.

Which Sui RPC provider has the best free tier?

Alchemy gives 30M CUs/month (~1.2M Sui calls). Ankr gives 200M API credits/month. Chainstack’s Developer plan (3M RU/month, 25 RPS) is smaller but includes confirmed gRPC access. Quicknode has no permanent free plan — only a 30-day trial.

How do I migrate from JSON-RPC to gRPC on Sui?

Confirm your provider supports gRPC, then update your SDK (@mysten/sui for TypeScript, sui-sdk for Rust, pysui for Python). Point it at your provider’s gRPC endpoint and port, validate with a checkpoint query, and migrate call sites. Chainstack, Quicknode, Dwellir, and Ankr all have per-language migration guides.

Does average latency matter when comparing Sui RPC providers?

No — p95 and p99 latency under load matters. A provider averaging 40ms that spikes to 800ms under concurrent subscriptions breaks wallets, games, and DeFi bots. Always benchmark against your actual method mix, not a quiet single-request test.

Which Sui RPC providers are enterprise-ready?

Chainstack (SOC 2 Type II and ISO 27001, dedicated nodes, 99.99%+ SLA) and Quicknode (SOC 2 Type II + ISO 27001, dedicated clusters, formal 99.99% SLA) are the strongest. Alchemy holds SOC 2 Type II. Ankr achieved SOC 2 Type 2 in 2025. Dwellir requires direct validation.

Is Chainstack’s request-unit pricing more predictable than CU-based models?

Yes, for mixed Sui workloads. Chainstack charges 1 RU per request regardless of method — checkpoint reads, archive calls, and event subscriptions all cost the same. CU models (Alchemy, Quicknode) weight heavier methods higher, making cost forecasting harder when your method mix varies.

Additional resources

Exit mobile version