Product

One policy. Two layers that carry it to a decision.

The engine stores and runs the rules. The pipeline fetches what's missing before the decision. Both in one account, with the same audit trail.

01

Decision engine

Your credit policy as a DMN decision table — the OMG's open standard. Versioned, published without a deploy, exportable any time.

rules outside the code
02

Data pipeline

Bureau, API, file and queue fetched at the same time, with a timeout per source and your own credentials.

done when the slowest source is
Ways to use it

All of it, or just the part you're missing

Describing the whole machine is intimidating. Nobody needs all of it on day one — and moving up a level later doesn't mean redoing the integration.

You already haveStart withWhat changes on your side
Rules in code and five integrations to maintainpipeline + engineone call instead of five
The data at hand and the rule in an ifthe engineone line instead of the if

Start with the engine. Add the pipeline when it makes sense