Private Polkadot People RPC Endpoints on a Dedicated Node

No. Polkadot People is a Polkadot system parachain (parachain ID 1004), not a standalone Layer 1. It hosts the on-chain identity system for the Polkadot ecosystem: the identity pallet, along with its data, was migrated off the relay chain to this chain. It stores web3 usernames, social profiles, judgements, and on-chain credentials, and is secured by the Polkadot relay chain.

If your wallet or app resolves Polkadot identities, it queries the People Chain for usernames, profile fields, judgements, and credentials. A dedicated node gives you a private endpoint for those reads and writes with unlimited requests and zero rate limits, so identity lookups stay fast during launches and traffic spikes instead of inheriting a shared pool's throttling.

Most teams start with a full node because it serves current identity state and submission with lower storage needs. Choose archive when your product must query full history, power identity explorers, run deep analytics, or support heavy historical lookups. Tell us your workload and we will map you to the right node type.

People Chain is a Substrate / Cumulus system parachain. The node runs the polkadot-parachain binary from the Polkadot SDK, which also runs an embedded relay-chain node, so storage and sync cover both the parachain and its relay connection. The runtime itself lives in the polkadot-fellows/runtimes repository. We handle the binary config, ParityDB tuning, and snapshot sync.

Yes. People Chain serves the standard Substrate JSON-RPC (chain_, state_, system_) over HTTP and WSS, so Polkadot.js and Substrate tooling connect with no changes. Most developers use WebSocket for subscriptions and real-time updates. You can keep the endpoint private or public based on your access model, and restrict access by IP for tighter control.

A shared RPC provider runs many customers on pooled infrastructure, which can mean unpredictable latency during spikes, shared rate limits, and noisy-neighbor slowdowns. A dedicated Polkadot People RPC node gives you single-tenant resources, your own access rules, and clearer fault boundaries. You control performance and security instead of inheriting someone else's traffic.

For production People Chain RPC you need fast NVMe storage, enough RAM for caching, and a stable network. Many teams start with 8+ cores and 32 to 64 GB RAM for a full node, then scale to 16+ cores and 128 GB RAM as concurrency rises. Archive RPC requires larger NVMe capacity, since the parachain plus its embedded relay history and identity state grow continuously.

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.