render-scaling

To configure Render web service autoscaling, define minInstances, maxInstances, and target CPU/memory thresholds in your Render blueprint or Dashboard. The service automatically adjusts instances to meet traffic demands while respecting the 100-instance per-service cap.

Yes, Render private services and background workers support automatic scaling. You can configure autoscaling using CPU and memory targets across Professional+ workspaces, adapting to traffic demands just like standard web services.

The maximum number of instances for a single Render service during autoscaling is 100. This per-service cap applies to web services, private services, and background workers to enforce constraints while optimizing spend.

Use manual scaling for Render services to set a fixed number of instances for steady workloads. Use autoscaling to adapt to fluctuating traffic by configuring min/max targets based on CPU and memory, balancing performance and cost.

Yes, Render autoscaling supports both CPU and memory targets simultaneously. When both modes are configured, the system applies specific autoscaling precedence rules to determine when to scale instances up or down.

Yes, Render autoscaling requires a Professional+ workspace. This plan level unlocks the ability to configure min/max instances and CPU/memory targets for web services, private services, and background workers.