CLI Referencescale

lizard scale

Scale a service (replicas / CPU / memory / storage).

Usage

lizard scale [service] [flags]

Flags

FlagDescription
-s, --service <name>Service name or ID (default: the linked service; same as the service argument)
-p, --project <id>Project name, slug, or ID
--replicas <n>Replicas (apps), up to your plan’s limit: 1 until the first paid Pro invoice (so during the trial), 5 after it on every paid plan and on Enterprise
--cpu <cores>1, 2, 3, or 4
--memory <mb>128–8192 MB
--storage <mb>Addon volume size, grow-only: 512, 1024, 2048, 4096, 8192, or 16384

Examples

Scale replicas horizontally

lizard scale --service api --replicas 5

Each replica is its own pod behind the load balancer. Make sure your app is stateless so replicas are interchangeable. An app with more than one replica does not sleep when idle. On a paused app, --replicas saves the count, and it applies on resume.

Scale CPU and memory vertically

lizard scale --service api --cpu 4 --memory 8192

Grow addon storage

lizard scale --service postgres --storage 8192

Addon data volumes are grow-only — you can increase storage but not shrink it.

See also

portpause

Updated