---
title: "Decoupled authorization with Cerbos"
description: "Escape the chaos of intertwined authorization logic. Empower developers to focus on what truly matters: delivering exceptional products. Simplify, secure, and save with Cerbos."
canonical: "https://www.cerbos.dev/features-benefits-and-use-cases/decoupled-authorization"
source: "https://www.cerbos.dev/features-benefits-and-use-cases/decoupled-authorization"
---

# Decoupled authorization with Cerbos

Escape the chaos of intertwined authorization logic. Empower developers to focus on what truly matters: delivering exceptional products. Simplify, secure, and save with Cerbos.

## The perils of embedded authorization

When authorization logic is deeply embedded within core application code, it becomes a ticking time bomb. As applications evolve, intertwined authorization doesn't just lead to technical challenges. It diverts valuable developer time and resources away from product innovation:

- **Confusion:** Overlapping permissions and roles create a maze that's hard to navigate.
- **Security risks:** Unintended access and data breaches due to overlooked or misconfigured permissions.
- **Development delays:** Developers spend weeks, if not months, untangling and fixing authorization issues.
- **Cost overruns:** Time spent fixing these issues translates to increased costs and delayed product releases.
- **Lost innovation time:** Every hour spent untangling authorization is an hour not spent on feature development, user experience improvements, or innovation.
- **Delayed releases:** Complex authorization issues can push back release dates, affecting product roadmaps and market positioning.
- **Reduced developer morale:** Constantly firefighting tangled authorization issues can demotivate developers, reducing their job satisfaction and productivity.

[#F9FAFB]

## Reclaim control, clarity, and cost-efficiency with Cerbos

Cerbos simplifies authorization, restoring clarity and control to development teams. This streamlined approach cuts development delays and reduces security risks, saving costs. With Cerbos, you accelerate from ideation to market, gaining a competitive edge.

- **Clear separation:** By decoupling authorization from your core application code, Cerbos ensures clarity and reduces complexity.
- **Agile:** Easily adapt and scale your authorization logic without touching the core application, ensuring flexibility and robustness.
- **Reduced security risks:** Minimize the chances of unintended access and data breaches with a dedicated authorization layer.
- **Time & cost savings:** Reduce development delays and associated costs. Let your team focus on core functionalities while Cerbos handles authorization.
- **Streamlined operations:** With Cerbos, product, security and development teams can easily collaborate, ensuring that authorization policies align with business needs without compromising security.
- **Clear focus on product development:** By handling authorization outside the core code, developers can channel their energy and creativity into building standout features and improving user experience.
- **Faster time-to-market:** With a dedicated authorization layer, product updates and new features can be rolled out more swiftly, keeping you ahead of the competition.

[bg]

## Master decoupled authorization with Cerbos

- [What is decoupled authorization](https://www.youtube.com/watch?v=ngr8VeO7AMk) — Learn more in our explainer video
- [How to adopt externalized authorization](https://solutions.cerbos.dev/how-to-adopt-externalized-authorization) — A 10-step roadmap for adopting externalized AuthZ with practical frameworks and policy examples
- [No to hard coding access controls](https://www.cerbos.dev/blog/badly-designed-authorization-is-technical-debt) — Learn why badly designed authorization is technical debt
- [Scalable authorization](https://www.cerbos.dev/blog/designing-an-authorization-model-that-scales-with-your-business) — Why authorization rules have to evolve with the business needs
- [Cerbos demo](https://www.cerbos.dev/blog/cloud-native-live-modernizing-authorization) — Modernizing authorization, from basic roles to decoupled ABAC
- [Contributor podcast](https://www.cerbos.dev/blog/contributor-podcast-decoupling-authorization) — Decoupling authorization
- [The technical complexities of decoupled authorization](https://www.cerbos.dev/blog/technical-complexities-of-decoupled-authorization) — Decoupled authorization can add new technical challenges that aren’t always apparent at the start of a project. Explore useful strategies for avoiding pitfalls
- [Authentication vs authorization](https://www.cerbos.dev/blog/authentication-vs-authorization) — Discover the differences and the value of each solution
- [AuthN vs Authz](https://youtu.be/v9aqaw5G_vo?feature=shared) — Find out more about authentication and authorization in the following video
- [Where to implement authorization in your architecture](https://youtu.be/03XgWf_7dzI) — Find out more in the following video
- [How do we distribute Cerbos](https://youtu.be/Rvw0DTTQmSw) — Find out more in the following video
- [Community insights](https://community.cerbos.dev/?_gl=1*5ozo82*_ga*MTk1NjcwNzQ1MC4xNjY2Mjc5NjI2*_ga_8G3G3MS838*MTY5NDE5MTE5Ny41MjcuMS4xNjk0MTkyNzgyLjIwLjAuMA) — Engage with the Cerbos community, learning from real-world scenarios and solutions