Prebuilt images

Your CI already builds your app’s image: while deploys it as is, with the same plan and the same rollback.

Updated November 9, 2026.

You, to your agent: Deploy the image ghcr.io/acme/planning:1.2.0.

What your agent writes

Your agent writes it in while.yaml, at the root of your app:

while.yaml

services:
  - name: web
    image: ghcr.io/example/app:1.2.0
    port: 8080

When to use it

Use it when your CI already builds the image: give it, preferably with its digest, and while deploys it as is.

How it works

while deploys an OCI image built elsewhere, by your CI for example. Planning, deploying and rolling back work as for an image built by while.

What to know

The image comes from a public registry that while relays (docker.io, ghcr.io, quay.io, registry.k8s.io, gcr.io, mcr.microsoft.com, public.ecr.aws), or from the project’s registry, registry.while.sh. Another registry only works if it answers over IPv6, and while does not connect to an external private registry. An image’s vulnerabilities are only inventoried if it carries its list of components (docker buildx build —sbom=true).

Pricing

These prices are the same on every plan, excluding VAT:

Resource	Price	Details
CPU and memory	€17 per vCPU·month and €8.50 per GiB·month	apps by usage, caches by reservation

Your agent’s MCP tools

Your agent handles it with the deploy_app tool.

Guides

Deploy a Docker container from your AI agent, over MCP