Decision
Decision rules in DMN tables, with published versions and outcome traceability.
Decision engine
Data pipeline
Layered integration
Gather the data
Pass the data in the call or configure the pipeline's sources.
Select the policy
The decision uses the published version of the DMN table.
Run the rules
The same input and the same policy determine the response.
See the reason
Each execution stores input, output, rule, and version. Anything that needs human review is flagged.
What this composition organizes.
Decision engine
Versioned DMN tables, published without changing the consuming application.
Data pipeline
Declared external sources, queried in parallel with a per-source timeout.
Layered integration
Use the engine alone with your own data, or combine it with the pipeline.
The pieces behind the experience.
Decision Engine
Business rules in DMN tables, versioned and changed without a deploy
Production↗DecisionDecision Platform
The pipeline that fetches the data, applies the policy and returns the verdict
Beta↗DataBureaus
Credit bureau query with caching that prevents paying twice for the same CPF
Beta↗IdentityIAM
Identity, organizations and permissions for the entire building block catalog
Production↗PlatformAudit Trail
Who did what, when, and what changed — across the platform, by organization
Beta↗Accountability and context.
Decision Engine and Decision Platform are at different stages in the catalog. The first is marked as Production and the second as Beta. The product page and the documentation each have their own scope.
See the full source↗