Edit: and I just saw the pricing... 1k API calls a month? I'd quite literally hit that in minutes. :)
In terms of initial setup and configuration, I agree there's room to improve and remove friction. We're building tools and integrations that should just make this much easier.
We're also iterating on price and do offer volume discounts. So if that's an issue, reach out to us! ([email protected])
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...
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 way less complex to build it in the application. That's why we're building Oso as an open source library instead. You get to leave your application data in the application, and don't need to worry about adding an external service to the critical path.
How do you plan on monetizing, if you haven't already?
Sorry didn’t mean to word that negatively btw. On mobile not at home.
We're a little less active about it in YC launch threads, though, because of the first principle of HN moderation: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu.... That's why I haven't said anything in the places this has happened in today's thread.
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.
Borrowing a lot of LaunchDarkly's playbook for feature flagging will serve you well here. Server Sent Events and providing a self host-able "relay proxy"[1] will be extremely valuable in terms of perf and redundancy.
- 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.
This actually sounds really cool. It’s always a pain recreating JWT and setting up security between the backend and frontend. Doing this as a framework and an api seems like a good approach. Thanks for sharing.
If you sell to a midmarket or enterprise customer base, they regularly need custom stuff.
eg group X of employees cannot see group 1 of customers' data. Or to use a more concrete example: US employees cannot see EU customer data because of GDPR. But it's never that simple: more fine grained, or with other exceptions.
This stuff took up way more eng time than I mentally budgeted; I could see a use case for a service.
Super interesting how many companies are building authorization systems based on Zanzibar suddenly! This is a bit of a shameless plug, but I just wrote a blog post earlier today talking through how to build Zanzibar from scratch in ~150 lines of code: https://news.ycombinator.com/item?id=28076549
Not many people talk about how Zanzibar requires you re-architect your application around authorization when you really don't need to do that at all. Any sufficiently powerful authorization framework can handle the same flexibility. If not more, since most Zanzibar implementations can't handle simple attribute-based controls (e.g. anyone can read a document if its public). Which means you'll end up implementing a bunch of authorization logic in your app anyway.
---
Edit to add: I realise in hindsight I got a bit too absorbed in thinking about the Zanzibar part to say congrats on the launch! It's awesome to see the space heating up, and love to see more focus on the developer experience :)
I don't agree with your point that it requires developers to re-architect their systems or that it doesn't handle attribute-based controls well. If anything, I think Zanzibar actually helps developers enforce the best authz practices in their system. This becomes increasingly helpful as an application changes or grows in complexity.
To be clear, Warrant isn't just a Zanzibar implementation. We're building Authz as a service with devxp as the central focus.
To give a simple example of an attribute-based control that is tough with the service model: if you want to express "anybody can read a document if it's public", then you need to push that "public" field into the service. Every attribute that you want to use for authorization becomes something that you need to either move or synchronise into the service. Or you leave that logic in the application.
If not, how are user signups supposed to work? If I create a user and set up their permissions in Warrant, will my users' first-time experience consist of a permission denied error?
Will watch progress closely. Key business piece imo will be getting libraries and plugins out for enterprise development platforms, and possibly creating a private tenant concept. Can absolutely see why this was included in the batch.
Building SaaS from India (assuming that you eventually will) is always going to be advantageous [0] given the comparatively lower wages and access to a global client-base. Apart form that, in what ways does warrant differentiate itself from authzed.io, another YC-backed startup? I see that both these services are influenced by Zanzibar, but I am particularly curious if DevX is warrant's focus? If so, what might be the current competitors missing?
Thanks.
[0] Given the Indian SaaS ecosystem is up and running and there does not seem to be dearth of talent, community (https://archive.is/B5OHl) or capital (https://archive.is/ZXvzL).
And yes, devxp is one of our main focus areas. After dealing with authz at prev small and big companies, we're building the components/infra/plugins we believe will save app developers time across their stack. And in terms of Zanzibar, like others, we think it's a very flexible approach to modeling permissions and access control, so we're basing parts of our implementation on it.
> ...we're building the components/infra/plugins we believe will save app developers time across their stack.
I ask because I have been keenly following authzed's progress, after walking away particularily impressed with their pricing (which is 1/10th of warrant's?).
> Are you asking if we specifically plan to build/hire in India in the future (we're based in the US)
I am postulating that warrant'd have a leg up on competition because I presume its founders would be more receiptable to building/hiring in India...
Authzed is focused on delivering all of the capabilities of Zanzibar (rewrites, consistency, scalability) in a consumable form to everyone outside of Google. We've started with Zanzibar and are iterating from there, rather than cherry-picking particular concepts from the paper.
You can checkout our post on "What is Zanzibar" to learn why you'd want the whole package: https://authzed.com/blog/what-is-zanzibar/
Congrats to Warrant! There's plenty of room for innovation in the developer UX for permissions, especially with frontend code.
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.