Skip to main content
Scale tier services and Enterprise tier services with standard 1:4 profiles support autoscaling based on CPU and memory usage. Service usage is constantly monitored over a lookback window to make scaling decisions. If the usage rises above or falls below certain thresholds, the service is scaled appropriately to match the demand.

Configuring vertical auto scaling

Organization members with the Admin role can configure vertical autoscaling for Scale services and Enterprise services with standard 1:4 profiles. Go to the Settings tab for your service and adjust the minimum and maximum memory, along with CPU settings as shown below. Enterprise services with custom profiles require support-assisted vertical resizing.
Single-replica Scale services and Enterprise services with standard 1:4 profiles support vertical autoscaling. Enterprise services with custom profiles require support-assisted vertical resizing. Basic tier services remain fixed in size and can’t be scaled.
Set the Maximum memory for your replicas at a higher value than the Minimum memory. The service will then scale as needed within those bounds. These settings are also available during the initial service creation flow. Each replica in your service will be allocated the same memory and CPU resources. You can also choose to set these values the same, essentially “pinning” the service to a specific configuration. Doing so will immediately force scaling to the desired size you picked. It’s important to note that this will disable any auto scaling on the cluster, and your service won’t be protected against increases in CPU or memory usage beyond these settings.
For Enterprise tier services, standard 1:4 profiles support vertical autoscaling. Custom profiles don’t support vertical autoscaling or manual vertical scaling. Contact support for vertical resizing.
Last modified on August 3, 2026