Credit decision engine your risk team runs

For lenders and insurers, the risk team changes rules and decision tables, then tests them on real applications before release. Your system calls one endpoint per decision.

Decisimo Sphere
Visual decision flow
builder
Custom
ML models
Rule Engine
Multiple Data
Connections

From written policy to a decision your system receives

The risk team owns the policy from writing through release. The lender's system calls one endpoint for each decision.

  1. Write the policy

    Write rule sets, decision tables, scorecards and functions in the portal, or upload a PDF or Excel file for the assistant to propose them.

  2. Test the policy

    Test parts with chosen inputs, then run current and proposed policies on the same applications to see which decisions change.

  3. Release the policy

    Release it with sign-off by roles when the endpoint requires one; the lender's system keeps the same URL.

  4. Receive the decision

    Your system sends a JSON document and receives the decision and reason in the same call; data sources run in parallel.

  5. Keep the record

    Input and output can be written to the lender's Postgres; decisions waiting for documents or a person are worked as cases.

The assistant proposes. Your team decides.

Upload the policy as PDF or Excel, or paste it. The assistant proposes rules, tables and scorecards. The team sees each proposal as a difference and applies it; nothing runs until it is released.

Ask a question
New Rule Added If credit_score > 750
NEW
Updated Threshold DTI: 0.45 → 0.35
UPDATE
Legacy Flow Removed Manual review bypass
REMOVE

Simple, usage-based pricing

From € 500 per month with 50,000 decisions included, then € 0.01 per additional decision. Unlimited rules, models and users. Free trial, no credit card needed.

Questions we get asked

What is a credit decision engine?

A credit decision engine is software that runs a lender's credit policy on each application and returns a decision. Decisimo lets the risk team write, test and release the policy itself.

Can the risk team change rules without developers?

The risk team edits rule sets and decision tables in the portal and tests chosen inputs before release. Each save creates a revision.

Can a policy change be tested before it goes live?

The current and proposed policies run on the same applications, and decisions that would change are listed. With past decisions kept in the lender's database, a change can be run over them.

Can it turn an existing credit policy document into rules?

Upload a credit policy as PDF or Excel, or paste it. The assistant proposes rules, tables and scorecards for the team to review.

What happens when the policy cannot decide an application?

The policy writes “refer” for an application it should not decide. The lender's system sends it to a case type's endpoint, and an underwriter works it from a role's inbox. The decision is posted back to the lender.

How is Decisimo priced?

Pricing is from EUR 500 a month with 50,000 decisions included, then EUR 0.01 per additional decision. Plans include unlimited rules, flows, models and users.

Policy decisions can be explained

Reasons stay with decisions

Each row writes a reason; on request, the response includes the steps that ran and rules that fired. Input and output can be kept in the lender's database.

Policy changes have a record

Every save creates a revision. Two releases can be compared step by step, and a release can require sign-off.

Start with the policy you have

Start by writing a policy in the portal or uploading it as PDF or Excel.