Thank you so much for sharing this! We launched Alicorn to focus on one thing only: multicloud. Digger value prop was less clear. Under the hood Alicorn uses s

Thank you so much for sharing this! We launched Alicorn to focus on one thing only: multicloud. Digger value prop was less clear. Under the hood Alicorn uses same Digger engine, but adds PaaS mode as a starting point and Kubernetes to be truly cloud agnostic. Understanding targets docs fixed- thank you for pointing that out! The missing bit for cloud agnostic specs is targets. It's essentially a meta-template, collection of "Terraform generators" that take in higher level stack definition aka "infrastructure interface" and producing Terraform specific to a given cloud provider. You don't have to provide it, but you can customise Targets, or built entirely bespoke - it's essentially TF + basic templating on top. Check out https://github.com/diggerhq/target-fargate https://github.com/diggerhq/target-fargate as an example