Cloud Apps
How Cloud Apps work: subscriptions and apps
A subscription is a pool of CPU, memory and disk. Apps draw from it, and you are billed for the pool rather than per app.
Cloud Apps has two things in it, and keeping them straight makes everything else obvious.
A subscription is a pool of CPU, memory and disk that you buy. An app is one piece of software running inside that pool.
You are billed for the subscription. Deploying an app into it is never invoiced separately.
What that means in practice
A Small subscription is 1 vCPU, 2 GB of memory and 50 GB of disk. You might run Uptime Kuma, a link shortener and an RSS reader inside it at the same time. Three apps, one bill.
When you deploy an app you choose how much of the pool it may use. The panel shows the remaining headroom as you do it, and refuses a deployment that would not fit.
Running out of room
If a subscription is full you have two options: give an existing app less, or move to a larger subscription. Both are in the panel. Changing an app's allocation is on its Resources tab; changing the subscription is under Cloud Apps → subscriptions.
Resizing a subscription upward is immediate. Resizing downward only works when what is already running still fits.
Where your app lives
Every app gets a hostname the moment it deploys, with HTTPS already working. You can point your own domain at it later — see Using your own domain with an app.
Still stuck? Get in touch — a person reads every message.