GoRules is an open-source business rules engine for teams that want decision logic such as pricing, eligibility, approvals, and routing to live outside application code. Business analysts model the rules visually as readable rules, tables, and flows, developers execute them inside their own services through an API or SDK, and releases move from testing to staging to production untouched.[1]
Quick verdict
Teams that revise business rules weekly will gain the most from GoRules. Its visual editor lets non-developers change rules, tables, and flows while developers consume the result through versioned execution APIs. Teams without anyone comfortable owning a rules lifecycle should look elsewhere, since rule design, testing, and governance still need an owner. If your stack has fast-changing domain rules and someone to own them, GoRules is worth a pilot; if you need a finished no-code app rather than a decision layer, choose a full workflow product instead.[1][2]
Key features
Rules that read like sentences Conditions are written and displayed the way the business states them, with the developer view one toggle away, so analysts and engineers never drift apart.[1]
One visual decision canvas Inputs, tables, and routing sit on a single canvas that reads like a flowchart, and executable documents keep prose, data model, and tables together.[1]
Version control, environments, and approvals Branches, commits, and history come with review and publish workflows across development, staging, and production. Business and Enterprise tiers add enforced reviews and approvals.[1][2]
Scenario testing before release Test suites run on every change with coverage measured against decision paths rather than lines of code. Vendor-shown timings are vendor-published examples, not independent measurements.[1]
Embeddable Zen engine with unlimited evaluations The engine runs inside the team's own application, keeping decision latency local, and every plan includes unlimited evaluations via the engine or agent.[1][2]
Nine runtimes, one engine, plus a REST API The same decision model returns the same answers in every supported runtime, and services without a native SDK can call decisions over HTTP.[1]
AI copilot and MCP server An assistant drafts, tests, and explains rules while staying reviewable, and an MCP server exposes decisions to agent-based workflows. Each plan bundles monthly AI credits.[1][2]
Self-hosted or managed deployment Teams run on Docker or Kubernetes themselves or consume managed cloud across AWS, Azure, and GCP. Self-hosted plans start at a free tier with paid Team and Business tiers; audit logs, SOC 2 reports, SSO, and SLAs are gated to paid cloud tiers.[1][2]
Who will love it
Teams with fast-changing domain rules: pricing, promotions, and eligibility logic that changes weekly stops requiring engineering sprints once rules live in versioned, tested decision models.[1][2]
Developers standardising decisions across services: one decision model executed through SDKs and a REST API beats duplicated conditionals scattered across repositories.[1]
Regulated teams needing decision traces: paid-plan audit logs plus version history give compliance reviewers the record of what was decided and why.[1][2]
Who should avoid it
Teams with nobody to own the rules: the editor is visual, but designing correct, complete, and tested decision tables is still skilled work that needs an owner.[1]
Builders wanting a finished application: GoRules supplies the decision layer, not screens, workflows, or databases.[1]
Tiny static rule sets: a handful of rarely changing conditions is simpler and cheaper as plain code than as a governed rules platform.[1]
What the reports suggest
Empty inspected sample: G2 listing with zero reviews observed 2026-10-11 plus one unread Reddit launch thread. No testimonials selected.
1 cited community source. No firsthand user reports could be inspected: G2 shows zero reviews and the one Reddit thread found was unreadable. No prevalence or satisfaction claims are made; operational experience remains unverified.
What the available evidence suggests: official documentation supports the capability and pricing claims above, but no independent user reports could be inspected in this session, so operational experience remains unverified. No testimonials are quoted and none are fabricated to fill this section.[1]
Questions worth asking
What is the best GoRules alternative for non-technical users?
Is GoRules really no-code?
Authoring individual rules in the visual editor needs no code, but connecting decisions to real systems takes developers: SDK integration, API wiring, deployment, and rule testing remain engineering work. Treat it as low-code for authors and pro-code for integrators.[1]
How much does GoRules cost per month?
As checked on 2026-10-11, GoRules Cloud costs $0, $200, or $600 per month on monthly billing ($167 and $500 per-month equivalents for Pro and Business on annual billing) plus custom Enterprise pricing, with per-plan limits on users, projects, models, and environments and unlimited evaluations via the engine or agent. Self-hosted plans are priced separately starting at a free tier.[1]
Can you self-host GoRules?
Yes, on Docker or Kubernetes. The official structured data lists a free self-hosted tier plus paid Team and Business self-hosted tiers, while audit logs, SOC 2 reports, SSO, webhooks, and SLAs are gated to paid tiers.[1]
Sources and editorial review
Source research. Reviewed on October 11, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
Empty inspected sample: G2 listing with zero reviews observed 2026-10-11 plus one unread Reddit launch thread. No testimonials selected. No firsthand user reports could be inspected: G2 shows zero reviews and the one Reddit thread found was unreadable. No prevalence or satisfaction claims are made; operational experience remains unverified.
- GoRules: Open-source Business Rules Engine
official · Observed October 11, 2026
Primary evidence from directly inspected homepage (v2.0): readable rules, canvas, versioning, environments, approvals, scenario testing, Zen embed, nine runtimes, AI copilot, MCP server, PySpark, cloud-native deployment, and vendor-reported scale figures.
- Pricing - GoRules
official · Observed October 11, 2026
Primary evidence from directly inspected pricing page: $0/$200/$600 monthly billing ($167/$500 annual equivalents), per-plan limits, unlimited evaluations, Business-tier audit/SOC2/SLA/reviews, Enterprise SSO/webhooks/roles/SLA/support, self-hosted tab.
- ADR: gorules-zen vs Drools
community · Observed October 11, 2026
Corroborating attestation that the gorules/zen engine is MIT licensed; snippet only, full page not inspected.
- @gorules/zen-engine
community · Observed October 11, 2026
Corroborating registry metadata recording an MIT licence for the Zen engine package; snippet only.
- streaming-cep-pipeline
community · Observed October 11, 2026
Corroborating licence table identifying GoRules as MIT licensed in an embedding project; snippet only.
- awesome-decision-automation-platform
community · Observed October 11, 2026
Corroborating listing describing GoRules as an open-source business rules management system; snippet only.
- GoRules Reviews on G2
community · Observed October 11, 2026
G2 listing shows zero GoRules reviews at observation time; no quotable user reports available. A Reddit launch thread was found but its body could not be read.
Compared with these products
No explicit proprietary baseline is recorded.