flisk vs Dockge
Local app development and Compose stack management compared
flisk runs multi-service applications locally, generating Docker Compose and Tilt configuration from service manifests and offering controls to AI agents through MCP. Dockge provides a self-hosted web interface for editing and operating Docker Compose stacks; it keeps stack files accessible for standard Compose commands.

flisk: Run Multi-Service Apps Locally for AI Agents
Flisk is a TypeScript CLI for running multi-service apps locally, with or without Docker. It generates Docker Compose and Tilt configuration from service manifests and exposes runtime controls to AI coding agents through an MCP server.

Dockge: Manage Docker Compose Stacks in a Self-Hosted UI
Dockge is a self-hosted, stack-oriented manager for Docker Compose, built on Docker Compose V2. It lets you edit, deploy, and monitor compose.yaml stacks through a reactive web interface while keeping their files on disk for normal CLI use.
| flisk | Dockge | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Stars | 51 | 24.8k |
| Forks | 109 | 865 |
| Last analyzed | Nov 17, 2026 | Nov 7, 2026 |
Key differences
- flisk focuses on local development stacks, including dependencies and a gateway; Dockge focuses on managing Compose stacks rather than individual containers.
- flisk can run services as local processes without Docker when they have a declared start command; Dockge requires Docker or Podman and Compose.
- flisk generates configuration from service manifests and checks for manual edits; Dockge lets users edit compose.yaml while keeping files in a regular directory.
- flisk provides an MCP server for agents to inspect and control services; Dockge provides a web interface with deployment output, an interactive terminal, and multi-host agents.
- flisk targets macOS and Linux, with its container workflow on Windows running in Ubuntu on WSL2; Dockge supports listed Linux architectures and excludes Windows.
- Both projects are TypeScript and MIT-licensed, but their scale differs: the supplied data lists 51 stars for flisk and 24.8k for Dockge.
Choose flisk if you…
- need to start and inspect a multi-service local app from service manifests.
- want AI coding agents to check health, retrieve logs, or control the running stack through MCP.
- prefer a local-process option for eligible services without requiring Docker.
Choose Dockge if you…
- want a self-hosted web interface for editing and operating Compose stacks.
- manage stacks across multiple Docker hosts or need live deployment output and an interactive terminal.
- want Compose files to remain directly usable with standard Compose commands.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.