[SynasterBeiter]

Cool concept, but I have a couple of unanswered questions.

- The docs link to digger and I don't really understand what Alicorn is. Is it just a GUI for resources defined using digger?

- The digger docs look unfinished, e.g https://learn.digger.dev/overview/understanding-targets is missing.

- From my understanding, to achieve cloud-agnostic infrastructure specification, digger abstracts the individual pieces of the infrastructure to things like Components and Resources. It then uses these abstractions to generate Terraform (and k8s) files for a given cloud provider. But where is this mapping between, say, a resource and a piece of terraform config for AWS? Do I have to provide it? What's the point, then? Does digger offer some already-prepared Resources? If yes, where?

- Having an example setup would really help to understand.

[igorzij]

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 as an example