If an AI agent generated a Docker Compose file for your project, treat it as a draft deployment contract. It is a useful starting point, but it still needs human-readable validation before it becomes production infrastructure.

compose.new is a browser-based tool with a Compose file generator, syntax validator, and service graph visualizer. Use it to inspect the file visually, fix common Compose issues, and keep the service graph understandable before you deploy with Defang.

Agent-generated Compose review checklist

Confirm each service has the intended image or build context (Defang also supports Railpack for zero-Dockerfile deployments).
Confirm only public services expose ports.
Add health checks for web and API services.
Move real secrets out of the file. Use defang config set SECRET_NAME to store them securely.
Keep required environment variable names in the file.
Confirm persistent data uses volumes or managed-service annotations.
Make sure service names are stable and descriptive.

Why Compose is a good agent output

Docker Compose is compact enough for humans to review and structured enough for agents to edit. It keeps the deployment shape in one file: services, ports, dependencies, health checks, environment variables, and persistent backing services.

That is much easier to inspect than a pile of generated cloud infrastructure files.

Use compose.new before deploying

Paste the file into the validator or start from a template. The goal is not only syntax correctness. The goal is to make the app topology obvious enough that a developer can approve it.

Use Defang Agent Skills

If you use Claude Code, Codex, or another coding agent, install Defang Agent Skills so the agent has Defang’s estimate, deploy, and debug workflows available after the Compose file is reviewed.

After the Compose file looks right, deploy it with Defang:

defang login                           # authenticate
defang stack new                       # interactive: select provider, region, name the stack
defang compose up                      # deploy

Practical workflow

Use compose.new to inspect the service graph, then use Defang to deploy the reviewed Compose file to AWS or GCP. The important step is review: the generated file should be clear enough that you understand what will run before it becomes cloud infrastructure.