Enterprise DNA

Instead of DecisionRules

Stop renting DecisionRules. Own your business rules.

We build your version around how you route orders, assign service priorities and review policy changes. We bring your DecisionRules rules across, check their outcomes with you and run your system.

DecisionRules Public Cloud Premium is quoted to your requirements. Its smaller Lite plan lists €3,500 billed annually, excluding VAT.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The subscription comparison

Paying for DecisionRules means choosing a platform plan

The Public Cloud price depends on the plan and its allowances. Premium is quoted. Check your actual contract before comparing it with a system built for your operation.

paid

An annual Lite subscription

Lite lists €3,500 billed annually, excluding VAT. Premium has a separate quote.

layers

A rule allowance

Lite includes 30 business rules and flows. Premium tailors the allowance.

group

Access for the people involved

Lite includes one user. Premium tailors the user count and adds central team management.

speed

A volume allowance

Lite includes 10,000 solver calls. Premium provides a tailored usage allowance.

history

Decision and user audit features

The Premium offering lists decision and user-action auditing alongside business insights.

support_agent

A support arrangement

Premium offers tiered support and a tailored service commitment. An owned system needs its own operating arrangement.

Your operational rules

A decision has an owner, a version and a reason

Rule reviews

See what is due before the next change

A rule can work as written and still be out of date. Keep its purpose and review date beside the person responsible.

  • check A named owner for each operational rule
  • check Reviews due in the next fortnight
  • check Open exceptions beside each rule
  • check Your review calendar joined to your exception backlog

Change checks

Find the orders a proposed change would reroute

Try a new version against saved examples before it becomes active. Keep the earlier definition for comparison.

  • check Explicit inputs and matching conditions
  • check Saved examples with expected outcomes
  • check Activation blocked when the examples fail
  • check A separate named reviewer for each approval

Decision evidence

Keep the result and the rule that produced it

An unmatched case stays visible. Read the version and matching rows behind a recorded result.

  • check A business reference on each recorded decision
  • check Results grouped by rule version
  • check Unmatched outcomes counted separately
  • check Retention review dates for personal records

Weekly work

Turn exceptions into an owned follow-up list

Give unresolved cases an owner and a due date. Prepare a review pack from the same records.

  • check Overdue cases ordered by due date
  • check A written resolution when a case closes
  • check Rule cards and change review packs in your brand
  • check A Monday review combining dates, outcomes and exceptions

Make it yours

Design your own DecisionRules replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from DecisionRules. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your DecisionRules replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your DecisionRules data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Business Rules for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Business Rules for Claude Code

Connected to your own database

Which rule reviews are overdue and who owns them?

Returns routing

Ner re
Hana Patel
View due da
2026-09-20
Ys overdue ac
25
Tive version te
1
St cases op
3
En exceptions
1

Order routing

Ner re
Mere Thompson
View due da
2026-10-08
Ys overdue ac
7
Tive version te
1
St cases op
3
En exceptions
1

Service priority

Ner re
Alex Chen
View due da
2026-10-25
Ys overdue ac
-10
Tive version te
1
St cases op
3
En exceptions
1

Ask it anything

Questions about your own rules and records

These questions run against the demonstration records. Your installed version connects them to your own operational evidence.

chat_bubble Which rule owners have a review overdue and unresolved exceptions?
chat_bubble Which rule versions have no recorded passing test run?
chat_bubble Which orders were left without a matching route?
chat_bubble Which proposed change sends our New Zealand orders to a different depot?
chat_bubble Which version made a recorded decision, and which rows matched?
chat_bubble Which urgent service records have passed their retention review date?
chat_bubble Which case owners have missed an exception due date?
chat_bubble What did the previous reviewer approve before a version became active?
chat_bubble Which rule has more than one version waiting for review?
chat_bubble What changed, who recorded it, and what needs attention on Monday?

Switching

How to switch from DecisionRules

A move usually involves exporting a decision table, checking which rules the import supports, and separately mapping any complex logic, connections or history you need to keep.

  1. 1

    Export one decision table

    Start with one decision table your team uses and export it from DecisionRules as JSON. Keep the original export, including its rules and structure, so you can refer back to it. If your account does not offer the documented JSON export, export what the account allows, usually CSV or Excel, and check the available options with DecisionRules before proceeding.

  2. 2

    Load the rules as a draft

    Have the supported export loaded into the database as an unapproved draft. The import supports a subset of literal-text conditions and results. It does not activate the rules, so do not treat the draft as ready for live decisions. Complex expressions and flows need separate mapping, and unsupported logic is refused rather than silently changed.

  3. 3

    Check the import and examples

    Review what the import accepts and what it flags or rejects. Compare the draft with known examples from your current rules, including which rule matches when more than one could apply. Test the draft against saved examples before approval. Unsupported logic, scripts, flows, external connections and historical logs may need separate mapping before you can decide what to bring across.

  4. 4

    Run both systems side by side

    For a short agreed period, run the same cases through DecisionRules and the new system. Compare the outcomes and matching rules, and investigate differences before relying on the new system. Keep DecisionRules available while you check the results. The new version should remain a draft until its examples pass and a different named reviewer approves it.

  5. 5

    Switch off DecisionRules

    Once you have checked the results and agreed the new rules are ready, move operational use to the new system and switch off DecisionRules. Keep the original export and any history you have chosen to retain. If you still need DecisionRules records that were not included in the table export, make sure their separate mapping or retention is addressed before closing the account.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, especially complex expressions, flows and connections, then deciding which historical logs you need to bring across. Importing a supported table is only part of the move. If you have Enterprise DNA install and run the system, they do this mapping and migration work as part of scoping your version.

Not ready for a call?

Get your DecisionRules switch plan by email

We will send you the step-by-step plan for moving your business off DecisionRules, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to run

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Import a supported DecisionRules JSON export and reconcile the examples
  4. 4 Review the exact version before approving it and connect your own database when needed
Get it on GitHub

Built around your business

We customise it

Scoped setup, with ongoing support agreed

  • check Your fields, review intervals and decision rules
  • check Your DecisionRules exports mapped and checked
  • check A web front end for your team if you want one
  • check A different technology stack if your business needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Connections to the systems that supply your decisions
  • check Backups, access controls and review routines agreed with you
  • check A person responsible for keeping your version working
Book a call with Sam

Questions

Instead of DecisionRules, answered

Is this a replacement for the whole DecisionRules platform? expand_more

The free version covers operational routing, service priorities, rule reviews and decision evidence. Enterprise DNA scopes your required connections, interfaces and hosting into your version. We compare the actual rules your team uses before agreeing the build.

Will our DecisionRules rules import without changing their meaning? expand_more

Supported literal-text conditions and results import as an unapproved version, with the original export retained. More complex expressions and flows need mapping. Unsupported logic is rejected. We compare known examples and matching order before anything becomes active.

Can somebody change a rule without checking it? expand_more

An approved definition stays intact. A new version needs at least two passing examples and a different named reviewer before activation. The free version records names for attribution. We add the identity and access controls your shared installation requires.

Does it certify that our decisions meet legal requirements? expand_more

It checks review dates, unresolved cases, and recorded privacy accuracy and retention dates. Those checks support your review process. They do not certify compliance or make regulated decisions on your behalf. The free version is designed for operational routing.

What will Enterprise DNA charge us? expand_more

We agree a setup fee for your rules, data migration and connections, then a monthly retainer to operate the system. Bring your DecisionRules contract and a sample of the rules you use. The scope follows that evidence.

Put your rulebook to work in a system you own

Spend 30 minutes with Sam. Bring your DecisionRules bill, one export and a recent change that was difficult to check. We will look at what your own version needs and what it takes to run it.

Book a 30-minute call Get the free version

Business Rules for Claude Code is free and open source, published by Enterprise DNA.

Done paying for DecisionRules?

Get your version built