[jag729]

Thanks for your feedback! We've weighed these considerations quite a bit in choosing the right first step for the product.

The docker-compose approach is a valid angle — we’ve seen a couple products built around that workflow. A weakness that led us to our approach is that they generally lack support for projects that involve cloud-specific services. Most of the startups we’ve talked to already have some infra-as-code that describes their cloud infrastructure, and we’re rolling out support for CloudFormation/Pulumi very soon, so customers will be able to bring over infrastructure in any major format. As far as limiting the breadth of services spun up, we've found that removing unnecessary services from the IaC config provides reasonably good results. We plan on adding support for a Docker-compose approach soon, but we felt that starting with IaC would bring us better generalizability out of the gate.