Rego (Open Policy Agent)
Shares rank 3 of 4 authorization engines by recommenders
Policy language for Open Policy Agent that keeps a JSON-in, JSON-out pipeline and suits jq-style queries. Main caveat: dynamically typed, so little type protection.
Policy language for Open Policy Agent that keeps a JSON-in, JSON-out pipeline and suits jq-style queries. Main caveat: dynamically typed, so little type protection.
6 people gave an opinion
- recommend it
- 5
- criticize it
- 1
- approval share
- 83%
Recommended in 5 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 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
Dynamically typed, little type protection
“Rego is dynamically typed, so no real protection.”
Comment from 20 May 2026 in “The Mercury logic programming system”
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.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Cedar policy language | 7 | 0 | 100% | 4 | — | — |
| OpenFGA | 6 | 0 | 100% | 5 | — | — |
| Rego (Open Policy Agent)This page | 5 | 1 | 83% | 5 | — | — |
| SpiceDB | 5 | 2 | 71% | 7 | — | — |
What people said
All 6 comments that mention it, newest first. Each links to the original comment.
“Rego doesn't know what a clearance, classification, security compartment, etc. means.”
“with Rego as a policy language”
“Rego is dynamically typed, so no real protection.”
“it was actually a pretty nice syntax for jq type use cases”
“Rego is much more powerful, and can do things cel can't.”
“I like the idea that the entire pipeline is “JSON in, parse it, JSON out””
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.