Flisk generates the Docker and Tilt config for every service, so you skip the setup week and go straight to building. No Kubernetes. No Compose file to maintain. Built for engineers and AI agents.
npm install -g @flisk-sh/flisk
flisk project --yes # set up the project
flisk resource orders-api --type backend --stack shop --yes # scaffold a service
flisk up shop # run it with hot reloadDescribe each service once in service.json. Flisk wires up the rest: proxy, Postgres, monitoring, health-checked startup order, and hot reload.
- Onboard in one command, not a week. New teammates clone, run
flisk up, and code. - Run only what you need. Start the
shopstack without booting the whole system. - Nothing hidden. The generated Docker and Tilt files are plain and readable.
Give your coding agent one contract instead of a pile of Compose and Dockerfiles. Agents write service.json, run flisk up, and get a working local environment on their own. tdk-skills gives them the skills to do it.
| What you get | Flisk | Compose | Local Kubernetes | Tilt |
|---|---|---|---|---|
| Scaffold a new service in one command | ✅ | ❌ | ❌ | ❌ |
| Hot reload on file change | ✅ | ✅ | ||
| Health-checked startup order | ✅ | ✅ | ||
| Proxy, Postgres, monitoring included | ✅ | ❌ | ❌ | ❌ |
| Runs without a cluster | ✅ | ✅ | ❌ | |
| Start one slice of a big system | ✅ flisk up <stack> |
100 services. All healthy in 112 seconds. 1.6 GiB of memory. Zero OOM kills. On a 16 GB machine. See the benchmark (generated
/healthfixture, not a product example).
Yes, if you're an engineer or tech lead running several services locally and you spend more time on Compose, Dockerfiles, and onboarding than on shipping.
Not yet, if a single Compose file already works for you. Production deploys stay on Helm; Flisk is for the inner loop.
Project one repo, one local landscape
Stack a business slice: shop, identity, kitchen… → flisk up <stack>
Resource one API, frontend, worker, or database
service.json what it is and what it depends on
.autogenerated/ generated local wiring
Docker runs the containers. Tilt runs the dev loop. Flisk writes the config. Generated files are plain and readable, with no hidden platform.
| I want to see… | Start with |
|---|---|
| The smallest working setup (2 stacks, 4 services) | tdk-example |
| A SaaS dashboard with a checkout button | tdk-saas-starter |
| A storefront and catalog API (Vue 3 + Hono) | tdk-ecommerce-example |
| Auth, queues, and email locally (OIDC, NATS JetStream, Mailpit) | tdk-auth-queue-email-example |
| A multi-stack business system (reservations, kitchen, menu, floor) | tdk-restaurant-example |
| Identity admin, portal, and compliance stacks | tdk-user-management |
| Flisk inside Docker Compose, no host install | tdk-docker-compose-example |
| Guided lessons | tdk-labs |
| 100 services at once | tdk-erp-system |
| ⭐ flisk | The CLI |
| website | Docs |
| releases | Prebuilt binaries for Linux and macOS, with checksums |
| tdk-skills | Agent skills so AI agents can write service.json and run flisk up |
| awesome-tdk-framework | Curated examples, docs, and community projects |
- Find a first task:
good first issue· CONTRIBUTING.md - Show what you built: open an issue and we'll feature it in Awesome Flisk.
- Like it? A star helps other developers find it.
Also from us: free code-scanning actions on GitHub Marketplace
Each action runs checks and uploads SARIF to GitHub Code scanning. Unofficial community actions, not made or endorsed by GitHub or the CodeQL team.
| Action | Checks |
|---|---|
| Starlark Analyzer | Tiltfiles and *.star files |
| Goose Analyzer | *.goose files |
| Lobster Analyzer | Lobster checks |
