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.
The build output is uploaded once and served from every region.
Images are emitted for static delivery without a runtime optimizer.
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.
Static delivery
A static release is published rather than placed, so it carries no capacity or health contract.
A contract is written when a repository is first detected. Detect this one and its commands and runtime appear here.
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 / 5 days ago
15Application 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