Oops; I posted on this earlier (by a few hours) submission [1] on SpiceDB story.<p>Reposting (with small edits) here for visibility by founders:<p>Super cool. I’ve been looking at other groups trying to implement such systems, many of which appear very nascent or otherwise missing key features.<p>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 (whether that's a fool’s errand is 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.<p>QUESTION: 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 dilemma, equally great for both )<p>[1] <a href="https://news.ycombinator.com/item?id=28707072" rel="nofollow">https://news.ycombinator.com/item?id=28707072</a>