Skip to main content
Older Drools 7.x applications typically run on the legacy KIE Server / RHPAM stack with monolithic deployments. The modern path is to move that logic onto the cloud-native Kogito runtime — keeping your existing DMN, DRL, and BPMN assets while gaining faster execution, smaller footprints, and container-native deployment. Aletyx is positioned as a drop-in replacement for aging Drools 7.x, jBPM, RHPAM, and KIE Server deployments, so you can modernize without rewrites, behavior changes, or re-certification. The recommended approach is to:
  • Bring your existing rule and process assets into Aletyx as-is.
  • Validate behavior with natural-language and regression testing.
  • Deploy to cloud-native, multi-environment infrastructure.
See docs.aletyx.ai for migration guidance.

​
Where to go next

Why Update Drools

The security, support, and compliance risks of staying on Drools 7.x.

Drools 7 EOL

What end-of-life means for your deployments and how to plan the move.

Modernize Legacy

How to modernize jBPM, RHPAM, or KIE Server without rewrites.

Kogito

The cloud-native runtime your DMN, DRL, and BPMN assets move onto.

Deployment

Deploy to cloud-native, multi-environment infrastructure.

Performance Gains

The execution and footprint improvements you can expect after modernizing.