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 polygon pos rpc node
Private Polygon PoS RPC Endpoints on a Dedicated Node
A private Polygon PoS RPC endpoint on single-tenant bare metal. Full, archive, or validator builds on the Heimdall + Bor stack, with zero rate limits and no compute units.
- Private Endpoint, Zero Rate Limits
- No Compute Units, Unlimited Requests
- Full, Archive & Validator Builds
- Heimdall + Bor, Erigon Archive
- 20+ Global Tier III Locations
deploy.shlive
$ rs deploy polygon --type full --region fra
allocating single-tenant bare metal
restoring bor + heimdall snapshot
starting heimdall consensus
starting bor evm execution
attaching DDoS shield + IP allowlist
private endpoint live · https + wss
- UnlimitedRequests
- ZeroRate Limits
- 100%Isolation
// why redswitches
Why Teams Run Polygon PoS 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. Heimdall + Bor config, Erigon archive, sentry topology, and IOPS tuning, handled by people who run Polygon 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. 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, with sentry-first isolation, designed and tuned by our engineers.
// request your endpoint
Configure Your Polygon PoS 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
Polygon PoS Full Node
For dApps, wallets, bots & indexers
- CPU
- 8–16 high-clock cores
- RAM
- 32–64 GB
- Storage
- 2.5–4 TB NVMe (6 TB recommended, grows)
- Network
- 1 Gbit/s+ on a 10/25 Gbps port
- Stack
- Heimdall consensus + Bor execution
Best for
- eth_getLogs, receipts, and contract reads
- Latency-sensitive DeFi bots and indexers
- Private HTTP and WebSocket 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 Polygon PoS documentation.
View official Polygon PoS node docs →Polygon PoS Archive Node
For deep history, tracing & compliance
- CPU
- 16–32 high-clock cores
- RAM
- 64–128 GB
- Storage
- ~6 TB NVMe (Erigon); 16 TB+ class SSD (Bor)
- Network
- 1 Gbps
- Stack
- Heimdall + Bor, Erigon for archive queries
Best for
- Older-block eth_call and analytics backfills
- Long-range log scans and trace_ workloads
- Historical state at any block height
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 Polygon PoS documentation.
View official Polygon PoS node docs →Polygon PoS Validator Node
For staking & consensus operations
- CPU
- 8–16 high-clock cores
- RAM
- 64–128 GB
- Storage
- 2.5–4 TB NVMe
- Network
- 1 Gbit/s+ symmetric
- Stack
- Heimdall + Bor + a private sentry node
Best for
- Staking with sentry-first topology
- Core node kept private off the public edge
- You hold the keys, we run the metal
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 Polygon PoS documentation.
View official Polygon PoS 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 Polygon PoS RPC
Shared Polygon PoS RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Polygon PoS 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 Polygon PoS calls the moment traffic spikesZero rate limits, your Polygon PoS 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 Polygon PoS 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 Polygon PoS endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Polygon PoS 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 Polygon PoS client and tuning you choose
// network details
Polygon PoS Node Specifications
The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated Polygon PoS node ships with. Built to a standard so your existing tooling connects with no changes.
Chain Parameters
- Networks
- Polygon PoS (Mainnet), Amoy testnet
- Chain IDs
- Mainnet 137 · Amoy 80002
- Native token
- POL
- Consensus
- Proof of Stake, checkpoints to Ethereum
- Stack
- Heimdall (consensus) + Bor (EVM execution)
- Block time
- ~2 seconds
- Transports
- HTTPS (8545) and WebSocket (8546)
- Archive
- Full historical state (Erigon recommended; Bor larger)
- Explorer
- polygonscan.com
Supported Clients
Node stack
- Heimdall
- Bor
- Erigon (archive)
JSON-RPC Namespaces
- eth_
- net_
- web3_
- debug_
- txpool_
- bor_
You control which namespaces are exposed. Enable debug and trace on archive builds, keep the rest private behind IP allowlisting.
// use cases
What Teams Build On Polygon PoS Nodes
Where a private, uncapped endpoint beats a shared RPC pool.
DeFi Bot Execution
Swaps and arbitrage without shared throttles. A dedicated Polygon node keeps nonce reads, fee estimates, and call simulations steady during volatility.
Indexer Event Pipelines
Scan blocks, logs, and contract events all day with predictable throughput. Dedicated nodes stay consistent during backfills and reorg handling when disk reads spike.
Explorer Search Backends
Serve explorer pages and search APIs that never stop reading. Full covers latest blocks; pair with an Erigon archive so old-state queries do not time out under load.
Wallet API Reliability
Wallet flows need fast balances, transfers, nonce checks, and receipts. Private RPC removes the rate-limit errors that break user actions at the worst moment.
WebSocket Log Feeds
Stream logs and subscriptions for alerts and bots without falling over on reconnect bursts. Stable storage reads keep WS feeds healthy; keep them private.
Multi-Region Read RPC
Place read nodes near users and app servers. One primary for writes plus regional readers absorbs spikes, scaling cleanly on dedicated servers.
// how it works
From Polygon PoS 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 Polygon Node
Choose full, archive, or validator. We run the Heimdall + Bor stack (Erigon for archive); tell us the region closest to your users.
- 02
We Provision Bare Metal
Your single-tenant Heimdall + Bor node deploys on high-IOPS NVMe, snapshot-bootstrapped, so you skip the long sync.
- 03
Get Your Private Endpoint
Receive a dedicated HTTPS + WSS RPC URL 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 Polygon PoS 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 Polygon PoS 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.
Why choose Dedicated Polygon RPC Nodes instead of public RPC?
Public RPC endpoints share capacity across unknown tenants. You can hit rate limits, sudden latency jumps, and intermittent method restrictions during busy periods. With dedicated Polygon RPC nodes, you control compute, memory, disk, and network for your own workload. Your app stops competing for shared resources, so reliability becomes an engineering choice, not luck.
What is a Polygon PoS RPC node?
A Polygon PoS RPC node is the infrastructure your app calls to read blockchain data and broadcast transactions. It serves JSON-RPC methods used by wallets, dApps, indexers, and bots. A dedicated setup gives you your own RPC endpoint, so your reads, writes, subscriptions, and indexing load do not depend on public gateways.
Do I need to run both Heimdall and Bor for Polygon RPC nodes?
Yes. Polygon PoS is a two-service stack. Heimdall handles checkpointing and validator coordination. Bor executes EVM transactions and tracks the chain head for RPC reads and writes. A real dedicated Polygon node runs both services correctly and keeps them compatible. If either service drifts, your RPC can look up but still serve stale or inconsistent results.
Full node vs archive node: which one should I deploy?
Start with a full node if your product needs current balances, receipts, logs for recent ranges, and normal contract reads. Choose an archive node when you need historical state at older block heights, long-range log scans, or analytics that query deep history. Many teams use a full node for production RPC and add an archive node later for research, compliance, or advanced indexing.
When do I need an Erigon archive node on Polygon?
You need Erigon archive when history becomes a product feature, not a one-off task. Examples include explorers, analytics dashboards, compliance exports, long backfills, and apps that query historical state at specific blocks. Archive mode adds major storage and I/O demands, so it fits best on dedicated Polygon RPC nodes where you can size disk and IOPS for sustained history queries.
Which RPC methods stress Polygon nodes the most?
The biggest stressors are wide-range eth_getLogs, heavy eth_call workloads that touch many contracts, tracing and debug methods, and high-frequency WebSocket subscriptions. These calls drive random reads and database pressure. A dedicated Polygon RPC node provider should plan for this by sizing NVMe IOPS, RAM headroom, and network capacity for your real query patterns.
Why do NVMe and high IOPS matter for Polygon RPC performance?
Polygon RPC is read-heavy and random-read heavy. Calls like contract reads, receipts, and log scans hit the database constantly. Low IOPS disks create slow calls, timeouts, and long catch-up windows after restarts. NVMe with strong IOPS keeps state access responsive and reduces the "node is online but unusable" problem that teams see on under-sized disks.
Do I need a sentry node, and what topology should I use?
If you care about uptime and security, yes. A sentry-first topology keeps public P2P exposure on the sentry node, while your core node stays private. This reduces the attack surface and keeps your RPC and signing surfaces away from the open internet. It also makes incident response cleaner because you can rotate exposure without touching the core node.
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
Polygon PoS Developer Resources
Official Polygon PoS 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 Polygon PoS 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.