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 demoSee 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+42
Approved by a reviewer
Explained in plain English
47rule formats, from IBM ODM and DMN to SQL, SAS and Cedar
100sof requirements generated in one run
100%of rules checked against your vocabulary before anyone sees them
0lock-in: every rule is a standard file you keep

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
Lending and creditAffordability checks, credit policy, referral limits, pricing rules

Command Centre

Every charge you pay, checked against what was agreed

One place to check the money that leaves your business: port charges and disbursement accounts, bank fees, loan interest and insurance. Every line is found in the document, worked out from the official source or your agreement, and shown with the working. It adapts to your business: a shipping company sees ports, a bank sees banking.

Ports

Official tariffs for the top ports, every charge worked out for a vessel, and proforma and final DAs checked in bulk.

See ports →

Banking

Bank statements and charge invoices checked against your agreed fee schedule, and card interchange against the legal caps.

See banking →

Lending

Loan interest worked out again from the central bank's published rate, plus your margin, floor and day count.

See lending →

Insurance

Premium tax and broker fees on premium invoices, and repairers' labour, parts and fees against your rate cards.

See insurance →

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.

  1. 1Policy or rate changes
  2. 2Write it in English
  3. 3Generate and check
  4. 4Explain in English
  5. 5Review and approve
  6. 6Export rule files
  7. 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.

app.rulegenz.com
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
app.rulegenz.com
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

Verified in your engine

Know your engine accepts the rule before you approve it

app.rulegenz.com
A rule verified in Open Policy Agent, with editable test cases and their results in the engine

Choose your engine. Every rule is loaded into it and tested.

RuleGenz loads each rule into a real copy of your rules engine and runs its test cases. Edit the suggested cases or add your own, and see what the rule does in your engine, case by case.

  • Rules are run in 41 engines at fixed versions, including Drools, Camunda 8, Apache KIE DMN, NRules, Microsoft RulesEngine, Open Policy Agent, GoRules, json-rules-engine, PostgreSQL, MariaDB, Easy Rules (MVEL), Spring (SpEL), Cedar, SWI-Prolog, CLIPS, Saxon and PMML
  • Optional rule: nothing is approved until it passes, enforced by the database
  • Engine, version, results and who ran them, in every download

SQL Server rules are checked against the T-SQL grammar, and IBM ODM, SAS, Jess, XACML, Datalog and SQL/PSM rules by RuleGenz's own checks, because those engines can't be hosted. Verification in Drools and in the Camunda and Kogito DMN engines is coming.

Migration

Moving engines? Bring your rules with you.

app.rulegenz.com
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
  • Proof the new rule decides like the old one: both run on the same test cases, or replay thousands of decisions your old system really made
  • Every difference listed with its reason; intended ones accepted and signed off
  • 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.

Audit evidence

The auditors are coming. Your evidence is one click away.

Evidence report.docx
The traceability matrix in an audit evidence report: each policy clause, its rule, its engine test results and who approved it

Download the full audit evidence pack for any project

No more weeks of screenshots, emails and spreadsheets. One download gives the auditor every clause traced to its rule, its tests, its engine results and its approval, with the gaps flagged before anyone else finds them.

  • A traceability matrix from each policy clause to the rule, the tests and the approver
  • Exceptions listed first: rules approved without a passing test in your engine, outdated rules and clauses with no rule
  • What every rule does, in plain English, with the approved rule and its test cases
  • Signed engine results, policy change history and the audit log for the project
  • Tamper-evident: every file in the pack is fingerprinted with SHA-256

The pack is built from the records RuleGenz already keeps, without AI. Every download is itself recorded in the audit log.

Industry standards

Rules that speak your industry's language

RuleGenz comes with vocabularies built on the published standards of each industry, so rules use the same names for data as the invoices, payment messages and documents you already exchange. Every term is tagged with the standard field it follows.

Supplier invoices and contracts

EN 16931, the European e-invoicing standard used by Peppol and UBL. Check invoices against contract prices, rebates and service levels.

Payments

ISO 20022, the global standard for payment messages. Payment holds, approval limits, screening and charges.

Lending and credit

FIBO, the Financial Industry Business Ontology. Affordability, credit policy, collateral and referral limits.

Insurance

The OMG Property and Casualty Data Model. Claims triage, claims authority, underwriting referral and appetite.

Shipping and port costs

IMO FAL forms, DCSA Port Call, BIMCO Laytime Definitions and UN/LOCODE. Laytime, demurrage, port costs and screening.

Crew flight and duty

EASA ORO.FTL and US 14 CFR Part 117. Flight duty limits, rest and extensions.

Standard terms first, your own terms on top

  • Each vocabulary lists what the standards don't cover, such as contract rates, approval limits or underwriting appetite, so you know exactly what to add
  • Add your own fields on top of the standard from a data dictionary or database. Your terms are marked as yours, and updates to the standard reach you automatically
  • A set of sample rules for each industry to start from

Port Command Centre

Every port charge worked out, and every DA checked

RuleGenz keeps a library of the official tariffs of 219 top ports in 101 countries, read from each port's own published documents and checked daily for new editions. For any other port, upload its tariff and it is read the same way.

Every charge for a vessel

Give the vessel and the port: light dues, port dues, VTS, pilotage, towage, berthing and running of lines are worked out from the tariff, with the calculation and the tariff's own words for each.

DAs checked automatically

Upload a proforma or final DA. Every line is checked against your agreements, the port's tariff and what the port has cost you before, with currencies converted and the final DA compared with its proforma.

Approve or query in one click

Clear DAs go to approval, or are approved automatically under your limit. Overcharges get a ready-to-send query for the agent with the proof, and revised DAs are checked again.

How the port charges calculator works

Give it the port and the vessel (gross and net tonnage, length, days alongside, number of tugs and services). The rules are read from the port's own tariff, never typed in by hand, so a new edition is picked up as soon as the port publishes it.

1. Findthe sections of the tariff that apply to a vessel calling at the port
2. Readeach charge into a formula: fees per 100 tons or part, per 24 hours, size bands, minimums, surcharges and the conditions they depend on
3. Verifyevery number in every formula must be printed on the page it came from, or the charge is held back and reported
4. Calculateeach charge with the working shown, the page and the tariff's own words, plus charges that may also apply

Accurate to the cent

Tested on a national port authority's tariff book: all six charges for the test vessel match the tariff to the cent. The arithmetic is done by the calculator, never by the AI, and how each rate is counted (per 100 tons or part thereof, pro rata per 24 hours) is set from the tariff's own words.

Read once, used every time

A tariff is read once per edition. Every later calculation and every DA check for that port uses the same verified formulas, instantly and at no extra cost.

Any port, in bulk

Upload any port's tariff as a PDF, Excel file or web page, or a whole folder of them at once. Each file's port is found from the document, and the tariffs are read side by side, with live progress.

Fast, and right

A whole batch of DAs at once

Drop in every proforma and final DA for the week. They are read and checked side by side, and each verdict appears as it is ready: clear, check or query, with the amount at stake.

Nothing taken on trust

A charge is only used when every number in it is printed in the tariff, next to the words quoted for it, in the right section. Anything that can't be proven is left out and reported, never guessed.

People decide, not the software

Overcharges come with a ready-to-send query and the proof. Clear DAs wait for a reviewer, or are approved automatically under the limit you set. Every step is recorded.

Proof for every number

  • Each charge links to the port's document, the page and the exact words it came from, with a kept copy of the document
  • Stop lights show which ports are up to date, which changed and which need attention, and what changed in each new edition
  • Approved DAs go to your own system for payment or export to your accounting system, with a full history of who checked, queried and approved them
  • A monthly report shows what was checked, how fast, what was queried and what revised DAs took off the bill, by port and by agent
  • Documents that contain no charges are recognised and set aside before any reading, so you only pay to read real tariffs

Banking, lending and insurance

Every charge checked against what was agreed

The same checking, for the money that leaves your business through banks, lenders and insurers. Upload the statement or invoice: every line is found in the document, worked out from your agreement and official data, and shown with the working and the source. Banking, Lending and Insurance each get their own Command Centre, and a workspace shows only the industries it works in: a bank sees banking, not ports.

Bank charges

Payments, FX margins, account and card fees checked against your agreed fee schedule, and card interchange against the legal caps.

Loan interest

Interest worked out from the official reference rate (SONIA, €STR, SOFR and more, collected daily from the central banks) plus your margin, floor and day count.

Insurance

Premium tax and broker fees on premium invoices, and repairers' labour, parts and fees against your rate cards.

The product

See every rule before it goes live

app.rulegenz.com
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
app.rulegenz.com
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 / FEEL and S-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
  • JSON rulesjson-rules-engine, or your own JSON format
  • Python business-rulesJSON rules for Django and other Python back ends
  • Java (Easy Rules, MVEL)Java applications using Easy Rules
  • C# (NRules).NET applications using NRules
  • Microsoft RulesEngine.NET applications using Microsoft's RulesEngine
  • CLIPS and JessExpert-system rule engines
  • Decision table (Excel)Business sign-off and spreadsheet-based rule tools

Expression languages

  • JSON LogicEvaluated in JavaScript, Python, Java, .NET, PHP and Go
  • CELGoogle's Common Expression Language
  • SpELSpring applications
  • JEXLApache Commons JEXL in Java applications
  • OGNLJava frameworks that use OGNL
  • Unified ELJakarta EL in Java web applications

Application code

  • PythonDjango, FastAPI and other Python back ends
  • TypeScript / JavaScriptNode.js, Angular and React applications
  • GoGo services, common in fintech and payments
  • REXXMainframe and legacy automation

Databases

  • SQL Server (T-SQL)Rules run directly against your tables
  • PostgreSQL (PL/pgSQL)Functions in PostgreSQL
  • Oracle PL/SQLProcedures in Oracle Database
  • MySQL / MariaDBStored procedures
  • ANSI SQL and SQL/PSMPortable SQL, IBM Db2 and other ISO SQL databases

Policies and access control

  • Rego (OPA)Policies evaluated by Open Policy Agent
  • CedarAWS Verified Permissions and Cedar policies
  • XACML 3.0Enterprise attribute-based access control

Analytics and credit risk

  • SASDATA step rules used by credit-risk teams
  • PMMLRule sets and decision trees for scoring engines

Logic programming

  • PrologSWI-Prolog and other ISO Prolog systems
  • DatalogSoufflé and other Datalog engines

XML and semantic web

  • XPath, XQuery and XSLTRules over XML documents
  • SchematronThe standard rules language for XML
  • SWRL, SHACL and SPARQLRules over ontologies and knowledge graphs
  • OCLConstraints on UML models

Configuration languages

  • CUE, Jsonnet and DhallRules as typed configuration and data checks
Your own rule formatRules kept as JSON in your own system, or in an in-house engine? RuleGenz is set up to write your exact format from a few of your existing rules, so every download imports directly. Your existing rules can be read in the same way.
Several systems, one approved ruleWhere rules live in more than one system, each keeps its own format and its own screens. RuleGenz drafts, checks and tests the rule once, then writes the file each system needs.
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, and the whole audit evidence pack downloads in one click.

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.

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

  1. Week 0Kick-off

    Agree users, requirements and success measures.

  2. Weeks 1–2Set-up

    Workspace, AI connection, your vocabulary and your own rule format.

  3. Weeks 3–8Generate and review

    Rules for one real policy, approved by your experts.

  4. 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