From ff0a6c83e23c1880688a5bbbe42194eb97bc5bb4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Aur=C3=A8le=20Brothier?= Date: Fri, 30 May 2025 16:07:27 +0200 Subject: [PATCH] chore: add Pix4D as adopters for its RBAC service (#7645) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Marc-Aurèle Brothier Signed-off-by: Marc-Aurèle Brothier --- ADOPTERS.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ADOPTERS.md b/ADOPTERS.md index e314476e07..032cd2d3f3 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -173,6 +173,11 @@ production users that have added themselves (in alphabetical order): integration handles ~400K QPS without caching. With caching the system handles ~8.5M QPS. For more information see this talk from [OPA Summit 2019](https://www.youtube.com/watch?v=LhgxFICWsA8). +* [Pix4D](https://www.pix4d.com/) uses OPA to run and define RBAC authorization policies for + the users of its cloud platform. Defining the policies in OPA ensures a single source of + controls and a consistent policy enforcement for any microservices. It operates as a + sidecar to a Django application exposing access roles of users over resources. + * [Plex Systems](https://www.plex.com) uses OPA to enforce policy throughout their entire release process; from local development to continuous production audits. The CI/CD pipelines at Plex leverage [conftest](https://github.com/instrumenta/conftest),