Flisk CLI
Your whole stack, running locally.
FreeCLIDevOpsCode15 impressionslaunches Oct 141 comment
Maker links to DevHunt
Comments
>log in to commentHello DevHunt community! Flisk lets you define each service in a simple service.json and spin up your whole multi‑service stack locally with a single `flisk up`. It auto‑generates Docker, Tilt wiring and local domain URLs, keeping production on Helm. Would love your thoughts on the workflow.
More CLI tools →74 free dev tools →
Flisk CLI runs a multi-service stack locally with a single command using service.json definitions.
- for
- Developers building and testing multi-service microservice applications locally.
- pricing
- freemium
- license
- MIT
Key features
- Service manifest — Define each service once in a service.json file.
- One-command start — Run all services with `flisk up`.
- Auto-generated Docker/Tilt wiring — Creates Dockerfiles and Tilt configs for live code updates.
- Fast startup — 14 services become healthy in 4.6 s on a 16 GB M1 after images exist.
- Contract verification — Generated files can be verified with `flisk config verify`.
- Open-source core — Core CLI is MIT-licensed and requires no license key.
Use cases
- Develop and test a full e-commerce microservice stack locally
- Provide a readable topology for AI coding agents
- Iterate quickly on dozens of inter-dependent services without Compose files
- Prototype new services while keeping production on Helm
Flisk CLI vs alternatives
 Flisk CLI |  Docker |  Railway |  Coolify |  Daytona | |
|---|---|---|---|---|---|
| Best for | Local multi-service stack orchestration | Container execution | Cloud dev platform | Self-hosted app platform | Remote dev environments |
| Pricing | Freemium | Subscription | Subscription | Free | Free |
| DevHunt upvotes | 1 | 0 | 0 | 0 | 339 |
| Launched | Oct 2031 | — | — | — | May 2024 |
- Flisk CLI vs Docker: Docker provides container runtime but no automatic multi-service orchestration from a single manifest.
- Flisk CLI vs Railway: Railway offers cloud dev environments and deployments, whereas Flisk focuses on local stack orchestration.
- Flisk CLI vs Coolify: Coolify is a self-hosted Heroku/Vercel alternative with CI/CD, not a local CLI for multi-service startup.
- Flisk CLI vs Daytona: Daytona sets up remote development environments with a single command, while Flisk runs the stack locally on your machine.
Flisk CLI FAQ
Is Flisk a deployment tool?+
No, it is only for local development; production deployments stay on Helm.
Do I need Kubernetes to use Flisk?+
No, Flisk runs locally without Kubernetes or Compose files.
How fast can services start?+
In the demo, 14 services became healthy in 4.6 seconds on a 16 GB M1 after images were present.
Is the CLI open source?+
Yes, the core CLI is MIT-licensed and does not require a license key.
What is the premium offering?+
Premium features are optional; the core CLI remains free.
Summarized by DevHunt from flisk.sh · Oct 26, 2026. Details may change; check the official site.
