Run microservices locally.
No Kubernetes required.
TDK CLI lets you run 5-120+ microservices locally with Docker only.
One service.json file generates 10+ configurations automatically.
Join the Waitlist
This opens your email app with a pre-filled message. Just hit send!
The Kubernetes Learning Curve
Every microservice tool forces you to learn infrastructure you don't need for local development.
Don't know Kubernetes
Yet every tool forces them to learn it
Cloud dev environments
What teams pay when they give up
Garden startup
vs 5s with TDK
Services proven
Running locally at scale
From one manifest to 10+ configs
Write the source of truth. TDK handles the rest.
Write service.json
Simple JSON with app name, type, port, and features
TDK generates
Docker, Vite, TSConfig, nginx, env files, and more
Tilt orchestrates
Built on Tilt. Hot reload. Docker containers.
You write code
No K8s knowledge needed. Focus on your product.
One manifest. Multiple configs.
Head-to-head with alternatives
TDK is the only tool that's manifest-driven AND Kubernetes-free.
| Feature | TDK CLI | Garden | Skaffold | DevSpace |
|---|---|---|---|---|
| Kubernetes required | ✓ No | ⚠ Optional | ✗ Yes | ✗ Yes |
| Manifest format | Simple JSON | Complex YAML | Complex YAML | YAML |
| Auto-generated files | ✓ 10+ files | 3-5 files | ✗ Manual | ✗ Manual |
| Golden Docker images | ✓ L1-L4 | ✗ DIY | ✗ DIY | ✗ DIY |
| Auto-discovery | ✓ Scans dirs | ✗ Manual | ✗ Manual | ✗ Manual |
| Local-only mode | ✓ Docker only | ✗ Needs cluster | ✗ Needs cluster | ✗ Needs cluster |
| Open source | ✓ MIT | ✓ Apache | ✓ Apache | ✗ Commercial |
Winner: TDK — only tool that's manifest-driven AND Kubernetes-free
Who should use what
Choose the right tool for your team's expertise.
Platform Engineers
Use Garden or DevSpace
They WANT Kubernetes and have the expertise to manage it.
Senior Backend Devs
Use Tilt or Skaffold
They tolerate K8s complexity and can handle the learning curve.
Full-Stack Developers ✓
Use TDK
Don't know K8s, don't want to learn it. Just want to write code.
Product Teams ✓
Use TDK
Need to test features across 10+ services without waiting for DevOps.
Startups ✓
Use TDK
Outgrew "works on my machine" but not ready for platform team overhead.
Common questions
Quick answers to frequent concerns.
But we need Kubernetes for production
Local dev doesn't need to match production. Use TDK for fast local iteration (5s startup), K8s for prod when ready. Decoupled.
What about CI/CD?
TDK is completely decoupled from your CI. Use it for local development, whatever you want for CI/CD. No lock-in.
We already use Garden
TDK complements Garden. Use TDK for local speed (5s vs 30s startup), Garden for prod-like integration tests. Best of both.
Is 120+ services realistic locally?
Yes, with selective startup. You don't run all 120 at once—just what you need. Proven at scale with proper resource management.
Be the first to try TDK CLI
Join 500+ developers on the waitlist. Get early access, exclusive updates, and help shape the future of local microservice development.
Which features interest you?
No spam • Early access invites • Unsubscribe anytime
Want to contribute or star the project?
Star on GitHubWe're building something special
TDK CLI is currently in active development. The core generators are working, the architecture is solid, and we're battle-testing it with 120+ services.
Join the waitlist to get:
- Early access to the beta release
- Exclusive updates on new features
- Shape the roadmap — your feedback matters
- First dibs on documentation & tutorials
Current Status
Expected Launch: Q1 2026