Terminal
Terminal/Skill
Scales Render services by setting instance counts, choosing compute plans, configuring autoscaling, and cutting cost.
By Render
Works with
npx skills add render-oss/skills --skill render-scalingThis skill covers how to scale Web Services, Private Services, and Background Workers on Render: manual instance counts, autoscaling with a Pro workspace or higher, compute plan choices, and platform limits. Deeper guidance lives under references/.
When a service has or might need an attached disk, read references/persistent-disks.md before choosing a scaling architecture.
numInstances, scaling, planBefore recommending an autoscaling policy, establish the service type, workspace plan, whether the service is stateless or has a disk, the desired minimum and maximum instance counts, and whether CPU or memory is the limiting resource.
Render computes a candidate instance count from utilization vs target:
new_instances = ceil(current_instances * (current_utilization / target_utilization))
new_instances values (the more conservative scale-out).| Constraint | Behavior |
|---|---|
| Per service | Maximum 100 instances |
| Persistent disk | Cannot scale to multiple instances—disk-attached services stay single-instance |
| Static sites | Not scalable (served by CDN) |
| Cron jobs & Workflows | Scaling model does not apply (different execution model) |
plan field.references/compute-plans.md for current terminology, canonical plan discovery, and guidance on scaling up versus out.Sustained low CPU and memory across every instance indicates likely over-provisioning. Consult references/compute-plans.md, then test a smaller current compute plan, fewer manually scaled instances, or autoscaling that can scale down toward an appropriate utilization target (approximately 70% CPU is a common starting point for CPU-bound services). Change one dimension at a time when practical, and verify CPU, memory, latency, and errors under representative production traffic before keeping the change.
Manual instance count:
numInstances: 3
Autoscaling:
scaling:
minInstances: 1
maxInstances: 10
targetCPUPercent: 70
targetMemoryPercent: 80
Compute plan:
plan: 1c-2g
Do not rely on numInstances to cap autoscaling when a scaling block is present—autoscaling takes precedence. Preview behavior for scaling is detailed in references/autoscaling-guide.md.
| Topic | File |
|---|---|
| Compute plans and vertical vs horizontal scaling | references/compute-plans.md |
| Persistent disk constraints and storage alternatives | references/persistent-disks.md |
| Enabling autoscaling, targets, min/max, mistakes, previews | references/autoscaling-guide.md |
Whenever this skill directs you to consult current Render documentation:
curl. Do not substitute web-search summaries for the document.When a task requires multiple references, apply this workflow to each one and distinguish the documents you verified from those that remain unavailable.