Supra Dedicated RPC Node & Private Supra RPC Endpoint

An RPC endpoint that only your applications use. It sits on a dedicated Supra node that is yours alone, on your own domain if you want one, and answers only the IP addresses you allowlist. No other customer's traffic shares the machine, so nobody else's burst becomes your latency, and there is no rate limit to hit.

As soon as it has synced with the Supra network, and we tell you the moment it is ready. Sync time depends on the node type (an archive node replays the full history, so it takes longest) and the client you pick (supra_node (validator, Docker), rpc_node (Docker)), so your quote carries an estimate for your exact setup rather than a number that is sometimes wrong. The quote itself lands within the hour, around the clock.

Everything the node can do, with the premium add-ons other providers bill separately included free: unlimited RPS, every RPC method including heavy queries, unlimited WebSocket connections, your own domain with an IP allowlist, 18 cities to choose from, a 99.99% SLA with credits, 24/7 engineer support and live p50/p99 in your dashboard. There is no add-on price list because nothing is an add-on.

A machine that meets Supra's official requirements with headroom on top. We never build at the minimum, because a node sized to the minimum becomes the bottleneck the day the chain grows. Your quote names the exact CPU, RAM and NVMe before you pay.

We do not run free trials. Ask us for a latency report for Supra from the city you want and you see the numbers before you order. Billing is monthly with no lock-in, so you can cancel at the end of any month.

supra_node (validator, Docker): The validator binary that participates in Moonshot consensus (smr_settings.toml, genesis_parameters.toml); only for approved operators. rpc_node (Docker): The RPC node that syncs from a validator over WebSocket (needs a validator-issued certificate) or from another RPC node over REST, and serves the public REST/WebSocket API; this is the component an RPC buyer would run.

Yes. Supra's documentation describes full-history operation; we run Supra archive nodes from $799/mo with historical queries unmetered.

Node operation is currently limited to select operators per official docs. We run every node type the chain actually offers and none it does not.

Yes. A dedicated Supra node speaks the same REST and WebSocket (Supra-native /rpc/v4/ws) and EVM JSON-RPC and WebSocket (/rpc/v1/eth, SupraEVM early access) interfaces as the shared endpoint you use today, so migration is pointing your application at your own endpoint. Billing is monthly with no lock-in on our side, and support engineers are on the channels 24/7 during cutover.

Any of 18 Tier-3 datacentre cities across North America, Europe, Asia-Pacific. Deploy near your users for an app, or ask us where Supra latency is lowest for a bot; we answer from measurement. Need a city we do not list? Ask.

No artificial ones: unlimited RPS and no connection cap. The machine is yours alone, so the hardware is the only ceiling: if it can serve the request, you can send it. There is no per-plan connection cap because there is no plan tier.

Visa, Mastercard, bank transfer or crypto, billed monthly; crypto payments need no KYC. Cancel at the end of any monthly term; the node is provisioned for you alone, so there is no meter to escape and no exit fee.

Argusnodes is dedicated-only: a private Supra endpoint on a bare-metal node with no rate limits, at one fixed price from $99/mo with every add-on included. Per their own pricing pages: QuickNode sells dedicated clusters through enterprise sales without published prices, Chainstack bills dedicated nodes per hour on top of a paid plan, and Zeeve applies monthly request allowances on dedicated plans below its Enterprise tier (all checked August 2026); GetBlock lists dedicated nodes from $1,000/mo, with IP allowlisting and a custom endpoint URL sold as $199/mo add-ons each (checked September 2026). The comparison table on this page links every source.