The compose stack moves off the laptops

Your product is nine services in a docker-compose file, and every laptop on the team pays for it: fans, RAM, the weekly "compose is broken again" thread. Move the whole thing into a Hoody container. A debian/13 container runs the Docker daemon natively: apt install docker.io, clone the repo, docker compose up. Nested containers are supported, not tolerated.

Two things change. Every service port in the stack is reachable as an HTTPS URL, because any port on the container is an address: a teammate opens your dev stack from their machine, or their phone. And the entire Docker host: images, volumes, the seeded database: is one filesystem, so one snapshot captures the stack in a state compose alone can't describe.