Alchemy CU calculator
Use to show why “requests/month” is not enough: methods have different CU weights.
Use this page in discovery calls to move buyers away from “which provider is cheapest?” and toward method mix, peak RPS, archive/debug usage, support, and dedicated-capacity triggers.
Defaults use Alchemy’s published rough average of 27 CU/request as a starting point from the source-gated research. Replace with real customer logs when available.
Use to show why “requests/month” is not enough: methods have different CU weights.
Use to compare monthly credits and visible RPS ceilings separately.
Use to discuss Request Units and method/feature uplift explicitly.
Use to separate daily quota from credit/second throughput risk.
| Signal | Interpretation | Recommended motion |
|---|---|---|
| Peak ≥ 800 RPS | Shared plans may hit operational ceilings even if monthly cost looks fine. | Pitch dedicated/limitless proof pilot. |
| Archive/log/debug ≥ 15% | Weighted units can distort cost and job completion. | Run method-level workload review. |
| Backfills or launch windows | Average daily volume hides burst risk. | Benchmark p95/p99 and error rate by region. |
| Enterprise procurement | SLA/security/support docs matter as much as price. | Attach reliability pack + RCA template. |