For banks and lenders
Built to clear model validation.
Banks, lenders and credit unions already have an engine. What's costly is proving to the validator, the auditor and the Central Bank what it decided — and changing a rule without a six-month project.
What the risk team asks for
What validation asks, the decision already keeps
CMN 4,557
Model validation
Independent validation, including of third-party models. The policy is a readable table, and every published version stays in the history with its date.
arts. 9 · 51 · 58
CMN 4,966
Methodology history
Every execution stores the policy version, the inputs and the result. Nothing is overwritten and nothing is recalculated later.
history per instrument
CMN 4,893
Where data is processed
Our own infrastructure in Brazil: the contract is notified afterwards, not authorized beforehand.
arts. 15 · 16
Coexistence
Without switching off what already runs
Start with one portfolio. A DMN policy comes in as is; one that lives in code runs side by side, with the test key, until the outputs match.
- One portfolio first
- One product, one policy. The rest stays on the current engine until the numbers convince you.
- Above 300,000
- Volumes above 300,000 decisions a month are negotiated on the Enterprise plan.