Business rules, generated and governed

From policy to production-ready rules in minutes, not weeks.

Your experts write the rule in plain English. RuleGenz writes it in your rules language, checks it against your own data, explains it back and records who approved it.

Book a demo See how it works

IBM ODM · DMN · Drools · Python · SQL · C# · Java + more
Your own AI account
Data hosted in the UK

Shipping · PC-001

If the demurrage claimed on a laytime claim is more than USD 50,000, put the claim on hold for manager review.

Generate · check · explain

Checked ruleValid draft

if
  the demurrage amount of 'the claim'
  is more than 50000
then
  put 'the claim' on hold ;

IBM ODMDMNDroolsPythonSQL+10

Approved by a reviewer

Explained in plain English

For any rule-heavy business

Wherever policies turn into rules

InsuranceClaims referral limits, underwriting appetite, pricing adjustments, fraud indicators

Shipping and logisticsDemurrage and laytime claims, port costs, disbursement checks, sanctions screening

Banking and paymentsPayment holds, approval limits, customer due diligence, fees and charges

AviationCrew duty and rest limits, rostering rules, pay and allowances

The challenge

Every rule change passes through several hands

A policy owner writes the change. An analyst interprets it. A developer codes it. A tester finds what was lost in translation, and it goes round again.

Policy ownerwrites the change in a document or email

Analystinterprets it and writes a specification

Developerwrites the rule in the rules language

Testerfinds what was misunderstood

…and back to the start when something was lost in translation

Meaning is lost

Each hand-off rewrites the policy in someone else's words.

Changes take weeks

Simple threshold or rate changes queue behind larger work.

Hard to prove

Business owners cannot easily read the rule that went live.

A policy-to-rules platform

Keep your rules engine. Govern what goes into it.

RuleGenz sits between your policies and whichever engine runs your rules. There is nothing to replace, and nothing to migrate unless you want to.

Engine independent

IBM ODM, Drools, DMN, GoRules, .NET, Java, Python, SQL and more. The same approved rule, in the language you run today or tomorrow.

Governed

Every rule checked, explained in plain English and approved by a named reviewer, with its full version history.

Traceable to policy

Each rule links to the clause and policy version it implements, so audit questions take minutes, not weeks.

Change impact

When the policy changes, see which rules are affected, which values now conflict and which rules to retire, before anything goes live.

How it works

Seven steps from a policy change to a live rule

RuleGenz drafts rules; people approve them. Your normal testing and release process does not change.

1Policy or rate changes
2Write it in English
3Generate and check
4Explain in English
5Review and approve
6Export rule files
7Load, test and release

Your business team RuleGenz Your developers and systems

Write it in English

Type a requirement, paste a list, or import a whole policy: Word, Excel, CSV, PDF or text.

Checked against your data

Only your own business terms and valid syntax. Failed checks are corrected automatically.

Explained and approved

Every rule is read back in plain English, with assumptions and gaps listed, then approved by a named reviewer.

Exported in your format

One file per rule plus a combined file for a single import, each traced to its requirement ID.

Policy change impact

The policy changed. Which rules are now wrong?

Upload the new version of the policy. Every clause is compared with the rules you already have, and you see the impact before anything changes.

Policy version 1 compared with version 4: one clause changed with a value conflict, one new clause, one removed, four unchanged

From "what changed?" to a signed-off update

A limit drops from USD 50,000 to USD 40,000. RuleGenz finds the clause, sees that the live rule still uses 50,000, flags the conflict and shows the approval that must be repeated.

Changed, new and removed clauses, word by word
Value conflicts between the new policy and your rules
Affected rules regenerated from the current rule, then re-approved
Rules to retire listed, and an impact report for sign-off

A rule's version history comparing the old and new rule, with generated boundary test cases

Every version kept, every rule tested

Each change records who made it, when and why, and who had approved the version before. Compare any two versions side by side.

Version history for the requirement and its rule
Test cases at, just below and just above every limit
Tests in every download, ready for your engine's test harness

Migration

Moving engines? Bring your rules with you.

A Drools rule and the converted rule side by side, with its assumptions

Import the old rules, review the new ones side by side

Upload rule files or a zip from Drools, DMN, JSON rules, Microsoft RulesEngine, NRules, Python, SQL, IBM ODM and more. Each rule is split out, converted, checked and explained, then exported to the engine you are moving to.

Original and converted rule side by side, with assumptions and gaps
A migration report of every rule and what it became
IBM ODM rules convert without AI

Conversion from other languages is AI-assisted, and every converted rule is reviewed before approval.

The product

See every rule before it goes live

Generating a rule: a requirement in plain English and the checked rule with its assumptions

One sentence becomes a checked rule

Write the requirement as you would in an email. RuleGenz writes the rule, checks every term against your vocabulary and lists the assumptions it made, such as whether exactly USD 50,000 counts.

Valid draft, partly covered or needs fixing: always clear
Plain-English explanation for sign-off
Assumptions and gaps listed, never hidden

A requirements project dashboard showing drafted, partly covered, needs fixing and approved rules

A whole policy document at once

Import a policy, contract or requirements list and generate every rule in one run. The dashboard shows what is drafted, approved or needs attention.

Vocabulary gaps list exactly which business terms are missing
Reviewers approve; every approval is recorded
Export approved rules in one download

Rules languages

One rule, written in the language your systems run

Choose the language once and every rule is generated, checked and downloaded in it. Switch at any time to see the same rule in another format, at no extra AI cost.

Rules engines

IBM ODM (BAL)IBM Operational Decision Manager
DMN / FEELCamunda, Kogito, Trisotech and other DMN 1.3 engines
Drools (DRL)Red Hat Decision Manager and Apache KIE
GoRules (JDM)The open-source Zen engine and GoRules editor
C# (NRules).NET applications using NRules
Microsoft RulesEngine.NET applications using Microsoft's RulesEngine
Java (Easy Rules)Java applications using Easy Rules with MVEL

Application code and data

PythonDjango, FastAPI and other Python back ends
TypeScript / JavaScriptNode.js, Angular and React applications
SQL Server (T-SQL)Rules run directly against your database tables
JSON rulesjson-rules-engine and systems that store rules as JSON
JSON LogicEvaluated in JavaScript, Python, Java, .NET, PHP and Go

Tables, expressions and policies

Decision table (Excel)Business sign-off and spreadsheet-based rule tools
CELGoogle's Common Expression Language
Rego (OPA)Policies evaluated by Open Policy Agent

Rules from other enginesPaste a rule from FICO Blaze Advisor, Pega, InRule, Progress Corticon, SAP BRF+, Oracle Intelligent Advisor or anywhere else to check it, explain it in plain English or convert it.

Built for bulkExport a whole project, such as 100 rules, as one file per rule plus a combined file for a single import.

Benefits

Faster changes, fewer errors, full control

Faster change

A threshold or rate change becomes a sentence, a check and an approval, not a ticket in a development queue.

Fewer errors

Every rule is checked against your data before anyone sees it, and assumptions are raised up front instead of in testing.

Proof for audit

Each live rule traces to its requirement, its plain-English explanation and the person who approved it.

Business stays in control

Policy owners read and approve rules in English; they no longer need to read rule code.

Scales with you

Ten rules or a thousand: new customers, tariffs and regulations without growing the team at the same rate.

Safer policy changes

See every rule a policy change affects before it goes live, with conflicts flagged and nothing missed.

Return on investment

Work out your own saving

Rule changes a year × hours saved per change × blended hourly cost

In an illustrative case, a team makes 100 rule changes a year, each taking 12 hours of analyst, developer and tester time. If RuleGenz brings that to 4 hours, the team saves 800 hours a year: about £48,000 at £60 an hour, before counting faster changes and fewer production errors.

Illustrative figures only, not a promise. A pilot measures your real figures against your current process.

Today

1,200 hours

With RuleGenz

400 hours

800 hours saved a year in the illustrative example

Security and control

Designed for enterprise security reviews

Security Overview, Data Protection Pack and completed security questionnaire available for your IT and procurement teams.

Your own AI account

Azure OpenAI, OpenAI or Anthropic, under your agreements. The key is encrypted and never shown again.

Data stored in the UK

Workspace data and the rule engine are hosted in London, encrypted in transit and at rest.

Two-step login and SSO

Invitation-only accounts, two-step login for everyone who can change rules, single sign-on and allowed email domains.

Separated workspaces

Each organisation's data is isolated by the database itself, not only by the application.

Complete audit log

Sign-ins, imports, approvals and downloads, with who and when. Entries cannot be edited or deleted.

You own your rules

Standard files that keep working without RuleGenz. Download all your data at any time.

Founding customer pilot

Start small, with success agreed up front

Week 0Kick-off
Agree users, requirements and success measures.
Weeks 1–2Set-up
Workspace, AI connection and your vocabulary.
Weeks 3–8Generate and review
Rules for one real policy, approved by your experts.
Weeks 9–12Test and decide
Test a sample in your environment and review the results.

As a founding customer

Founder-led onboarding
Direct line to the founder, with a reply within one working day
Pricing fixed for 24 months
A say in the roadmap
Pilot fee credited to your first year
Keep every rule produced, whatever you decide

Book a demo

See it on your own rules

A 30-minute demonstration, then a 60 to 90-day pilot on one of your real policies, measured against your current process.

We reply within one working day
No obligation, and no sales pressure
Bring a real policy, and we'll show it working