Interesting. My initial feeling is this is weird - acl in ORM. But it kinda makes sense with a second thought. Rules are closer to the source of the problem (schema). It can probably remove lots of headaches securing things at an upper layer. Not sure how well this scales when you have tons of rule though.

Is there any plan for Drizzle support?

Thank you for the recognition. We have some production users who have hundreds of policy rules. While they mentioned that having visual tools for new users to quickly understand the policy would be beneficial, overall it is functioning well. They state that it is more transparent and efficient compared to the traditional approach.

The current approach relies on schema and code generation, which is not possible in Drizzle. We could have used decorators and string literals to achieve this, but that would negatively impact the developer experience. Therefore, at least for now it's not in our plan.

I have the same thought on this as we are on Drizzle too

This looks fun! Someone tells a serious use case please haha

This is sad. Evernote was phenomenal and I really loved it, years ago.

Especially when it was a C++ application, not C#.

Why did they rewrite?

probably for developers' sanity :)

Good write up. If I were to build a new SaaS and I’m not anticipating lots of users and concurrency. Regardless the single writer concern, does it suffice as the main storage? What’s is the consistency guarantee?