An application is billed for the resources it uses, drawn from your account credit, not a flat monthly plan. Usage is sampled every minute and billed by the hour.
What is metered
| Resource | Billed on |
|---|---|
| Memory | What the instance actually uses, per GB-hour |
| vCPU | What it actually consumes, per vCPU-hour |
| Disk | What you allocate, per GB-hour |
| Egress | Outbound traffic, per GB |
The headline figures you set under Configure your application are ceilings. You are charged for real CPU and memory use under those ceilings, not for the ceilings themselves. Disk is the exception: it is billed on what you allocate, because space you have claimed is held for you even after you delete a file.
A persistent container is billed while stopped
An application that keeps its disk (a Docker image or a template) still holds that disk when it is not running, so its storage keeps being billed. Deleting the application is what stops the charge.
Where you see the cost
Each application shows its cost so far this month and a ceiling, the most it could cost if the instance used everything it is given for the whole month. The create form shows a worked example for a small app so you can estimate before you deploy. These are live figures from your actual usage; the per-unit rates are the current platform rates, shown in-product and summarized on Pricing.
Databases
A managed database is billed separately, per second, on the memory, vCPU and disk it is provisioned with. See Deploy a managed database for its pricing.