Scaling
Set replicas, turn on autoscaling, and let idle services sleep to zero.
Scale a service by hand with replicas, automatically with autoscaling, or all the way down to zero when it’s idle.
Replicas & resources#
In the service’s Settings, the Resources card sets how much each service gets. Changes apply on the next deploy.
- Replicas
- How many copies run, from 1 to 10 (your plan caps the maximum).
- Memory (MB)
- Memory per replica, in steps of 128 MB.
- CPU (vCPU)
- CPU per replica, in steps of 0.1 vCPU.
Autoscaling#
On Pro and higher, turn on autoscaling to add and remove replicas based on CPU load. Set the minimum and maximum replicas and a CPU target percentage (10–95%), and Gheima holds the target between those bounds.
Scale to zero (sleep)#
Set “Sleep after (minutes idle)” to scale a service to zero when it gets no traffic; it wakes automatically on the next request. Set it to 0 to disable.
Sleeping is great for staging or low-traffic services — you don’t pay for replicas while they’re asleep.
Pause & resume#
To stop a service entirely, use “Pause” in the Danger zone — it stops all replicas. Resume it to bring it back with its previous replica count.
Limits at a glance#
- Memory
- 128–8192 MB per replica.
- CPU
- 0.1–8 vCPU per replica.
- Replicas
- 1–10, capped by your plan.
- CPU target
- 10–95% for autoscaling.
- Sleep after
- 0–1440 minutes (0 disables).
Autoscaling reacts to CPU load only. Memory and CPU per replica stay fixed at the values you set.
✦ Your service uses exactly the capacity it needs: fixed replicas, CPU-driven autoscaling, or zero while idle.