Private Phala RPC Endpoints on a Dedicated Node

Phala Network is a Polkadot parachain for confidential, off-chain compute: Phat Contracts run inside TEE Worker nodes, while the parachain itself coordinates state and payments in PHA. A Phala RPC node gives you Substrate JSON-RPC access to that parachain, balances, blocks, events, and transaction submission, over HTTP and WSS, on hardware you control rather than a shared pool.

Most teams start with a pruned full Phala 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. We deploy phala-node with the collator flag enabled on single-tenant bare metal, tuned for single-thread performance with SMT disabled. Phala uses Aura for collator block production and inherits security and finality from the Polkadot relay chain. You hold the session keys; we run the metal with IPMI and KVM for fast recovery.

A shared Phala RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Phala 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. Your dedicated Phala RPC node can expose WebSocket endpoints for app usage, and you can keep them private or public based on your access model. If you want tighter control, you can restrict access by IP and allow only trusted clients.

Phala nodes use the standard Substrate ports, typically 9944 and 9945 for RPC and WebSocket and 30333 and 30334 for P2P. We recommend exposing only what you need. Many teams restrict access to known IPs, put a reverse proxy in front, and keep admin surfaces closed. With a dedicated server, you can define firewall rules that match your risk level and traffic profile.

For production Phala RPC, you need fast NVMe storage, sufficient RAM for caching, and a stable network. Many teams start with 4 to 8 cores and 32 to 64 GB RAM for a pruned full node, then scale to 16+ cores and more RAM as concurrency rises. Archive RPC requires 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 Phala 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.