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.
Raw Method Costs
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:
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).
On-Demand 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 Per Unit
$0.0000032 ($3.20/1M CU)
$0.0000025 ($2.50/1M CU)
$0.0000020 ($2.00/1M CU)
$0.0000016 ($1.60/1M CU)
$0.0000012 ($1.20/1M CU)
Rate Limits (CUPS)
Rate Limits serve to protect users from malicious actors or runaway scripts. Each tier has prioritized rate limit allocations designed for ultimate reliability.
CUPS are a measure of the number of compute units used per second when making requests. 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 310 CUPS.
If you are experiencing rate limits, or want create a more robust and reliable experience for your users, we recommend implementing retries.