Apps Pricing
How web services and static sites are priced, and what a build costs.
Apps use two different models depending on what you deploy.
| What | Rate | Detail |
|---|---|---|
| Web service | Per instance size | Each size carries its own monthly price, covering vCPU, memory, and a bandwidth allowance |
| Static site | USD 3 / month | Flat rate per site, CDN delivery included |
| Builds and deploys | USD 0 | Not metered — deploy as often as you push |
Web services
A web service is priced per instance size. Each size fixes three things:
- vCPU
- memory
- a monthly bandwidth allowance
The size's monthly price covers all three. There is no separate meter for CPU time, requests, or bandwidth within the allowance.
The deploy wizard lists every size with its monthly price, and shows the prorated amount you will be charged today before you confirm.
Changing size
Moving a service to a different size changes what it costs from that point on. The charge is adjusted against the current period rather than restarting it, so you are not billed twice for the same days.
To change size, open the app's General tab and select Change next to Plan. The plan page shows what moving to each size costs right now, so you can compare sizes without committing to one.
Static sites do not run on a sized instance, so they cannot be resized.
Static sites
A static site is a flat monthly price regardless of traffic or the number of files. CDN delivery in front of it is included — there is no separate delivery meter as there is for object storage buckets.
Builds and deploys
Building an image and rolling out a release are not metered. Deploy as often as you push; only the running instance is billed.
A build that fails does not create a billable resource.
What stops the charge
Deleting the app. A stopped or failed app still holds its instance, so it is still billed — see How Pricing Works.
Deleting an app credits back the unused part of the period, as described under Removing Resources and Credits.