GoRules

Organizations have business logic like pricing, eligibility, credit decisioning, underwriting, and fraud rules that changes frequently but is often buried in code across multiple codebases, requiring developer time and full deploys for every change. This creates friction between the business teams who understand the rules and the developers who must implement them, and makes it hard to audit or explain why a decision was made. Running the same logic consistently across servers, edge devices, and batch jobs over millions of rows typically requires separate implementations or costly per-row API calls, as illustrated by the page's example of 28 hours via API calls versus 4 minutes embedded in a batch job for 10 million rows. Without a shared system, rule changes lack version history, review workflows, and rollback, making compliance and audit trails difficult to maintain.

GoRules provides a decision layer where rules are written as readable sentences, tables, and visual flowcheart-like canvases that both business users and developers can view and edit without drift between the two representations. It includes version control with branches, commits, and history, environments for dev, staging, and production, and approval flows for reviewing and publishing changes, plus an AI copilot and MCP server for building and modifying rules. The open-source ZEN engine can be embedded directly in an application as a library across nine languages (TypeScript, Python, Go, Rust, Java, C#, Kotlin, Swift, and more), run behind an API, or embedded in big data tools like PySpark for batch processing over large datasets without per-row calls. Scenario test suites run on every change to measure coverage against decision paths, and releases are promoted unchanged from testing through staging to production, with the same engine version answering everywhere, including instant rollback capability.