CPU, memory & storage
Every app has a size: the CPU, memory, and storage each of its deployments runs with. You pick the size in the app's Settings tab in the console, and every deployment of the app (production and each preview) gets its own virtual machine at that size, with those resources reserved for it.
New apps start at 0.5 CPU, 1 GB memory, 5 GB storage, a sensible size for an internal tool, and you can size up as the app grows.
CPU and memory
CPU and memory come in steps, and the memory choices follow the CPU choice (between 1× and 4× the cores):
| CPU (cores) | Memory options (GB) |
|---|---|
| 0.5 | 0.5 · 1 · 2 |
| 1 | 1 · 2 · 4 |
| 2 | 2 · 4 · 8 |
| 4 | 4 · 8 · 12 · 16 |
The memory you pick is what your containers actually get: the platform's own overhead inside the machine is not carved out of it.
Storage
Storage is a single per-deployment budget, chosen in 5 GB steps from 5 GB to 100 GB. One number covers everything the deployment keeps:
- your persistent and ephemeral volumes,
- the data of any managed database,
- and the backup history (snapshots and the database change stream) that protects it.
The deployment page shows how much of the budget is in use. Storage can always be increased; it never shrinks, so the history and data you've accumulated are never squeezed out by a settings change.
Changing the size
Size applies when a deployment's machine is created. To resize:
- Stop the deployment (its data is kept; see stopping vs. deleting).
- Change the size in Settings. The size controls unlock once the app has no running deployments.
- Deploy again. The deployment comes back at the new size, on the same data and URL.
Project quotas
Each project has an overall budget across its running deployments: total CPU, total memory, total storage, and a count of deployments. A deploy that would go over the budget is rejected before anything starts, with a message naming the limit it would exceed; nothing half-deploys.
Two things to know when you hit one:
- Stopped deployments release their CPU, memory, and deployment slot: stopping a preview you're done with immediately frees room to deploy something else. Storage stays counted until a deployment is deleted, since the data still exists.
- Quotas are adjustable. The defaults (listed in Limits & quotas) fit a project with a handful of modest apps; contact support to raise them.
Usage and billing follow the size you provision: you pay for the resources reserved for your deployments, not for traffic spikes or bytes written.
Where to go next
- Limits & quotas: every limit and default in one table.
- Volumes: what consumes the storage budget.
- Backups & recovery: the history kept inside it.