How to Evaluate Alchemy as an RPC Provider for Your Web3 Project

Alchemy Evaluation Decision Checklist

Before committing to Alchemy (or any RPC provider), verify these points against your project's requirements:

Alchemy's Core Offerings

Alchemy is a well-known blockchain infrastructure company founded in 2017. Its primary product is an RPC API that provides access to multiple blockchain networks, including Ethereum, Polygon, Solana, Arbitrum, Optimism, and many others. Beyond basic RPC endpoints, Alchemy offers enhanced APIs (e.g., NFT API, Token API, Transfers API), transaction simulation, and a suite of developer tools like the Alchemy SDK and dashboard.

Alchemy's platform is designed to abstract away the complexity of running nodes, offering both shared and dedicated node options. It is widely used by dApps, wallets, and DeFi protocols that require reliable and scalable blockchain access.

Key Evaluation Criteria

1. Network Support

Alchemy supports over 40 chains, including all major Ethereum Virtual Machine (EVM) chains and some non-EVM chains like Solana. However, coverage for testnets and less popular networks may vary. Always verify that the specific networks you need (e.g., Ethereum Sepolia, Base Sepolia, or BNB Testnet) are available on your chosen plan.

2. Pricing and Compute Units

Alchemy uses a compute unit (CU) pricing model, where each RPC method consumes a certain number of CUs. For example, a simple eth_blockNumber might cost 10 CUs, while a heavy eth_getLogs over a large block range could cost thousands. The free tier offers 300 million CUs per month (roughly 30 million simple calls), which is generous for prototyping but may be insufficient for production workloads.

Paid plans start at a monthly fee and include a CU allowance. Exceeding the allowance incurs overage charges. This model can make costs unpredictable for data-intensive applications. To estimate true cost, calculate the CU cost per million requests for your typical workload and compare across providers.

3. Rate Limits and Throughput

Shared endpoints on Alchemy have rate limits that vary by plan. The free tier typically allows around 25 requests per second (RPS). Paid plans offer higher limits, and dedicated nodes provide isolated resources with no shared throttling. If your application requires sustained high throughput, a dedicated node may be necessary.

4. Archive and Trace Data

Alchemy provides archive node access on certain plans, allowing queries of historical state. It also supports the Trace API (e.g., trace_block, trace_transaction) for Ethereum, which is essential for block explorers, analytics platforms, and debugging. However, archive and trace access may be restricted to higher-tier plans or incur additional CU costs.

5. WebSocket Support

Alchemy offers WebSocket endpoints for real-time data streaming. This is critical for applications that need to subscribe to new blocks, pending transactions, or contract events. Verify that your plan includes WebSocket access and that the connection limits meet your needs.

6. Uptime and Reliability

Alchemy advertises a high uptime SLA on paid plans. While this is a strong commitment, actual performance can vary. It is advisable to monitor endpoint health independently and have a fallback provider for critical applications. Consider using a multi-provider strategy to mitigate single points of failure.

7. MEV Protection

For Ethereum-based applications that submit transactions, MEV (Maximal Extractable Value) protection is crucial. Alchemy offers private transaction submission through its Flashbots integration, which helps prevent front-running and sandwich attacks. This feature is available on paid plans and is a key differentiator for DeFi projects.

8. Developer Experience

Alchemy provides a comprehensive dashboard for monitoring usage, debugging transactions, and managing API keys. The Alchemy SDK simplifies integration for popular frameworks like ethers.js and web3.js. Documentation is extensive, with guides and code examples. However, some developers report that the CU-based billing can be confusing to track in real time.

How Alchemy Compares to Other Providers

When evaluating Alchemy, it is helpful to compare it against other major RPC providers like QuickNode, Infura, Chainstack, and OnFinality. Key differentiators include:

• Pricing model: Alchemy's CU system vs. per-request or per-month flat fees. For heavy eth_getLogs usage, CU costs can escalate quickly.
• Free tier: Alchemy's free tier is among the most generous, but it comes with lower rate limits and no SLA.
• Chain support: Alchemy supports many chains, but some providers offer broader coverage for niche networks.
• Dedicated nodes: Alchemy offers dedicated nodes, but pricing is typically higher than some competitors.

For a detailed comparison of RPC providers, see our guide on how to choose an RPC provider.

Practical Evaluation Steps

1. List your requirements: Document the chains, RPC methods, expected request volume, and any special needs (archive, trace, WebSocket, MEV protection).
2. Estimate costs: Use Alchemy's CU calculator or run a pilot to measure CU consumption per typical request. Compare with other providers' pricing.
3. Test performance: Use tools like curl or custom scripts to measure latency and throughput from your deployment region. Example:

curl -X POST https://eth-mainnet.g.alchemy.com/v2/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

4. Check rate limits: Send requests at increasing frequency to identify throttling thresholds.
5. Evaluate support: Test response times from customer support and review documentation quality.
6. Plan for redundancy: Consider using a secondary provider as a fallback. OnFinality offers RPC endpoints for many chains with transparent pricing.

Common Pitfalls When Evaluating Alchemy

• Underestimating CU costs: A single eth_getLogs call can consume thousands of CUs. Monitor usage closely during development.
• Ignoring rate limits: Shared endpoints may throttle during peak usage. Upgrade to a dedicated node if needed.
• Assuming all chains are equal: Not all networks receive the same level of performance or feature parity. Test each chain individually.
• Overlooking migration complexity: Switching providers later may require code changes if you use provider-specific APIs. Stick to standard JSON-RPC where possible.

Key Takeaways

• Alchemy is a mature, feature-rich RPC provider suitable for many Web3 projects, especially those that benefit from enhanced APIs and developer tools.
• Its CU-based pricing can be cost-effective for light usage but may become expensive for data-heavy workloads.
• Always verify network support, rate limits, and archive/trace access for your specific use case.
• Consider a multi-provider strategy for high-availability production systems.
• For transparent pricing and a wide range of supported networks, explore OnFinality's RPC service as an alternative or complement.

Frequently Asked Questions

Q: Does Alchemy support all Ethereum L2s? A: Alchemy supports major L2s like Arbitrum, Optimism, Base, and Polygon zkEVM, but coverage may vary. Check their documentation for the latest list.

Q: How do Alchemy's compute units compare to other providers' metrics? A: Each provider uses a different unit (CUs, request units, etc.). To compare, calculate the cost per million calls for your typical request mix.

Q: Can I use Alchemy for free in production? A: The free tier is intended for development and testing. Production use requires a paid plan to get adequate rate limits and SLA.

Q: What is the best way to monitor Alchemy endpoint performance? A: Use Alchemy's dashboard or third-party monitoring tools. Set up alerts for latency spikes and error rates.

Q: How do I migrate from Alchemy to another provider? A: Since most providers support standard JSON-RPC, migration often involves changing the endpoint URL and API key. Test thoroughly before switching.

For more information on RPC provider selection, see our comprehensive guide.