What problem does it solve? Scaling Render services correctly requires knowing platform rules like the 100-instance cap, Professional-tier autoscaling requirements, disk-attached single-instance limits, and how autoscaling overrides manual counts. This Skill consolidates those rules so you configure scaling without misconfigurations or surprise costs. ## Core Features & Use Cases - Manual and Autoscaling Configuration: Set instance counts from 1 to 100 via Dashboard, CLI, API, or Blueprint, and configure CPU/memory autoscaling targets with min/max bounds. - Instance Type Selection: Choose between vertical scaling (plan upgrades from free to pro_ultra) and horizontal scaling based on workload characteristics. - Cost and Constraint Guidance: Apply per-second billing implications, spike-protected scale-down behavior, and constraints for disks, static sites, cron jobs, and preview environments. - Use Case: A web service hitting high CPU during traffic peaks needs autoscaling. Use this Skill to write a Blueprint with minInstances 2, maxInstances 10, and 70% CPU target, while avoiding the mistake of combining it with a persistent disk. ## 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 percent CPU target.