The build, delivery, and runtime contract that every deployment of this application reads.
Framework contract
Framework behavior is explicit, so what a build produces and what a release carries stay reviewable before a deployment.
Produces a minimal server artifact with its dependencies traced.
Images are served without a runtime optimizer.
Instance memory holds incremental rendering and revalidation state.
Middleware is left out of the deployment plan.
Build configuration
Commands and paths are explicit, editable, and recorded with each immutable build.
The repository path used as the build context.
Runs with the selected lockfile and package-manager cache.
Produces the immutable deployment artifact.
Used for builds and for executable JavaScript runtimes.
Stays in the foreground and handles graceful termination.
The runtime also provides this value through PORT.
Answered before a release is considered built.
Runtime and placement
Placement, capacity, health, and the lifecycle an executable release is held to.
Where an instance of this application may be placed.
AshburnThe floor a release holds whether or not anything is calling.
The ceiling a release may scale to before requests wait.
Measured in mebibytes, and the same for every instance of a release.
Measured in shared vCPU, and the same for every instance of a release.
Requests per ready instance before another one is added.
How long one request may run before the runtime ends it.
Traffic starts only after this check succeeds.
Repeated failure replaces the instance.
How often the readiness and liveness paths are asked.
Failed checks in a row before an instance is replaced.
Existing requests drain before termination.
Only private callers reach this release.
A warm floor is held whether or not anything is calling.
Configuration
Typed non-secret values are scoped by environment and phase. Repository, inherited, detected, and overridden sources stay visible.
Number / Server runtime / From the repository / 15 days ago
500Application secrets
Readable values exist only while they are entered. What is kept is encrypted material and safe version metadata.
Encrypted values scoped to an environment, the services they reach, and the rotation and revocation each one carries.
Manage secrets