Launching today
Flisk
Your AI agent builds the app. Flisk runs it on your laptop.
4 followers
Your AI agent builds the app. Flisk runs it on your laptop.
4 followers
Ask Claude Code, Cursor or Codex for an app with a website, an API, a database and an AI agent. Flisk gets every piece running together on your laptop with one command. Change the code and the app updates instantly. When something breaks, your agent can see what went wrong and fix it. Big project? Start just the part you are working on. Free, open-source core that runs entirely on your machine. Already used by Lekast, MakeOffer, mfin.services and Red Moon Digital.
Interactive
Free Options
Launch Team / Built With
Hi Product Hunt 👋
Most apps aren’t one program. They’re a website, a back end and a database that all have to start together.
Getting that running on your own laptop usually means a pile of setup files nobody wants to own. AI helpers make it worse: they write the app just fine, then break the setup and burn your tokens fixing it.
Flisk does that part for you. You (or your AI helper) describe each part of the app in one small file and run one command. The whole app then runs on your computer: open the link it prints and click around. Change something, and it updates as you save.
Try it in one line:
npx @flisk-sh/flisk demo
(The demo needs Docker. Smaller apps run without it.)
👶 Never written code? There’s a step-by-step guide that starts from “open the Terminal”:
https://github.com/flisk-sh/flisk/blob/main/docs/start/first-time.md
🤔 Not sure it fits your team? Three quick questions, and you get a score:
https://github.com/flisk-sh/flisk#is-flisk-right-for-your-team
✅ What it is: the setup part of building an app. It starts every part, connects them, and keeps them in sync while you work. flisk doctor tells you in plain words what’s missing on your machine.
❌ What it isn’t: hosting. It doesn’t put your app on the internet. And if Docker Compose or Tilt already works for you, keep it.
Free and open source (MIT), no account or key needed. Works on Mac and Linux; on Windows through WSL2 (Ubuntu).
For developers: one service.json per service. Flisk writes the Dockerfiles, the Compose file and the Tiltfile; Docker runs the containers and Tilt live-updates them. flisk up shop starts just that stack, flisk config verify catches drift, and flisk ui is the terminal dashboard. Production stays on Helm, Argo CD or Kustomize.
A question for you: if your app already runs fine on your laptop, would one small file per part be worth it, or just one more thing to keep in sync?
⭐ GitHub: https://github.com/flisk-sh/flisk
🗞 Also on Hacker News today: https://news.ycombinator.com/item?id=50187746