# Auto-Scale Groups | Cycle.io

Canonical URL: https://cycle.io/docs/portal/auto-scale-groups

## Auto-Scale Groups.

There are two settings for scaling on Cycle:

1.  Through the [container config](https://cycle.io/docs/portal/container-auto-scaling-configuration).
2.  Through infrastructure [auto-scale groups](https://cycle.io/docs/platform/scaling-and-auto-scaling).

To dive deeper on either topic please see the links above, but from a high level these infrastructure auto-scale groups provide the mechanism that will add (and remove) additional compute resources to the cluster.

### Auto-Scale Dashboard

To manage auto-scale groups, head over to the auto-scale dashboard.

To get there:

1.  Select the **Infrastructure** tab from the main, left-hand navigation.
2.  Select the **Auto-Scaling** tab from the infrastructure sub-navigation.
    
    ![screenshot of the auto-scaling dashboard in the Cycle portal](https://cycle.io/_cdn/auto-scale-dash-2400x1346-webp.webp)
    

#### Groups Summary

At the top of the dashboard, users will find a list of auto-scaling groups for the hub for quick and easy navigation.

#### Next Step

Quick options to open the auto-scaling dropdown or create a new group.

#### Documentation

Curated links to documentation specifically scoped to subject matter for auto-scaling.

### Create Auto-Scaling Group

Click the **Add** button to open the Create Auto-Scaling Group modal. From here a user can add the settings most appropriate for their group.

![Auto-Scaling Create Form](https://cycle.io/_cdn/docs-65e5d0d0-create-autoscale-form-1215x858-webp.webp)

| **Field** | **Description** |
| --- | --- |
| Name | The name of the auto-scaling group. |
| Identifier | A unique resource identifier for the auto-scaling group, important for CLI operations. |
| Cluster | The infrastructure cluster with which the auto-scaling group is associated. |
| Scale Up | The settings and conditions for adding more servers to the auto-scaling group. |
| Scale Down | The settings and conditions for reducing the number of servers and managing server TTLs. |

### Deployable Infrastructure

Users can add server models to the deployable infrastructure page. Each entry specifies a **provider**, a **server model**, one or more **locations** (with their **availability zones**), and a **priority** that determines the order Cycle attempts to deploy from when a scaling event requires new infrastructure. The list of deployable infrastructure is what Cycle uses when a scaling event comes in that requires infrastructure to be added. Servers added through auto-scaling also inherit features and constraints settings shown below.

The **Add Model** button will open a wizard, from which users can add their choices. Entries on this page can be edited after they are created.

### Settings

Name and Identifier can be changed in the basic settings, but cluster cannot. For users who have not configured the **Scale Up** or **Scale Down** settings during create, those can be toggled and configured here as well.

The **Scale Up** settings for an auto-scaling group set the upper limit of how many servers can be created to support scaling demands for containers in the group.

The **Scale Down** settings expose a few more options.

| **Field** | **Description** |
| --- | --- |
| Min TTL | The minimum amount of time a server must remain online before it can be removed. |
| Inactivity Period | The period of time a server can remain idle (without activity) before it is removed. |
| Scale Down Method | The strategy used for scaling down servers, such as Last-In-First-Out (LIFO), First-In-First-Out (FIFO), or Default. |

### Constraints

Constraints govern _what_ is allowed to schedule onto the servers this auto-scale group provisions.

| Setting | Description | Default / Notes |
| --- | --- | --- |
| [**Tags**](https://cycle.io/docs/portal/server-settings#tags) | Node tags applied to every server this group provisions. A container's deployment constraints (`node.tags` with `any`/`all` matching) use these tags to target — or avoid — these servers. | None selected |
| [**Allow Pool**](https://cycle.io/docs/portal/server-settings#allow-pool) | Whether these servers join the general (untagged) pool and can run workloads that don't explicitly target them. When off, only workloads that match this group's tags land here. | Off |
| [**Allow Services**](https://cycle.io/docs/portal/server-settings#allow-services) | Whether environment service containers (Load Balancer, Discovery, VPN, Scheduler, Gateway) may run on these servers. | Off |
| [**Allow Overcommit**](https://cycle.io/docs/portal/server-settings#allow-overcommit) | Permit oversubscribing resources scheduling containers whose reserves total more than the server physically has. Enables the **Overcommit Multiple** field. | Off |

### Features

Features enable capabilities on the servers this group provisions.

| Setting | Description | Default / Notes |
| --- | --- | --- |
| [**Allow SFTP**](https://cycle.io/docs/portal/server-configure#allow-sftp) | Allow the server to accept incoming SFTP connections (through the remote-volume integration). | Off |
| [**Custom Base Volume Size (GB)**](https://cycle.io/docs/portal/server-configure#custom-base-volume-size) | Override the size of the base volume — where Cycle stores container images on each server. Leave blank to use the platform default. | Blank = platform default which ends up being around 28GB usable space. |
| [**Gateway Type**](https://cycle.io/docs/portal/server-configure#gateway) | The gateway service mode for these servers. `Platform Default` defers to the platform; otherwise choose an explicit type (e.g. **BGP** or **Static**). | Platform default is static and BGP is not yet supported. |

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
