InRule vs. MLReef

With InRule, we are expecting to be able to move business logic out of the developer domain and back into the business domain. Business logic is currently captured in UI (data validation) and middleware layers. These are areas in any application where leveraging InRule's capabilities allow for changes in business logic to be made with little or no IT involvement.

Works well if you have to involve different roles in different organizations in a project. Less suited when you have a complex system of custom developed tools

• It is easy to tweak business rule parameters.
• Create new logic with low barriers.

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Helps us to take on more client projects
• Can be used by data analysts as well as casual users

• Needs more debugging capabilities.

• Out of the box support for major cloud vendors

InRule's Support Portal provides a "one stop shop" for submitting support questions, accessing training information, managing licenses, and getting updates on InRule's roadmap.

InRule offers a more organized software design, a well-structured framework in design, and is easier for new users to start contributing given documentation. Drools is spreadsheet-based and lacking the capability to do really advanced pseudo-programming.

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• It is always reliable and efficient.
• Has won customers over.

• We can handle 4 to 6 times more projects at the same time with our team
• We stay engaged with our customers well beyond the project duration