Hacker ApprovedDepartments

Cedar policy language

The most recommended of 4 authorization engines

Open-source language for writing authorization policies that can be formally analyzed and return a binary allow or deny decision.

Open-source language for writing authorization policies that can be formally analyzed and return a binary allow or deny decision.

7 people gave an opinion

recommend it
7
criticize it
0
approval share
100%
Each figure is one person. RecommendsCriticizes

Recommended in 4 of 13 months

  1. November 2025: recommended
  2. December 2025: not recommended
  3. January 2026: not recommended
  4. February 2026: recommended
  5. March 2026: recommended
  6. April 2026: not recommended
  7. May 2026: not recommended
  8. June 2026: not recommended
  9. July 2026: not recommended
  10. August 2026: not recommended
  11. September 2026: recommended
  12. October 2026: not recommended
  13. November 2026: not recommended (month in progress)

Why it doesn’t carry the badge

  • 7 people recommend itNeeds 10 or more, not met.
  • Nobody criticizes itNeeds 2 to 1 or better, met.
  • Recommended in 4 of 13 monthsNeeds 4 or more, met.

The same three rules apply to every product, and the badge can’t be bought. How the badge works

What people say about it

The reasons people give, with the number of comments that give each one. Open a reason to read what they said.

What people warn about

Each mark is one comment

  • Requires a server round trip

    “you are better suited with a different solution that does not require a server roundtrip like Cedar”

    Comment from 16 Mar 2026 in “Event Publisher enables event integration between Keycloak and OpenFGA”

Other authorization engines people recommend

The three most recommended other authorization engines, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.

Cedar policy language compared with 3 alternatives
ProductRecommendCriticizeApprovalMonthsOwnedBadge
Cedar policy languageThis page70100%4——
OpenFGA60100%5——
SpiceDB5271%7——
Rego (Open Policy Agent)5183%5——
See all 4 authorization engines, ranked

What people said

6 of the 7 comments that mention it, newest first. Each links to the original comment.

“They could have embedded Cedar into their system without adding on-premium burden.”

RecommendsComment from 12 Sep 2026 in “How we rebuilt complex permissions without migrating to Zanzibar”

“If you can't run Lean in production, then their approach is compelling.”

RecommendsComment from 18 Mar 2026 in “Mistral Releases Leanstral”

“you are better suited with a different solution that does not require a server roundtrip like Cedar”

RecommendsComment from 16 Mar 2026 in “Event Publisher enables event integration between Keycloak and OpenFGA”

“Cedar allows us to write formally analyzable policies that return a binary ALLOW or DENY”

RecommendsComment from 10 Mar 2026 in “Hooking Coding Agents with the Cedar Policy Language”

“Policy engines (OPA/Rego, Cedar, Casbin) are excellent at”

RecommendsComment from 18 Feb 2026 in “Show HN: Trust Protocols for Anthropic/OpenAI/Gemini”

“OPA or Cedar enforces policy at runtime.”

RecommendsComment from 1 Nov 2025 in “How are you handling identities for AI agents?”

Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.