Scale

The Scale area lets you review and adjust the runtime capacity assigned to an ioLoop Project.

Every Project includes one Compute Unit. If an application needs more capacity to support additional users or more demanding workloads, you can add Compute Units from this area. Additional units are provisioned as Project add-ons and begin contributing capacity after they become active.

Scale changes the resources available to run the application. It does not change the Project's pages, Database design, Cloud Flow logic, AI Agents, Connections, or access settings.

Understanding Compute Units

A Compute Unit provides runtime capacity for the Project. Additional units allow incoming application work to be distributed across more runtime capacity.

Compute Units can help when an application has:

• More simultaneous users or requests.
• Sustained demand that exceeds the capacity of the included unit.
• Request-driven Cloud Flow or integration work that increases runtime load.
• Periods of heavier application activity that require additional capacity.

Adding a Compute Unit does not automatically correct inefficient application behavior. Slow Database queries, unnecessary repeated requests, unbounded Cloud Flow operations, large responses, or delays from an external service may still need to be investigated and optimized.

Scale currently uses manually managed Compute Units. It does not provide automatic scaling rules, utilization thresholds, or minimum and maximum instance settings.

Review Current Capacity

Open Scale in the Project Editor and expand Compute Units if the section is collapsed.

The page explains that one Compute Unit is included with the Project. The table lists only additional Compute Units, so the Project's total is:

1 included Compute Unit + listed additional Compute Units

Each additional unit displays:

Column	Meaning
Instance ID	Identifies the additional Compute Unit. Use it to distinguish units when reviewing status or removing capacity.
Status	Shows whether the unit is being added, is active, is being removed, or encountered an error.
Remove	Starts removal of that specific additional unit.

If no additional units have been added, the table reports that no additional Compute Units are present. The included unit remains available and is not shown as a removable row.

Add a Compute Unit

Additional Compute Units are paid Project add-ons. The current subscription must support additional compute capacity.

If additional capacity is not available under the subscription, the Add control is disabled and shown as Add (Paid Feature). Availability is determined by the account subscription.

To add a unit:

1. Open Scale in the Project Editor.
2. In Compute Units, select Add.
3. Select an available Compute Unit license or choose a new license.
4. Select Next.
5. Review the Project, add-on, monthly charge, and immediate charge information.
6. Select Add to confirm.
7. Wait for the operation to complete, or select Continue in Background.
8. Confirm that the unit reaches Active before relying on the additional capacity.

The confirmation step displays current pricing and billing details. Use the amount shown there rather than assuming a fixed Compute Unit price.

Available and New Licenses

The purchase flow can present two sources for the additional unit:

• Available License: Uses a compatible Compute Unit license already available to the account. An expiration date is shown when applicable.
• New License: Adds a new recurring Compute Unit license to the account subscription.

When a new license is selected, the confirmation displays the prorated amount charged for the remainder of the current billing period and the monthly charge that begins with the next bill.

When an available license is selected, it is assigned to the Project immediately. The confirmation explains when monthly charging resumes.

For subscription charges, invoices, payment methods, and the next billing date, see Billing.

Compute Unit Status

Adding or removing a Compute Unit involves several runtime provisioning steps and may take time. The Scale page summarizes those steps with the following statuses:

Status	Meaning
Adding	The additional runtime capacity is being allocated and prepared.
Processing	The operation is progressing through another provisioning or removal step.
Active	The Compute Unit is ready and contributes additional Project capacity.
Removing	The unit is being taken out of service and its resources are being released.
Error	The add or remove operation did not complete successfully.

The progress dialog periodically checks the operation. If it takes longer than expected, the page offers Continue in Background so you can leave the dialog while provisioning continues. Return to Scale to review the latest status.

Do not count a unit as available capacity while it is still Adding or Processing. Likewise, a unit being removed may remain in the list until deprovisioning finishes.

Remove a Compute Unit

Removing a Compute Unit reduces the Project's available runtime capacity. Consider current and expected application demand before proceeding.

To remove a unit:

1. Open Scale in the Project Editor.
2. Locate the additional unit by its Instance ID.
3. Select its remove button.
4. Verify the Instance ID in the confirmation message.
5. Confirm the removal.
6. Wait for removal to finish, or select Continue in Background.
7. Return to Scale and confirm that the unit no longer appears in the list.

Removal is asynchronous. ioLoop first stops using the additional unit, then removes its runtime resources. The included Compute Unit cannot be removed from the Scale page.

The associated license is released after deprovisioning completes. If the license remains valid for part of the current billing period, it may become available for reuse until its displayed expiration date. Review Billing to confirm the resulting recurring subscription items and charges.

When to Add Capacity

Add capacity in response to observed or expected runtime demand rather than application size alone. A Project with many pages may require little runtime capacity, while a smaller application can have demanding request processing or many concurrent users.

Before adding a unit:

1. Identify the user activity or workload that is affected.
2. Confirm that the limiting factor is Project runtime capacity rather than a Database query, external provider, network dependency, or application defect.
3. Record representative response times, throughput, or failure behavior.
4. Add one unit and wait for it to become Active.
5. Repeat the same representative workload and compare the result.

Capacity requirements can change over time. Review additional units after traffic patterns, integrations, AI workloads, or backend processing change.

Billing and Capacity Changes

Adding a new Compute Unit can create a prorated immediate charge and a recurring subscription item. The confirmation dialog shows the applicable amounts before the add-on is submitted.

Removing a unit starts deprovisioning immediately, but the associated license is not released until that process completes. Billing changes follow the license state and billing period rather than the moment the remove button is selected.

If the account has a payment error or outstanding balance, the purchase flow may prevent a new add-on from being created. Billing issues are managed from the Account Dashboard.

Good Practices

• Wait for a Compute Unit to become Active before evaluating its effect.
• Add capacity incrementally and measure the result after each change.
• Test with a workload representative of actual application use.
• Optimize inefficient pages, queries, workflows, and external calls instead of treating capacity as the only performance control.
• Keep enough active capacity for expected peaks before removing a unit.
• Review current pricing and charge details in the confirmation dialog.
• Review Billing after adding or removing recurring capacity.
• Use Instance IDs to confirm that you are removing the intended unit.