Container resources
Each app runs with:
These are fixed today and not configurable from the dashboard. Antideploy sets
no time limit of its own on a request or a connection. Cloudflare sits in front
of every app and applies its own limits, such as a 100 MB request body.
Scale to zero
An app with no traffic is scaled down to zero instances. It costs nothing while idle.The trade-off is cold starts. The first request after an idle period has to
start a container before it can be served. In our measurements that took 2.9 to
13.9 seconds, depending on the stack. Subsequent requests hit the warm
instance.
Single instance
If your app needs to serve real concurrent traffic, this is the limit to plan around.Region
Apps run in one region, Singapore, with the database beside the app. Choosing a region is not offered today.Builds
Your container is built from source on every deploy.- Buildpacks detect your runtime and produce an image with no Dockerfile required.
- Your own Dockerfile, when one sits at the root of the directory being built, is used instead. A Dockerfile nested in a subdirectory is not: the build runs at the root and would not find it.
- Static sites skip the buildpack lifecycle entirely and are layered onto a minimal server image, roughly seventy seconds instead of three minutes.
Deployment history
Release history, and how to undo a deploy.