Unlimited RPS & Responses
One node, unlimited requests and responses. No compute units, no rate caps, no overage bills. A flat monthly price, run as hard as the hardware allows.
// dedicated polkadot coretime rpc node
Private Polkadot Coretime RPC Endpoints on a Dedicated Node
A private Polkadot Coretime RPC endpoint on single-tenant NVMe bare metal. Full or archive Substrate nodes serving JSON-RPC over HTTP and WSS, with zero rate limits and no compute units.
- Private Endpoint, Zero Rate Limits
- No Compute Units, Unlimited Requests
- Full & Archive Builds
- Substrate JSON-RPC Over HTTP & WSS
- Embedded Relay Chain Sync
- 20+ Global Tier III Locations
deploy.shlive
$ rs deploy coretime --type full --region fra
allocating single-tenant bare metal
restoring coretime chain snapshot (paritydb)
syncing embedded relay chain + parachain
serving substrate json-rpc over http + wss
attaching ddos shield + ip allowlist
private endpoint live · http + wss
- UnlimitedRequests
- ZeroRate Limits
- 100%Isolation
// why redswitches
Why Teams Run Polkadot Coretime Nodes With RedSwitches
A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.
Dedicated Account Manager
A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.
Direct Engineering Access
Talk to the engineers who run the metal. The polkadot-parachain (Cumulus) binary, the embedded relay-chain sync, ParityDB vs RocksDB, snapshots, and single-thread CPU tuning, handled by people who run Polkadot system parachain nodes daily.
20+ Global Data Centers
Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.
Pay In Crypto
Settle in crypto or fiat, DOT included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.
Tailored Load Balancing
Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.
// request your endpoint
Configure Your Polkadot Coretime Node
Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.
1 Dedicated Node = Unlimited RequestsNo Compute Units$0 Overages, Guaranteed
Polkadot Coretime Full Node
For marketplaces, wallets, bots & backend APIs
- CPU
- 4–8 high single-thread cores, 16+ for heavy traffic
- RAM
- 16–32 GB
- Storage
- 200 GB+ NVMe incl. embedded relay chain (grows with state)
- Network
- 1 Gbps+ on a 10/25 Gbps port
- Clients
- polkadot-parachain (Polkadot SDK / Cumulus) · RocksDB / ParityDB
Best for
- Current-state reads and transaction submission
- Polkadot.js over WSS subscriptions
- Private JSON-RPC for coretime app and wallet backends
Included with every node
- Unlimited RPS, no rate limits
- HTTPS & WebSocket (WSS)
- 99.99% uptime SLA
- Multi-region endpoints
- Private networking + IP allowlisting
- 24/7 Web3 engineering support
From$199/moflat, no compute units
Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.
Node specs above are based on the official Polkadot Coretime documentation.
View official Polkadot Coretime node docs →Polkadot Coretime Archive Node
For explorers, indexers & analytics
- CPU
- 8–16+ high single-thread cores
- RAM
- 32–64 GB+
- Storage
- 1 TB+ NVMe for full history incl. relay chain (grows continuously)
- Network
- 1 Gbps
- Clients
- polkadot-parachain (archive mode) · ParityDB
Best for
- Coretime sale and region history for explorers
- Long-running indexers and ETL pipelines
- Historical broker-pallet state for analytics
Included with every node
- Unlimited RPS, no rate limits
- HTTPS & WebSocket (WSS)
- 99.99% uptime SLA
- Multi-region endpoints
- Private networking + IP allowlisting
- 24/7 Web3 engineering support
From$199/moflat, no compute units
Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.
Node specs above are based on the official Polkadot Coretime documentation.
View official Polkadot Coretime node docs →Request Sent
Thanks. A Web3 engineer will spec your private endpoint and reach out shortly.
Something went wrong. Please try again or email sales@redswitches.com.
// why dedicated
Stop Fighting For Bandwidth On Shared Polkadot Coretime RPC
Shared Polkadot Coretime RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Polkadot Coretime node is your own private backbone: flat-priced, uncapped, and yours alone.
CapabilityShared RPC PoolRedSwitches Dedicated
Request limitsHard rate caps and compute-unit quotas throttle your Polkadot Coretime calls the moment traffic spikesZero rate limits, your Polkadot Coretime node serves unlimited requests up to what the hardware can push
ResourcesA noisy-neighbor pool where another tenant's mint or airdrop steals the throughput you paid for100% single-tenant CPU, RAM, and NVMe, reserved for your Polkadot Coretime workload alone
BillingPer-compute-unit metering with surprise overage bills at the end of the monthOne flat monthly price for the whole node, $0 overages and no usage math
NetworkShared, throttled bandwidth you can neither see nor controlA dedicated 10 / 25 Gbps port, metered or unmetered, that is yours alone
PrivacyA public, pooled endpoint with a wide, shared attack surfaceA private Polkadot Coretime endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Polkadot Coretime archive with custom RAM and disk, sized to your query depth
ControlNo server access, the provider picks the client, version, and configFull root, KVM, and IPMI, run the Polkadot Coretime client and tuning you choose
// network details
Polkadot Coretime Node Specifications
The networks, node software, data interfaces, and chain parameters your dedicated Polkadot Coretime node ships with. Coretime serves the Substrate JSON-RPC over HTTP and WSS, so Polkadot.js and Substrate tooling connect with no changes.
Chain Parameters
- Networks
- Polkadot Coretime (Kusama, Westend variants)
- Parachain ID
- 1005 (Polkadot)
- Native token
- DOT
- Role
- Agile Coretime sales + core scheduling (Broker pallet)
- Consensus
- Collator authoring (Aura), secured by Polkadot relay chain
- Finality
- Inherited from Polkadot relay chain (GRANDPA)
- Block time
- ~6 seconds
- Framework
- Substrate / Cumulus (Polkadot SDK)
- Archive
- Full history (ParityDB) vs pruned full
- Explorer
- coretime-polkadot.subscan.io
Supported Clients
Node software
- polkadot-parachain (Polkadot SDK / Cumulus)
- RocksDB / ParityDB
Data interfaces
- JSON-RPC (HTTP)
- JSON-RPC (WSS)
- Polkadot.js API
JSON-RPC methods
- chain_
- state_
- system_
Coretime runs no smart contracts; its application logic is the Broker pallet that sells and schedules coretime. An RPC node also syncs an embedded relay-chain node. Keep your endpoint private behind IP allowlisting and a reverse proxy, and keep admin RPC closed.
// use cases
What Teams Build On Polkadot Coretime Nodes
Where a private, uncapped endpoint beats a shared RPC pool.
Coretime Marketplace Backends
Coretime marketplaces need fast, reliable reads of bulk sales, on-demand orders, and renewals. Your dedicated endpoint serves broker-pallet state and submission without shared rate limits during sale periods.
Parachain Operations
Parachain teams track core assignments, renewals, and prices to keep blockspace continuous. A dedicated node gives steady reads of region and core state for automation and alerting.
Explorer And Indexing
Explorers and indexers process Coretime blocks nonstop and run historical queries. A dedicated archive node supports long-running ingestion of sales and region records without shared-endpoint limits.
WebSocket App Streams
Many Coretime apps rely on WSS feeds for live sale and scheduling events. A dedicated endpoint keeps long-lived connections stable during busy sale windows, fit for dashboards and notifications.
Core Utilization Analytics
Analytics teams read region, core, and on-demand pricing data to study blockspace usage. A dedicated archive node serves deep historical queries without throttling or noisy-neighbor slowdowns.
Private Internal RPC
Teams want Coretime access without exposing endpoints publicly. Restrict access by IP and network rules for internal tooling, back-office services, and partner systems, with a clearer security posture.
// how it works
From Polkadot Coretime To Private Endpoint In 3 Steps
Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.
- 01
Pick Your Coretime Node
Choose a full or archive node. We run the polkadot-parachain binary with an embedded relay-chain node on ParityDB; tell us your region and query depth.
- 02
We Provision Bare Metal
Your single-tenant node deploys on NVMe tuned for single-thread speed, snapshot-synced for both the Coretime parachain and the embedded relay chain, so you skip the long cold sync.
- 03
Get Your Private Endpoint
Receive a dedicated Substrate JSON-RPC endpoint over HTTP and WSS with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.
// latency & locations
Put Your Node Where Milliseconds Are Won
RPC latency is mostly a function of distance. A dedicated node lets you choose the exact region, so you sit next to the traffic that matters instead of fighting for routing on a shared, far-away endpoint.
Place It Where Your Users Are
Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Polkadot Coretime node in the region your traffic actually comes from, not wherever a shared pool happens to route you.
Cut The Round Trips
RPC latency is mostly physical distance. Running in the same region as your users and the Polkadot Coretime network's peers shaves the round-trips a far-away, shared endpoint can never give back, which is what high-frequency reads and transaction submission live or die on.
Multi-Region By Design
Run a primary node plus regional read replicas for fast reads everywhere and built-in redundancy. Split public read endpoints from private admin, debug, and trace endpoints.
Need a node within a target latency budget of a specific region or venue? Tell us the endpoint and we'll recommend the closest facility.
// supported chains
One Backbone For Every Major Chain
Run validators, RPC, and archive nodes across the chains your stack depends on, all on the same dedicated bare metal, with the same isolation, speed, and control.
Ethereum
Solana
Polygon PoS
BNB Chain
Avalanche
Cardano
Cosmos
NEAR
Sui
Aptos
TRON
Polkadot
Kusama
Algorand
Tezos
TON
Fantom
XRP Ledger
Hedera
0G
Berachain
Celestia
Flare
Flow
Gnosis Chain
Hyperliquid
Injective
Japan Open Chain
Kaia
Monad
Nomina
Osmosis
peaq
Plasma
Ronin
Sahara AI
Sei
Sonic
Stellar
Story
Vana
Cronos
ZetaChain
XDC Network
PulseChain
Filecoin
IoTeX
Chiliz
Viction
Tempo
Stable
SORA
Waves
Moonbeam
Moonriver
Moonbase Alpha
Astar
Shiden
Aleph Zero EVM
Darwinia
Manta Atlantic
Acala
Karura
Bifrost
Hydration
Basilisk
Centrifuge
Interlay
Phala
Aleph Zero
Bittensor
Enjin
Nodle
Frequency
Humanode
Crust Network
Robonomics
Integritee
NeuroWeb
Tangle
Mythos
Pendulum
Amplitude
Aventus
Acurast
Energy Web X
Heima
Krest
Liberland
BalanceAI
Zeitgeist
xx network
Hyperbridge
Polkadot Asset Hub
Polkadot Bridge Hub
Polkadot Collectives
Polkadot Coretime
Kusama People
Polkadot People
Westend People
Paseo
Arbitrum
Base
Optimism
Polygon zkEVM
Linea
Scroll
zkSync Era
Starknet
Abstract
Arbitrum Nova
B3
Blast
Celo
Cyber
Fluent
Fraxtal
Fuel
Gravity
Hemi
Immutable zkEVM
Ink
Lens
Lisk
Mantle
Mode
Morph
Movement
Soneium
Sophon
Stacks
Taiko
Unichain
World Chain
Xai
Zora
opBNB
Manta Pacific
Boba Network
MegaETH
Bitcoin
Dogecoin
Litecoin
// customer reviews
Trusted To Run Production Nodes
Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.
- 25Gbps Bare Metal
Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
- VPN Operations
Network has been rock solid. They’ve got Tier 1 carriers like Arelion, GTT, and TATA… We just ping them on Telegram and they sort things out quickly.
- Validators
Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
- Full Root Access
As a sysadmin, I care more about control than flashy dashboards. RedSwitches gives me root access, IPMI, and actual hardware specs I can configure. Good for serious users.
- Enterprise Uptime
We were searching for a truly reliable and stable hosting provider with maximum uptime and a powerful network infrastructure to ensure the lowest possible latency. RedSwitches not only met but exceeded our expectations.
- Cloud Exit
RedSwitches gave us full control over our infrastructure without the vendor lock-in we kept running into with cloud hosts. Customizable builds, fast provisioning, and actual humans handling support tickets. It’s refreshing.
- 99.99% Uptime
My website works smoothly, thanks to their 99.99% uptime guarantee. The support team is another plus for me, as I always have been able to get help whenever I needed it in just 5 minutes on average.
- ETH & BTC Nodes
Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
- 10Gbps RPC
They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
- Streaming
I am using their 10gbps streaming server for last 6 months and I have no complaints. Extremely quick live chat support and I love that they accept crypto.
- Bare Metal
A really great hosting provider - what stands out the most is the stability of the network connection and the wide selection of bare metal servers. We’re very satisfied, and RedSwitches covers all of our needs.
- AI Workloads
Pros: Extremely reliable hardware, low-latency network, transparent billing… Great choice if you need raw power without cloud complexity. Works well for our dev environment and some AI workloads.
- Switched Provider
I have worked with OVH and Contabo in the past, but RedSwitches hit a better balance of price vs. support. Not the cheapest, but I get better performance and faster help.
- Game Servers
Been using RedSwitches for 6 months now for my small game server biz. Uptime has been great, and I haven’t run into any hidden charges.
- AI Storage
Using the storage servers to archive logs and snapshots from our AI pipeline… I also love that I could pick the datacenter closest to our team.
- Support
Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
- Instant Delivery
They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
- Fast Provisioning
A dedicated server has been installed within 30 minutes. Thirty minutes. It takes DAYS for some famous providers out there, but these guys do their work right.
- 5+ Years
I have been using their services for over 5+ years… Uptime: 10/10, Network: 10/10, Hardware Quality: 10/10, Customer Support: 20/10 (No, That’s Not A Typo).
- 1 to 14 Servers
They offer top quality hardware, excellent uptime and very responsive support… They helped us scale our business exponentially and we went from 1 server to 14 dedicated servers in less than a year.
- Reliability
Great hardware, non congested network and excellent service. Already using them for over a year and would definitely recommend Redswitches if you are looking for a reliable hosting provider.
- Global Locations
With servers available in numerous strategic locations, RedSwitches offers exceptional versatility and performance for our company’s diverse hosting needs. Plus, their no setup fee policy really helps keep costs down.
- Exam Platform
"Your server is ready" - I read this message within 30 mins of starting the chat with their Sales Team… Excellent DELL Hardware and 100% Uptime.
- Bare Metal Cloud
The dedicated server I got from RedSwitches has been incredibly reliable and fast. Their bare metal cloud solutions offer excellent performance, and the cloud VPS options are perfect for scaling. Highly recommended!
- Zero Downtime
I have been using their dedicated server from 9 months now. Starting from pre-sales till today I have not experienced downtime or lack of support.
- 24/7 Support
First of all, all services work as expected - secondly - support is outstanding, no matter when you start the conversation with colleagues at support they have knowledge to help you out.
- Since 2021
We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
- Easy Onboarding
Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
- Bare Metal
Very good experience using their bare metal servers. Their customer service is one of the finest I have experienced - always prompt at resolving troubles. Highly recommend.
// faqs
Frequently Asked Questions
Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.
What is the Polkadot Coretime chain, and is it a standalone Layer 1?
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.
Which Coretime node type do I need: full RPC or archive RPC?
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.
What is the difference between a shared Coretime RPC provider and dedicated Coretime RPC node servers?
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.
Does a Coretime RPC node also run a relay-chain node?
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.
Can I use Polkadot.js with your endpoint, and do you support WSS WebSocket connections?
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.
Do you offer a Coretime validator node?
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.
What hardware specs do you recommend for low-latency Coretime RPC at scale?
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.
Can I scale CPU, RAM, and NVMe as traffic grows without changing providers?
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.
Do you charge per request or per compute unit?
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.
How is this different from a shared RPC endpoint?
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.
Do I have to sync the node myself, or wait days for it?
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.
Can I deploy close to a specific region or sequencer?
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.
// developer resources
Polkadot Coretime Developer Resources
Official Polkadot Coretime resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.
// launch your node
Launch Your Private Polkadot Coretime Node
From $199/mo flat, sized to your chain's node specs and typically 30-40% below other providers. Snapshot-ready provisioning, zero setup fees, 24/7 Web3 engineers, no compute units, no rate limits.