Why FlexRule?

We provide a powerful Business Rule Engine (BRE) for .Net based software you develop. Our rule and logic engine supports the Procedural, Inference and Flow rules that they can be externalized from your application.

FlexRule also as a rule engine provides a framework to be extended on your own, no matter if we do not support a specific command or functionality you want, you can extend our rule engine easily.

FlexRule also is an Event Driven Rule Engine that provides infrastructure so you can manage and control the rule processing much more effective than normal rule engines. This means you can create and raise event to you application right inside from your rules.

Also, as an inference engine, we provide RETE based Inference Engine Engine integrated into our framework with two high level languages (XML and S-Expression). Also API mode of our inference engine is accessible for developers to communicate to RETE engine directly using Net programming languages such as C#.

Our framework fully implemented with C# .Net and this allows you to use it very easily in your applications, no matters of your application type; Windows form, Services, WCF, ASP.Net...

Latest News

FlexRule is the Business Rule Engine that helps you to bring decision making into your application.

When do you use a rules engine?

Not all applications should use a rules engine. If your business logic code includes a bunch of if-else statements, you should consider using one. Maintaining complex Boolean logic can be a difficult task, and a rules engine can help you organize this logic. Changes are significantly less likely to introduce errors when you can express the logic using a declarative approach instead of an imperative programming language.

You should also consider a rules engine if code changes can cause major financial losses . Many organizations have strict rules about deploying compiled code in their hosting environments. For instance, if you need to modify the logic in a Java class, usually a long, tedious process must occur before the change makes it to the production environment: The application code must be recompiled. The code is dropped in a test staging environment. The code is inspected by data-quality auditors. The change is approved by the hosting environment architects. The change is scheduled for deployment. Even a simple change to one line of code can cost an organization thousands of dollars. If you need to follow such strict rules and find yourself making frequent changes to your business logic code, then it would make sense to consider a rules engine.