Private Pendulum RPC Endpoints on a Dedicated Node

Most teams start with a pruned Pendulum full node because it serves current state reads and transaction submission with far lower storage needs. Choose an archive node when your product must query full history, power explorers, run deep analytics, or support heavy historical lookups. If you are unsure, tell us your workload, and we will map you to the right node type.

A shared Pendulum RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Pendulum RPC node servers give you single-tenant resources, your own access rules, and clearer fault boundaries. You control performance and security instead of inheriting someone else's traffic.

Yes. Most developers use Polkadot.js over WebSocket for subscriptions and real-time updates. Pendulum is a Substrate-based Polkadot parachain, so your dedicated node exposes the standard Substrate JSON-RPC (chain_, state_, system_, author_) over HTTP and WSS. You can keep WebSocket endpoints private or public based on your access model.

Yes. Spacewalk is Pendulum's trustless bridge to Stellar, and apps using it need reliable block tracking for cross-chain transfers. Your dedicated node gives you a stable, uncapped endpoint for confirmations and settlement monitoring, without the rate limits or noisy-neighbor latency of a shared pool.

Pendulum runs WASM smart contracts (ink!) today, and EVM compatibility via Frontier is on its roadmap. We currently provision Pendulum nodes serving the Substrate JSON-RPC, not Ethereum eth_ namespaces. If you need EVM access, tell us your timeline and we will confirm the current chain capability before provisioning.

For production Pendulum RPC, you need fast NVMe storage, sufficient RAM for caching, and a stable network. Many teams start with 8+ cores and 32 to 64 GB RAM for a pruned full node, then scale to 16+ cores and 128 GB RAM as concurrency rises. Archive nodes require larger NVMe capacity and more cache headroom, as historical queries and indexing are storage and memory intensive.

Yes. That is a core benefit of running a dedicated Pendulum 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.