How to get a Sui RPC endpoint in 2026

Created Feb 27, 2026 Updated Feb 27, 2026

Alex Usachev

TL;DR

Sui’s Move-based object model and parallel execution architecture require RPC infrastructure optimized for object queries and checkpoint reads—not just account/log patterns from EVM chains.

A Sui RPC endpoint is the core infrastructure layer your app uses to read object state, track checkpoints, and submit transactions on Sui. This guide explains how to choose the right Sui RPC endpoint in 2026, compare public and private options, and move to production-ready infrastructure with reliable performance, archive access, and API roadmap compatibility.

What is a Sui RPC endpoint?

A Sui RPC endpoint is your app’s gateway to Sui’s Move-based blockchain. Unlike EVM chains where you query accounts and logs, Sui is object-centric: you query owned/shared objects, track checkpoint sequences, and submit transactions that reference object versions.

This fundamental difference means:

API evolution differs (Sui is actively moving beyond JSON-RPC)
Query patterns differ (object IDs, not account addresses)
Historical data needs differ (checkpoint history, not just block logs)

How Sui RPC differs from EVM RPC

What	Sui	Typical EVM
Data Model	Object-centric (Move)	Account-based
Consensus	Narwhal-Tusk DAG (parallel)	Sequential (Proof of Stake/Work)
Primary Queries	Objects + checkpoints	Accounts + logs/events
Historical Needs	Checkpoint/object history	Block/log history
API Status (2026)	Migrating from JSON-RPC	JSON-RPC stable
Indexing	Sui-specific strategy needed	Many off-the-shelf options

This is exactly why provider selection for Sui should include API roadmap and indexing fit, not just raw RPS.

Sui RPC endpoint options

Choosing the right endpoint is mostly a reliability decision. You’re balancing convenience, cost, and operational risk.

Public vs Private Sui RPC endpoints

Common public endpoints:

Mainnet: https://fullnode.mainnet.sui.io:443
Testnet: https://fullnode.testnet.sui.io:443
Devnet: https://fullnode.devnet.sui.io:443

Feature	Public RPC	Private RPC (Chainstack)
Access	Free and open	Restricted access
Resources	Shared infrastructure	Dedicated resources
Performance	Variable, rate-limited	Stable, high throughput
Object queries	May timeout under load	Consistent response times
Checkpoint access	Limited historical depth	Full archive available
Best use case	Development & testing	Production workloads

Public RPC endpoints are useful for testing and experimentation, but treat them as shared community resources.

For production workloads, use an infrastructure RPC provider with clearer performance and availability guarantees.

Full node vs Archive access on Sui

Your data requirements should drive this decision.

Full node access	Archive-capable data access
Current state reads	Deep historical analysis
Standard wallet/dapp interactions	Explorer-like products
Typical transaction workflows	Compliance/reporting use cases
	Large historical backfills

If your product depends on long-range historical queries, validate archive availability before launch.

HTTPS vs WebSocket

Transport choice impacts system behavior, especially at scale.

HTTPS	WebSocket
Request/response model	Better for event-heavy or real-time workflows
Simple operationally	Can reduce overhead for high-frequency interactions
Good for most standard backend reads/writes	Requires stronger reconnect/error handling patterns

In practice, many teams use HTTPS broadly and add persistent channels only where real-time behavior is required.

How to get a private Sui RPC endpoint with Chainstack

Log in to the Chainstack console (or create an account).
Create a new project.
Select Sui as your blockchain protocol.
Choose Sui Mainnet Network
Deploy the node.
Open Access/Credentials and copy your endpoint and auth details.
Run a quick connectivity check in your SDK/client before wiring it into production code.

This flow keeps setup simple while giving you production-grade infrastructure earlier in the lifecycle.

Is Chainlist applicable for Sui?

Not really.
Chainlist is mainly used for EVM wallet-network configuration and is not the standard infrastructure path for Sui. For Sui, use your provider dashboard and official SDK tooling instead.

How to choose the best Sui RPC provider in 2026

Most teams pick an RPC provider too early based on “it works in dev.” For Sui, that can backfire in production because your workload profile changes quickly once users, bots, or indexers hit your app.

Use this evaluation framework before you commit:

Evaluation Criteria	What to Check	Why It matters for Sui
Reliability under load	• SLA terms and incident history • Traffic burst handling • Regional failover behavior	Sui’s parallel execution can spike RPC load unpredictably. Shared infrastructure may throttle during network congestion.
Performance	• p95/p99 latency from your backend regions • Consistency during peak windows	Object queries and checkpoint reads are latency-sensitive. Users notice slow wallet updates immediately.
API roadmap compatibility	• Support for Sui’s API transition path • SDK stack compatibility	Sui is moving away from legacy JSON-RPC. Ensure your provider supports your integration path.
Data access depth	• Archive/checkpoint retention • Historical backfill capabilities	Sui’s checkpoint-based history model requires archive nodes for analytics and compliance queries.
Operational controls	• Key management and access rules • Usage analytics and alerting • Support escalation process	Production incidents need fast response. Monitoring prevents surprises at scale.
Pricing predictability	• Request-based vs compute-unit pricing • Model costs at 3x expected traffic • Overage rules and dedicated options	Object-heavy queries cost more. Understand pricing before you scale.

A practical rollout model:

Start on public/dev endpoints for prototyping
Move to managed shared endpoints for staging
Use managed production tier with fallback provider before launch

Chainstack pricing for Sui RPC

Chainstack pricing is request-unit-based and easier to forecast than method-weighted credit systems.

Plan tiers	Cost	Overage (per extra 1M requests)
Developer	`$0/mo`, 3M requests included, ~25 RPS	`$20`
Growth	`$49/mo`, 20M requests, ~250 RPS	`$15`
Pro	`$199/mo`, 80M requests, ~400 RPS	`$12.5`
Business	`$349/mo`, 140M requests, ~600 RPS	`$10`
Enterprise	from `$990/mo`, 400M requests, custom throughput	from `$5`

How to estimate your likely monthly cost quickly:

Forecast average and peak requests/day
Convert to monthly request units
Add a 20–30% buffer for spikes
Check if RPS limits match your peak traffic profile
Compare shared tier vs dedicated economics at projected scale

If your traffic is bursty (bots, analytics, event-heavy apps), throughput limits and overage policy matter more than base plan price.

Production readiness checklist

Before launch, validate these basics:

Primary + fallback RPC provider configured
Request timeout policy set
Retry logic with exponential backoff implemented
Endpoint and network validated at startup
Credentials stored in env/secret manager (never hardcoded)
Monitoring for latency, error rate, and throttling
Alerts for sustained degradation

These controls prevent most avoidable RPC incidents in production.

Troubleshooting common Sui RPC issues

Issue	Likely cause	How to fix
Frequent rate limits	Shared endpoint saturation	Move to managed endpoint, reduce polling, batch requests
High latency spikes	Region mismatch or overloaded shared infra	Route to closer region and enable fallback endpoint
Intermittent request failures	No retry/timeout strategy	Add bounded timeouts + exponential backoff
Missing historical data	Endpoint not archive-capable	Use archive-capable tier/provider
Authentication errors	Missing/invalid token config	Verify auth headers/tokens and rotate credentials

Conclusion

Sui’s object-centric architecture makes RPC selection more critical than on EVM chains. Your provider needs to support Sui’s unique data model, API migration path, and checkpoint-based historical queries—not just provide raw RPS.

Use public endpoints for prototyping, then move to managed infrastructure with proven Sui support, clear object indexing strategy, and SLA-backed uptime before production launch.

Start with Chainstack’s free tier (3M requests/month), validate your query patterns in staging, then scale to dedicated infrastructure as traffic grows.

Start building with Chainstack →

FAQ

How is Sui RPC different from EVM RPC?

Sui uses a Move-based, object-centric data model instead of the account-and-log model used by EVM chains. Developers query object states, versions, and checkpoints rather than accounts and events, which changes integration and indexing patterns compared to typical EVM RPC setups.

What SDK should I use for Sui?

For TypeScript, @mysten/sui is the primary SDK path. Confirm compatibility with your chosen API mode.

Should I still use JSON-RPC in 2026?

JSON-RPC is still supported, but it should no longer be the default for new Sui integrations. Use it only where required for legacy compatibility or existing tooling, and plan a structured migration to gRPC or GraphQL for better performance, stronger typing, and long-term ecosystem support.

Is Sui Testnet enough for staging?

Yes for most integration and pre-production testing. Sui Testnet is suitable for validating contract logic, object lifecycle flows, SDK integrations, and API compatibility. However, you should also simulate realistic traffic patterns, concurrency, and data growth to uncover rate limits, latency spikes, and indexing edge cases before launching on Mainnet.

What should I monitor on Sui RPC?

Track p95/p99 latency, failure rate, throttle events, and endpoint availability. Alert early, before user-facing transactions degrade. Monitor trends over time to detect gradual performance regression, not just sudden outages.