I think it would probably be unreasonable to say "IAM Conditions when?" in a Launch HN if one had to build those things from scratch. That would be ferociously hard and not a sane ask right out of the gate. But since IAMSpy already exists, and according to you there's some non-trivial amount of IAM evaluation already in Cartography, then what I'm asking is whether you envision your future as one of ("eh, it's good enough", "we're integrating more libraries that attempt to formalize IAM", or "we'll roll our own policy engine in python, how hard could it be")
Further illustrating my point, you linked to a .yaml file with "s3:GetObject" seemingly applied to an S3Bucket saying "can read" but that's for sure not systemically true for a monster list of reasons. I get the impression that Wiz makes their bread and butter on helping people understand when they actually have open S3 buckets and not just giving them a report full of false positives
I do appreciate this can come across as busting your chops, but I don't mean to shit on you, or your product, or your launch. I'm just pointing out that if you put "You can think of us as an open-core Wiz alternative" in the 2nd sentence of your announcement, there is a massive opportunity for expectations being out of alignment unless you have a plan to get from where you are to Industrial Grade Introspection. The other side of that coin is that if you do have the background for it, as your pseudo-resume implied, then it's a massive opportunity to give them a run for their $5 billion, too
1: and it's the misconfiguration that I would want a reasonable tool to chirp about, not "omfg token.actions.githubusercontent.com can get into your Role!"