---
title: "Updating Scale"
description: "Fly introduces a new scaling model and command set intended to simplify how applications distribute instances across regions and manage global load. Instead of assigning instance counts to a fixed regional list, the system uses a pool of allowed regions plus global minimum and maximum instance counts, with Standard and Balanced models determining placement. Standard distributes instances evenly through the minimum and adds demand-driven instances without relocating them, while Balanced can move instances from other regions once the maximum is reached to match regional demand. The new flyctl regions command manages the pool, and flyctl scale show, standard, balanced, set, and vm commands configure or inspect scaling mode, counts, and VM size. Regional allocation can still fall back to a nearby region when the selected region cannot create an instance."
---

# Updating Scale

[Fly.io](https://yomu.fyi/company/fly-io) · May 13, 2020

**Type:** Announcement

## Summary

Fly introduces a new scaling model and command set intended to simplify how applications distribute instances across regions and manage global load. Instead of assigning instance counts to a fixed regional list, the system uses a pool of allowed regions plus global minimum and maximum instance counts, with Standard and Balanced models determining placement. Standard distributes instances evenly through the minimum and adds demand-driven instances without relocating them, while Balanced can move instances from other regions once the maximum is reached to match regional demand. The new flyctl regions command manages the pool, and flyctl scale show, standard, balanced, set, and vm commands configure or inspect scaling mode, counts, and VM size. Regional allocation can still fall back to a nearby region when the selected region cannot create an instance.

## Context

The previous scaling interface used a fixed regional list with per-region instance counts. Although functional, it required unintuitive operations to remove regions, was rigid, and offered less automation for managing global load.

## Approach / What changed

The new system separates a pool of possible regions from global minimum and maximum instance counts. Standard and Balanced models control placement and movement, while flyctl regions manages the pool and flyctl scale configures the model, counts, and VM size.

## Takeaways

- A region in the application pool is an eligible location, not a guarantee that an instance will run there; allocation can fall back to a nearby region when necessary.
- Standard distributes instances evenly across pool regions up to the minimum, then adds instances where demand occurs without relocating existing instances.
- flyctl regions replaces flyctl scale regions, with list, add, and remove subcommands; flyctl scale adds show, standard, balanced, and set controls.

**Tags:** [Autoscaling](https://yomu.fyi/topic/autoscaling), [Fly.io](https://yomu.fyi/topic/fly-io)

- Source: [Fly.io](https://fly.io/blog/updating-scale)
- Source URL: https://fly.io/blog/updating-scale
- Ingested by Yomu: 2026-09-03T01:26:09.541Z

[Read original post](https://fly.io/blog/updating-scale)