Deployments & rollbacks

What triggers a build

Trigger	When it fires
`manual`	You press Deploy or Redeploy in the console.
`webhook`	A push arrives from the connected GitHub App.
`preview`	A pull request opens or updates.
`redeploy`	You re-run a previous deployment's exact revision.
`agent`	The AI agent opened the change.

Lifecycle

A deployment moves through PENDING → BUILDING → RUNNING, or FAILED. When a new deployment succeeds, the previous one becomes SUPERSEDED but its image is kept, which is what makes rollback instant.

Rollback

Open Project → Deployments, pick the deployment you want to restore and choose Redeploy. The platform reuses the stored image digest, so the rollback skips the build entirely.

Logs

Build logs stream live from the build job; runtime logs stream from the pod. Both are available over the API:

bash

curl -N "https://api.tngat.com/api/builder/deployments/{{deploymentId}}/logs/stream" \
  -H "Authorization: Bearer $TNGAT_API_KEY"

Metrics

CPU, memory and restart counts are collected per deployment and surface in Project → Metrics and in the organization Usage page, where they feed the billing meter.