Dedicated Polkadot Bridge Hub RPC Node & Polkadot Bridge Hub RPC Endpoint | RedSwitches
// dedicated polkadot bridge hub rpc node

Private Polkadot Bridge Hub RPC Endpoints on a Dedicated Node

A private Polkadot Bridge 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.

Get a QuoteStart Live Chat
  • Private Endpoint, Zero Rate Limits
  • No Compute Units, Unlimited Requests
  • Full & Archive Builds
  • JSON-RPC Over HTTP & WSS
  • Bridge Relayer & Indexer Ready
  • 20+ Global Tier III Locations
deploy.shlive

$ rs deploy bridge-hub --type full --region fra

allocating single-tenant bare metal

restoring bridge-hub snapshot (ParityDB)

syncing parachain + embedded relay chain

serving substrate json-rpc over http + wss

attaching DDoS shield + IP allowlist

private endpoint live · http + wss

region Frankfurt · system parachain 1002 · ~6s blocks

  • UnlimitedRequests
  • ZeroRate Limits
  • 100%Isolation
// why redswitches

Why Teams Run Polkadot Bridge Hub 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.

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 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 binary config, ParityDB vs RocksDB, embedded relay-chain sync, snapshots, and single-thread CPU tuning, handled by people who run Polkadot system-chain 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 Bridge Hub 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 Bridge Hub Full Node

For bridge relayers, wallets & backend APIs

CPU
8 high single-thread cores, 16+ for heavy traffic
RAM
32–64 GB
Storage
200 GB+ NVMe (pruned, grows with state)
Network
1 Gbps+ on a 10/25 Gbps port
Clients
polkadot-parachain (Polkadot SDK) · RocksDB / ParityDB
Best for
  • Current-state reads and transaction submission
  • Snowbridge and XCM relayer message tracking
  • Polkadot.js over WSS subscriptions
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 Bridge Hub documentation.

View official Polkadot Bridge Hub node docs →

Inquiring about: Polkadot Bridge Hub · Full Node

Replies in ~5 minA RedSwitches Web3 engineer specs your private endpoint

No compute units, no rate limits. From $199/mo, flat.

Prefer to talk it through first? Start Live Chat

// why dedicated

Stop Fighting For Bandwidth On Shared Polkadot Bridge Hub RPC

Shared Polkadot Bridge Hub RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Polkadot Bridge Hub 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 Bridge Hub calls the moment traffic spikesZero rate limits, your Polkadot Bridge Hub 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 Bridge Hub 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 Bridge Hub endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Polkadot Bridge Hub 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 Bridge Hub client and tuning you choose
// network details

Polkadot Bridge Hub Node Specifications

The networks, node software, data interfaces, and chain parameters your dedicated Bridge Hub node ships with. Bridge Hub serves the Substrate JSON-RPC over HTTP and WSS, so Polkadot.js and Substrate tooling connect with no changes.

Chain Parameters

Networks
Bridge Hub on Polkadot, Kusama, Paseo, Westend
Type
Polkadot system parachain (para ID 1002)
Native token
DOT (fees)
Consensus
Relay-chain secured · BEEFY + GRANDPA for bridges
Finality
Inherited from the Polkadot relay chain (GRANDPA)
Block time
~6 seconds
Role
Trustless bridges: Snowbridge, Polkadot to Kusama, Hyperbridge
Framework
Substrate / Cumulus (Polkadot SDK)
Archive
Full history (ParityDB) vs pruned full
Explorer
bridgehub-polkadot.subscan.io

Supported Clients

Node software
  • polkadot-parachain (Polkadot SDK)
  • RocksDB / ParityDB
Data interfaces
  • JSON-RPC (HTTP)
  • JSON-RPC (WSS)
  • Polkadot.js API
JSON-RPC methods
  • chain_
  • state_
  • system_
  • author_

Bridge Hub runs no application smart contracts; it hosts the bridge pallets (Bridge GRANDPA, Bridge Parachains, Bridge Messages, XCM Bridge) and on-chain light clients. A Bridge Hub node also runs 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 Bridge Hub Nodes

Where a private, uncapped endpoint beats a shared RPC pool.

Bridge Relayer Operations

Snowbridge and XCM relayers read finality proofs and bridge-message state nonstop. A dedicated Bridge Hub node serves that traffic without shared rate caps, so relayers stay timely during cross-chain congestion.

Cross-Chain Monitoring

Teams tracking Polkadot to Ethereum or Polkadot to Kusama transfers need reliable event reads. Your node powers dashboards and alerting on bridge messages, light-client updates, and delivery confirmations.

Explorer And Indexing

Explorers and indexers run heavy historical queries and process blocks continuously. A dedicated archive node supports long-running ingestion and search of bridge history without shared-endpoint limits.

WebSocket App Streams

Many Substrate apps rely on WSS feeds for live events and UI updates. A dedicated endpoint keeps long-lived subscriptions stable during busy periods, fit for bridge dashboards and notification systems.

Wallet And Backend Reads

Wallet and backend services need fast reads and steady submission for XCM and bridge actions. A dedicated setup avoids congestion-driven timeouts during launches and high-volume transfer windows.

Private Internal RPC

Enterprises want Bridge Hub access without exposing endpoints publicly. Restrict access by IP and network rules for internal apps and partner systems, with a clearer security posture.

// how it works

From Polkadot Bridge Hub To Private Endpoint In 3 Steps

Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.

  1. 01

    Pick Your Bridge Hub Node

    Choose pruned full or archive. We run the polkadot-parachain binary on ParityDB with an embedded relay-chain node; tell us whether you target Polkadot, Kusama, or a testnet, and your region.

  2. 02

    We Provision Bare Metal

    Your single-tenant node deploys on NVMe tuned for single-thread speed, snapshot-synced for both the parachain and relay chain, so you skip the long cold sync.

  3. 03

    Get Your Private Endpoint

    Receive a dedicated 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 Bridge Hub 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 Bridge 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.

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.

// customer reviews

Trusted To Run Production Nodes

Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.

  • 4.8/525Gbps Bare Metal
    Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
    Felix MartinsenDenmark
  • 5.0/5VPN 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.
    TomasNetherlands
  • 4.8/5Validators
    Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
    Peppe TerranovaSouth Korea
  • 5.0/5Full 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.
    Eun-Woo GimSouth Korea
  • 5.0/5Enterprise 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.
    AppsLabGermany
  • 5.0/5Cloud 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.
    Princeton OttUnited States
  • 5.0/599.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.
  • 5.0/5ETH & BTC Nodes
    Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
    Ervin KaruGermany
  • 5.0/510Gbps 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.
    Atri MukherjeeIndia
  • 5.0/5Streaming
    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.
    Tarun GhoshIndia
  • 5.0/5Bare 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.
    Борис ВербицкийPoland
  • 5.0/5AI 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.
    Henry HarrisonUnited States
  • 5.0/5Switched 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.
    Samual SuttonUnited Kingdom
  • 5.0/5Game 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.
    Jerold PerkinsUnited States
  • 5.0/5AI 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.
    Eino KoppelEstonia
  • 4.8/5Support
    Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
    Boniface LeandreUnited States
  • 5.0/5Instant Delivery
    They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
    Daniel StuartSri Lanka
  • 5.0/5Fast 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.
    Ярослав СавенковNetherlands
  • 5.0/55+ 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).
  • 5.0/51 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.
    Sandip PanditIndia
  • 5.0/5Reliability
    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.
    CandiceUnited States
  • 4.8/5Global 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.
    Tiberiu RomanUnited States
  • 5.0/5Exam 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.
    Mridul MehtaIndia
  • 5.0/5Bare 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!
  • 5.0/5Zero 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.
    Amit BhatiaIndia
  • 5.0/524/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.
    LukaSlovenia
  • 5.0/5Since 2021
    We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
    Eitan WaisgerberIsrael
  • 5.0/5Easy 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.
    Birk SpillumNorway
  • 5.0/5Bare 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 Polkadot Bridge Hub and why run a dedicated RPC node for it?

Bridge Hub is a Polkadot system parachain (para ID 1002) that hosts Polkadot's trustless bridges, including Snowbridge to Ethereum and the Polkadot to Kusama bridge, using on-chain light clients and BEEFY and GRANDPA proofs. It is not a standalone Layer 1. A dedicated Bridge Hub RPC node gives relayers, indexers, and monitoring tools a private, uncapped endpoint to read bridge-message state and finality data without shared rate limits.

Which Bridge Hub node type do I need: pruned RPC or archive RPC?

Most teams start with a pruned Bridge 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 on bridge messages, or support heavy historical lookups. If you are unsure, tell us your workload and we will map you to the right node type.

Can I run a Snowbridge or XCM relayer against your Bridge Hub node?

Yes. A dedicated Bridge Hub node exposes the Substrate JSON-RPC over HTTP and WSS that relayers use to read finality proofs, light-client updates, and bridge-message state. You get full root access, so you can colocate relayer software or point an external relayer at your private endpoint with IP allowlisting.

Does a Bridge Hub node also sync the Polkadot relay chain?

Yes. As a parachain node, the polkadot-parachain binary runs an embedded relay-chain node alongside the Bridge Hub collator/full node, so it tracks relay-chain finality to validate parachain blocks. We provision and snapshot both layers so your node reaches a usable head without a multi-day cold sync.

Can I use Polkadot.js with your endpoint, and do you support WSS WebSocket connections?

Yes. Most developers use Polkadot.js over WebSocket for subscriptions and real-time updates. Your dedicated Bridge Hub RPC node can expose WebSocket endpoints for app usage, and you can keep them private or public based on your access model. For tighter control, restrict access by IP and allow only trusted clients.

What hardware specs do you recommend for low-latency Bridge Hub RPC at scale?

For production Bridge Hub RPC you need fast NVMe storage, sufficient 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 128 GB RAM as concurrency rises. Archive RPC requires larger NVMe capacity and more cache headroom, as historical queries and indexing are storage and memory intensive.

Can I scale CPU, RAM, and NVMe as traffic grows without changing providers?

Yes. That is a core benefit of running a dedicated Bridge 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 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 Bridge Hub Developer Resources

Official Polkadot Bridge 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.

// launch your node

Launch Your Private Polkadot Bridge Hub 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.

Get a QuoteStart Live Chat