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 bitcoin rpc node
Private Bitcoin RPC Endpoints on a Dedicated Node
A private Bitcoin RPC endpoint on single-tenant NVMe bare metal. Full or archive (txindex) nodes serving the Bitcoin Core JSON-RPC, REST, and ZMQ interfaces, with zero rate limits and no compute units.
- Private Endpoint, Zero Rate Limits
- No Compute Units, Unlimited Requests
- Full & Archive (txindex) Builds
- JSON-RPC, REST & ZMQ Interfaces
- NVMe Tuned For UTXO Reads
- 20+ Global Tier III Locations
deploy.shlive
$ rs deploy bitcoin --type full --region fra
allocating single-tenant bare metal
restoring bitcoind snapshot
verifying blocks to chain tip
serving json-rpc + rest + zmq
attaching DDoS shield + IP allowlist
private endpoint live · json-rpc + rest + zmq
- UnlimitedRequests
- ZeroRate Limits
- 100%Isolation
// why redswitches
Why Teams Run Bitcoin 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. Bitcoin Core (bitcoind) config, the txindex versus pruning tradeoff, ZMQ notifications, and UTXO read tuning, handled by people who run Bitcoin 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, BTC 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 Bitcoin 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
Bitcoin Full Node
For wallets, payments, bots & backend APIs
- CPU
- 4–8 high-clock cores
- RAM
- 16–32 GB
- Storage
- 1–2 TB NVMe (pruned 200 GB–1 TB)
- Network
- 10/25 Gbps uplink, metered or unmetered
- Stack
- Bitcoin Core (bitcoind), full or pruned
Best for
- Wallet UTXO checks, balances, and broadcasts
- Payment confirmation and mempool tracking
- Private JSON-RPC over HTTP and HTTPS
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 Bitcoin documentation.
View official Bitcoin node docs →Bitcoin Archive Node
For explorers, analytics & deep tx lookups
- CPU
- 8–16 high-clock cores
- RAM
- 32–64 GB
- Storage
- 2–4 TB NVMe (txindex=1, no pruning)
- Network
- 10/25 Gbps uplink, unmetered for backfills
- Stack
- Bitcoin Core (bitcoind) with txindex=1
Best for
- Historical tx lookups by txid at scale
- Explorer, indexer, and analytics backfills
- Compliance and audit query workflows
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 Bitcoin documentation.
View official Bitcoin 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 Bitcoin RPC
Shared Bitcoin RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Bitcoin 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 Bitcoin calls the moment traffic spikesZero rate limits, your Bitcoin 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 Bitcoin 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 Bitcoin endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Bitcoin 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 Bitcoin client and tuning you choose
// network details
Bitcoin Node Specifications
The networks, node software, data interfaces, and execution model your dedicated Bitcoin node ships with. Bitcoin Core exposes the JSON-RPC API alongside REST and ZMQ, not EVM-style namespaces.
Chain Parameters
- Networks
- Mainnet, Testnet, Signet
- Native token
- BTC
- Consensus
- Proof of Work (SHA-256)
- Block time
- ~10 minutes (target)
- Finality
- Probabilistic (~6 confirmations)
- Execution
- Script (no smart contracts)
- Supply
- Capped at 21M BTC, halving every ~210,000 blocks
- Archive
- Full node + txindex=1 (no pruning)
- Default ports
- P2P 8333 · RPC 8332
- Explorers
- mempool.space · blockstream.info
Supported Clients
Node software
- Bitcoin Core (bitcoind)
- Bitcoin Knots
Data interfaces
- JSON-RPC
- REST
- ZMQ
Keep your endpoint private behind IP allowlisting and firewall rules. Bitcoin Core has no eth_*-style namespaces: integrate over JSON-RPC for queries and broadcasts, REST for read paths, and ZMQ for block and mempool notifications.
// use cases
What Teams Build On Bitcoin Nodes
Where a private, uncapped endpoint beats a shared RPC pool.
Wallet RPC Backends
Run your wallet on a dedicated Bitcoin RPC node serving UTXO checks, balances, fee estimation, and broadcasts. Dedicated CPU, RAM, and NVMe keep reads steady, with no shared rate caps to break send flows at peak.
Payment Confirmation Tracking
Confirm payments with consistent access to blocks, headers, and mempool state. Your backend watches confirmations, detects stuck transactions, and triggers fulfillment without delay, even when customers refresh status nonstop and checkout traffic spikes.
Exchange Deposit Systems
Power deposit and withdrawal workflows on a dedicated Bitcoin RPC node you control. Isolate RPC access, tune headroom, and schedule updates safely, cutting outage risk from third-party policy changes and keeping hot wallet operations stable under load.
Explorer API Services
Serve block, transaction, and mempool queries for explorer pages and search APIs. An indexed txindex build supports deep historical lookups, while NVMe and cache headroom reduce timeouts during major events and news-driven traffic surges.
Indexer Data Pipelines
Build pipelines that scan new blocks, backfill history, and feed analytics stores without public endpoints. Dedicated compute and storage improve catch-up after downtime, fitting ETL jobs and monitoring tools that need predictable reads and repeatable reprocessing.
Mempool Monitoring Feeds
Track mempool changes for fee markets, replace-by-fee behavior, and broadcast success checks. Dedicated infrastructure helps when mempool churn is high and your services poll frequently, holding stable response times when shared providers throttle.
// how it works
From Bitcoin 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 Bitcoin Node
Choose a full node for wallets and payments or an archive (txindex) build for explorers and deep lookups; tell us the region closest to your users.
- 02
We Provision Bare Metal
Your single-tenant Bitcoin Core (bitcoind) deploys on NVMe, snapshot-bootstrapped so you skip the multi-day cold sync and block verification.
- 03
Get Your Private Endpoint
Receive a dedicated JSON-RPC, REST, and ZMQ endpoint 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 Bitcoin 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 mining pools 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.
How do I connect my app to your dedicated Bitcoin RPC node?
You connect over HTTP or HTTPS using the RPC host, port, username, and password you set in Bitcoin Core. Most teams keep RPC private and allow access only from their application servers. If you need public access, use an allowlist and strict authentication. This setup gives you stable access to your Bitcoin RPC node without relying on shared endpoints.
Can I run a Bitcoin validator node?
No, and not because we do not offer it. Bitcoin uses Proof of Work mining, not Proof of Stake, so there is no staking validator to run. New blocks are produced by miners using ASIC hardware and a power strategy, which is a separate activity we do not provide. What we provision is what apps actually need: a fast, dedicated full or archive RPC node running Bitcoin Core, with txindex available for historical transaction lookups by txid.
Do you offer full, pruned, and indexed Bitcoin Core node builds?
Yes. RedSwitches supports full nodes, pruned nodes, and indexed builds on a dedicated Bitcoin RPC node server. Full nodes fit most production apps. Pruned nodes reduce disk usage when you only need validation and recent chain data. Indexed builds (txindex=1) fit advanced lookup workloads.
Do you support txindex=1 for historical transaction lookups?
Yes. We can deploy a node with txindex=1 when your application needs historical transaction retrieval by txid. This is common for explorers, analytics pipelines, and backfills. It requires more storage and time to build the index, so we treat it as a workload choice, not a default. Note that pruning and txindex cannot be used together.
Can I run a pruned node, and what RPC limitations come with pruning?
Yes, pruning is supported. A pruned node validates the full chain but keeps only a limited set of recent blocks on disk. The tradeoff is that some historical lookups may not work because old blocks are removed. If your product depends on long-range history, use a full node or an indexed build instead.
Which ports must be opened for RPC and peer-to-peer connectivity?
Bitcoin peer-to-peer connectivity typically uses port 8333 for mainnet. Bitcoin Core's default RPC is 8332, unless you change it. Best practice is to keep RPC private and allow only specific IPs or a private network path. This approach reduces abuse risk for your dedicated Bitcoin RPC node.
Do you support ZMQ notifications for blocks and transactions?
Yes. Many teams use ZMQ to react to new blocks and mempool events without constant polling. It is a clean way to power confirmation tracking and real-time pipelines. If you want ZMQ enabled, we can deploy with the right configuration and network rules based on your architecture.
How long does initial sync take, and what affects sync time?
We provision from current snapshots, so your node is typically live and serving in hours rather than syncing from genesis for days. Sync time otherwise depends on storage speed, CPU, RAM cache, peer connectivity, and whether you enable indexing. NVMe improves the experience, and an indexed build takes longer because it builds additional database structures. If you need a node ready by a specific deadline, we size hardware around that requirement.
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
Bitcoin Developer Resources
Official Bitcoin 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 Bitcoin 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.