Permit.io - Never build permissions again

@benln @asafchn @or_weis Permit provides permissions as a service👍Congratulations on the launch of Permit.io. good job guys❗️

@benln Thanks for hunting us - you rock :)

@product_at_producthunt , Oh wow! That's a fantastic statement. Can we quote you on that? 😉

@gemanor Go for it! I also suggest you go to the source and reach out to @eric_whitney aka OldCoderGuy (https://www.tiktok.com/@oldcoderguy)

@eric_whitney @oldcoderguy @product_at_producthunt noted!

@rrhoover Spot on - exactly the same pains I went through - that brought me to create Permit.

@rrhoover, this summarises the background story of most of our team. We are very passionate about solving that problem 😉

@gemanor @or_weis big fan of solving problems you really understand. :) On that note, why hasn't this been solved already? RBAC and permissioning is a long-standing challenge and known problem for many. Curious how Permit.io compares to other solutions or if you're taking a different approach.

@or_weis @rrhoover Permit is a solution for (mostly) application-level permissions. We are giving developers the power of advanced authorization into their application with single lines of code. Permit.io isn't about RBAC only. It is a one-stop shop that allows developers to seamlessly scale for more advanced models (ABAC, ReBAC). It also solves problems in scaling distributed applications (which is quite a new challenge), centralized audit, and more. In general, Permit is new because the fast-paced app development world that made such solutions necessary.

@rrhoover @gemanor to add to Gabriel's answer - an important factor is maturity of standards and mindset - before Authentication as a service matured with standards like JWTs and before devs learned that this type if critical infrastructure is better acquired from experts (nowadays who would be building AuthN on their own) - talking about Authorization as a service was basically impossible.

@gusoliveira_ Hi - for sure - just take a look at our ReBAC modeling , it supports recursive nesting and role derivation. https://docs.permit.io/how-to/bu... We have multiple levels of audit logs, webhooks, and more

Hey @kingromstar, You've brought up some good points here, and I want to address them from two perspectives. From a technical standpoint: Authorization that is implemented as part of the application is limited. * It is hard to use it in multiple apps (which is the usual case in the distributed computing/cloud world) * It's expensive to scale from one permission model to another (think of the need for a relationship between resources and roles in different apps) * It creates spaghetti code between the permission configuration and the enforcement point. From a product standpoint: * Every change needs a code change and engineering work. * Auditing and analyzing authorization decisions is complex. * The application architecture limits the flexibility of the permission model. I can list some more limitations, but the main point is: Why should we reinvent the wheel to solve it for every app if we can use a well-defined product? We can see the same wave if we look at the authentication space for the last ten years. We hope to bring the same revolution to the authorization space. I hope that I have answered your question. Here are some more related information and reading materials: https://www.permit.io/blog/roll-... https://www.permit.io/blog/zanzi... https://www.permit.io/blog/autho... We are also very easy-going, and you can find some time with our engineering team here to discuss further: https://calendly.com/permitio/me...

@thomas_collett thank you 🙏 Looking forward to see you as a user ☺️

@thomas_collett @gemanor he already is :D

@thomas_collett @or_weis Sorry, my late-night English-Hebrew transform took time to process Thomas to Tom. Good to see you here ☺️

@dliecht soon to be used as part of your work applications ;) Thanks for the comments

@alex_chepovoi, this is just a hint for the DevEx in our product. Thanks for your support :)

Thanks @liran_tal1 Love the SDK reference 💪

Well, @itspatzer,permissions company == privacy as a first-class citizen 🤩 Thanks for your support

@itspatzer Credit is also due to our awesome legal team at Pearl Cohen 💪

Thanks for your kind words, @chetanmedia. We look forward to hearing more about your experience after taking a ride on the product.

@yowmamasita Thanks Ben it's really great to work with you, and to have your support

@felixhaberle Hi Felix! Thanks for the question! 1. Permit supports RBAC, ABAC, and ReBAC, all with a no-code UI. It also allows you to create whichever custom authorization code you want on top of it for more complex use cases. 2. Yup! We support both React, Vue, and Angular, as well as - via our FE SDK [1] - which is based on CASL.js 3. As far as migration goes, we usually recommend migrating from your existing permission solution gradually, and you can do it app by app, service by service (And even function by function) while keeping both systems operational until you feel fully comfortable migrating (initially with Permit in "read-only" mode). We also provides guides from migrating identities from your AuthN solution (e.g. auth0[2]) [1]: https://github.com/permitio/perm... [2]: https://docs.permit.io/category/...

Thanks, @stoicbasil. BTW, you still have a chance to win. Permit.io is very easy to integrate with existing products and helps them to grow with Policy as Code, ReBAC/ABAC, or even to manage audit logs. Waiting to see you here ;)

Thank you for your support, @iamadityaa . Waiting to see you redeeming the voucher ;)

@sheldon_at_fabrie, YEAH! Low-code and no-code is definitely one of our first-class citizens. If you have any practical ideas, we will be happy to hear more of them in our Slack community and prioritize them - https://io.permit.io/blog-slack

Thank you, @ishwarjha ! You can also refer them to join our Slack community to get support and answers if needed https://io.permit.io/opalcommunity

Thanks for the kind words, @officialexaking. We are on a mission of simplifying permissions. Keep watching 😎