Private Moonriver RPC Endpoints on a Dedicated Node

Moonriver is Moonbeam's sister network running on Kusama (EVM chain ID 1285), serving as an incentivized canary network. It provides a full Ethereum-like environment under real economic conditions, so developers can deploy and test applications with live MOVR before moving to Moonbeam on Polkadot. The tooling, EVM compatibility, and Substrate runtime match Moonbeam, which makes it a faithful staging ground.

Most teams start with a full Moonriver node, which serves current-state reads and transaction submission with lower storage needs. Choose an archive node when you must query full history, run debug and trace, power explorers, or run deep analytics. A collator node is for block production and MOVR staking in the active set. If you are unsure, tell us your workload and we will map you to the right node type.

Yes. Moonriver runs the moonbeam client with the Frontier EVM, so your dedicated node exposes Ethereum JSON-RPC (eth_, net_, web3_, plus debug and txpool) for MetaMask, ethers.js, and web3.js, and Substrate JSON-RPC (chain_, state_, system_) for Polkadot.js. Both are available over HTTP and WSS. You decide which interfaces to expose and can keep them private behind IP allowlisting.

A shared Moonriver RPC provider runs many customers on pooled infrastructure, so you inherit rate limits, compute-unit billing, and noisy-neighbor latency during spikes. Dedicated Moonriver RPC node servers give you single-tenant CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.

Provisioning is fast. The real variable is sync time, which depends on node type, storage speed, and network conditions. Because a Moonriver node also syncs an embedded Kusama relay node, we provision from current snapshots so you skip the long cold sync. A full node reaches a usable state sooner than an archive node, which has far more data to process. We deploy according to real sync time, not a fake instant promise.

You can expose the standard RPC and WebSocket ports used by the moonbeam client for both Ethereum and Substrate JSON-RPC. We recommend exposing only what you need. Many teams restrict access to known IPs, put a reverse proxy in front, and keep admin and debug surfaces closed. With a dedicated server, you define firewall rules that match your risk level and traffic profile.

Yes. That is a core benefit of running a dedicated Moonriver RPC node on dedicated servers. You can scale up resources as load grows, add storage for archive needs, and move to higher core counts for heavy concurrency. This keeps your endpoint stable while your product grows, without rebuilding everything on a new platform.

No. Unlike shared RPC providers that bill per "compute unit" and throttle you past a quota, a dedicated node is a flat monthly price with unlimited requests and zero overages. One node equals all the throughput your hardware can serve. That makes budgeting predictable and removes the surprise bills that come with usage-based RPC pricing.

Shared RPC pools serve thousands of customers from pooled infrastructure, so you inherit rate limits, noisy-neighbor latency, and compute-unit billing. A RedSwitches node runs on single-tenant bare metal that is yours alone: reserved CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.

No. We provision from current snapshots so your node is live in hours rather than syncing from genesis for days. You can run it yourself with full root access, or choose our fully managed option where our engineers handle the sync, updates, and monitoring. Either way you receive a working private endpoint, not an empty server.

Yes. With 20+ Tier III locations across the US, EU, Asia, and Australia you can place your node in the same region as your users or a chain's sequencer to cut round-trip latency. Tell us your target region and we will recommend the closest facility. You can also run multi-region nodes for redundancy and split read and write endpoints.