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

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.

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:

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.

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

Inspect the Location’s allocations and Servers:

blossom capacity:show
blossom capacity:server:list
blossom spending:show

Change reserved room with a definition file:

blossom capacity:init

capacity.yml:

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 and spending references for other settings.