The Deployment API makes project versions available in runtime environments. A release identifies content, an environment supplies configuration, and a deployment connects the two.
Releases
A release records a version of project content. Its asset manifest describes the associated build assets and build progress. Source and branches are managed through the Projects API.
Test and production environments can use the same release with different credentials and domains. Later source edits do not change the release selected for production.
Environments and deployments
An environment groups settings such as variables and domains. A deployment records the selected project, release, and environment. These identifiers are fixed after creation. Serving another release requires a new deployment.
Creating a release, completing its build, and serving the application are separate stages. A deployment record identifies the intended version and destination. Runtime health and the application's endpoint show whether it is available.
Environment variables configure the release without changing its source. The same release can use a test service account in development and a production account in production.
Servers and routing
A server runtime serves application routes and hosted agent services over time. Its deployment selects the project release and environment configuration used by that capacity.
Project server operations manage servers for project environments. Account server operations manage account-owned servers and environment links. Both enforce their ownership and project permissions.
Proxy metadata supports routing and access checks. Routing and authorization metadata have different freshness requirements. Each endpoint defines its caching contract.
Investigating a deployment
The release ID identifies the content involved in an incident. The environment identifies its configuration. Both help explain why the same source behaves differently between test and production.
The Observability API supplies logs, metrics, and traces. A successful deployment does not establish that an agent or task run completed. Inspect those results through the Execution API.
Get started
Deploy a project: create a release, assign it to an environment, and verify the application.