Private Polkadot Coretime RPC Endpoints on a Dedicated Node

No. Polkadot Coretime is a Polkadot system parachain (parachain ID 1005), not a standalone Layer 1. It runs the Broker pallet that sells and schedules Agile Coretime, both bulk 28-day allocations and on-demand cores, for the relay chain. On-demand orders pay in DOT per block, and it inherits security and finality from the Polkadot relay chain. An RPC node for Coretime targets this parachain, not the relay chain itself.

Most teams start with a full Coretime node because it serves current-state reads and transaction submission with lower storage needs. Choose archive RPC when your product must query full history, power an explorer, run deep analytics on coretime sales, 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 Coretime RPC provider runs many customers on pooled infrastructure, which can create unpredictable latency during spikes plus shared rate limits and noisy-neighbor slowdowns. Dedicated Coretime 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. Like every Polkadot parachain, a Coretime collator or RPC node syncs an embedded relay-chain node alongside the parachain database, which is why disk and sync time are larger than the parachain alone suggests. We provision from current snapshots for both layers so you skip the long cold sync, and we size NVMe for the combined footprint.

Yes. Coretime exposes the standard Substrate JSON-RPC, so Polkadot.js over WebSocket works with no changes for subscriptions and real-time updates. Your dedicated node can expose WebSocket endpoints for app usage, kept private or public based on your access model. For tighter control, restrict access by IP and allow only trusted clients.

No. Coretime is a system parachain, so it has no permissionless validator set: its collators are allocated through Polkadot network governance, and security and finality come from the relay-chain validators. We provide full and archive RPC nodes for reading and submitting to Coretime, not a validator or governance-allocated collator slot.

For production Coretime RPC you need fast NVMe storage, enough RAM for caching, and a stable network. Many teams start with a few high single-thread cores and 16 to 32 GB RAM for a full node, then scale cores and memory as concurrency rises. Archive RPC requires larger NVMe capacity and more cache headroom, since historical queries and indexing are storage and memory intensive, and the embedded relay-chain database adds to the footprint.

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