platform

Build images on the platform from your laptop or codespace with BuildKit.

Remote builds

tngat build builds a container image on the platform from any machine — a laptop, a codespace, or CI — and streams the build logs back to your terminal. You do not need Docker installed locally.

Quick start

Create an organization key on API keys, then:

bash
export TNGAT_API_KEY=tngatc_…
export TNGAT_API_URL=https://api.tngat.com
npx @tngatcloud/cli build

The command packs the current directory (honouring .dockerignore, falling back to .gitignore), uploads it over HTTPS, and builds ./Dockerfile in an isolated, rootless BuildKit Job. Logs stream live; the image is pushed to the platform registry with layer cache and SBOM/provenance attestations.

Building several images

Commit a workflow file at .tngat/build.yaml:

yaml
version: 1
builds:
  - name: api
    context: services/api
    dockerfile: Dockerfile
    target: production
    args: { NODE_ENV: production }
  - name: web
    context: apps/web

tngat build runs the images sequentially. Use --no-cache to bypass the registry layer cache, or --file to pick a different workflow.

Deploy the image

--deploy runs each successful image instead of stopping at the registry. The project is resolved from --project (or the workflow's project), created if needed, and deployed to its production environment with the same orchestrator, environment variables and custom domains as a Git release.

bash
tngat build --deploy --project shop --port 8080

Build secrets

Secrets reach BuildKit through --mount=type=secret and are never stored on the build row. They are written to a per-run Kubernetes Secret, mounted at standard /run/secrets/<id> path, and deleted when the Job ends.

bash
tngat build --secret id=npm_token,env:NPM_TOKEN
dockerfile
RUN --mount=type=secret,id=npm_token \
    NPM_TOKEN=$(cat /run/secrets/npm_token) npm ci

Pricing

Builds are metered per minute (rounded up) against the organization wallet. The rate card uses the enterprise billing models: standard (one unit price), graduated (each tier prices its slice), volume (the final tier prices all minutes) and package (flat blocks). Each run records its billable minutes and cost, shown on the Builds page.

Why not expose buildkitd?

BuildKit's gRPC has no authentication layer of its own. Exposing it would mean client certificates plus a TCP/SNI proxy, and a shared daemon would mix layer cache between tenants. Instead every run is a per-tenant Kubernetes Job behind the platform's API-key auth, RBAC, quota and audit trail. The Job is rootless, needs no Docker socket, and is deleted after it finishes.

Commands

CommandPurpose
tngat build [dir]Pack and build; add --deploy to run the image
tngat listRecent builds in this organization
tngat status <id>Build detail and stored logs
tngat cancel <id>Cancel an in-flight BuildKit Job

The console's Builds page lists runs, reopens their logs and cancels a running build. Build history is persisted, so it remains after the Job's pod is garbage-collected.