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.
A private Polkadot Asset Hub RPC endpoint on single-tenant NVMe bare metal. Full or archive nodes serve the Substrate JSON-RPC over HTTP and WSS, with zero rate limits and no compute units.
$ rs deploy asset-hub --type full --region fra
allocating single-tenant bare metal
syncing polkadot-parachain (asset-hub-polkadot)
tracking the polkadot relay chain
serving substrate json-rpc over http + wss
attaching ddos shield + ip allowlist
private endpoint live · http + wss
A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.
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.
A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.
Talk to the engineers who run the metal. The polkadot-parachain binary config, the asset-hub-polkadot chain spec, ParityDB pruning, relay-chain sync, and snapshot restores, handled by people who run Polkadot system parachains daily.
Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.
Settle in crypto or fiat, DOT included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.
Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.
Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.
For wallets, exchanges & asset backends
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 Asset Hub documentation.
View official Polkadot Asset Hub node docs →For explorers, indexers & analytics
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 Asset Hub documentation.
View official Polkadot Asset Hub node docs →Thanks. A Web3 engineer will spec your private endpoint and reach out shortly.
Something went wrong. Please try again or email sales@redswitches.com.
Shared Polkadot Asset Hub RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Polkadot Asset Hub node is your own private backbone: flat-priced, uncapped, and yours alone.
The networks, node software, data interfaces, and chain parameters your dedicated Polkadot Asset Hub node ships with. Asset Hub serves the Substrate JSON-RPC over HTTP and WSS, so Polkadot.js and Substrate tooling connect with no changes.
Asset Hub is a Polkadot system parachain, not a standalone Layer 1; it inherits security and finality from the Polkadot relay chain, which your node also tracks. Keep your endpoint private behind IP allowlisting and a reverse proxy, and keep admin RPC closed.
Where a private, uncapped endpoint beats a shared RPC pool.
Wallet services need fast asset reads and steady submission. Your Asset Hub endpoint serves balances, asset metadata, fee estimation, and broadcast, so a dedicated node avoids congestion-driven timeouts during launches.
Exchanges track Asset Hub deposits and withdrawals across DOT and listed assets. Your node becomes the backbone for confirmations, alerting, and withdrawal automation, with tighter internal access control for finance-grade operations.
Projects minting, burning, and transferring fungible or NFT assets need reliable RPC for the Assets and Uniques pallets. A dedicated node keeps issuance and admin-role operations responsive without shared-pool throttling.
Explorers and indexers run heavy historical queries and process blocks nonstop. A dedicated archive node supports long-running ingestion and asset-history search without shared-endpoint limits, fit for repeatable data access.
Many Asset Hub apps rely on WSS feeds for live events and UI updates. A dedicated endpoint keeps long-lived connections stable during busy periods, fit for dashboards and real-time notification systems.
Teams moving assets between Asset Hub and other parachains via XCM need dependable reads on both ends. Your node serves state and transaction status when timing matters, where shared endpoints cause failed or delayed transfers.
Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.
Choose pruned full or archive. We run the polkadot-parachain binary on ParityDB; tell us your region and whether you also need a relay-chain RPC alongside.
Your single-tenant node deploys on NVMe tuned for single-thread speed, snapshot-restored and synced against the asset-hub-polkadot chain spec, so you skip the long cold sync.
Receive a dedicated JSON-RPC endpoint over HTTP and WSS with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.
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.
Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Polkadot Asset Hub node in the region your traffic actually comes from, not wherever a shared pool happens to route you.
RPC latency is mostly physical distance. Running in the same region as your users and the Polkadot Asset Hub 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.
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.
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.
Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.
Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
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.
Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
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.
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.
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.
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.
Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
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.
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.
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.
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.
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.
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 is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
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.
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).
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.
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.
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.
"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.
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!
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.
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.
We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
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.
Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.
Asset Hub is a Polkadot system parachain, not a standalone Layer 1. It is a specialized chain for creating, managing, and transferring fungible and non-fungible assets with low fees, filling the gap left by the relay chain, which does not natively handle assets beyond DOT. Security and finality are inherited from the Polkadot relay chain, which your node also tracks. You run it with the polkadot-parachain binary, the same way you run any Cumulus system chain.
Most teams start with a pruned Asset Hub node because it serves current state reads and transaction submission with far lower storage needs. Choose archive RPC when your product must query full history, power explorers, run deep analytics, or support heavy historical asset lookups. If you are unsure, tell us your workload, and we will map you to the right node type.
A shared Asset Hub RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Asset Hub 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. An Asset Hub node already tracks the Polkadot relay chain for security and finality, and many stacks also want a dedicated relay-chain RPC for operations and ecosystem tooling. We can deploy Asset Hub RPC, relay-chain RPC, or both, and separate the roles so one workload does not interfere with the other.
Yes. Most developers use Polkadot.js over WebSocket for subscriptions and real-time updates. Your dedicated Asset Hub 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.
Provisioning is fast. The real variable is sync time, which depends on chain state, node type, storage speed, and network conditions. A pruned RPC usually reaches a usable state earlier than an archive setup because an archive has far more data to process. We deploy from current snapshots where possible, so you are not sold a fake instant promise.
For production Asset Hub 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 pruned RPC, then scale to 16+ cores and more RAM as concurrency rises. You can expose the standard Substrate RPC and WebSocket ports, restrict them to known IPs, and put a reverse proxy in front, keeping admin surfaces closed on your dedicated server.
Yes. That is a core benefit of running a dedicated Asset Hub 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.
Official Polkadot Asset Hub resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.
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.