Oso engineer, Mike Cen, gives us a firsthand look into jumping back into the weeds as an individual contributor after being a manager for seven years.

Oso engineer, Jordan Killpack, relishes opportunities to be a beginner and to follow interests down twisty passages to unknown destinations. Read about how this curiosity led her into knitting and working at Oso!

As Oso’s first developer experience engineer, Corey Ashby, walks through creating a functional sample application using Oso Cloud.

Oso engineer, Vijay Ramamurthy, shares his journey into formal logic which all stemmed from writing an AI project to play Pokemon.

A look into Jesse Lax's, Oso Engineer, journey into software engineering and why he chose to work at Oso.

A case study on why to perform request validation on the data coming into your APIs, and how we wrote a type inference algorithm for ours - Oso Cloud.

Abhishek Parmar, co-creator of Google Zanzibar & Airbnb Himeji, joins Oso as technical advisor.

Oso Summer 2022 Hackathon

how to use Kubernetes Authorization webhooks to defer authorization decisions to Oso Cloud, a fully-managed authorization service.

How we use Rust, SQLx and Rocket to power Oso Cloud, our fully-managed authorization as a service

An overview of different patterns for building authorization in GraphQL

Nearly every application needs to enable its users to see only their data. Many other applications go further and add more controls, like sharing, or making some content private and public. In this post, use Django and django-oso to build a simple social app that allows users to share posts, like Twitter. Our app will use oso to implement access control for posts.

Oso winter hackathon 2021 - an opportunity to push boundaries and hack on fun projects we think the Oso product could do.

How we built Language Server Protocol (LSP) support for the Oso VS Code extension with Rust, WebAssembly (Wasm), and TypeScript.

Wayfair's journey from monolith into microservices and how it subsequently built out distributed authorization using Oso.

How we developed Oso to let you query your database using your authorization policy.

Oso is an authorization library that includes a declarative policy language. OPA is an authorization product that includes a declarative policy language. Despite that, there are many significant differences between the two! Here's a comparison.

Oso has libraries for Python, Ruby, Java, Javascript, Go, and Rust, and each of those libraries are based on a core that is written in Rust.

Guy Podjarny (Founder & President of Snyk.io) on optimizing developer experience, introducing security to developers, and when to offer a freemium product.

#PermissionsPepTalk. Not enough celebrities have talked about authorization and permissions in the public domain, so today we're bringing the topic to the fore as well. Here's what Alice Cooper, Lisa Loeb, Ghostface Killah, Kenny G, Mike Ditka, and Lena Headey have to say to developers working on permissions...

0.20 includes new approaches to: 1. Authorization modeling, including built-in primitives for common patterns like RBAC and ReBAC. 2. Data filtering for authorizing collections of data 3. APIs for enforcing authorization at different layers of the stack

Lea Kissner (co-designer of Google Zanzibar and Head of Privacy for Twitter) on Zanzibar’s design decisions, user-friendly ways to structure access controls, and when (not) to write your own Zanzibar.

We sat down with Simen A. W. Olsen of Bjerk.io, an expert software consultancy. He's used Oso in three projects now, each very different from the other: Indiv, Tabetalt, and nest.js-oso

A configuration-based approach to adding role-based access control to your Ruby application.

Oso's Developer Den interview with Jason Warner (VC at Redpoint Ventures, formerly CTO of GitHub and Head of Engineering at Heroku) on his path to computers, the trickiest technical problems, and programming as a superpower.