We have been enjoying Casbin (ABAC): - technically: embedded in your DB, so not another infra problem + can stay in-DB for hotpath queries (ex: view all). As

We have been enjoying Casbin (ABAC): - technically: embedded in your DB, so not another infra problem + can stay in-DB for hotpath queries (ex: view all). As db-native RLS etc keeps maturing, my bet is this is where a lot will end up anyways. This is orthogonal to their discussion of service vs monolith - it enables working at the data tier vs app tier. - governance: our app does not depend on an outside company At the same time, it was surprisingly slim pickings for such a core thing, so more diversity the better! Edit: For context, we have been thinking a lot about authorization recently and investing here, so a recent post on 'The Sharing Paradox' on how we view it as an important way to grow successful team use, esp with modern features like friendly ABAC UIs: https://www.graphistry.com/blog/100x-sharing-paradox https://www.graphistry.com/blog/100x-sharing-paradox