Oso Cloud

What do you like best about the product?

Oso was great for organizing and standardizing our thinking around authorization for both user-to-resource and resource-to-resource relationships, providing maximum flexibility in our implementation.

Using Oso has allowed us to move faster in shipping products to our customers while ensuring that we maintain the highest standard of authorization. The company has been an excellent partner, with tremendous support and service.

We love using Oso and are glad to have chosen them as our authorization partner.

What do you dislike about the product?

No complaints come to mind at the moment.

What problems is the product solving and how is that benefiting you?

Authorization and authorization management.

What do you like best about the product?

Way it authorizes; works with current tools and good support avaialble.

What do you dislike about the product?

Gui can be a bit more simpler. Training documents can be made more graphic

What problems is the product solving and how is that benefiting you?

solve authorization challenges in software development. it reduces the time developers spend building complex authorization logic from scratch.

What do you like best about the product?

The product is solid, the documentation stellar, and the support excellent. Whenever we encountered issues—performance or otherwise—the Oso team was quick to respond and implement any necessary changes. They really stood out.

What do you dislike about the product?

We encountered some feature and performance issues back when we started using Oso in 2023, but the Oso team was always quick to respond, implement changes and worked with us to address those issues. Nowadays there isn't anything we dislike about the product or Oso.

What problems is the product solving and how is that benefiting you?

Oso is solving our biggest pain point: managing and scaling permissions across a complex, global platform.

Building a fully-fledged authorization system in-house would have taken a lot of time and energy. We quickly realized it would be best to focus on our core business and offload most of the heavy lifting and maintenance to a specialized provider.

Oso has allowed us to centralize and automate our authorization logic, reducing human error and giving us more control over who can access what, when, and where. This has been a huge benefit as we’ve been able to scale faster and more securely, with more confidence in our data privacy and security compliance across different regions.

What do you like best about the product?

Authorization – determining who can do what with which resources – is a fundamental aspect of building secure and functional applications. Yet, in the fast-paced world of software development, it often gets treated as an afterthought. It's something to be "added in later," sprinkled throughout the codebase with
if statements and database checks. This approach, however, is a
recipe for complexity, security vulnerabilities, and significant development headaches down the line.

This is where a service like Oso Cloud becomes invaluable. Oso Cloud is an Authorization-as-a-Service (AuthZ-as-a-Service) that provides a centralized, structured, and scalable way to define, manage, and enforce authorization logic. Its very existence is a testament to the principle that authorization deserves dedicated attention and should be a core part of your application's design, not an afterthought.

What do you dislike about the product?

I think it would be better if a "car" was provided out of the box. The Auth component is great, but is often overlooked at POC stage, leading to usually thinking about the complexity of Auth later. Auth is the "engine". Maybe do like a Subaru vs Toyota.

The Subaru BRZ and Toyota GR86 are essentially the same car, built on a shared platform and featuring the same engine and drivetrain. Auth is an abstraction layer that is critical to security, and can make or break an app. You have a great product, let's connect the engine to the car.

What problems is the product solving and how is that benefiting you?

When authorization is treated as an afterthought, it typically results in:

Scattered Logic: Authorization rules are embedded directly within application code, database queries, and API endpoints, making them hard to find, understand, and modify.

Inconsistency: Different developers or teams implement similar authorization rules in slightly different ways across various services, leading to security gaps and unpredictable behavior.

Increased Complexity: As applications grow and authorization requirements become more fine-grained (Role-Based Access Control, Relationship-Based Access Control, Attribute-Based Access Control), the tangled web of if statements becomes a maintenance nightmare.

Slow Development: Modifying or adding new authorization rules requires changes in multiple places, increasing development time and the risk of introducing bugs.

Security Risks: The scattered and complex nature makes it easy to miss an access control check, potentially exposing sensitive data or functionality.

Difficulty Auditing: Understanding exactly how authorization decisions are being made across the application becomes incredibly challenging.