Our take
Newless than six months old and changing fast- Activity
- 90
- Community
- 82
- Issues
- 92
- Pull requests
- 84
- Merges more pull requests than 96% of the projects we track
- Releases more often than 93% of the projects we track
- Closes issues faster than 81% of the projects we track
Flisk is a capable, actively developed local runtime for teams that want generated multi-service setup and agent-accessible controls, but it is still a young project.
Good fit if
- You want a single local workflow for multiple app services and are comfortable describing them with service.json.
- You want coding agents to operate the local runtime through MCP, or need an optional Docker-free process mode for simpler apps.
- You can work with Node.js 22.12 or newer and, for container-based stacks, Docker and Tilt.
Look elsewhere if
- Your existing Compose or Tilt setup already works and you do not want generated configuration or Flisk manifests.
- You need Flisk to deploy to production or target Kubernetes, which the project explicitly does not do.
- You need a mature, long-established tool: the project is new, even though its release and commit activity is high and contributions are not concentrated in a single contributor.
All health signals
| Last commit | 2026-11-17 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 100+ (latest v1.4.69, 2026-11-17) |
| Contributors | 100+ (top contributor: 45% of commits) |
| Issues closed, last 90 days | 34+ (typically closed in 0 days) |
| Pull requests merged, last 90 days | 94 (typically merged in 0 days) |
| Project age | 59 days |
Checked on 2026-11-17 with the GitHub API.
Project history
Daily GitHub snapshots since Nov 18, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
53Forks
109More snapshots will appear as the daily collection continues.
Overview
Flisk is a TypeScript CLI for local development of multi-service apps. It generates and manages Docker Compose and Tilt configuration from service.json manifests, so developers can start services, dependencies, and a local gateway together instead of maintaining that setup by hand. Small apps can run as local processes without Docker; the container-based workflow uses Docker and Tilt.
An MCP server lets AI coding agents such as Claude Code, Cursor, and Codex inspect and control the running stack. Flisk targets macOS and Linux directly. On Windows, local-process projects work natively, while the Docker-based workflow runs in Ubuntu on WSL2. It is a local development runtime, not a production deployment platform.
Key Features
- Generates Dockerfiles, Compose entries, Tilt configuration, gateway routes, and health checks from per-service
service.jsonfiles. - Starts services in health-checked dependency order and provides local URLs through a gateway.
- Supports live updates through Tilt for container-based development.
- Offers a local-process mode for services with a declared start command, without requiring Docker.
- Imports existing Docker Compose projects into Flisk service manifests.
- Provides an MCP server with tools for agents to check health, inspect logs, and control services.
- Includes scaffolding for app services and AI agent systems, with optional databases and MCP tool servers.
- Checks generated configuration for manual edits and reports environment requirements with
flisk doctor.
Use Cases
- A developer building a website, API, and worker can start and inspect the whole local stack without hand-maintaining its Compose and Tilt configuration.
- A team with an existing Compose project can import it and use Flisk's commands and agent interface to manage local runs.
- A developer using Claude Code, Cursor, or Codex can let an agent start services, check their health, and retrieve logs through MCP.
- An AI application developer can run an agent alongside its tools and data services as one local stack.
What you need
Detected in the repository
- Node.js >=22.12.0 (from package.json)
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the CLI and try the demo:
npm install -g @flisk-sh/flisk
flisk demo
The demo can use local processes without Docker; the full multi-service container workflow requires Docker and Tilt. See the README for setup details and platform-specific instructions.
Alternatives
- Dockge: Dockge manages existing Docker Compose stacks through a web UI, while Flisk generates Compose or Tilt config from service manifests and offers agent controls.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| flisk | TypeScript | MIT | 51 | New |
| Dockge | TypeScript | MIT | 24.8k | Maintained |
Considerations
- Flisk is young, so its active development and frequent releases do not yet establish a long track record. The repository also has a substantial open-issue backlog, worth reviewing for issues relevant to your workflow.
- The container workflow depends on Docker and Tilt. Windows users need WSL2 Ubuntu for that path; native Windows support is limited to local-process projects and selected inspection commands.
- The project manages local development configuration and does not replace production deployment tools. Teams should keep their existing production workflow.
- Generated files are intended to be managed by Flisk. The tool checks for manual edits, so teams that prefer to maintain Dockerfiles, Compose files, or Tiltfiles directly may find its workflow restrictive.
- The core CLI is MIT-licensed; the README describes some optional Premium extras that require a key.
Found this useful?
Share it with someone who would like flisk.