warrant VS jolt

Warrant — Hosted enterprise-grade authorization and access control service for your apps. The free tier includes 1 million monthly API requests and 1,000 authz rules.

The specific challenge with authz in the app layer is that different apps can have different access models with varying complexity, especially the more granular you get (e.g. implementing fine grained access to specific objects/resources - like Google Docs).

Personally, I think a rebac (relationship/graph based) approach works best for apps because permissions in applications are mostly relational and/or hierarchical (levels of groups). There are authz systems out there such as Warrant https://warrant.dev/ (I'm a founder) in which you can define a custom access model as a schema and enforce it in your app.

Let's use warrant.dev as an example. The system provides a set of REST APIs for you to define object types and access policies (called warrants). The general process is first to create object types using HTTP POST:

https://warrant.dev/ (Provider) Relatively new authZ provider, they have a dashboard where you can manage your rules in a central location and then use them from multiple languages via their SDKs, even on the client to perform UI checks. Rules can also be managed programmatically via SDK.

I would describe this debate more as Policy-as-Data (Zanzibar) vs Policy-as-Code (OPA et al).

In Zanzibar, all of the information required to make an authorization decision (namespaces, relationship tuples, etc.) is stored in Zanzibar, and the decision engine resolves access checks based on this data. This data can be scaled horizontally (and consistently) as needed for an application’s needs. This makes Zanzibar a centralized, unified solution for all of an application’s authorization needs. I’ve found this approach more purpose built / well suited for application authorization.

With OPA and other policy engines, the data required for performing access checks lives somewhere else (maybe the application’s database) and must be separately queried and included as part of the authorization check because OPA et al. are stateless decision engines. This makes it such that you need to piece together data from different sources in order to get your final decision, which IMO is something most developers don’t want to deal with.

On the flip side, Zanzibar’s “namespaces” are a very simple policy layer not well suited to querying against data outside of Zanzibar’s scope (e.g. geolocation, time, etc). For scenarios like this, a full fledged policy-as-code solution is great. However, it should be noted that some open source Zanzibar implementations like Warrant[1] and SpiceDB[2] (mentioned in the article) also offer a policy-as-code layer on top of Zanzibar’s graph-based/ReBAC approach to tackle these scenarios.

Disclaimer, I’m one of the founders of Warrant.

[1] https://github.com/warrant-dev/warrant

[2] https://github.com/authzed/spicedb

Hey HN, I recently shared my thoughts on why Google Zanzibar is a great solution for implementing authorization[1] and why we decided to build Warrant’s core authz service using key concepts from the Zanzibar paper. As I mentioned in the post, we recently open sourced the authz service powering our managed cloud service, Warrant Cloud[2], so I thought I’d share it with everyone here. Cheers!

[1] https://news.ycombinator.com/item?id=36470943

[2] https://warrant.dev/

More than two years after choosing to build Warrant atop Zanzibar’s core principles, we’re extremely happy with our decision. Doing so gave us a solid technical foundation on which to tackle the various complex authorization challenges companies face today. As we continue to encounter new scenarios and use cases, we’ll keep iterating on Warrant to ensure it’s the most capable authorization service. To share what we learn and what we build with the developer community, we recently open-sourced the core authorization engine that powers our fully managed authorization platform, Warrant Cloud. If you’re interested in authorization (or Zanzibar), check it out and give it a star!

If you just want movies and shows, check out Jolt. An app I'm building that's meant to be the social hub of your media server.

If you're interested in media serving, Jolt needs a lot of work with many features. The project management isn't quite setup yet for large teams, but I'd be open to chatting about collaboration. :)

I'm working on Jolt which syncs with your Jellyfin server and shows movies and shows you've watched, and you can go to your own profile to see a grid of the media.

Combined with GolangCI-Lint, a project I'm working on right now called Jolt makes sure errors are handled, pointers are used correctly, variable naming is following all the conventions and a bunch of more stuff. Setting up a toolchain like this in Python would be a huge pain.

A couple days ago I posted about Jolt, a social hub for media servers that allows users to rate, review, recommend media and track what they've watched as well as add media to their watchlist, and got a very positive response from this subreddit.

I've been working on a platform that generates suggestions for movies based on what users have watched and their ratings of those movies. The project is Jolt, if you guys want to check that out. Now I'm trying to brainstorm a sort of scoring/weighting algorithm that could take more things into account, when overlapping scores are generated based on the parameters outlined.

I'm also currently working on a project - and have been posting some updates here and on r/selfhosted, called Jolt which takes a social approach to discovery. In addition to using TMDB to find popular shows and movies, as well as generating suggestions based on what you like, it allows you and your friends to discover media together, and recommend it to one another.

I am working on a small open-source project at the moment, called Jolt, for which I really want to keep my CI/CD as simple as possible. I have experience in GitLab and Drone pipelines, as well as some others, but with the publicly available GH Actions I'm having trouble setting up something that does the following:

Hey, I noticed we're both working on extremely similar projects. Jolt also tracks what you've watched, allows you to maintain a watchlist, and generates recommendations based on your ratings.

Hey everyone, yesterday I posted about Jolt, which is a social hub for media servers that is meant to be used hand-in-hand with Jellyfin. With some help from the community, I have semi-automatic builds of the Docker image running now in GitHub Actions, which means that an early version is available to test for those interested!