Ross ROSS = Recommend OSS · open-source software intelligence for agents

gorules/zen

Open-source Business Rules Engine for your Rust, NodeJS, Python, Go, Java, C#, Kotlin (JVM), Kotlin (Android) and Swift (iOS) applications. observed · 2026-08-28

github.com/gorules/zen · homepage · Rust · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

97/100

  • Activity 99
  • Release rhythm 99
  • Longevity 89
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 0.0
  • age_days: 1253
  • days_rel: 9
  • days_push: 8
  • n_releases_24m: 49

Full methodology

Adoption not part of the score

1945 stars · 204 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

ZEN Engine is an open-source Business Rules Engine written in Rust with native bindings for Node.js, Python, Go, Java, Kotlin, C#, Swift, and Android. Rules are authored as decision tables, graphs, or policy documents in a portable JSON format (JDM) and evaluated in microseconds with identical results across all runtimes.

Use cases

  • evaluate business rules without redeploying code
  • run loan approval and credit policy decisions
  • implement dynamic pricing rules editable by business teams
  • separate decision logic from application code
  • share one rules definition across Rust, Node, Python and Java services
  • embed a fast rules engine in a microservice hot path
  • audit and version business decisions for compliance
  • give AI agents a deterministic decision layer

When to choose

  • you need business-readable rules that non-developers can own and edit
  • you want one rules definition running identically across multiple languages and platforms
  • you need microsecond-level rule evaluation in latency-sensitive paths
  • you want portable JSON decision models you can store in files, databases, or services
  • you need an MIT-licensed, embeddable alternative to heavyweight commercial BRMS platforms

When to avoid

  • your logic is simple if/else that fits naturally in application code
  • you need a full rules management UI with versioning and approvals without using the separate GoRules BRMS product
  • you require forward-chaining inference or RETE-style rule engines
  • your rules depend on ecosystem features of a specific platform like Drools

Facets

library · maturity stable

workflow-automation developer-tools sdk developer-tools backend fintech cross-platform rust python go jvm dotnet cross-platform business-rules-engine decision-engine decision-tables expression-language jdm rules-as- bre decision-automation automation nodejs swift android ios

10 sources

Member repositories

RepositoryRoleHealth v2
gorules/zenmain97

For agents

markdown · JSON · MCP: product_card(name="gorules/zen")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem