Our take
Activeregular commits and releases- Activity
- 77
- Community
- 52
- Issues
- 21
- Pull requests
- 72
+64 stars in the last 30 days
- Releases more often than 93% of the projects we track
ZEN is an actively maintained, MIT-licensed Rust engine with broad language bindings, making it a strong option for teams that want portable decisions rather than rules tied to one application stack.
Good fit if
- You need the same business decisions to run from Rust and one or more of its supported language bindings.
- Your team wants rules represented as readable graphs or policy documents and evaluated from portable JSON.
- You can work with the Rust-based engine and accept its MIT license.
Look elsewhere if
- You need a project that accepts general code contributions, since the README currently limits contributions to documentation and additional tests.
- Your use case requires a rules engine for a runtime not listed among its supported bindings.
- You need measured evidence of recent issue resolution: the supplied health data reports no issues closed in the past 90 days.
All health signals
| Last commit | 2026-10-27 (3 days ago) |
|---|---|
| Commits, last 90 days | 46 |
| Releases, last 12 months | 100+ (latest zen-types-v2.1.6, 2026-10-21) |
| Contributors | 12 (top contributor: 52% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 47 (typically merged in 0 days) |
| Project age | 3 years |
Checked on 2026-10-31 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
2,141Forks
233Change since Nov 18, 2026: +1 stars·0 forks
Overview
GoRules ZEN Engine is an open-source business rules engine built in Rust. It gives teams one portable JSON decision model that business owners can read and applications can evaluate, with bindings for Rust, Node.js, Python, Go, Java, Kotlin, .NET, Swift and Android. This helps keep business rules consistent when they need to run in multiple systems or languages.
Decisions can be modeled as visual graphs or policy documents, and the engine evaluates them without requiring a network service. The repository provides the engine and language bindings; the GoRules platform offers separate managed and self-hosted tools around it.
Key Features
- Model decisions with tables, switches, expressions, functions and reusable sub-decisions.
- Write policy documents with typed data models, expressions, decision tables, match blocks and assertions.
- Load portable JSON decision content from a file system, database or service.
- Use native bindings across Rust, Node.js, Python, Go, Java, Kotlin, .NET, Swift and Android.
- Analyze policy and graph workspaces with type checking, exhaustiveness checks, write-conflict detection and diagnostics.
- Collect selected decision-table output columns across matching rows while other columns remain first-match.
- Compile decisions at load time and evaluate them with hardened handling for malformed inputs and numeric edge cases.
- Use configurable loaders and batch evaluation in supported bindings.
Use Cases
- A product team can centralize eligibility or pricing rules in a decision model and run it from services written in different supported languages.
- A business analyst and developer can review the same rules in readable form while keeping an executable source of truth.
- A Rust application can evaluate JSON-based decisions locally when a network call to a rules service is undesirable.
- Teams with multi-step decisions can compose tables, conditions and reusable sub-decisions into a graph or policy document.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
For Rust, add the dependency:
[dependencies]
zen-engine = "2"
See the repository README and its binding guides for setup and evaluation examples in other languages.
Considerations
The core is written in Rust, so Rust tooling is part of the development path even when using a language binding. The repository is active, with recent commits and releases and contributions from multiple people; contributor activity is not concentrated enough in the supplied metrics to indicate dependence on one person. However, the health data reports no issues closed in the measured 90-day period, which is worth weighing alongside the open issue list. The project is MIT-licensed, and the README notes a migration change for Rust users: arbitrary-precision number handling is no longer enabled by default in the 2.x crates. The README also says general code contributions are not currently accepted, apart from documentation and additional tests.
Found this useful?
Share it with someone who would like zen.