Private Aleph Zero RPC Endpoints on a Dedicated Node

This page is for the Aleph Zero Substrate L1, the standalone WASM layer 1 that runs AlephBFT consensus and uses the Substrate JSON-RPC (chain_, state_, system_). It is not the same as Aleph Zero EVM, which is the Ethereum-compatible network that exposes eth_* JSON-RPC. If your app calls eth_* methods, you want the Aleph Zero EVM node instead. If it uses Polkadot.js, substrate-interface, or ink! contracts, this Substrate L1 node is the right one.

Aleph Zero uses AlephBFT, a DAG-based Byzantine Fault Tolerance protocol combined with Proof of Stake. A rotating committee of validators orders transactions through a DAG, and the chain is built from that ordering. It tolerates up to one-third malicious participants and delivers deterministic, subsecond finality rather than probabilistic confirmation, with roughly one-second block times.

Most teams start with a pruned 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.

Yes. Aleph Zero exposes the Substrate JSON-RPC, so Polkadot.js, substrate-interface, and the Go substrate client all connect with no changes. Most developers use WebSocket (WSS) for subscriptions and real-time updates. Your dedicated node can expose HTTP and WSS endpoints, and you can keep them private or restrict access by IP based on your access model.

Aleph Zero's docs call for a modern x86_64 CPU with at least 8 cores, 32 GB RAM, and fast NVMe, and they recommend bare metal over VMs. We provision a pruned full node from around 500 GB NVMe and an archive node from 2 TB+ NVMe, scaling cores and RAM as concurrency rises. Archive RPC needs more disk and cache headroom because historical queries and indexing are storage intensive.

Yes. We run the aleph-node validator on single-tenant bare metal tuned for low latency and steady uptime, with IPMI and KVM for fast recovery. You hold the validator keys; we run the metal. Aleph Zero recommends bare metal for validators, so this setup avoids the noisy-neighbor jitter that can cost a committee member missed blocks.

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