← Directory

ComposeCraft

ComposeCraft is a tool for managing, editing, and sharing Docker Compose files.

  • Cloud
  • Infrastructure
  • Other
  • Productivity
  • Tools & Utilities
ComposeCraft is a tool for managing, editing, and sharing Docker Compose files. It provides a clean graphical interface for building multi-container configurations, reviewing services, and exchanging reusable compose files. Use it to create or adjust stacks without hand-editing YAML and to share reusable app recipes.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
44last commit 293 days ago
Popular
601,039 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
1,039
Open issues
16
Last commit
2025-12-26
Latest release
v1.1.3
License
MIT
Activity
stale

Checked 8 days ago - source: GitHub (composecraft/composecraft)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set up compose.yaml with ports and volumes Write your compose.yaml (the recipe for your app) with the services you need, the ports to expose, and volumes that connect your local files to the containers. Without ports and volumes, the app may not be reachable or your data/settings may be lost when the container restarts. source
  • Give your project a clear name If you run several Compose apps on the same machine, use the -p flag (project name) to list, stop, or read logs for the right set of containers. Without it, containers and logs can be hard to tell apart. source
  • Open a shell to check a service Use docker compose run web bash (or the service name in your compose file) to start a one-time copy of the service and inspect files, logs, or config. This helps when the app starts but you can't tell what is wrong inside the container. source

Fetched 13 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I run the recommended self-hosted ComposeCraft stack?

Clone the repository, move into the webapp directory, and run docker compose up -d. It then starts at port 3000.

Which environment variables are required for self-hosting?

Set SECRET_KEY, MONGODB_URI, and URL in the .env.local file.

How can I disable SaaS and telemetry features?

Use the optional CORE_ONLY variable to disable SaaS features and the DISABLE_TELEMETRY variable to disable PostHog analytics.

Can I bring an existing docker-compose.yml into ComposeCraft?

Yes, it supports importing existing docker-compose.yml files and exporting your creations.

How can I share a ComposeCraft diagram?

Generate a public link to share the Docker Compose diagram with others.

Answers sourced from composecraft.com, github.com

Community

Collected 11 days ago - public community threads