Scaling
Scale your web service on lowcloud Platform. Autoscaling (HPA), fixed replicas, and the scaling activity log.
Last updated: June 8, 2026
Scaling
Every web service has its own Scaling tab. It controls how many instances run and how they react to load. The live replica count (ready / desired) is shown on the Deployment card on the service's General tab.
Autoscaling (HPA)
Stateless services scale automatically based on CPU utilization (target: 80%).
- Autoscaling on: set the minimum and maximum number of instances. lowcloud adds instances when CPU rises and removes them when it falls.
- Autoscaling off: the service runs a fixed number of replicas that you set manually.
Web services scale up to 10 instances.
Persistent volumes
A service with a persistent volume is pinned to a single replica and cannot autoscale. The volume is read-write-once, so only one instance can mount it. To scale horizontally, move state to a database or object storage.
Scaling activity
The Scaling tab keeps a log of recent scaling events. Each entry shows the replica change (e.g. 1 → 2), whether it was Autoscaled or Manual, and when it happened.