The hyper-efficient

Business Rules Engine

Hyperon is a rules engine for developers who appreciate the performance, flexibility in modeling and robust decision tables
Watch video 2:28
Works with any tech stack
The hyper-efficient

Business Rules Engine

Hyperon is a rules engine for developers who appreciate the performance, flexibility in modeling and robust decision tables
Why is Hyperon better

than other rules engines?

In June 2019, we conducted a series of tests to determine Hyperon and Drools performance. Hyperon proved from 62 to 119 times faster than the other rules engine.
Works with any tech stack
Hyperon is technology agnostic. It has a flexible REST interface, so you can add new input data without rebuilding your software.
Ruby on Rails
Native JVM library
You can embed the Hyperon Runtime library directly into your application if your app is built using JVM language.
Not another workflow
Not every use case suits workflow engines. You shouldn't be forced to define a process, just to get a decision.
Web browser based
Hyperon Studio is a web application, no more troubles with installing applications on users' desktops.
Cloud or on-premise
Self-host on Oracle, MsSQL, PostgreSQL, H2, or go cloud with AWS, Azure, Docker, Google Cloud, and others.
Free proof of concept
A new tool requires you to spend your time to analyze and assess whether it suits your business needs. We want to make this process as smooth as it can be for you. That's why we will do some heavy-lifting. You provide your set of rules, and we prepare a tailor-made proof of concept and demo for free.
Contact us
Hyperon Expert
Tech Lead
Powerful decision tables
Add new input levels, define rules of matching decision, and stack decision table one on another. Parameters (decision tables) are designed to work with millions of rows.
Define parameter's (decision table) behavior. 
Each row describes one matrix column and its properties.
Condition columns (IN) may be bound to any model property or created dynamically by function. Use different matchers if the standard one is not enough.
Define OUT columns that hold result values for matched conditions.
Parameter matrix. Fill in the table according to your logic.
Define each table cell as a literal value or cascade reference to function or cascade reference to another parameter.
Learn more
Flexibility with functions
It's impossible to model every business rule as a decision table. In such a case, you could benefit from a function. Write it in a standard programming language like Rhino (JavaScript) or Groovy (JVM), not DSL.
Use provided API to get access to all Hyperon parameters, functions, and other elements. Make use of the standard library to operate on dates, numbers, etc.
Use simple autocompletion for parameters' codes, functions' codes, and context paths.
Write a function where a decision table is not enough. Use the full power of programming languages like Groovy or Rhino.
Define function arguments if necessary.
Use the instant tester to verify code snippets.
Learn more
Technical specs
Focus on the challenges
Leave configuration work to the business people
Hyperon empowers business users to maintain existing decision tables in an error-proof environment
Domain organized configuration
The configuration is organized in a clear and easy to understand tree of business objects with attributes. Each attribute represents a decision to be made.
Users can make ad-hoc tests or prepare the whole set of regression tests to run before publishing a new configuration.
Each change is logged. You can go back and see previous versions of configuration and track changes and their authors.
Configuration migration
Hyperon provides tools to quickly and efficiently migrate configuration between environments. It can be done manually but also with CI tools.
Success stories
Check Hyperon implementations
Wygodny interfejs użytkownika
The interface that is so easy to use
Design your domain and keep all the configurable elements (business rules) in one place. The tree hierarchy enables you to organize it, so it is easy to maintain and modify. Connect your applications and systems with Hyperon. Thanks to the user interface, you can publish changes without the need for a new version release.
Decision table (parameter)
A parameter reminds an Excel spreadsheet. The columns on the left (input data) present conditions, and the ones on the right (output data) show results (decision outcomes). A Hyperon parameter is more powerful than an Excel table, because it includes the ranges, and you filter the matrix according to the most accurate match.
Granting discounts is a good example of the business rules configuration. The business user can autonomously decide when a system grants discounts or enables an end-user to use a promo code. The discounts can be defined, for example, as a constant or percent value.
Publish modifications
The changes made by a user are not visible for others, till she or he publishes a session. Hyperon keeps a detailed history of modifications. You can check who is responsible for a particular change and revert it to the previous state if necessary. Hyperon enables you to keep a business configuration in a few states. For example, you updated the quotation algorithm on Wednesday, but you want all the open sales processes that started before, to operate on the previous rates. It's possible with Hyperon.
Business rules influence the financial outcome. Every error might generate losses. That's why it's crucial to test values before publishing. You can test single values, or create test-cases, and regression tests in Hyperon.

Business Rules Engines

Definitions and explanations for rookies
Show the content

What are Business Rules?

Business Rules are instructions on how the system (software or service) should behave given the exact conditions. The typical business rules structure looks like this:

  • when [condition],
  • then [result].

Business Rules usually refer to statements that concern a business model, pricing, offer, product/service attributes, or communication with a customer.  

Business Rules examples

The following statements are Business Rules:

  • In banking: when a customer is new, then offer a $200 bonus. 
  • In retail: when a customer buys three items of the same product, then make the third one free. 
  • In insurance: when a customer has a history of claims, then raise the price by 10%. 

Who uses Business Rules?

As the name suggests, business people create business rules. 

The companies use business rules among others to: 

  • gain new clients (special offers for new customers), 
  • upsell (quantity discounts),
  • segment clients (higher prices for more costly clients)

When to use Business Rules?

The when-then statement is generic, and it can cover a lot. Consider the following sentence:

  • When a user clicks on the buy button, then she or he goes to the checkout card. 

Is it a Business Rule or not? It might be, but it's standard e-commerce button behavior, and the business people usually don't focus on it. Instead, they concentrate on the Rules that are not obvious and need a business decision (such as the amount of the discount). 

The examples in the previous subchapter are simple on purpose. They highlight the main idea. In real business reality, business rules are far more complicated. The more complicated system or service, the more sophisticated the rules are. 

Business Rules should help you simplify and organize the business process. 

What is a Business Rules Engine?

A Business Rules Engine is a software that helps you manage and execute Business Rules. The main advantage of the engine is the separation of the business logic from the hard code. It leads to:

  • easier maintenance (business users might update the rules by themselves after the initial configuration) 
  • and faster deployment (sometimes there is no need for releasing the new version of the system).

The users might model the rules as (depending on an engine):

  • decision tables,
  • decision trees,
  • functions (code),
  • DSL (Domain Specific Language),
  • workflow (with visual graphs modeling). 

Usually, Business Rules Engines deliver user interface in the form of:

  • web browser app,
  • desktop native app,
  • or through Excel.

Business Rules Engine might come as:

  • a library for the specific language,
  • or an autonomous component that connects by API.

You can install Business Rules Engines:

  • on-premise,
  • or in the cloud.

When to use a Business Rules Engine?

You should decide on a Business Rules Engine if at least one of the statements above is valid:

  • you change the Business Rules frequently (a few times a month),
  • you want to empower the business users to update the rules autonomously,
  • the Business Rules are multilayered, and it's challenging to test them (most Business Rules Engines simplifies tests).

On the other hand, implementing the rules engine might occur an unnecessary effort, if:

  • your business logic is very seldomly modified, 
  • or there is no will for engaging the business people as users, 
  • or your Business Rules are plain simple (for instance, the only variable is a one-size-fits-all price).

Which Business Rules Engine is the best fit for me?

It depends on several factors:

1) Who is going to use the Engine?

Are they business users, technical users, or both? Do they need the user interface? Do they prefer Excel? Hyperon provides the GUI and supports working in Excel.

2) Do you need to install it on every user's computer?

Some solutions require installing a desktop native application on every user's computer. Others are browser-based (Hyperon, for instance), and it makes it easier to access the tool. 

3) Cloud or on-premise?

Most Business Rules Engines (including Hyperon) works both ways.

4) How complicated are your Business Rules?

a) Simple (several when-then statements, almost none exceptions, no scoring needed)

Look for tools supporting:

  • natural language, 
  • decision trees, 
  • and workflows.

b) Medium (hundreds when-then statements, some exceptions, simple scoring)

Look for tools supporting:

  • natural language, 
  • decision trees, 
  • workflows,
  • decision tables.

c) Advanced (thousands or more when-then statements, lots of exceptions, advanced scoring)

Look for tools supporting:

  • highly customizable decision tables,
  • functions as a flexible addition to modeling.

Hyperon is the best fit for advanced Business Rules. Decision trees or natural language processors with thousands of rules lose clarity. Decision tables are more straightforward to comprehend. Moreover, functions add unlimited possibilities to modeling. 

How does Hyperon work?