A guide to understand Alchemy's pricing plans.
Pricing Plans
| Feature | Free Tier | Growth Tier | Scale Tier (Monthly) | Scale Tier (Yearly) | Enterprise Tier |
|---|---|---|---|---|---|
| Base Compute Units | 300,000,000 | 400,000,000 | 1,500,000,000 | 1,500,000,000 | Custom |
| Approx. # Requests | 12,000,000 | 16,000,000 | 60,000,000 | 60,000,000 | Custom |
| Base Rate | Free | $49 | $289 | $199 | Custom |
| # of apps | 5 | 15 | 30 | 30 | Unlimited |
| Throughput (CUPS) | 330 | 660 | 3000 | 3000 | Custom |
| Full Archive Data | ✅ | ✅ | ✅ | ✅ | ✅ |
| Supernode | ✅ | ✅ | ✅ | ✅ | ✅ |
| Build | ✅ | ✅ | ✅ | ✅ | ✅ |
| Monitor | ✅ | ✅ | ✅ | ✅ | ✅ |
| Notify | ✅ | ✅ | ✅ | ✅ | ✅ |
| Multichain (Mainnet & Testnets) | ✅ | ✅ | ✅ | ✅ | ✅ |
| No daily request limit | ✅ | ✅ | ✅ | ✅ | ✅ |
| 24/7 Support | ✅ | ✅ | ✅ | ✅ | ✅ |
| Enhanced APIS (NFT, Transfers, Token, Notify) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Trace, Debug APIs | ❌ | ✅ | ✅ | ✅ | ✅ |
| Reinforced Transactions | ❌ | ✅ | ✅ | ✅ | ✅ |
| Transaction Simulation | ✅ | ✅ | ✅ | ✅ | ✅ |
| Auto-scaling Compute Units | ❌ | ✅ | ✅ | ✅ | ✅ |
| On-demand rate per 1M CUs | - | $1.20 | $1.00 | $1.00 | Custom |
| Pre-paid rate per 1M CUs | - | - | - | $0.70 | Custom |
| Custom SLAs | ❌ | ❌ | ❌ | ❌ | ✅ |
| Committed Use Discounts | ❌ | ❌ | ❌ | ❌ | ✅ |
| Pay in Crypto or NFTs | ❌ | ❌ | ❌ | ❌ | ✅ |
| Access to paid tier chains (BSC, Metis, Avalanche C-Chain) | ❌ | ✅ | ✅ | ✅ | ✅ |
Auto-Scale Compute (Growth & Scale Tier Only)
Turning on autoscale gives you instant access to on-demand compute at volume discounts. No more worrying about your node going down due to a spike in traffic, or even waiting days for new nodes to sync. Autoscale gives you infinite scalability at affordable prices.
| Tier | Base Monthly Compute Units (CU) | Price per 1M CUs over base CUs | Price for Pre-Paid CUs over base CUs (per 1M CUs) |
|---|---|---|---|
| Growth | 400,000,000 | $1.20 | - |
| Scale Monthly | 1,500,000,000 | $1.00 | - |
| Scale Yearly | 1,500,000,000 | $1.00 | $0.70 |
Throughput (CUPS)
Each application has reserved dedicated Throughput, measured in Compute Units per Second. Applications can greatly exceed their dedicated throughputs based off of elastic demand in our system.
Since each request is weighted differently, we base this on the total compute units used rather than the number of requests. For example, if you send one eth_blockNumber (10 CUs), two eth_getLogs (75 CUs), and two eth_call(26 CUs) requests in the same second, you will have a total of 212 CUPS. Note that even if your application limit is 200 CUPS, this throughput will likely be allowed still by the system.
| User | CUPS |
|---|---|
| Free | 330 |
| Growth | 660 |
| Scale | 3000 |
| Enterprise | Custom |
If you are experiencing throughput errors, or want create a more robust and reliable experience for your users, we recommend implementing retries.