Everything You Need to Know About TDK CLI Core

The TDK project released TDK CLI Core, an open-source command-line tool that generates local runtime files from per-service service.json descriptions and launches the full stack with Docker and Tilt. The tool supports service types including frontend, backend, worker, and mcp, routes traffic through Traefik, and offers JSON output for status, doctor, and logs commands. It is scoped to local development only, with production deployment left to Helm, Argo CD, or Kustomize.

TDK CLI Core is the command-line tool at the centre of TDK. It describes each service of an application in a small service.json file, generates the local runtime files from those descriptions, and starts the whole stack with Docker and Tilt. You write the application code. The tool writes the plumbing. service.json with its runtime, port, and dependencies. .autogenerated/ . tdk up runs the containers, routes traffic through Traefik, and keeps them updated with Tilt. tdk project --yes . tdk resource <name --type <type . Types include frontend, backend, worker, mcp, and bring-your-own. tdk up main --dry-run . tdk ui , or check readiness with tdk status --json . tdk doctor --json checks whether the machine can run the stack. tdk logs --json --service <name --tail <n prints recent lines for one service. tdk down stops the stack. TDK CLI Core is for local development. It is not a deployment tool, and production deployment stays with Helm, Argo CD, or Kustomize. It also needs a container runtime. Without one, tdk doctor says so and the stack does not start. The repository https://github.com/tdk-landscape/tdk-cli-core has the full command reference. The generated files reference https://github.com/tdk-landscape/tdk-cli-core/blob/main/docs/generated-files.md explains what appears under .autogenerated/ . The example repos https://github.com/tdk-landscape/tdk-erp-system show complete projects.