🚀
Introduction
✨
Enhanced APIs
⛓
Chain APIs
📖
Documentation
💻
Tutorials
📜
Guides
📚
Resources
Compute Units (CUs)
Explanation for what Compute Units are and how we use them.
Compute units are a measure of the total computational resources your apps are using on Alchemy. You can think of this as how you would pay Amazon for compute usage on AWS. Some queries are lightweight and fast to run (e.g., eth_blockNumber) and others can be more intense (e.g., large eth_getLogs queries). Each method is assigned a quantity of compute units, derived from global average durations of each method.
We're obsessed with providing the most developer-friendly experience across our platform, and this doesn't stop at pricing. Pricing on compute units allows us to provide developers with the most fair and transparent pricing possible. No more over-paying for simple requests, you only pay for what you use, period.
Pricing Plans
Feature
Free Tier
Growth Tier
Enterprise Tier
Compute Units
300,000,000
400,000,000
Custom
Approx. # Requests
12,000,000
16,000,000
Custom
# of apps
5
15
Unlimited
Throughput (CUPS)
330
660
Custom
Full Archive Data
✅
✅
✅
Supernode
✅
✅
✅
Build
✅
✅
✅
Monitor
✅
✅
✅
Notify
✅
✅
✅
Multichain (Mainnet & Testets)
✅
✅
✅
No daily request limit
✅
✅
✅
24/7 Support
✅
✅
✅
Auto-scaling Compute Units
❌
✅
✅
Custom SLAs
❌
❌
✅
Committed Use Discounts
❌
❌
✅
Pay in Crypto or NFTs
❌
❌
✅
Raw Method Costs
Method
CU
net_version
0
eth_chainId
0
eth_syncing
0
eth_protocolVersion
0
net_listening
0
eth_uninstallFilter
10
eth_accounts
10
eth_blockNumber
10
eth_subscribe
10
eth_unsubscribe
10
eth_feeHistory
10
eth_maxPriorityFeePerGas
10
eth_createAccessList
10
bor_getAuthor
10
bor_getCurrentProposer
10
bor_getCurrentValidators
10
bor_getRootHash
10
bor_getSignersAtHash
10
eth_getTransactionReceipt
15
eth_getUncleByBlockHashAndIndex
15
*To view the batch request breakdown in the dashboard click on "raw request"
WebSocket and Webhook Costs
Webhook and WebSocket subscriptions on Alchemy are priced based on bandwidth: the amount of data delivered as part of the subscription.
Each subscription type is priced identically, per byte:
Bandwidth
CU
1 byte
.04
On average, a typical webhook or WebSocket subscription event is about 1000 bytes, so would consume 40 compute units. Note that this can vary significantly based on the specific event delivered (
alchemy_newFullPendingTransactions subscription type has a much higher compute unit cost than others).Auto-Scale Compute (Growth 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.
Monthly Compute Units (CU)
Price
400,000,000
$49.00
Every 1,000,000 over 400M
$1.20
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
Enterprise
Custom
If you are experiencing throughput errors, or want create a more robust and reliable experience for your users, we recommend implementing retries.
Last modified 1mo ago