Number of Seats/Users: Cerbos offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Cerbos that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Cerbos. Cerbos reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Cerbos offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Cerbos. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Cerbos often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Cerbos is seen as a strong, developer‑friendly choice for handling authorization, with a few clear areas to watch before purchasing.

Key positive themes from Spendbase clients:

• Smooth integration
• Often described as “easy” and “robust”
• Works well across both:
  • Self‑hosted setups
  • PDP (policy decision point) endpoint usage

• Frontend use cases like ReactJS are called out as working “smoothly”

• Good developer experience

• Clear, helpful core documentation
• Logical model for roles, permissions, and policies

• Fits well when teams want to decouple auth logic from app code

• Architecture and control

• Self‑hosted model is appreciated by security‑sensitive teams
• Centralized policy management helps reduce duplication across services
• Fast rollout of access changes across systems is seen as a big plus

Main friction points Spendbase clients highlight:

• Documentation gaps
• While the core docs are praised, “how‑to” style guides are missing in places
• Some clients report early struggles with troubleshooting and setup examples

• This can increase onboarding time for less experienced teams

• Feature expectations

• Clients are happy but expect “more cool features” over time
• Signals that Cerbos already covers the basics well, but advanced scenarios may still need custom work

What this means from a Spendbase discount perspective:

• Cerbos tends to reduce engineering time spent re‑implementing auth logic across apps.
• There may be initial ramp‑up costs for teams that rely heavily on step‑by‑step guides.
• It is best suited for:
• Teams with at least moderate backend experience
• Organizations that value self‑hosting and tight control over authorization

In short, our internal data shows that Cerbos delivers strong value on integration and control, with documentation maturity and advanced features being the main areas to plan for when negotiating pricing and rollout timelines.