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
rules outside the code
Decision engine
Your credit policy as a DMN decision table — the OMG's open standard. Versioned, published without a deploy, exportable any time.
02
done when the slowest source is
Data pipeline
Bureau, API, file and queue fetched at the same time, with a timeout per source and your own credentials.
Around the three
What comes with every plan
SimulatorMove a threshold and see which rule decides, before you publish
Versions and audit trailInput, output, rule, timing and the exact version of every decision
AI, no black boxAI writes, reads and explains — and doesn't decide on credit
Limits and quotasA quota enforced before execution and a test key that never bills
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 have | Start with | What changes on your side |
|---|---|---|
| Rules in code and five integrations to maintain | pipeline + engine | one call instead of five |
The data at hand and the rule in an if | the engine | one line instead of the if |