Super cool, and surprised this has t gotten more traction (so far). I’ve been looking at other groups trying to implement such systems, many of which appear ver

Super cool, and surprised this has t gotten more traction (so far). I’ve been looking at other groups trying to implement such systems, many of which appear very nascent or otherwise missing key features. This looks like it solves a lot of problems for me, a solo developer, trying to build a enterprise-targeted product as a side project (hopefully not a fool’s errand, but that’s another discussion). In particular, correct and efficient implementation of PER OBJECT permission seems like a hard problem, and many other (external) solutions merely control by object type. Building per object control into the product (integrated in the code itself, with no external gateway/proxy/layer) requires really detailed thought and planning related to ACL, group membership, etc., and any change in plans later means changes to potentially deeply integrated code. Question: profitability and commercializability of this product and associated support, hosting etc. etc. notwithstanding, do you see greater value for (a) large teams with huge and complex products involving many moving pieces, that need a consistent AuthZ layer, or (b) small teams that need robust AuthZ and don’t have the time and human power to develop it themselves? (Or c, false dilemm, equally great for both ) edit: Apparently this was also posted here: https://news.ycombinator.com/item?id=28709886 https://news.ycombinator.com/item?id=28709886