Polygon Dedicated RPC Node
Polygon PoS is a proof-of-stake EVM network run by POL-staking validators, with Heimdall-v2 for consensus and Bor for execution. Argusnodes runs it for you on bare metal that is only yours: no rate limits, every method on, one flat monthly price. Configure it below and a firm quote lands within the hour.
Everything your Polygon node needs. Nothing sold as an add-on.
- No rate limits: the hardware is the only ceiling
- Every RPC method on, debug and trace included
- Unlimited WebSocket connections
- Your own domain and an IP allowlist you control
- 18 Tier-3 datacentre cities, you pick
- 99.99% SLA in writing, with service credits
- 24/7 support answered by engineers
- Live p50 and p99 for your node in the dashboard
- Card, bank transfer or crypto; monthly, cancel any month
Configure your Polygon node. Firm price within the hour.
Pick the node type, client, tuning and region. The figure shown is the band's starting price; your quote is a firm, flat monthly number for exactly this configuration, around the clock.
Prefer to talk first? Reach an engineer on any support channel: same one-hour promise. Band pricing is explained on the pricing page.
What your Polygon dedicated node is built from.
Every row below is taken from Polygon's official documentation (docs.polygon.technology), last reviewed against it on 22 Aug 2026, not from what is convenient to sell. Where the documentation is silent, the row says so.
| Node software | Heimdall-v2, Bor, Erigon |
| Interfaces | JSON-RPC, WebSocket |
| Full node | Yes, from $349/mo (performance band) |
| Archive node | Yes, from $799/mo |
| Validator | Public validator role; quoted per setup. Staking-based role capped at 105 active validators (minimum 10,000 POL); new validators join by application when a slot opens, and a slot is not guaranteed. |
| Chain ID | 137 |
| Gas token | POL |
| Consensus | Proof-of-stake: Heimdall-v2 (CometBFT) consensus + Bor execution |
| Block time | 1 to 2 second Heimdall block times per official docs |
| Finality | 2 to 5 seconds via milestones; checkpoints anchor to Ethereum |
| Official hardware guidance | Polygon's prerequisites page lists mainnet full/sentry nodes at 8 core / 16 core CPU, 32 GB / 64 GB RAM and 4 TB / 6 TB storage (validator nodes the same), and an Erigon archive node at 16 core, 64 GB RAM and 16 TB storage (RAID), all with 1 Gbit/s network; the snapshot guide puts extracted mainnet data at 4 TB (Bor) + 500 GB (Heimdall), growing about 105 GB per day, with 8 TB disk suggested. source ↗ |
| Operator note | Official docs recommend snapshot sync (mainnet snapshots roughly 4.5TB extracted, 8TB disk suggested), 32 to 64GB RAM and 4 to 6TB storage for full nodes, 16TB for an Erigon archive. |
| Locations | 18 Tier-3 cities across North America, Europe, Asia-Pacific |
| SLA | 99.99% uptime, written, with credits |
What changed on Polygon recently (reviewed 22 Aug 2026)
- Heimdall v1 was replaced by Heimdall-v2 on mainnet on July 10, 2025 (new chain ID, CometBFT + Cosmos SDK v0.50, finality ~5 s); Heimdall API endpoint structure changed, so third-party integrations needed updating. source ↗
- Rio upgrade (October 8, 2025) introduced Validator-Elected Block Producers (VEBloP), witness-based stateless validation and reorg elimination, aimed at ~5k TPS and lighter node hardware. source ↗
- Full nodes must run Bor v2.0+ and Heimdall-v2 v0.2+; the erigon archive guide still pins Erigon v2.57.3. source ↗
Choosing the Polygon client for the workload.
Polygon's documentation covers 3 node clients. You name the client, or describe the workload and we recommend one; either way it is built, synced and tuned for you.
The consensus client (fork of Cosmos SDK v0.50 and CometBFT v0.38) that manages validators, spans, checkpoints and state sync; must run alongside Bor on every full node.
The execution client (v2.0+) that produces and serves EVM blocks and exposes the JSON-RPC/WebSocket API (--http 8545, --ws 8546).
The documented archive-node client (erigon --chain=bor-mainnet --db.size.limit=12TB, v2.57.3), needing 16 cores, 64GB RAM and ~15TB NVMe with 20k+ IOPS; remote Heimdall is not recommended in production.
What to order for your Polygon workload.
Each card is a configuration you can pick above, with the reason it fits.
Trading bots and MEV
Order: Full node · WebSocket on · bot/MEV tuning · city nearest Polygon's block producers
Burst as hard as the strategy needs. No rate limits and no noisy neighbours on the hot path; we pick the city from latency measurement, not a map.
BUILT FOR BOTS →Indexing and analytics
Order: Archive node from $799/mo · indexing tuning
Backfills, trace and historical queries on Polygon run unmetered on your own machine.
BUILT FOR INDEXERS →dApps and wallets
Order: Full node · your domain · IP allowlist · city near your users
Serve your users from your own Polygon endpoint with unlimited connections and a 99.99% SLA in writing.
WHY DEDICATED →Exchanges and payments
Order: Full node · IP allowlist · transaction-heavy tuning · per-node monitoring
Deposit and withdrawal scanning on Polygon from an endpoint only your systems can reach.
BUILT FOR EXCHANGES →Staking and validator ops
Order: Validator setup, quoted · same 24/7 watch as RPC nodes
Polygon has a public validator role. Tell us the stake setup and we quote the machine and the operations.
CONFIGURE A VALIDATOR →The Polygon RPC node provider comparison: Argusnodes vs QuickNode vs Chainstack vs Helius vs Allnodes vs Zeeve vs RPC Fast.
Which providers actually sell a dedicated Polygon node, and on what terms. Every competitor cell was read from that provider's own public pages; sources are linked below the table.
| Provider | Dedicated Polygon node | Dedicated offering | Pricing model | Rate limits | Support |
|---|---|---|---|---|---|
| Argusnodes | Yes, from the standard bands, quoted in an hour | Dedicated only: bare metal, single tenant, every node | One flat monthly price, nothing metered | None. The hardware is the only ceiling | 24/7 engineers on ticket, chat, Telegram, Slack. No paid tier |
| QuickNode | Shared yes; dedicated not published | Dedicated Clusters, an Enterprise add-on: two or more nodes of one chain, isolated, at a fixed monthly rate | API credits per method call, monthly allotments plus overage | 15 to 500 requests/sec by plan (Free through Business+); "Custom RPS" on Enterprise | Ticket support with 24h to 8h SLAs by plan; priority support is a paid add-on on Business+; dedicated support on Enterprise |
| Chainstack | Yes | Managed dedicated nodes, single tenant, from the Pro plan up | Request Units per API call, monthly quotas plus overage | 25 to 600 requests/sec by plan; unlimited on Enterprise | Priority support is paid: $100/mo Professional, $1,000/mo Premium |
| Helius | No, Solana-only platform | Dedicated Solana nodes from $2,900/mo; Solana only | Credits, monthly allotments per plan | 10 to 500 requests/sec by plan, plus sendTransaction/sec caps; no rate limits on dedicated nodes | Chat on paid plans; Telegram and Slack from the $999/mo plan up |
| Allnodes | No | Per-node plans; a dedicated server on the Enterprise tier of its EVM chains and on every Solana tier | Per-node monthly plans, tiered by server type (shared, VPS or dedicated) | Advertises unlimited requests on its Base, BSC, Arbitrum and OP Mainnet node plans; not stated for other chains | Basic, priority or high-priority support by tier |
| Zeeve | Yes | Dedicated RPC plans: $149, $299, $599 per month billed monthly (25% less on annual) | Monthly plans with request allowances: 250M/mo Basic, 2B/mo Advance; unmetered only on Enterprise | Monthly request caps on dedicated plans below Enterprise; no requests/sec figure published | Premium on Basic; priority support and Telegram/Slack from the $299/mo plan up; account manager on Enterprise |
| RPC Fast | Yes, as a cluster from $2,000/mo plus infrastructure costs | Dedicated Solana in three tiers from $2,200/mo (their dedicated-nodes page says from $2,500); other chains as node clusters from $2,000/mo plus infrastructure costs | Shared plans on compute units with overage at $5 per 1M CU; dedicated priced per node or cluster | 15 to 500 requests/sec plus WebSocket caps on shared plans; the Pro dedicated Solana tier says no rate limits | Community on free; email with 24h and 12h SLAs; priority chat with 8h SLA from the $499/mo plan |
Competitor facts read from each provider's own public pricing and documentation pages, August 2026: QuickNode · Chainstack · Helius · Allnodes · Zeeve · RPC Fast. Their terms can change; check their pages for current figures. Spot an error? Tell us and we will fix it the same day. Provider names link to the full comparison.
The Polygon RPC node endpoint provider that hands you the keys.
Your Polygon endpoint lives on your own domain, locked to the IPs you allowlist, served from the city you choose across 18 Tier-3 datacentre locations. The node exposes JSON-RPC, WebSocket as documented by Polygon. Live p50 and p99 latency for your node streams to your dashboard, and the 99.99% SLA applies in writing. New to dedicated nodes? The dedicated RPC node guide covers the model end to end.
Chain facts on this page are sourced from Polygon's official documentation, and you can check them yourself:
Polygon dedicated node: the questions buyers ask.
How long until my Polygon node is live?
A firm quote lands within the hour, around the clock. Go-live depends on Polygon's sync characteristics for your configuration and the client you pick (Heimdall-v2, Bor, Erigon); your quote includes a go-live estimate for exactly that setup rather than a number that is sometimes wrong.
What is included in the from $349/mo for my Polygon node?
Everything the node can do: no rate limits, every RPC method including debug and trace, unlimited WebSocket connections, your own domain with an IP allowlist, 18 cities to choose from, a 99.99% SLA with credits, 24/7 engineer support and live p50/p99 in your dashboard. There is no add-on price list because nothing is an add-on.
Which Polygon client should I choose?
Heimdall-v2: The consensus client (fork of Cosmos SDK v0.50 and CometBFT v0.38) that manages validators, spans, checkpoints and state sync; must run alongside Bor on every full node. Bor: The execution client (v2.0+) that produces and serves EVM blocks and exposes the JSON-RPC/WebSocket API (--http 8545, --ws 8546). Erigon: The documented archive-node client (erigon --chain=bor-mainnet --db.size.limit=12TB, v2.57.3), needing 16 cores, 64GB RAM and ~15TB NVMe with 20k+ IOPS; remote Heimdall is not recommended in production.
Does Argusnodes run Polygon archive nodes and trace methods?
Yes. Polygon's documentation describes full-history operation; we run Polygon archive nodes from $799/mo with trace and historical queries unmetered. Debug and trace methods are on for full nodes too, within their state window.
Can I run a Polygon validator with Argusnodes?
Yes. Polygon has a public validator role (Staking-based role capped at 105 active validators (minimum 10,000 POL); new validators join by application when a slot opens, and a slot is not guaranteed), and we operate validators under the same monitoring and support as RPC nodes, quoted per setup. Pick "Validator" in the configurator and describe the stake setup.
Can I migrate my Polygon endpoint from QuickNode, Chainstack or another provider?
Yes. A dedicated Polygon node speaks the same JSON-RPC and WebSocket interfaces as the shared endpoint you use today, so migration is pointing your application at your own endpoint. Billing is monthly with no lock-in on our side, and support engineers are on the channels 24/7 during cutover.
Which city should I pick for my Polygon node?
Any of 18 Tier-3 datacentre cities across North America, Europe, Asia-Pacific. Deploy near your users for an app, or ask us where Polygon latency is lowest for a bot; we answer from measurement. Need a city we do not list? Ask.
Are there rate limits or connection caps on a dedicated Polygon node?
No artificial ones. The machine is yours alone, so the hardware is the only ceiling: if it can serve the request, you can send it. There is no per-plan connection cap because there is no plan tier.
How do I pay for my Polygon node, and can I cancel?
Visa, Mastercard, bank transfer or crypto, billed monthly. Cancel at the end of any monthly term; the node is provisioned for you alone, so there is no meter to escape and no exit fee.
How does Argusnodes compare to QuickNode, Chainstack and other Polygon RPC providers?
Argusnodes is dedicated-only: a bare-metal Polygon node with no rate limits at one flat price from $349/mo. As of August 2026, per their own pricing pages: QuickNode sells dedicated clusters through enterprise sales without published prices, Chainstack bills dedicated nodes per hour on top of a paid plan, and Zeeve applies monthly request allowances on dedicated plans below its Enterprise tier. The comparison table on this page links every source.
Also deployed from the same sheet.
Configure your Polygon node.
Node type, tuning, region. Firm quote within the hour, one flat monthly price.