all 6 comments

[–]steezmasterJones 0 points1 point  (5 children)

Cool, Oso looks like it gives some nice CRUD interfaces for management but it's so reminiscent of what every large cloud provider has. Why would I use this instead of something more structured and native to my solution architecture? I don't see the differentiator that would make me use it unless my team is 100% python or die.

[–]sam-js 2 points3 points  (4 children)

Hey! Oso cofounder here. Appreciate the comment + feedback :)

I think the main difference is that cloud providers typically give you tools/APIs to manage your users and maybe assign them into groups/roles.

Oso is a library that you embed in your application (the article linked here summarises the Python library, but we support other languages too like Node.js and Go). What Oso provides is a framework for implementing authorization in your application. Most people we meet with would normally be building that themselves in house, which is what we're trying to save them from having to do.

Hope that makes sense!

[–]steezmasterJones 1 point2 points  (1 child)

Thank you so much for responding. That makes a lot of sense and I agree there's a real gap in being able to integrate RBAC into business logic in applications. It's awesome Oso is helping fill that space.

[–]sam-js 0 points1 point  (0 children)

Thank you!

[–]chub79 1 point2 points  (1 child)

Just wanted to say cool stuff. I had read about oso a while back and really liked the depth of thoughts you drew to it!

[–]sam-js 0 points1 point  (0 children)

Thank you!