What problem does it solve? Scaling Render services correctly requires knowing platform rules—autoscaling formulas, plan tiers, the 100-instance cap, and constraints like disks blocking multi-instance setups. This Skill consolidates those rules so you configure scaling correctly the first time. ## Core Features & Use Cases - Autoscaling Configuration: Set min/max instances and CPU/memory targets (1–90%) for Professional+ workspaces, with guidance on how Render computes new instance counts. - Manual Scaling & Plan Selection: Set instance counts from 1 to 100 and choose instance types from free through pro_ultra based on CPU and RAM needs. - Constraint & Cost Guidance: Understand limits (persistent disks force single-instance, static sites and cron jobs don't scale) and per-second billing implications. - Use Case: Your web service hits high CPU during traffic spikes. Use this Skill to write a Blueprint scaling block with min 2, max 10, and 70% CPU target, while avoiding the mistake of relying on numInstances alongside autoscaling. ## Quick Start Ask the assistant to configure autoscaling for your Render web service with a minimum of 2 instances, a maximum of 10, and a 70% CPU target.
