cfs VS cloudknit

I started something like this here. It’s a tool that lets you visually (or via the CLI) search and view all your AWS cloud resources.

https://github.com/khalidx/cfs

I mostly use it when starting a new job or contract and am trying to get the “lay of the land” — what exists where, how many resources there are, etc.

Thanks for the question. I'm assuming you are talking about the open source Pulumi and Terraform CLI. We don't compete with them but rather integrate with them. These IaC tools and even other cloud native tools like Helm/Kustomize work well to manage individual components of your "Environment" but folks still need to write pipeline code on top of these tools to get an Environment thats useful. The pipeline code is imperative and becomes very difficult to manage as you scale. Environment as Code is a declarative way (with state management) to provision entire environment.

If you think about this using a Lego analogy, CloudKnit connects various lego pieces (components within your environment like networking, eks, db, web apps, backend apps) and builds a lego toy (entire environment). Those various components will still be provisioned using Pulumi, TF, Helm Kustomize etc.

We also provide workflow, visibility for the environments.

We have a diagram in our README (https://github.com/cloudknit-io/cloudknit#readme) that explains how CloudKnit fits in with existing tools. Please check "Diagram 1: Where does CloudKnit fit in with existing tools".

Also, here is a talk I gave about Environment as Code that might help understand the concept behind CloudKnit better: https://www.youtube.com/watch?v=INCUMYl2B-0&t=9s

Hope this helps.

Thank,