Software Alternatives & Reviews

Oso VS Cerbos

Compare Oso VS Cerbos and see what are their differences

Oso logo Oso

A batteries-included system for authorization.

Cerbos logo Cerbos

Cerbos helps teams separate their authorization process from their core application code, making their authorization system more scalable, more secure and easier to change as the application evolves.
  • Oso Landing page
    Landing page //
    2023-10-16

Drop Oso Cloud into your apps to quickly add roles, sharing, fine-grained access, or any other access model you can think of.

  • Cerbos Landing page
    Landing page //
    2023-08-21

Cerbos is a self-hosted, open source authorization layer that separates your authZ logic from your core application code.

Cerbos allows for swift and secure set up and modification of complex roles and permissions. Unlike traditional methods that require intricate code manipulation, Cerbos simplifies the process by making changes through configuration. This reduces risks associated with authZ changes, such as downtime or security incidents.

Cerbos' structure, independent from the app code, allows both business stakeholders and non-expert engineers to understand the permissions structure. A broader range of stakeholders can make changes to the authZ logic without needing extensive coding knowledge or risking the stability of the core application.

In an era where authZ logic is business logic, the ability to quickly adapt and scale this element is vital. Cerbos makes this possible, facilitating an agile response to new markets and customer needs while maintaining a mature product.

Oso videos

OSO Vintage Style Chronograph 70's Style Watch Review

More videos:

  • Review - $300 For A Super Functional Retro Chronograph! (OSO Orbit Chronograph Review)
  • Review - The 70s With A Twist! - OSO Orbit Hybrid Chronograph Review

Cerbos videos

Cerbos - How It Works - Intro

Category Popularity

0-100% (relative to Oso and Cerbos)
Developer Tools
51 51%
49% 49
Security
50 50%
50% 50
Identity And Access Management
Access Control
100 100%
0% 0

Questions and Answers

As answered by people managing Oso and Cerbos.

Which are the primary technologies used for building your product?

Cerbos's answer:

  • Go
  • Protobuf
  • gRPC
  • CEL

What makes your product unique?

Cerbos's answer:

Cerbos stands out in the crowded authorization landscape due to its innovative approach to managing roles and permissions. Unlike traditional systems that embed authorization logic within an application's core code, Cerbos introduces a standalone, self-hosted, stateless service, transforming intricate coding tasks into simpler configurations. This separation not only streamlines the authorization process but also reduces potential security risks and system bottlenecks.

Being open-source, Cerbos fosters a strong community backing, ensuring its evolution aligns with real-world developer needs. Its adaptability is evident in its support for multiple SDKs, YAML configuration, and dynamic context handling, which cater to a wide range of environments and use-cases. This flexibility is further enhanced by Cerbos Cloud, a premium solution offering advanced policy management tools.

Furthermore, Cerbos emphasizes transparency, allowing both technical and non-technical stakeholders to understand and modify the permissions structure. This democratization of authorization logic management reduces reliance on specialized coding expertise. Additionally, its commitment to robust security features, including audit logging and risk mitigation, ensures that businesses can trust Cerbos to safeguard their authorization processes.

In essence, Cerbos' unique blend of innovation, adaptability, community support, and security focus reshapes the way businesses approach and manage authorization, making it a game-changer in the field.

How would you describe your primary audience?

Cerbos's answer:

Cerbos' primary audience is best described as forward-thinking engineering leaders at the helm of emerging startups, particularly within the FinTech and Software Development sectors. These leaders typically oversee small to medium-sized teams, with 5-20 engineers, in companies that have a workforce ranging from 0 to 100 employees. Their technological stack prominently features Kubernetes (k8s), indicating a modern and scalable infrastructure.

Financially, these companies are in their early growth stages, having secured funding between 0 to 10 million dollars, primarily in the Seed to Series A range. This suggests that they are in a phase of rapid expansion and are actively seeking solutions that can seamlessly scale with their growth.

The primary objectives of Cerbos’ users revolve around finding a reliable solution to their authorization challenges, ensuring that the chosen solution can be implemented without disruptions, and that it scales effortlessly as the company grows. In essence, the Cerbos champion is a visionary engineering leader, keen on adopting innovative solutions that align with their company's rapid growth trajectory.

What's the story behind your product?

Cerbos's answer:

Cerbos, co-founded by Emre and Charith, emerged from a vision to revolutionize the way authorization is approached in modern, cloud-native applications. The duo recognized a persistent challenge in software development: the immense time and effort developers invest in crafting and continually updating custom permissions. This repetitive cycle not only consumes valuable time but also diverts attention from the core essence of product development.

Driven by this realization, Emre and Charith embarked on a mission with Cerbos: to make the implementation of access-control as seamless and painless as possible. Their goal was to eliminate the need for repeatedly writing and rewriting custom permissions implementations. Instead, they envisioned a world where developers could channel their energies and creativity into building outstanding products that resonate with and delight their customers.

Who are some of the biggest customers of your product?

Cerbos's answer:

Why should a person choose your product over its competitors?

Cerbos's answer:

A person should choose Cerbos over its competitors for several compelling reasons:

Innovative Design: Unlike many competitors, Cerbos separates the traditionally embedded authorization logic from the application's core code. This standalone, stateless service simplifies authorization changes, converting intricate coding tasks into straightforward configurations.

Open-Source Flexibility: Cerbos' open-source nature ensures continuous evolution based on real-world feedback. This community-driven approach ensures that the product remains relevant and adaptable to changing needs.

Transparency and Inclusivity: Cerbos' structure allows a broader range of stakeholders, both technical and non-technical, to understand and modify the permissions structure. This democratizes the authorization process, reducing the dependency on specialized coding expertise.

Robust Security: Cerbos places a strong emphasis on security, offering features like audit logging and risk mitigation. This commitment ensures businesses can trust Cerbos to maintain the integrity of their authorization processes.

Flexibility and Control: Cerbos provides complete control over its deployment, scaling, and monitoring. Unlike solutions that are solely cloud-based or hardcoded, Cerbos strikes a balance between flexibility, control, and security.

Clear Value Proposition: Cerbos offers straightforward pricing and a user-friendly approach, contrasting with competitors that may have complex pricing structures or less intuitive systems.

Community and Support: As an open-source project, Cerbos boasts a strong community backing, ensuring users have access to a wealth of knowledge and support.

In summary, Cerbos' unique blend of innovation, flexibility, transparency, and security makes it a superior choice in the authorization landscape.

User comments

Share your experience with using Oso and Cerbos. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Oso might be a bit more popular than Cerbos. We know about 6 links to it since March 2021 and only 5 links to Cerbos. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Oso mentions (6)

  • Solution for ReBAC authz using attributes?
    I know of warrant.dev, osohq.com, and Ory Keto but I don't see that these evaluate based on attributes. Source: over 1 year ago
  • Authorization Framework + Data Filtering
    Oso supports applying authorization logic at the ORM layer so that you can efficiently authorize entire data sets. For example, suppose you have millions of posts in a social media application created by thousands of users, and regular users are only authorized to view posts from their friends. It would be inefficient to fetch all of the posts and authorize them one by one. It would be much more efficient to... Source: almost 3 years ago
  • Node Authorization Framework
    Oso's Node library now provides a configuration-based approach to adding role-based access control (RBAC) to your application. This new library speeds up the time it takes to build fine-grained permissions using roles and related patterns. Here are the docs + quickstart. Source: almost 3 years ago
  • AuthZ: Carta’s highly scalable permissions system
    > It's crazy this still is part of the stack where there are no great solutions. Seems like a few others have come to the same conclusion :) We're working on this at Oso (https://osohq.com) - I'm the CTO. Oso is an open source framework for authorization. Policies can reference application directly, so any authorization decisions can be made dynamically based on the data. And your data doesn't need to leave your... - Source: Hacker News / almost 3 years ago
  • The basics of role-based access control (RBAC) in SQLAlchemy
    To celebrate a new release of Oso, our open-source authorization library, this blog post demonstrates a few ways of modeling role-based access control in Python and SQLAlchemy. It has complex examples to provide you with the building blocks for adding RBAC to your app and are written in a multi-tenant production system. - Source: dev.to / about 3 years ago
View more

Cerbos mentions (5)

  • Nuxt authorization: How to implement fine-grained access control
    In this tutorial you will learn how to use Cerbos to add fine-grained access control to any Nuxt web application, simplifying authorization as a result. - Source: dev.to / 4 months ago
  • 🖌️⚙️ Innovate Like Da Vinci: Blending Art and Science in Software Development
    In my work with Cerbos, I apply the lessons learned from Da Vinci to tackle authorization challenges. Our approach is to create solutions where functionality seamlessly integrates with developer experience. Constantly iterating and viewing the tools through the users' lens, helps ensure that our access control solutions are robust and dev-friendly. - Source: dev.to / 5 months ago
  • Feedback needed: Cerbos Hub is now in public beta!
    Hello fellow devs! I'm with Cerbos (https://cerbos.dev/), a tool designed to manage who can do what in your software applications. - Source: dev.to / 6 months ago
  • Show HN: Cerbos Hub – Implement roles and permissions in your app in minutes
    Hello HN! I'm on the DevRel team at Cerbos (https://cerbos.dev/), a tool designed to manage who can do what in your software applications. For a couple of years now, Open Worldwide Application Security Project (OWASP) is naming authorization a top 10 API security risk: https://owasp.org/API-Security/editions/2023/en/0x11-t10/ We are thrilled to announce that Cerbos Hub is now in public beta! - Source: Hacker News / 6 months ago
  • PHP + Cerbos: Revolutionizing Authorization in Laravel applications
    Learn more at: https://cerbos.dev/. Source: 8 months ago

What are some alternatives?

When comparing Oso and Cerbos, you can also consider the following products

authzed - The platform to store, compute, and validate app permissions

Aserto - Fine-grained, scalable authorization in minutes

Permit.io - Fullstack Authorization as a Service for cloud native applications

Warrant - Authorization and access control infrastructure for developers

LoginRadius Authentication - Secure and robust authentication, SSO with user management

Ory - Developer-first Access Management