Zero vendor lock-in. Every generated file is open standard code.

TDK CLI generates standard Dockerfiles, Vite configs, and Starlark Tiltfiles directly into your project. If you stop using TDK tomorrow, your stack keeps running without changing a single line of code.

Join waitlist Inspect generated output
Docker Standard L1-L4 • Starlark Tiltfiles • Vanilla TypeScript • MIT Open Source License • Vite Bundler Engine • Hono Web Framework • Zero Cloud Dependencies •

The escape hatch is the product foundation.

Most platform tooling locks you into proprietary agent daemons, custom cloud runners, or binary configuration files. TDK takes the opposite approach.

MANIFEST TO CODE

1. Human readable generated files

TDK reads your service.json and outputs plain, un-obfuscated files inside .autogenerated/. There are no hidden binary state blobs or proprietary control planes.

.autogenerated/Dockerfile.app.autogenerated
# Standard Docker L1-L4 Build Layering
FROM oven/bun:1.2-alpine AS base
WORKDIR /app
COPY package.json ./
RUN bun install
CMD ["bun", "run", "src/index.ts"]
STANDARDS FIRST

2. Built on open ecosystem tooling

Under the hood, TDK relies on Docker, Tilt, Vite, and Hono. Over 9,400 GitHub stars back the underlying container orchestration engine. You leverage industry standards instead of reinventing them.

OFFLINE CONFIDENCE

3. Zero cloud dependency

Your local environment runs completely offline. No mandatory cloud subscriptions, no remote container latency, and no surprise per-minute compute billing.

FULL OWNERSHIP

4. MIT license peace of mind

TDK CLI is licensed under the open source MIT License. You own your code, your topology specs, your generated build scripts, and your local developer workflow.

View GitHub org
SIDE BY SIDE COMPARISON

Proprietary cloud vs TDK open code

When platform vendors control your build configuration, migrating away requires months of custom devops rewrite work. TDK keeps your stack standard from day one.

Proprietary Cloud Workspaces

  • Closed source control planes with custom container runtimes
  • Per-user monthly cloud compute fees that scale indefinitely
  • Requires active internet connection to edit and test locally
  • Vendor lock-in: removing the tool requires rewriting all build plumbing

TDK Open Local Architecture

  • 100% open standards: Docker, Starlark, TypeScript, and Bun
  • Runs locally on ordinary developer laptops with zero cloud tax
  • Works completely offline on planes, trains, and remote setups
  • Zero lock-in: every generated file is committed standard code

Own your stack. Run it anywhere.

Join forward-thinking software teams building fast, reproducible microservice landscapes without vendor traps.

Join waitlist View reference repos