BYOC Auto-Scaling
Adoption and real activity of warehouse auto-scaling: who has it switched on, who tried it and stopped, which scaling mode customers use, and what scaling actually happens.
Charts​
| Chart | Shows |
|---|---|
| Clusters / Accounts: Auto-Scaling Enabled | Clusters and accounts with an enabled policy right now. |
| Clusters: Actively Scaling | Clusters that have actually scaled. |
| Clusters / Accounts: Ever Tried (All-Time) | Everyone who has ever created a policy. |
| Policy Churn Funnel | Policies by status: Enabled, Paused, Deleted. |
| Enabled Clusters by Scaling Unit | SINGLE (one warehouse) vs CN_GROUP (compute-node group) scaling. |
| Enabled / Paused Auto-Scaling Clusters by Customer | Per customer, split by scaling unit. |
| Scaling Events per Day | Scale-out vs scale-in events. |
| Most Active Clusters | Clusters ranked by scaling events. |
| Scaling Events — Outcome & Node Change | Recent events with their result and node counts before and after. |
| Enabled Policies / Paused & Deleted Policies — Detail | Policy-level lists. |
Click a number for the list behind it. The one filter, # Live Clusters in Account, narrows to accounts with that many live clusters (three of the lower charts don't follow it).
Good to know​
- Scaling events are recorded from 14 June 2026, so "actively scaling" means since then.
- A cluster can have more than one policy, so the policy-level lists can repeat a cluster.