64 karma · joined September 15, 2012
To this point specifically- "Do you offer a way of auditing and tracking who made changes to permissions" - Yes, check out Permit's audit-log interface
In general on top of the interfaces you get with OSS like OPA and OPAL, there are a lot more interfaces to build (e.g. audit logs, user mgmt, policy editing, approval flows, etc.) and none of them are unique to any application.
More fullstack than Aserto, but less than Permit.
More pure API play, but less than Aserto.
Compared to both Permit and Aserto, Warrant seems to lack open-source standards (e.g. Open Policy)
I have to say I really connect with your feedback, I had exactly the same thoughts when building Permit.io: the K8S sidecar (called PDP) and frontend management experiences on top (RBAC, audit logs, invite s, ...) Are really at the core of it.
An open-source event-driven engine like OPA+OPAL which can keep the PDP up to date is an easy way to approach this in scale (that's what we use as part of Permit.io)
K8S and general cloud migration grows the overall cloud market, and Google-Cloud benefits from it a lot.
For all companies these projects help with building communities and recruiting, which is a top priority for such companies.
But the most important point is that an alternative to open-core is needed, and open-foundation has all the mechanics to fill in the gap.
https://github.com/authorizon/opal https://opal.ac
Also happy to take questions here :)
Especially around accessing containers and observability. But ... That's where modern solutions of virtual-logging come in: e.g https://Rookout.com
When your software connects back to you and you can instrument it on the fly (Add logs line, non-breaking-breakpoints, etc.) most of these pain points are resolved
Wonder if it can be used to peer-to-peer other stuff, other than file downloads. CDN boosting ? Ajax broadcast content ( e.g. NewsFeeds, live marketing notifications )?