Skip to main content
GoRules consists of two main parts: the BRMS (Business Rules Management System) for managing rules, and the ZEN Engine (BRE) for executing them.
Business Rules
Management System
(BRMS)
Business Rules
Engine
(BRE)
GoRules BRMS
  • Enhanced Authoring Capabilities
  • Rule Repository with Version Control
  • Debugging and Simulation
  • Audit Logs
ZEN Engine (Open Source)
  • Rule Execution
  • Deterministic If-then Logic
  • Library - Foundational Element
The BRMS is the management platform where you author, test, version, and publish rules. It includes the ZEN Engine internally for testing and direct API evaluation. The ZEN Engine is the high-performance execution engine. It runs inside the BRMS, and also powers the Agent and SDKs that execute rules in your environments.

​
GoRules BRMS

The BRMS is the recommended starting point for most organizations. It provides everything you need to manage business rules at scale.
CapabilityDescription
Visual editorDrag-and-drop interface for building decision graphs
CollaborationMultiple users, projects, and access controls
Version controlTrack changes, compare versions, roll back
TestingBuilt-in simulator to validate rules before publishing
ReleasesPublish rules to different environments
Audit logsTrack who changed what and when
API accessEvaluate rules directly or publish to Agents/SDKs

​
When to use BRMS

  • Business users need to create or modify rules
  • You need version control and audit trails
  • Multiple teams collaborate on rules
  • You want a managed workflow for publishing rules

​
ZEN Engine

The ZEN Engine is the open-source rules execution engine that powers all of GoRules. It’s written in Rust for maximum performance.
CapabilityDescription
Sub-millisecondEvaluates most decisions in under 1ms
Cross-platformNative SDKs for Node.js, Python, Go, Rust, Java, Kotlin, Swift
EmbeddableRuns in-process with your application
Open-sourceAvailable on GitHub

​
Standalone usage

You can use the ZEN Engine without the BRMS if you only need rule execution and will manage rule files yourself.
ComponentPurpose
ZEN EngineCore execution library
JDM EditorReact component for building rules
Standalone EditorDesktop app for editing JDM files
When to use standalone:
  • Building a product with embedded rules
  • You have your own storage and versioning
  • Developers manage all rules (no business user access needed)
  • Maximum control over the rules lifecycle
When using the ZEN Engine standalone, you’re responsible for storing, versioning, and distributing JDM files to your applications.

​
Using them together

Organizations often use both BRMS and ZEN Engine together when they need maximum performance:
  1. Author in BRMS — Business users create and test rules in the visual editor
  2. Publish releases — Rules are published to object storage (S3, Azure, GCS)
  3. Execute via SDK — ZEN Engine runs embedded in your application
With the embedded SDK, rule evaluation is sub-millisecond because there’s no network overhead — no REST API calls, no serialization. The engine runs in-process with your application.

​
Choosing your approach

ScenarioRecommendation
Business users edit rulesBRMS
Need audit trails and version controlBRMS
Team collaborationBRMS
Building a product with embedded rulesZEN Engine standalone
Developers manage all rulesEither (BRMS adds convenience)
Maximum performance, minimal dependenciesZEN Engine standalone
Most organizations start with the BRMS and use Agents or SDKs for production execution. The standalone ZEN Engine is best suited for product teams embedding rules into their own software.