Projects & Stacks
Every Compose project, its status and its path — listed and searchable.
- Compose projects listed per host with live status
- Container counts and deployment path per project
- Source indicators for Git, language and visibility
- Four creation paths: Blank, Catalog, Git URL or YAML URL
- Pick the target host, branch and project name at creation time
- Environment variables written straight to .env in the project folder
- Create & Deploy in a single action, or manage an existing project in place
What it looks like
Group containers into Docker Compose projects per host, with running status, container counts, filesystem path, source indicators and a management action per project — and create new projects blank, from the catalog, from a Git URL or from a Compose YAML URL.


Project is the unit of work
APIs, backends and their dependencies belong to a project. Deploys, restarts and rollbacks operate on that boundary rather than on individual containers.
Four ways to start a project
A blank project for hand-authored Compose, a catalog template for a golden stack, a Git repository URL with an optional branch for code you already ship, or a plain Docker Compose YAML URL. Each path takes a project name, a target host and optional environment variables, then deploys immediately.
Git-aware projects
Projects that originate from a repository show their source, so an operator always knows which code produced a running stack.
Dozens of stacks stay legible
Grouping and search keep an estate of many APIs, databases and proxies navigable from a single table.