Earlier quoted context omitted.
As a founder of a startup building an authorization product, I can definitely say it's super appealing to build this as a service! It makes for a an easier story around monetising it. When we were building Oso [1], we were optimising for the best thing for developers, and reached the same conclusion as you... (a) It doesn't make sense to rearchitect your app to move all the data to a separate service, and (b) it's wa…
Seriously -- this looks *awesome.* Oso's policies look almost exactly like the Pundit policies in my business's Rails app, which is awesome to see. How do you plan on monetizing, if you haven't already?
We're heavily focusing on adoption of the open source product right now for helping developers with application authorization. We do currently charge for things like support + consulting, but in the future we're planning on providing additional functionality through a service that would be more on the operational/security side.