render-scaling

Name: render-scaling
Availability: InStock
Author: Render

Scale Render services manually or automatically with CPU and memory targets.

Updated Apr 14, 2026

Search Tags:#cost-optimization #autoscaling #render #scale #web-services #private-services

Ready to run

npx skills add https://github.com/renderinc/render-codex-plugin --skill render-scaling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: render-scaling
Source: https://github.com/renderinc/render-codex-plugin/tree/main/skills/render-scaling
Command: npx skills add https://github.com/renderinc/render-codex-plugin --skill render-scaling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Scales Render services to meet traffic demands without overprovisioning, helping you maintain performance while controlling costs.

Core Features & Use Cases

Manual scaling: set a fixed number of instances to meet steady workloads.
Autoscaling: configure min/max targets based on CPU and memory to adapt to traffic.
Plan decisions: choose appropriate instance types to balance performance and cost for web services, private services, and background workers.
Constraints and cost awareness: respect per-service caps and disk constraints while optimizing spend.

Quick Start

Configure autoscaling by defining minInstances, maxInstances, and target CPU/memory in your Render blueprint or through the Dashboard.

Frequently Asked Questions about render-scaling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure autoscaling for Render web services based on CPU and memory?▼

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.

Can I scale Render private services and background workers automatically?▼

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.

What is the maximum number of instances for a single Render service when autoscaling?▼

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.

When should I use manual scaling versus autoscaling for Render services?▼

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.

Does Render autoscaling work with both CPU and memory targets configured simultaneously?▼

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.

Do I need a Professional workspace to use Render autoscaling?▼

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.