Private Acurast RPC Endpoints on a Dedicated Node

Acurast is a decentralized, serverless cloud compute network that turns consumer hardware, primarily smartphones, into secure compute nodes using hardware-backed Trusted Execution Environments. The chain itself is a Substrate parachain that coordinates deployments, matching, and rewards, while the confidential compute runs off-chain on the device processors. Your RPC node serves the chain interactions, not the compute jobs themselves.

Acurast is live today as Acurast Canary, connected to the Kusama relay chain, and that is what dedicated nodes serve now. Acurast Mainnet on Polkadot (parachain ID 3396) is announced but not yet live. We deploy Canary nodes today and can stand up Mainnet nodes once it launches, so tell us which network your product targets.

Most teams start with a full (pruned) Acurast 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 Acurast RPC provider runs many customers on pooled infrastructure, which can create unpredictable latency during spikes, shared rate limits, and noisy-neighbor slowdowns. Dedicated Acurast 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. Acurast exposes the standard Substrate JSON-RPC, so Polkadot.js works over WebSocket for subscriptions and real-time updates, and HTTP works for request and response calls. Your dedicated node can expose WSS endpoints, and you can keep them private or public based on your access model, restricting access by IP for tighter control.

Yes. Acurast uses collators that author blocks with Aura consensus and submit them to the relay chain validators. You can run a collator on a dedicated single-tenant node with full root, KVM, and IPMI access. You register and hold the session keys, while we keep the hardware healthy with fast recovery if anything goes wrong.

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