NewLatest release

Run your multi-service stack on your machine with one command.

Define each service once in service.json, then run tdk up. TDK generates the local Docker and Tilt wiring, so services update as you code. No Kubernetes, no Compose file to maintain. Not a deploy tool. Production stays on Helm.

Install the CLI

npm install -g @tdk-landscape/tdk-cli-core
Requires Node.js 22.12+ Read the quickstart
Start free Watch it boot  Source on GitHub

Stability: 1.x local dev. Generated files are a contract; verify with tdk config verify. Core CLI is MIT and needs no key. Premium is optional.

14 tiny services healthy in 4.6s on a 16 GB M1 after images existed. Not a cold boot. Claim details.

Watch one manifest become a working service.

No more monolith-shaped AI output. TDK gives coding agents a legible topology, then keeps dozens of services independently owned, generated, and reachable through one local domain namespace.

tdk resource order-frontend --type frontend --stack commerce
input / service.json 1 source 
{
  "appName": "order-frontend",
  "appType": "frontend",
  "port": 3001,
  "framework": "vue",
  "backendName": "order-backend"
}
Reading the service contract
output / .autogenerated/ 0 / 17 files
  • .env.frontend.autogenerated
  • .npmrc.autogenerated
  • .npmrc.docker.autogenerated
  • AGENTS.md
  • Dockerfile.app.autogenerated
  • api-client.ts
  • api-index.ts
  • bunfig.autogenerated.toml
  • bunfig.docker.autogenerated.toml
  • env.ts
  • nginx.autogenerated.conf
  • playwright.config.autogenerated.ts
  • tsconfig.autogenerated.json
  • tsconfig.docker.autogenerated.json
  • validation-report.autogenerated.json
  • vite.config.build.autogenerated.ts
  • vite.config.frontend.autogenerated.ts
Stack contracts generated runtime config / service topology / dependency-manifest.json / docs/architecture.c4 / AGENTS.md

Every service is on the network in seconds.

It looks like weeks of integration. TDK CLI starts the services together and makes their local health URLs available.

14 services healthy in 4.6s On a 16 GB M1 once images exist. Every route goes live as soon as its service passes health checks. *.commerce.localhost
Storefronthttp://app.commerce.localhost/store
Operationshttp://app.commerce.localhost/ops
Orders APIhttp://api.commerce.localhost/api/v1/orders
Inventory APIhttp://api.commerce.localhost/api/v1/inventory
Identity APIhttp://api.commerce.localhost/api/v1/identity
Payments APIhttp://api.commerce.localhost/api/v1/payments

One hundred services, still readable.

A generated ERP-style fixture: finance, procurement, warehouse, payroll, billing, compliance, analytics. Every tiny manifest keeps ownership, port, runtime, and domain visible before an agent writes a single file.

In plain words

Setup delays can hold up new developers: computers need configuration, access needs granting, and instructions can go stale. TDK is designed so tdk doctor and tdk up replace a setup wiki; this has not been measured on a hiring cohort.

TDK CLI is a free, MIT-licensed CLI for starting your services locally. Most teams should stay on free. Premium is $19 per developer per month for extras only. See what waiting costs.

Warm start, images already built

Captured on a 16 GB M1 MacBook after images existed. This is not a cold boot. See the claim details.

4.6s 14 tiny services healthy in 4.6s on a 16 GB M1 after images existed. Not a cold boot.
zsh: tdk up

How it works

Docker runs the containers. Tilt watches services and live-updates containers as you code. TDK CLI writes the configuration Tilt uses.

One manifest in. A running local service out.

Describe a service once, then run it locally with hot reload and health checks.

One manifest

{
  "appName": "orders",
  "appType": "frontend",
  "port": 3001,
  "framework": "vue"
}
Grid of containers representing 100+ microservices
Generated /health fixture: 100 small generated services boot from scratch on a clean CI runner in about about 8 minutes (the run)

A real toolchain, wired together — not a template dump

Every artifact below is produced by an actual generator module in the TDK source tree. See our generated /health fixture with 100 services; it is not an ERP product.

Docker L1–L4 golden layers Docker Compose ×8 variants Tilt + Starlark engine React or Vue 3 frontends (Vite) Vite (frontend / backend / SDK / library) TypeScript ×5 tsconfig variants nginx Traefik Verdaccio local registry Infisical machine identities Prisma + DB migrator Playwright E2E PostgreSQL NATS JetStream Bun .npmrc + .env per service C4 architecture diagrams AGENTS.md for AI assistants Discovery daemon + tdk doctor

One manifest, local containers, selective startup, and a setup wiki replaced by tdk doctor and tdk up. TDK is designed for this flow; onboarding time has not been measured on a hiring cohort.

Everything you stop paying for

Teams assemble this stack from a dozen tools and months of DevOps work. TDK ships it in one CLI — on hardware you already own.

Cloud dev environments

Gitpod / Ona, GitHub Codespaces, Coder, Daytona, Codeanywhere, Replit

$20–$150 /dev/mo $0 — your machine's Docker

Kubernetes dev tooling

Garden, Skaffold, DevSpace, Telepresence, mirrord, Nocalhost — plus weeks of YAML

2–6 weeks DevOps one service.json

Golden Docker images

DIY base-image maintenance, CVE patching, cache strategy

ongoing burden L1–L4 layers included

Per-service build config

Hand-written Vite, TSConfig, Dockerfile, .npmrc and .env for every repo

repeated per service Local runtime configuration

Secrets infrastructure

Vault / Infisical wiring, machine identities, token lifecycle per service

setup + audit time identities pre-wired

Routing, registry and docs

nginx / Traefik configs, private npm registry, architecture diagrams, runbooks

constant maintenance generated, cannot rot

E2E test infrastructure

Playwright environment setup against the full running stack

days per project built-in Playwright

Onboarding runbooks

Wiki pages that rot within a month — replaced by tdk doctor and a live terminal UI

1–3 days per hire tdk up — minutes

Honest answers

Hover to expand. The same answers we give in engineering reviews.

We need Kubernetes for production
Local dev doesn't need to match production. The 14 tiny services were healthy in 4.6s on a 16 GB M1 after images existed. Not a cold boot. Production stays on Helm. Claim details.
What about CI/CD?
TDK is completely decoupled from your CI. Use it for local development and whatever you want for CI/CD. Nothing to migrate away from later.
Is 100 services locally realistic?
As a boot test, yes: this generated /health fixture has 100 small generated services (about 20 lines each) that all became healthy through Traefik in 472 s on a clean CI runner, images built from scratch (the run). It is a scale fixture, not a real ERP product. Real services with real dependencies use more memory. Selective startup runs only what you're working on, and golden L1–L4 layers keep rebuilds near-instant. The discovery daemon regenerates only what changed. Our daily driver is a 14-service stack on a 16 GB M1 MacBook, and it performs superbly; the same engine runs a 27-service monorepo every day.
Where do the savings numbers come from?
The calculator uses inputs you set. Its output is arithmetic, not savings. The starting value of five hours per week is only an editable input, not a typical measurement. We make no savings claim for your team.

Priced against what it replaces

Core stays free. Premium is a separate key for the extras above; no key required to run tdk up.

Free
$0 / MIT core

The full CLI, MIT-licensed, with no license key required.

  • tdk up, scaffold, Traefik, Postgres, Tilt live update, golden layers
  • Playwright, C4, and AGENTS.md when generated in-repo
  • No key required to run the core CLI
  • Community support
Start free →
Premium
$19 / dev / month

Unlocks the paid extras and gives your team a human on the other end.

  • Everything in Free
  • Verdaccio private npm registry for local package publishing and sharing
  • Verdaccio, DDD scaffold, and Sablier idle stop
  • Playwright, C4, and AGENTS.md implementations downloaded with a key
  • Up to 100 project IDs per license key
  • Priority support, next business day
  • Onboarding session for your stack
Request a license →

Need SSO, air-gapped, or an SLA? Pick Enterprise in the license request below — custom pricing.

How $19 compares

vs cloud dev envs

Gitpod starts at $20/mo plus compute. Codespaces runs $60–150 per dev per month at full-time usage. TDK Premium is $19 flat — compute is your machine.

vs enterprise CDEs

Coder and Okteto gate RBAC and SSO behind "contact sales". TDK Premium includes team policies at a self-serve price.

Adopters

Who uses TDK

Teams that run tdk up on their own code. Listed with their consent in ADOPTERS.md.

4 teams listed

Get your
Premium license.

Core stays free. Premium is a separate key for the extras above; no key required to run tdk up. Need SSO, air-gapped, or an SLA? Pick Enterprise.

Free needs no license key — install and run tdk up. Premium/Enterprise requests are submitted directly — no mail client needed, no spam, unsubscribe anytime.