GoRules Review (2026): Pricing, Features & Honest Verdict

TLDR

GoRules is a business rules engine with a free, MIT licensed Rust core called Zen Engine and a paid cloud platform on top. We found the open source engine excellent and the commercial tiers hard to justify. Best for: teams who want to embed the free Zen Engine. Price: free, then $167/mo. Rating: 6.1/10

What is GoRules?

GoRules moves business logic out of your codebase. Pricing tiers, eligibility checks, risk scoring, routing rules: the kind of logic that changes weekly because a product manager asked, and that currently lives duplicated across four services. GoRules puts it in one decision layer that non engineers can read and edit, with versioning, testing and deployment around it. You model decisions on a visual canvas built from decision tables, switches, expressions, functions and reusable sub decisions, then evaluate them through an API, an SDK, Spark or a serverless function.

The company started in 2023 out of frustration with legacy rules engines that were closed, heavyweight and locked to a single language stack. That same year it released Zen Engine as open source under the MIT licence: a decision engine written in Rust with bindings across nine languages including JavaScript, Python, Go, Java, C#, Kotlin for both JVM and Android, Swift for iOS, and Rust itself. GoRules is bootstrapped and cash positive rather than venture backed, remote by design, and in 2026 it reached SOC 2 Type II attestation and shipped a version 2 with a managed cloud. We dug into it because the free engine gets recommended constantly in Node and Rust circles, and almost nobody talks about what the paid platform actually costs.

What Are GoRules’ Key Features?

Zen Engine, the Open Source Core

Zen Engine is the reason GoRules has any name recognition. It is a business rules engine in Rust, MIT licensed, that you embed directly in your application rather than calling over the network, which is where the sub millisecond evaluation claim comes from. The bindings are real and maintained, not community afterthoughts, covering Rust, Node, Python, Go, Java, C#, Kotlin on JVM and Android, and Swift on iOS. If you have a Go service and a React Native app that both need to apply the same eligibility rules, this is a genuinely good answer. One caveat worth knowing before you plan a deployment: Linux musl is not currently supported, which rules out plain Alpine containers without a workaround.

Visual Decision Models and the JDM Canvas

The editor is where the paid product earns its keep. Decisions are modelled as a graph of nodes on a canvas: decision tables for the row and column logic an analyst can read, switches for branching, expression nodes using the ZEN Expression Language, custom functions for anything the tables cannot express, and sub decisions you reuse across models. The tables genuinely are business readable, which is the thing legacy engines like Drools never solved. The output is a JDM file, which is the same artefact Zen Engine consumes, so there is no translation layer between what you designed and what runs.

Versioning, Environments and Scenario Testing

GoRules treats decision models like code. You get branching, commits, history and change requests, plus GitSync on every tier including the free one. Scenario suites let you run a decision model against a table of expected inputs and outputs before release, which is the feature that separates a rules platform from a spreadsheet. Deployment environments cover dev, staging and production. This is also where the pricing starts to bite: the free plan includes zero deployment environments, Pro gives you one, and Business gives you two. Enforced reviews before merging to main are Business only, and enforced approval before a production release is Enterprise only.

AI Copilot and Embedded Execution

An AI copilot helps draft and explain decision models, and every plan ships with a monthly AI credit allowance. Execution is deliberately flexible: run rules through the hosted API, embed the engine in your service via SDK, run it in Spark for batch scoring, or drop it into a serverless function. All plans include unlimited evaluations via the Agent or SDK, which is unusual and welcome. Most rules platforms meter executions and that is where the surprise invoices come from. GoRules meters seats, projects and models instead.

How Much Does GoRules Cost?

The free plan is $0 and includes 2 users, 1 project, 10 decision models in that project, $10 a month of AI credits, change requests and GitSync. Critically it includes no deployment environments, so it is a BRMS you can design in but not deploy from. Pro is $167 a month, or $2,000 billed annually for a 17 percent saving, and gives you 5 users, 2 projects, 20 models per project, 1 deployment environment and $70 a month of AI credits. Business is $500 a month or $6,000 annually, with 20 users, 5 projects, 50 models per project, 2 environments, $200 a month of AI credits, audit logs, a SOC 2 Type II report, a standard SLA and enforced reviews to merge to main. Enterprise is custom and adds global roles, webhooks, SSO via OIDC, an enterprise SLA and dedicated support. Prices exclude VAT, and AI credits beyond your allowance are billed at 1.5 times Amazon Bedrock cost plus a regional premium.

Now compare. DecisionRules.io runs Entrepreneur at 59 euros a month, Small Business at 239 euros and Business at 449 euros, with a Starter tier at under 2 euros. Camunda Cloud starts around $200 a month for its Starter plan and Camunda 8 Self Managed has a starter licence from 99 euros a month, and that buys you full BPMN process orchestration alongside DMN decisions. Drools is free and open source forever. Against that set, GoRules Pro at $167 a month for 5 users and a single deployment environment is expensive for what it is, and Business at $500 a month to unlock audit logs and a compliance report will look like gating to any regulated team.

The structural problem is the gap between free and Pro. A team with three engineers and a staging environment is immediately on the $167 plan, and the free tier’s lack of any deployment environment means you cannot pilot the platform end to end without paying. That is a deliberate choice and it is the main reason our rating sits where it does.

Who is GoRules Best For?

Use GoRules if you want the open source Zen Engine. That recommendation is unambiguous. If you are running polyglot services that all need to evaluate identical business rules with low latency and no network hop, embed Zen Engine, store your JDM files in Git, and pay nothing. It is well built, permissively licensed and fast.

Use the paid platform if you have non engineers who genuinely need to author and change rules themselves, and your rule change rate is high enough that the editor and approval workflow save real engineering time. Fintech underwriting, insurance eligibility, marketplace pricing and fraud routing are the shapes that justify it. If a product analyst is editing a pricing table twice a week, $167 a month is nothing next to a developer ticket per change.

Skip GoRules if:

• Your rules change monthly, not weekly. A configuration file and a code review will be cheaper and simpler.
• You need process orchestration as well as decisions. Camunda does both; GoRules only does decisions.
• You need audit logs or a SOC 2 report for compliance and cannot spend $500 a month to get them.
• You deploy to Alpine or other musl based images, since Linux musl is not currently supported.
• You want to trial the full workflow for free. With zero deployment environments on the free plan, you cannot.

Best GoRules Alternatives

Camunda

Camunda is the enterprise standard and the obvious alternative if decisions are only half your problem. It pairs BPMN process orchestration with DMN decision modelling, so one platform covers the workflow and the rules inside it, and it has by far the largest ecosystem and hiring pool of anything here. Camunda Cloud starts around $200 a month with a self managed starter licence from 99 euros a month. The tradeoff is weight: Camunda’s decision engine is slower to change and more complex than GoRules, and if you only need decisions you are paying for a lot of BPMN you will never touch. Choose Camunda when you need end to end orchestration and enterprise support.

DecisionRules.io

DecisionRules.io is the closest like for like competitor and the cheaper one. Its tiers run from a Starter+ plan at under 2 euros a month through Entrepreneur at 59 euros, Small Business at 239 euros and Business at 449 euros. For a small team that needs a hosted rules editor with an API, Entrepreneur at 59 euros undercuts GoRules Pro at $167 by a wide margin. What you give up is the embeddable open source engine: DecisionRules is a hosted service, so every evaluation is a network call, and GoRules’ sub millisecond in process execution is not on the table. Choose DecisionRules if hosted convenience and price matter more than embedding and latency.

Drools

Drools is the free, open source, Apache licensed veteran of this category and it is still the answer for a lot of Java shops. It is mature, deeply capable and costs nothing at any scale. It is also Java only, notoriously heavy to operate, and its authoring experience is a long way behind a modern decision table canvas, which is precisely the gap GoRules was built to exploit. Choose Drools if you are a JVM organisation with the in house expertise to run it and zero budget for a rules platform.

Final Verdict: Is GoRules Worth It?

GoRules scores 6.1, and the number hides a split verdict. The open source Zen Engine is one of the better pieces of infrastructure released in this category in years: Rust core, MIT licence, nine language bindings, fast, and free. If that is all you need, take it and enjoy it. The visual JDM editor is also genuinely good, and treating decision models as versioned artefacts with scenario tests and GitSync is the correct design.

The commercial packaging is what drags the score down. A free tier with no deployment environments cannot demonstrate the product. Pro at $167 a month buys 5 users and one environment, well above DecisionRules at 59 euros for a comparable tier. Audit logs and the SOC 2 report sitting at $500 a month puts basic compliance out of reach for the small regulated teams most likely to want a rules engine. Add a young bootstrapped company with a small ecosystem and metered AI credits priced at 1.5 times Bedrock, and the paid platform is a harder sell than the engine underneath it. Our recommendation: adopt Zen Engine now, and only move to the cloud platform once you can point at non engineers who will actually edit the rules.