Bitcoin RPC Providers: Node-as-a-Service Compared
Compare Bitcoin RPC and node-as-a-service providers across uptime, rate limits, supported methods, and pricing for developers.
Bitcoin RPC Providers Overview
Bitcoin RPC providers offer hosted Bitcoin node infrastructure so developers can query the blockchain, broadcast transactions, and estimate fees without running their own hardware. These node-as-a-service platforms expose the Bitcoin JSON-RPC interface over HTTPS, handling node synchronization, storage, and uptime so applications can focus on business logic.
The tradeoff is straightforward: hosted RPC endpoints offer convenience and fast setup at the cost of trust and dependency on a third party. Running your own Bitcoin Core node gives you full sovereignty over your data and access to all 150+ RPC methods, but requires maintaining storage, bandwidth, and uptime yourself. Most production deployments use a combination of both.
Provider Comparison Table
The following table compares the major Bitcoin RPC providers across pricing, rate limits, uptime guarantees, and network support. All pricing reflects publicly available information as of mid-2026.
| Provider | Free Tier | Paid From | Free RPS | Uptime SLA | Testnet | Signet |
|---|---|---|---|---|---|---|
| QuickNode | 10M credits/mo | $49/mo | 15 | 99.99% | Testnet4 | No |
| GetBlock | 50K CU/day | ~$23/mo | 20 | 99% (shared) | Yes | No |
| Chainstack | 3M RU/mo | $49/mo | 25 | 99.9% | Yes | Yes |
| Alchemy | 30M CU/mo (~3M calls) | $0.45/M CU | 25 | 99.99% | Testnet3/4 | Yes |
| Blockdaemon | 3M CU/mo | Contact sales | 5 | 99.9% | Testnet3/4 | No |
| NOWNodes | 100K req/mo (trial) | €20/mo | 15 | 99.95% | Testnet4 | No |
| Blockstream Esplora | 500K req/mo | Custom | ~50 | 99.9% | Yes | Yes |
| Self-hosted (Bitcoin Core) | Unlimited | $20-80/mo VPS | Unlimited | Self-managed | All | All |
Note that free tier units are not directly comparable across providers. QuickNode uses API credits with per-method multipliers (Bitcoin methods cost 10 credits each). GetBlock and Alchemy use compute units. Chainstack uses request units where archive queries cost 2 RU instead of 1. NOWNodes counts raw requests but limits the free tier to a one-month trial.
Provider Deep Dives
QuickNode
QuickNode is one of the largest multi-chain node providers with Bitcoin support across mainnet and Testnet4. Their free tier includes 10 million API credits per month at 15 requests per second with no credit card required. Paid plans start at $49/month (Build tier) with 80 million credits and 50 RPS, scaling to Enterprise with custom pricing. QuickNode runs unpruned Bitcoin nodes, so all historical block and transaction data is accessible via getrawtransaction without needing a separate archive endpoint.
QuickNode also offers Blockbook add-on methods (the bb_* namespace) for address and xpub balance lookups, UTXO queries, and transaction history: functionality that Bitcoin Core RPC does not natively provide without a transaction index. Ordinals and Runes APIs are available as separate add-ons. WebSocket is not available for Bitcoin endpoints on QuickNode.
GetBlock
GetBlock offers one of the most affordable entry points for hosted Bitcoin RPC. The free tier provides 50,000 compute units per day at 20 RPS. Paid shared plans start around $23/month on annual billing, while dedicated Bitcoin nodes start at $1,000/month with unlimited requests. GetBlock documents 45 Bitcoin JSON-RPC methods across blockchain, mempool, raw transaction, PSBT, mining, and utility categories.
GetBlock also offers a "Limitless Node" option: flat-rate pricing from $150/month at 25 RPS with no per-request billing. This model is useful for applications with predictable throughput that want to avoid usage-based cost surprises. Shared node uptime SLA is 99%, while dedicated nodes guarantee 99.9%. Infrastructure runs across three regions: Frankfurt, New York, and Singapore.
Chainstack
Chainstack provides the most generous free tier for Bitcoin JSON-RPC: 3 million request units per month at 25 RPS. Their documentation lists 139 Bitcoin JSON-RPC methods, the most comprehensive coverage among hosted providers. All Chainstack Bitcoin nodes run unpruned with txindex=1 enabled, making every transaction from the genesis block queryable. Chainstack is one of the few providers with confirmed Bitcoin signet support alongside testnet.
Paid plans start at $49/month (Growth) with 20 million RU and 250 RPS. Wallet-related RPC methods (roughly 45 methods) require a dedicated node deployment. Enterprise plans include a 99.9% uptime SLA backed by service credits. Chainstack deploys across seven specific regions plus two global networks.
Alchemy
Alchemy added Bitcoin RPC support alongside its established EVM chain infrastructure. Bitcoin is a secondary offering compared to their Ethereum tooling, but the basics are solid. The free tier includes 30 million compute units per month at 25 RPS: since all Bitcoin RPC methods cost 10 CU each, this translates to approximately 3 million Bitcoin RPC calls per month. The pay-as-you-go tier charges $0.45 per million CU (first 300M), scaling down to $0.40/M CU at higher volumes, with 300 RPS.
Alchemy supports approximately 30 standard Bitcoin JSON-RPC methods covering blockchain queries, mempool inspection, raw transactions, fee estimation, and mining. Wallet methods are not exposed. Alchemy is one of the few providers supporting all four Bitcoin networks: mainnet, Testnet3, Testnet4, and signet. Archive data is included on all plans. WebSocket support for Bitcoin is not confirmed in their documentation.
Blockdaemon
Blockdaemon targets enterprise and institutional users with ISO 27001 and SOC 2 Type II compliance certifications. Their free tier is limited to 3 million compute units per month at just 5 RPS. Dollar pricing for paid tiers is not publicly listed: Starter and Growth plans require contacting sales. Blockdaemon documents 50+ whitelisted Bitcoin RPC methods plus proprietary bd_* custom methods for balance queries, UTXO lookups, and transaction listing by address.
Bitcoin support includes both Testnet3 and Testnet4 but not signet. Full history from genesis is available on shared endpoints. WebSocket is not supported for Bitcoin. The platform operates across 40+ node locations globally with Tier-3 data centers. Blockdaemon is the right choice for teams that need institutional-grade compliance and dedicated support, but the opaque pricing and limited free tier make it less suited for indie developers or early prototyping.
NOWNodes
NOWNodes offers a straightforward request-based pricing model with support for 120+ blockchain networks. The free Start plan includes 100,000 requests per month at 15 RPS, though it is limited to a one-month trial. Paid plans start at €20/month (Pro) with 1 million requests. Archive node access is included across all plans at no extra charge. WebSocket is available on paid plans for real-time block and transaction subscriptions.
NOWNodes runs full Bitcoin nodes and supports mainnet, testnet, and Testnet4. Signet is not currently available. The platform guarantees 99.95% uptime on shared plans and 99.99% on dedicated nodes. Dedicated Bitcoin node hosting starts at €800/month. Infrastructure runs across servers in Europe and the United States, with latency under 80ms reported for North American users.
Blockstream Esplora
Blockstream's Esplora is a free, open-source block explorer API available at blockstream.info/api/. Unlike the other providers on this list, Esplora is a REST API rather than a Bitcoin Core JSON-RPC endpoint. It provides read-only access to blocks, transactions, addresses, UTXO sets, mempool data, and fee estimates. It does not expose wallet methods, mining RPCs, or the full Bitcoin RPC interface.
The free tier allows approximately 500,000 requests per month. Esplora supports Bitcoin mainnet, testnet, signet, and the Liquid sidechain. The API is open source and can be self-hosted for unlimited usage. For applications that only need read access to blockchain data (checking balances, looking up transactions, monitoring addresses), Esplora is a strong option. For broadcasting transactions or querying mempool policy, you will still need a JSON-RPC endpoint.
Running Your Own Bitcoin Node
Self-hosting a Bitcoin full node remains the gold standard for sovereignty, privacy, and unrestricted RPC access. Bitcoin Core exposes approximately 150 RPC methods across blockchain, wallet, raw transaction, mempool, network, mining, and utility categories. You get unlimited requests with no rate limits, no API keys, and no third-party dependencies.
The tradeoffs are operational. The full unpruned blockchain is approximately 745 GB as of mid-2026, growing at roughly 70-80 GB per year. A pruned node can run with as little as 10 GB of block storage, but pruning disables getrawtransaction for historical transactions and is incompatible with txindex=1. Initial block download takes 2-7 days on modern hardware with an SSD.
VPS hosting costs for a full node range from $20-50/month on Hetzner (with included bandwidth) to $50-80/month on DigitalOcean. AWS is significantly more expensive at $390+/month due to egress charges. Minimum hardware requirements are 2 GB RAM and a modern dual-core CPU, though 8 GB RAM and an NVMe SSD are recommended for reasonable performance. Monthly bandwidth consumption is roughly 20-30 GB download and 200-300 GB upload with inbound connections enabled.
RPC Method Coverage Comparison
Not all providers expose the same set of Bitcoin Core RPC methods. Security-sensitive methods (wallet operations, node management) are typically disabled on shared infrastructure. The following table compares method availability across key categories.
| Category | Bitcoin Core | QuickNode | GetBlock | Chainstack | Alchemy | Blockdaemon |
|---|---|---|---|---|---|---|
| Blockchain queries | 28 methods | Yes | 13 methods | 19 methods | 10 methods | 9+ methods |
| Raw transactions | 17 methods | Yes | 4 methods | 8 methods | 4 methods | 7+ methods |
| PSBT | Yes | Limited | 13 methods | 5 methods | No | Limited |
| Mempool | Yes | Yes | 6 methods | 5 methods | 4 methods | 5 methods |
| Fee estimation | Yes | Yes | Yes | Yes | Yes | Yes + custom |
| Wallet methods | 65 methods | No | Disallowed | Dedicated only | No | Partial |
| sendrawtransaction | Yes | Yes | Yes | Yes | Yes | Yes |
| Custom/extended APIs | No | Blockbook, Ordinals | Blockbook, REST | No | No | bd_* methods |
| WebSocket | No (ZMQ only) | No | Via Blockbook | Limited | No | No |
Bitcoin Core itself does not support WebSocket natively. It uses ZeroMQ (ZMQ) for real-time push notifications of new blocks and transactions. Hosted providers that advertise WebSocket for Bitcoin typically route through a Blockbook or Electrum-based indexing layer rather than exposing raw bitcoind ZMQ streams. For a deeper comparison of Bitcoin node software options, see our Bitcoin node implementation comparison.
Sovereignty vs. Convenience
The choice between self-hosted and managed RPC comes down to your application's trust model. A hosted provider introduces a dependency: they can see your queries (including which addresses and transactions you monitor), throttle your access, or go offline. For privacy-sensitive applications, wallet backends, or infrastructure where uptime is critical, running your own node eliminates these risks.
For prototyping, testnet development, or applications that primarily need blockchain data (not wallet operations), hosted RPC providers are the pragmatic choice. Most providers support Bitcoin testnet and some support signet, making them ideal for development workflows before deploying against mainnet.
A common production architecture uses a self-hosted node as the primary RPC backend with a hosted provider as a fallback. This gives you sovereignty and privacy by default while maintaining availability if your node goes down for maintenance or during initial block download after an upgrade. For applications building on Bitcoin layer 2 protocols like Spark, the underlying RPC provider choice affects how your application queries and broadcasts on-chain transactions.
For a comparison of higher-level Bitcoin APIs that abstract over raw RPC, see our Bitcoin API comparison tool.
Frequently Asked Questions
What is a Bitcoin RPC provider?
A Bitcoin RPC provider hosts and maintains a Bitcoin full node on your behalf, exposing the node's JSON-RPC interface over HTTPS. Instead of syncing and storing the entire blockchain yourself, you send RPC calls (like getblock, sendrawtransaction, or estimatesmartfee) to the provider's endpoint and receive JSON responses. This is sometimes called "node-as-a-service" or "Bitcoin NaaS."
Which Bitcoin RPC provider has the best free tier?
Chainstack offers the most generous free tier with 3 million request units per month at 25 RPS. Alchemy provides 30 million compute units per month (approximately 3 million Bitcoin RPC calls since each method costs 10 CU). QuickNode offers 10 million API credits per month but credits are consumed at variable rates per method. Blockstream Esplora provides 500,000 free REST API requests per month but is read-only and does not expose the full JSON-RPC interface. For unrestricted development, running Bitcoin Core on regtest locally is free and instant.
Do I need to run my own Bitcoin node?
It depends on your use case. If you need wallet RPC methods, full privacy over your queries, or access to all 150+ Bitcoin Core RPCs, self-hosting is the right choice. If you primarily need to read blockchain data, broadcast transactions, and estimate fees for an application, a hosted RPC provider is faster to set up and easier to maintain. Many production systems use both: a self-hosted node as the primary backend and a hosted provider as a redundant fallback.
What is the difference between a full node and a pruned node for RPC?
A full unpruned node stores the entire blockchain (approximately 745 GB as of mid-2026) and can serve any historical block or transaction. A pruned node discards old block data after validating it, retaining only the UTXO set and a configurable window of recent blocks. Pruned nodes cannot serve getrawtransaction for transactions outside their retention window and cannot run with txindex=1. Most hosted providers run unpruned nodes with full transaction indexes enabled.
How much does it cost to run a Bitcoin full node?
Self-hosting on a VPS costs $20-50/month on budget providers like Hetzner or $50-80/month on DigitalOcean. You need at least 1 TB of SSD storage, 2 GB of RAM (8 GB recommended), and a modern dual-core CPU. The initial sync takes 2-7 days. Running at home on dedicated hardware (a Raspberry Pi 5 or mini PC with an external SSD) costs roughly $200-400 upfront with minimal ongoing electricity costs. AWS is significantly more expensive at $390+/month due to data transfer charges.
Which providers support Bitcoin signet?
As of mid-2026, Chainstack, Alchemy, and Blockstream Esplora support Bitcoin signet. Signet is a test network with a controlled block production schedule, making it more reliable than testnet for development and testing. QuickNode, GetBlock, Blockdaemon, and NOWNodes currently support testnet but not signet. Running your own Bitcoin Core instance supports all networks including signet, testnet, and regtest.
What Bitcoin RPC methods do hosted providers support?
Most providers support the core set of blockchain queries (getblock, getblockchaininfo, getblockhash), mempool inspection (getrawmempool, getmempoolinfo), transaction operations (getrawtransaction, sendrawtransaction), and fee estimation (estimatesmartfee). Wallet methods are almost always disabled on shared infrastructure for security reasons. Some providers offer extended APIs through Blockbook or proprietary methods for address balance and UTXO queries that Bitcoin Core does not natively provide.
This tool is for informational purposes only and does not constitute financial advice. Pricing, rate limits, and feature availability change frequently. Data is approximate and based on publicly available information as of mid-2026. Always verify current pricing and capabilities on each provider's official website before making infrastructure decisions.
Build with Spark
Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.
Read the docs →
