HNHacker News
TopNewBestAskShowJobs

kkajla

161 karma · joined January 31, 2018

submissionscomments
kkajla··on Launch YC S21: Meet the Batch, Thread #4
Thanks for the question! A couple of things that we think are killer features of Warrant:

- The flexible access control modeling. Implementing a basic RBAC scheme isn't too difficult with a couple extra database tables, but going further than that (fine-grained access control, inheriting access, etc.) is quite a bit of effort. With Warrant, you can model anything from RBAC to fine-grained access control and everything in between.

- End-to-end SDK support. There are many authorization libraries out there, but all of them seem to forget about the frontend. Warrant provides SDKs for authorizing access to your backend as well as a React SDK to make it easy to show/hide pages and components in your React app.

kkajla··on Launch YC S21: Meet the Batch, Thread #4
We’re Aditya and Karan, the co-founders of Warrant (https://warrant.dev/). We build APIs and infrastructure to help developers implement authorization and access control in their apps.

Implementing flexible authorization that grows with your application is difficult. Many products only need authentication early on but eventually require authorization; however, adding complex authorization to a mature, high usage product is even harder. We’re building Warrant to better abstract the complexity of authorization and reduce implementation cost and maintenance drag for engineering teams.

Warrant abstracts your authorization rules and access control logic outside of your application so it isn’t coupled to core business logic. We adopted concepts from Google Zanzibar to make Warrant flexible enough to support any access control model. Authorization rules are easy to enforce in backend and frontend code at runtime through simple API calls. Both developers and non-technical users can modify access rules through our dashboard to change application behavior without needing to change code.

We’re taking a service-driven approach to authorization. As companies get bigger and build out multiple services, authorization logic needs to be re-implemented in the new services or some central service. Whether you’re a small startup with a monolith or a company with many microservices, we think decoupling your authorization and having a dedicated authorization service is the right approach. Check out our demo app (https://github.com/warrant-dev/warrant-demo-app-ts) for an end-to-end example of how to use Warrant.

kkajla··on Warrant: Web Application Authorization as a Service
Hi HN! I decided to create Warrant because I've dealt with the pain of implementing some form of access control at every company I've worked at. It never gets less painful. While there are some really powerful open source libraries for implementing RBAC and other authorization schemes, they still require plenty of care and effort to maintain long term. I've also learned there's more to an effective access control solution than just being intuitive for engineers to work with. Warrant aims to solve these problems.

I'm currently allowing everyone to use Warrant for free as I'd like people to try it out on side projects and provide feedback on how I can make it easier to use. I'd appreciate feedback on anything and everything, and I hope you find it useful! Thank you

← PreviousPage 2 of 2