---
title: Capacity
url: "/docs/capacity/"
canonical_url: https://docs.blossom88.com/docs/capacity/
markdown_url: https://docs.blossom88.com/docs/capacity.md
summary: App capacity, Location limits, reserved room and billing
categories:
- capacity
- scaling
- billing
---

# Capacity

Capacity is the CPU and memory available to your Apps and Jobs. Blossom adds
Servers when needed and retires excess capacity after its idle time. Each
Location has its own capacity ceiling.

## Limits And Alerts

| Setting | Starts at | What it controls |
|---|---|---|
| Locations per Account | 3 | Where you can deploy |
| Capacity ceiling per Location | 32 vCPU / 64 GB | Compute commitments in that Location, including Data, Builders and dedicated Load Balancers |
| Monthly email alert | $225 | An email when Account charges reach the amount; it never stops resources |

Open **Manage account → Locations** to request more Locations. Open a Location
to request a higher capacity ceiling. Existing resources keep running while a
request is reviewed. A deployment waiting for an approved increase continues
after approval.

Set the monthly email alert in **Billing**. It includes compute, bandwidth and
storage; a capacity ceiling controls compute only.

## App Capacity

App capacity comes in **2 vCPU / 4 GB** units, shared by Apps in a Location.
A single unit provides **2 vCPU / 3.5 GB** for Containers; the remainder keeps
the host and routing running. Larger Servers can provide more usable memory
per unit. The Location page shows Service allocations against ready App capacity.

| Service size | CPU | Memory |
|---|---|---|
| Small | 0.5 vCPU | 875 MB |
| Medium | 1 vCPU | 1.75 GB |
| Large | 2 vCPU | 3.5 GB |

Memory uses decimal MB/GB. The API keeps exact bytes. Data, Builders and
persistent Services have separate capacity; spare App capacity cannot replace it.

## Reserved Capacity

Choose one mode in **Locations → Edit**:

| Mode | What happens |
|---|---|
| **Automatic** (default, recommended) | Keeps shared deployment room as your Apps grow. |
| **On demand** | Save money, but deployments may have to wait. Servers are not always available. |
| **Custom** | Set a fixed minimum and adjust it as your Apps change. |

Automatic follows your enabled Services and desired replicas, keeping room for
one replacement Container. With no App workloads, it reserves nothing. The
form shows the target and monthly estimate before you save. Concurrent deploys
may need more room.

All running capacity is charged, including spare room. Excess capacity retires
after idle retention, rather than immediately after a settings change. Automatic
covers Apps; Data and Builders manage their own capacity.

The Location's **Maximum capacity** can set a lower cap for Apps and Data.
Builders sit outside this optional maximum but still count toward the Location's
approved ceiling. On Blossom BYOC (bring your own cloud), **Servers Blossom may
use** controls the provider sizes available for future provisioning.

## Deployments And Scaling

Blossom uses existing headroom first, then adds capacity within the Location's
limits. A rolling deployment needs room for a replacement Container before
stopping the old one. Keeping that room ready avoids waiting for a Server.

Services declare their size and replica count. Autoscaling reserves approval
for the maximum you set, while billing follows capacity actually running.
The form shows the estimate at that maximum before you save.

## Billing

Blossom Cloud prices include compute and vary by region. Blossom BYOC App and
Builder management costs **$5 per 2 vCPU / 4 GB unit per 30 days**, plus your
provider's separate bill. Data management has its own rate. See
[current pricing](https://app.blossom88.com/pricing).

The first eligible Organization per owner receives **$20 in free BYOC management
each month**, automatically after payment setup. Cloud compute and your provider's charges
are separate. Saving plans and configuration does not require payment; starting
paid resources does.

Blossom bills by calendar month in UTC. The first $10 of usage is collected
early to confirm the payment method; subsequent usage is invoiced monthly.
Usage and credits appear in Blossom. Use **Billing → Manage payment details** for
Stripe's card management and invoices.

## CLI

Compare allocations and current monthly rates across your Account:

    blossom capacity:show
    blossom spending:show

Filter either view to one Location:

    blossom capacity:show --location location-100
    blossom spending:show --location location-100

The profile's selected Location does not filter these summaries. Monthly rates
change as resources start and stop; Account-wide spending also shows usage
charged so far this billing period.

Change reserved room in the selected Location with a definition file:

    blossom capacity:init

capacity.yml:

```yaml
capacity:
  reservation_mode: automatic # on_demand or custom
  # For custom, set the fixed minimum:
  # reserved:
  #   cpu_vcpus: 4
  #   memory_gb: 8
```

    blossom capacity:update --data capacity.yml

Request more Locations or capacity from the CLI:

    blossom capacity:limit_request:create --locations 4 --reason "Another region"
    blossom capacity:limit_request:create --location LOCATION_ID --units 20 --reason "More Apps"

Each capacity unit is 2 vCPU / 4 GB. The Web UI has the same **Request more** flow.
See the [`capacity`](/docs/reference/cli/capacity/) and
[`spending`](/docs/reference/cli/spending/) references for other settings.