flisk
Flisk is an open-source command-line tool for running an application's APIs, websites, workers, AI agents, and databases locally with one command. It uses service.json manifests to generate readable Docker, Compose, Tilt, routing, health-check, and environment configuration, with production deployment left to tools such as Helm.
At a Glance
- Engineering teams running several local services
- Startups and founding engineering teams
- Product engineers working across frontend, backend, workers, and data services
- Platform, DevOps, and developer-experience teams
- +2 more
AI Tools by flisk
(1)Flisk
Local Dev Runtime CLI for Docker
Discussions
No discussions yet
Be the first to start a discussion about flisk
Latest News
Flisk v1.4.12 released; signed binaries and the @flisk-sh/flisk@1.4.12 npm package announced.
The CLI added flisk os, which locates and starts the separately shipped FliskOS local desktop app for Flisk projects and coding agents.
Flisk v1.4.11 released with signed binary checksums and npm package update.
Flisk v1.4.10 released with signed binary checksums and npm package update.
Products & Services
MIT-licensed command-line tool distributed through @flisk-sh/flisk and prebuilt binaries. It discovers services, imports existing Docker Compose projects, scaffolds projects and resources, generates local infrastructure, and runs stacks with flisk up.
Optional keyed extensions for capabilities such as Verdaccio/local package registry, DDD scaffolding, on-demand service start/stop, synthetic monitoring, and selected generators. The core CLI remains free and open source; some generated capabilities including Playwright, C4, and AGENTS.md are available in-repository without a key while downloaded implementations require one.
The flisk os command locates the separately shipped FliskOS desktop app or fliskos executable and starts it for Flisk projects, coding agents, and Flisk apps; it does not install the app.
Market Position
Flisk positions itself as a local-first inner-loop workbench rather than a deployment platform, cloud IDE, or Kubernetes replacement. It differentiates from Docker Compose by scaffolding and wiring services, from local Kubernetes by avoiding a cluster, and from Tilt by generating the surrounding service contracts and infrastructure; its comparison materials also discuss Skaffold, Garden, Dev Spaces, Gitpod/Ona, Codespaces, Coder, Daytona, and Okteto. The key positioning is inspectable generated standard files, selective startup, health-checked topology, and AI-agent context with low lock-in.
Founding Story
Flisk was created to reduce the setup and maintenance burden of service-heavy applications: instead of asking developers or coding agents to hand-maintain Compose files, Dockerfiles, routing, and setup wikis, a small service contract describes each resource and Flisk generates an inspectable local environment. Development began on April 21, 2026; the current repository was created September 19, 2026, and the npm package was first published September 21, 2026.
Business Model
Revenue Model
The core CLI is free and MIT-licensed. Flisk's commercial model is optional Premium/Team licensing for keyed extensions and capabilities; the site also describes a per-developer Team plan.
Pricing Tiers
MIT-licensed core CLI; no key is required for flisk up and the basic local development workflow.
Public pricing shown on Flisk's September 2026 comparison page.
Optional keyed extensions; the quickstart says each key covers up to 100 distinct projects, while Enterprise is unlimited.
Target Markets
- Engineering teams running several local services
- Startups and founding engineering teams
- Product engineers working across frontend, backend, workers, and data services
- Platform, DevOps, and developer-experience teams
- Teams building with AI coding agents
- Organizations maintaining service-heavy or microservice repositories
- Local development of multi-service and microservice applications
- Replacing setup wikis and hand-written local infrastructure
- Rapid onboarding of developers to service-heavy repositories
- Running only the business slice or stack relevant to a task
- AI-assisted development where coding agents need explicit topology and service boundaries
- Importing an existing docker-compose.yml into manifest-driven local development
- Lekast
- MFin Services
- MakeOffer
- RedMoon.Digital