Red Hat Decision Manager

Quick Summary

Red Hat Decision Manager (RHDM) is Red Hat's commercial, enterprise-supported BRMS — formerly branded Red Hat JBoss BRMS — built on top of the open-source Drools engine, with the Business Central web UI layered on for rule and decision-table authoring. It adds Drools Fusion for complex event processing, OptaPlanner for resource optimization, and Kogito for cloud-native, OpenShift-Kubernetes-style deployment on top of what open-source Drools ships for free.

The single most consequential fact about RHDM in 2026 is not a feature gap — it's that the product has stopped moving forward. Version 7.13, released in 2022, is the last version Red Hat will ship. The product has been transferred to IBM and now continues life as IBM Decision Manager Open Edition (DMOE) / IBM BAMOE. Every organization still running RHDM today is, whether they've acknowledged it yet or not, on a migration clock — either toward IBM's roadmap or toward an alternative platform. Layered on top of that reality are the same operational costs that define Drools: DRL-only rule authoring for anything beyond a decision table, no native governance, heavy JVM and OpenShift operational overhead, and a subscription-based commercial model with no public pricing.

What Is Red Hat Decision Manager?

RHDM packages several components around the Drools core:

• Drools Engine: The same Rete-algorithm rule engine that powers open-source Drools — RHDM does not replace or fundamentally change the execution core.
• Business Central: A web-based authoring and management console meant to let business analysts view and edit decision tables, decision trees, and guided rules without writing raw DRL — in principle separating rule ownership (business) from deployment (IT).
• Kogito: The cloud-native evolution of the platform, enabling rules and processes to be deployed as independently scalable microservices on Kubernetes/OpenShift, integrating with Quarkus and OpenShift CI/CD pipelines.
• Drools Fusion: Complex event processing (CEP) capability for time-windowed, event-driven rule evaluation — relevant for fraud detection and streaming-data use cases.
• OptaPlanner: A constraint-solving and resource-optimization engine bundled with the platform, useful for scheduling, routing, and allocation problems alongside standard rule evaluation.
• KIE Server: The runtime execution server that hosts deployed rule and decision services, exposed via REST and other protocols.

RHDM's authoring model is fundamentally the same as open-source Drools: rules beyond simple decision tables are authored in DRL (Drools Rule Language), a Java-flavored domain-specific language. Business Central's guided editors and decision tables give non-developers a narrower, template-bound path to make changes — but the underlying rule logic is still DRL, and anything outside the guided templates routes back to a developer.

How We Analyzed Red Hat Decision Manager's Abilities?

For this RHDM review, we focused on what determines outcomes for a team actually running the platform in production today — not whether Drools' Rete engine is capable (it is), but whether Red Hat's commercial layer on top of it delivers governance, business-user accessibility, and a viable multi-year roadmap, given that the product itself has been discontinued.

We structured the analysis around the same eight parameters used across this comparison set. Each parameter maps to an in-depth section below.

Our analysis draws from Red Hat's product and documentation pages (access.redhat.com, docs.redhat.com), Red Hat's own end-of-life and IBM transition communications, IBM community posts describing the RHDM-to-BAMOE handoff, Gartner Peer Insights, TrustRadius, SourceForge listings, and comparison datasets maintained in this workspace.

How Red Hat Decision Manager Works

1. Rule Authoring: Developers author rules in DRL, or business analysts use Business Central's guided decision tables, decision trees, and scorecards — bounded by whatever templates and object model developers have already defined.

2. Rule Compilation and Packaging: As with open-source Drools, rules are compiled into KJar (Knowledge JAR) artifacts, requiring a build step before any change reaches a runtime environment.

3. Deployment via KIE Server or Kogito: Compiled rule services are deployed either to a traditional KIE Server or, in the cloud-native path, packaged as independently deployable Kogito microservices on OpenShift/Kubernetes.

4. Execution: Applications insert facts into a KIE session (or call a Kogito microservice endpoint), and the Rete-based engine evaluates and fires matching rules — architecturally identical to open-source Drools at this layer.

5. Business Central Governance (Limited): Business Central tracks asset versions inside its own repository and provides role-based views for its guided editors, but does not provide a maker-checker approval workflow, a compliance-ready audit log, or automated environment promotion.

6. Change Management: A rule change inside a guided template can be relatively fast; anything outside those bounds — a new attribute, a new rule pattern, integration with a new event source — reopens the DRL-compile-deploy cycle, with a developer in the loop.

7. Vendor Roadmap Transition: Because V7.13 is the final Red Hat release, any future capability, security patch, or platform enhancement now depends on IBM's BAMOE roadmap rather than Red Hat's own release cycle — a structural change in what "actively maintained" means for this platform going forward.

Who Uses Red Hat Decision Manager?

Existing Red Hat/OpenShift enterprise customers: Organizations that already run OpenShift, JBoss middleware, and Red Hat support subscriptions, and adopted RHDM as a natural extension of that ecosystem before the discontinuation was announced.

Financial services and insurance teams with legacy Drools-based systems: Organizations that adopted Drools-based decisioning years ago and layered Red Hat's commercial support and Business Central UI on top for governance and vendor accountability.

Government and public sector organizations: Regulated environments with existing Red Hat infrastructure investments and procurement relationships that make continuing on RHDM (for now) simpler than an immediate platform switch.

Enterprise architects planning a migration: Teams whose primary current activity with RHDM is not expansion but evaluation of where to move — IBM BAMOE, back to open-source Drools, or an entirely different decisioning platform.

RHDM is a poor fit for any organization evaluating a new BRMS purchase in 2026 — buying into a discontinued product line is difficult to justify regardless of technical merit. It's also a poor fit for organizations outside the Red Hat/OpenShift ecosystem, or those needing business teams to own rule changes without a developer in the loop.

Reviews

Pros

• Business Central gives non-developers a rule editing surface — in principle: Guided decision tables, decision trees, and scorecards let business analysts view and adjust rules within pre-built templates without writing DRL directly.
• Built on Drools — a production-proven engine: The same Rete-based execution core that has run in financial services, insurance, and government systems for decades, plus Drools Fusion for complex event processing and OptaPlanner for constraint-based optimization.
• OpenShift/Kubernetes-native via Kogito: Rules can be packaged and deployed as independently scalable microservices, integrating with OpenShift pipelines and Quarkus — a genuine architectural advantage for Red Hat shops already standardized on that stack.
• Standards support: DMN 1.3, BPMN 2.0, PMML, and FEEL are all supported, giving regulated teams a standards-compliant decisioning path where that's a procurement requirement.
• Strong fit for existing Red Hat ecosystems: For organizations already running OpenShift, Red Hat middleware, and Red Hat support contracts, RHDM integrates naturally with tooling and support relationships already in place.

Verified User, Gartner Peer Insights

"For teams already inside the Red Hat ecosystem, RHDM fit naturally into our existing OpenShift pipelines. The engine itself has never been the problem — it's what the platform requires around it that's the challenge."

Cons

• The product is discontinued. V7.13, released in 2022, is the last version Red Hat will ship. The product line has been handed to IBM as BAMOE. Any organization evaluating or continuing to invest in RHDM today is making a decision about a product with no further releases from its original vendor — the roadmap is now IBM's, not Red Hat's.
• Business Central is consistently flagged as complex in practice. Reviewers describe a meaningful gap between "business analysts can edit rules" in theory and the actual experience of navigating Business Central's interface — many teams route rule changes through developers regardless of the UI's existence.
• DRL learning curve persists underneath the UI. Guided editors handle simple decision tables; anything beyond that requires DRL authoring — Java-flavored code that non-Java teams find a steep, ongoing dependency.
• Heavy JVM and OpenShift operational burden. Running Decision Manager in production means managing the JVM runtime, GC/memory tuning, KIE Server operations, and, for Kogito deployments, OpenShift/Kubernetes operational expertise. Governance and business-facing controls beyond Business Central's UI are entirely custom builds.
• Red Hat/OpenShift ecosystem lock-in. Tight coupling to OpenShift, JBoss EAP, and Red Hat middleware means teams outside that stack face significant integration friction; going cloud-agnostic requires substantial custom work.
• No AI or modern authoring. No AI copilot, no natural-language rule creation, no MCP or agent integration — the authoring model is functionally unchanged from the JBoss BRMS era.
• Opaque, subscription-based pricing. No public pricing page, no self-serve trial for production use, and a sales-led enterprise pricing process that many mid-market teams find disproportionate to what they get relative to the platform's current (discontinued) status.

Verified User, TrustRadius

"We adopted Decision Manager as part of our broader Red Hat investment. It works, but the announcement that it's the last release changed the calculus overnight — we went from planning an expansion to planning a migration."

Verified User, SourceForge

"Business Central promises business ownership of rules. In our experience, anything beyond the simplest decision table still needed a developer who understood DRL. The UI didn't remove the dependency — it just moved where the friction showed up."

Features

1. Execution & Scale

RHDM inherits Drools' Rete-engine execution characteristics directly — capable of handling large, complex rule sets once tuned, with no fundamental performance ceiling on rule complexity. Kogito's Kubernetes-native packaging is a genuine step forward over classic KIE Server deployment: rules can be deployed as independently scalable microservices that integrate with standard Kubernetes horizontal pod autoscaling, rather than requiring bespoke JVM clustering.

The caveat is that "Kubernetes-native" is not the same as "auto-scaling out of the box." Horizontal pod autoscaling on OpenShift requires the customer's platform team to configure scaling policies, resource limits, and load-based triggers — RHDM does not ship a managed, zero-configuration scaling behavior the way a fully managed SaaS platform does. There is also no Red Hat-published uptime or latency SLA for self-managed RHDM deployments; performance depends entirely on the customer's OpenShift cluster configuration and JVM tuning.

Strengths:

• Drools' Rete engine handles high-volume, complex rule sets well once JVM-tuned — no theoretical ceiling on rule complexity.
• Kogito packages rules as independently deployable microservices, which is a meaningfully more cloud-native execution model than classic KIE Server.
• Standard Kubernetes horizontal pod autoscaling applies to Kogito-packaged rule services, once configured.

Drawbacks:

• No managed, zero-configuration auto-scaling — OpenShift scaling policies are the customer's responsibility to design and maintain.
• No published uptime or latency SLA for self-hosted deployments.
• Multi-step decisioning still requires pairing with jBPM or a separate process layer; Drools/Kogito alone orchestrate rule evaluation, not end-to-end decision flows.

2. Build & Author

Business Central is RHDM's answer to business-user authoring, and on paper it looks like a real one — guided decision tables, decision trees, and scorecards designed for analysts who shouldn't need to write DRL. In practice, this is the dimension where reviewer feedback is most consistently critical: Business Central's interface is repeatedly described as complex and unintuitive, and the gap between "a business analyst can edit this rule" and "a business analyst can navigate Business Central confidently" is wide enough that many organizations report rule changes still routing through developers, regardless of the UI's existence.

Structurally, the authoring model has not changed since the JBoss BRMS era: anything beyond a guided decision table within a pre-defined object model requires DRL — a Java-flavored rule language. There's no shared attribute library (a field rename means finding and updating every DRL rule and Business Central asset that references it), no simple formula/expression editor for non-technical logic, and no AI copilot or natural-language rule authoring on the roadmap, because there is no forward roadmap from Red Hat at all.

Strengths:

• Guided decision tables and decision trees genuinely lower the bar for simple, template-bound rule changes.
• DRL remains capable of expressing very complex logic — negation, temporal reasoning, accumulate patterns — for engineers who need it.
• Scorecards and DMN-based decision authoring are both supported for standards-compliant modeling.

Drawbacks:

• Business Central's usability is a consistently cited pain point — many teams route changes through developers anyway.
• Anything beyond guided templates requires DRL, keeping engineers in the critical path for most real-world rule changes.
• No shared attribute library, no formula/expression editor, no AI copilot — the authoring toolset has not evolved since the JBoss BRMS product line.

3. Operate & Govern

Business Central stores its rule assets in a Git-backed repository, which gives it a genuine edge over pure spreadsheet- or file-based competitors on version history and rollback mechanics — a prior asset version can be restored from the underlying Git history. Basic role assignment within Business Central lets an administrator scope who can access which project spaces.

What RHDM does not ship is a native maker-checker approval workflow: a rule change committed by an author does not require a distinct second party to approve it before reaching a deployable state, the way regulated industries increasingly require as a hard compliance control. "Audit trail" in practice means Git commit history for Business Central assets — useful for engineers, but not a compliance-facing, queryable log that a business or compliance user can review without technical translation. Environment promotion (dev → test → production) has no built-in workflow with configurable approval gates; it is whatever CI/CD pipeline the organization's platform team has built around KIE Server or Kogito deployment.

Strengths:

• Git-backed asset repository gives real version history and a rollback mechanism, ahead of engines with no native versioning at all.
• Basic project-level RBAC within Business Central provides a starting point for access control.
• SSO integration is supported for enterprise identity providers.

Drawbacks:

• No native maker-checker approval workflow — segregation-of-duties controls must be built as a separate process layer.
• No compliance-ready, business-readable audit trail — Git commit history is a developer artifact, not an auditor-facing record.
• No built-in environment promotion workflow with approval gates — promotion pipelines are entirely custom CI/CD, owned by the platform team.

4. Integrations & API

RHDM's integration model mirrors open-source Drools — REST APIs are available via KIE Server or Kogito-deployed microservices, and event-driven scenarios can be handled through Drools Fusion for complex event processing. All of this is genuinely capable for Java-centric teams comfortable building custom integration code.

There is no connector catalog, no no-code database or SaaS integration, and no visual data mapping layer. Every new data source that a decision needs — a partner API, a new internal system, an external data feed — is custom development work, same as it is for open-source Drools. Business Central's asset repository is Git-backed internally, but it is not the same as native, bidirectional GitHub sync integrated into an organization's existing source-control-first CI/CD workflow — teams wanting that typically build a bridge themselves.

Strengths:

• REST API exposure via KIE Server or Kogito microservices works for both Java and non-Java calling applications.
• Drools Fusion supports event-driven, time-windowed rule evaluation for streaming or fraud-detection use cases.
• Git-backed Business Central repository gives engineers a familiar versioning substrate to build CI/CD around.

Drawbacks:

• No no-code connectors — every new data source is custom Java integration work, identical to open-source Drools.
• No built-in webhooks, event triggers, or scheduler/cron as platform features.
• No native GitHub sync — the internal Git repository is not the same as an out-of-the-box connection to an organization's existing GitHub-based workflow.

5. Support / SLA

Red Hat's commercial subscription tiers do include support-desk access and, at higher tiers, a more senior support engagement model — this is a genuine benefit of paying for the commercial product over free open-source Drools. But the fact that sets RHDM apart from every other platform in this comparison set is the support lifecycle question: with V7.13 as the final release, "support" now means maintaining an aging, feature-frozen product rather than an actively developed one. Migration assistance toward IBM BAMOE, where it exists, is an IBM-led process, not a continuation of Red Hat's own roadmap — customers are effectively being handed off mid-relationship.

There is no published uptime SLA for self-hosted RHDM deployments, and training is a separate cost rather than something bundled into the subscription.

Strengths:

• Paid Red Hat subscription tiers include support-desk access and, at higher tiers, dedicated engagement — a real step up from unsupported open-source Drools.
• Large enterprise customers with existing Red Hat relationships have an established escalation path for critical issues.

Drawbacks:

• No published uptime SLA for self-hosted deployments.
• The product's own release lifecycle has ended — future patches and roadmap decisions belong to IBM's BAMOE product, not Red Hat.
• No included training, and migration assistance toward the successor product is IBM-led rather than a continuation of the original vendor relationship.

6. Security & Compliance

RHDM does not carry SOC 2, ISO 27001, or GDPR certification as a product — compliance posture is entirely a function of the customer's own OpenShift deployment, encryption configuration, and access controls. OpenShift itself provides strong security primitives (network policies, RBAC at the cluster level, standard Kubernetes security tooling), but translating those into an audit-ready compliance story for the decisioning layer specifically is customer-side work, unchanged from what open-source Drools requires.

Strengths:

• Self-hosted, flexible deployment (on-prem, private cloud, or OpenShift Dedicated/managed) gives full control over data residency and network isolation.
• OpenShift's Kubernetes-native security tooling (network policies, cluster RBAC) applies directly to Kogito-packaged rule services.
• Decades of precedent exist for meeting regulatory security requirements on Red Hat middleware in government and financial services.

Drawbacks:

• No platform-level SOC 2, ISO 27001, or GDPR certification for the decisioning layer — compliance evidence is entirely customer-built.
• No multi-tenancy or white-labeling as platform features.
• Security hardening and ongoing maintenance is the customer's job, made more complex by the fact that the underlying product will receive no further security patches from Red Hat beyond the V7.13 lifecycle window.

7. Logs / History / Reports

Business Central includes rule execution tracing and audit views intended for debugging — but these are developer-facing tools inside the workbench, not a business-readable report a compliance officer or product manager can open to answer "why did this decision fire?" There's no native analytics dashboard tracking decision volume, rule hit rates, or latency trends; organizations that want that visibility build it themselves, typically integrating KIE Server or Kogito logs with an OpenShift-native observability stack (Prometheus, Grafana, or similar).

Business Central's project spaces provide a basic organizational structure for grouping related rule assets, which is a step ahead of flat file-based competitors, but it is not the same as configurable tags, folders, and retention policies as first-class platform features.

Strengths:

• Business Central's execution tracing gives developers real visibility into rule firing sequences during authoring and debugging.
• Project-space organization within Business Central provides a basic structure for grouping related rule and process assets.
• OpenShift-native observability tooling (Prometheus/Grafana) integrates well with Kogito-deployed services, for teams that build that layer.

Drawbacks:

• No built-in analytics dashboard or business-readable reporting — decision volume and performance analytics require a custom observability build.
• Execution tracing is a developer tool inside Business Central, not accessible to compliance or business users investigating a specific decision.
• No native decision reason-code output, no configurable log retention policy, and no real-time monitoring as platform features.

Pricing

Red Hat does not publish pricing for Decision Manager — access is subscription-based via Red Hat sales, scoped to cores/nodes and support tier, with a free development-only subscription for evaluation and non-production use. Because the product is discontinued, every pricing conversation today effectively includes an implicit migration clock: customers are paying an enterprise subscription for a platform whose vendor has already committed to no further releases.

Total Cost of Ownership Comparison

What the Numbers Actually Mean

RHDM's fully loaded Year 1 cost — ≥$665K — runs above open-source Drools (≥$588K), despite sharing the same underlying engine and the same core operational costs (middleware, infrastructure, ops, change management). The delta is the Red Hat subscription itself, layered on top of a cost structure that is otherwise nearly identical to running Drools for free — because RHDM does not eliminate any of Drools' fundamental gaps (no governance, DRL-only authoring beyond guided templates, heavy JVM/OpenShift ops). Customers are paying an enterprise premium for commercial support and Business Central, on top of the same engineering-heavy operating model.

The additional line unique to RHDM in this comparison — a forced migration cost of ≥$100K — reflects a fact no other platform in this dataset carries: the vendor has already committed to no further releases. Every RHDM customer is going to pay a migration cost eventually, whether that's toward IBM BAMOE, back to unsupported open-source Drools, or to an entirely different platform. Modeling RHDM's TCO without that line understates the real decision organizations are facing in 2026 — it isn't "should we renew," it's "which migration do we fund, and when."

Nected's Year 1 floor of ≥$40K is 94% lower than RHDM's fully loaded cost, and unlike RHDM, that number represents a platform actively being developed — not a system whose vendor has already exited the roadmap. For organizations facing a mandatory RHDM migration decision regardless of budget, the practical question shifts from "can we afford to stay" to "which destination gives us the best economics and the least repeat-migration risk" — and a platform with built-in governance and no forced future migration answers both.

Alternatives

Head-to-Head: Red Hat Decision Manager vs. Nected vs. Drools vs. IBM ODM

Looking for the full list of Red Hat Decision Manager alternatives? See our deep-dive → Top 10 Red Hat Decision Manager Alternatives for 2026

Why Teams Compare Nected Against Red Hat Decision Manager

When teams evaluate Red Hat Decision Manager today — or reach the point of planning their exit — six reasons consistently drive the comparison with Nected:

1. The product's roadmap has already ended. RHDM's last release was V7.13 in 2022; the platform has been handed to IBM as BAMOE. Nected ships new capabilities continuously — AI copilot, MCP integration, auto-scaling. Choosing Nected means building on a platform with a future, not managing a migration off one without one.

2. Business Central promises self-service but consistently delivers developer dependency. Reviewers describe Business Central as complex enough that rule changes route through developers regardless of the guided UI. Nected's visual editor is built for ops and product teams from the ground up — no JBoss interface, no DRL underneath.

3. Red Hat/OpenShift lock-in versus API-first flexibility. RHDM is built for the Red Hat ecosystem — OpenShift, JBoss EAP, Red Hat middleware. Nected is API-first and integrates from any language, any cloud, any service, with no platform boundary to design around.

4. Zero governance out of the box, in a product that will get no more patches. RHDM ships no native maker-checker approval flow and no compliance-ready audit log — and any gap discovered going forward won't be fixed by Red Hat. Nected ships maker-checker approval, RBAC, and audit trails on all plans, actively maintained.

5. Opaque, subscription-gated pricing for a discontinued product. RHDM requires a Red Hat sales conversation and a subscription commitment before evaluation — for a product whose vendor has already moved on. Nected has transparent, self-serve pricing with a first rule live in hours.

6. A single migration, not a repeat one. Every RHDM customer faces a migration eventually — to IBM BAMOE, to open-source Drools, or elsewhere. Migrating once, to an independently developed and actively shipping platform, avoids paying that migration cost twice.

Nected is used by 500+ teams including PUMA, Bajaj Auto, and TATA 1mg. It is API-first, which means it integrates into existing backends without rearchitecting data layers or committing to a single vendor's infrastructure stack. Because rule changes go through a visual builder with a draft/publish lifecycle and maker-checker approval flows, business and compliance teams gain real ownership over policy — on a platform with an active roadmap, not one in transition.

Final Verdict

Red Hat Decision Manager was, for years, a credible commercial layer on top of a proven engine — Business Central's guided authoring, Kogito's cloud-native packaging, and Red Hat's enterprise support gave Drools users a more governed, more supportable path than the open-source project alone. That calculus has changed. With V7.13 as the final release and the product handed to IBM as BAMOE, the question for any organization touching RHDM today is no longer "is this a good BRMS" — it's "what does our migration look like, and when do we start planning it."

For teams still running RHDM in production, the near-term priority is understanding the IBM BAMOE transition path and comparing it honestly against alternatives — not assuming continuity that the vendor has already ruled out. For any organization considering a new RHDM deployment in 2026, the discontinuation alone is close to disqualifying, independent of how the platform's underlying Drools engine performs.