Private Integritee RPC Endpoints on a Dedicated Node

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

In October 2025 Integritee AG announced it would stop running its own infrastructure, including its collators, from November 10, 2025, citing Intel SGX (WireTap) vulnerabilities and reduced Polkadot ecosystem support. The Polkadot and Kusama parachains continue producing blocks only while community collators keep running them, and TEER remains transferable as an asset. We only deploy nodes against a live network, so tell us your target and we will confirm current status before provisioning.

A shared Integritee RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Integritee 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. We can provision a dedicated node running the integritee-collator binary with the embedded Polkadot or Kusama relay chain node, sized for steady block production. Collators bond TEER and you hold the keys, while we handle the metal with full root, KVM, and IPMI for fast recovery. Because the team wound down its own collators, community operators are what keep the network alive.

Yes. Most developers use Polkadot.js over WebSocket for subscriptions and real-time updates. Your dedicated Integritee node exposes the Substrate JSON-RPC over HTTP and WSS, and you can keep it private or public based on your access model. If you want tighter control, you can restrict access by IP and allow only trusted clients.

Yes. Integritee runs as a parachain on both Polkadot and Kusama. We can deploy a node for either network, or separate nodes for both, so a workload on one does not interfere with the other. Tell us which parachain your app calls and your region, and we will provision the right node.

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

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.