Official launch coming soon
Credit decisioning platform: data, policy, and execution
Kalliox is the credit decisioning infrastructure for banks, specialty lenders, and digital finance. A no-code platform built so the business team can focus solely on the product: the team itself designs and publishes products, journeys, and decision strategies without writing code, and every application runs through a single auditable flow.
- Reasons recorded with every decision
- Queryable audit trail
- Per-tenant isolation
- Portuguese, English, and Spanish
What Kalliox is
Credit decisioning infrastructure, not a tool
Kalliox is the credit decisioning platform for banks, specialty lenders, and digital finance companies: the point of convergence between credit data, policy, and execution. Each institution operates in its own tenant: origination, decisioning, work queues, and review in a single portal.
- Tier-1 banks
Governance and auditability
Risk policies, reasons and trace recorded with every decision, and a queryable audit trail: who did what, when, and to what.
- Specialty lenders
No-code agility
No-code studios where the business team designs and publishes niche credit products, such as auto, payroll-deductible, and agricultural loans, together with each product’s journeys and decision strategies, without writing code.
- Digital finance
Orchestration in a single flow
Automated decisioning and a human credit desk in the same flow: the journey alternates between automated steps and human tasks, and whatever needs review becomes a Case in a work queue.
Modules
No-code credit decisioning platform: how the modules connect
Business capabilities over a decision core, with governance and infrastructure as the foundation. The business team designs and publishes products, journeys, decision strategies, and policies in the no-code studios, without writing code and without depending on IT.
Business capabilities
- Origination
- Decision Engine
- Risk Policies
- BPMN Orchestration
- Catalog & Products
- Outcome Studio
Data sources
- Bureaus · Serasa / SPC
- Open Finance
- Feature Stores
- Documents · OCR / S3
- Events · Webhooks
Platform core
Data Fabric
- Integrations
- Origination
- Documents
Run-Time · Decision Core
- Decision Engine
- Feature Fabric
- Risk Policies
- Simulation Studio
APIs & Portals
- Connect / gRPC
- Portals (BFF)
- Event Fabric
Application Services
- Process / BPMN
- Catalog
- Tenant & Plans
- Billing
- Document Rules
- Reporting
Interfaces & APIs
- Admin Portal
- Bank Portal
- REST · Connect-RPC
- tRPC (BFF)
- Event Fabric
- SDKs
Platform module architecture
Data sources flow into the core, where the decision point sits; business capabilities build on it, interfaces and APIs come out of it, and everything runs on the security, observability, and infrastructure layers. Platform architecture; some of the connectors and modules will come into operation by the official launch.
What each module does
Business capability
Origination
Applications with product, amount, and term, from individual or business applicants, with a status and a timeline from the moment they are first recorded.
Business capability
Decision Engine
Runs strategies with rules, decision tables and decision trees, scorecards, expressions, and supported PMML models, records reasons and trace for every decision, and refuses what it cannot execute.
Business capability
Risk Policies
Risk policy groups that decide whether to approve, decline, or refer the application for manual review, with the reasons for each verdict recorded.
Business capability
BPMN Orchestration
The Workflow Engine runs the journeys designed in Workflow Studio, with automated steps and human tasks; whatever needs review becomes a Case, which the analyst picks up in My Queue.
Business capability
Catalog & Products
In Product Studio, the business team designs and publishes credit products, and the business object model (BOM) describes the data that flows through the credit workflow.
Business capability
Outcome Studio
An analytical twin to measure and simulate the outcomes of decisions.
Core
Data Fabric
Integrations configured per tenant and the documents of each application: the layer through which data from bureaus, Open Finance, and documents reaches the platform.
Foundation
Identity & Access
Corporate authentication via OpenID Connect on Keycloak, with token rotation and protected cookies, and access according to each user’s role.
Foundation
Governance & LGPD
Designed to support the security requirements of CMN Resolution 4,893 and the LGPD, with per-tenant isolation and actions recorded in an audit trail.
Foundation
Observability & Audit
A queryable audit trail of who did what, when, and to what, from which each application’s timeline is read.
Foundation
Tenant & Billing
Each institution is an isolated tenant, with provisioning subject to approval, status control, and per-tenant usage metering.
Foundation
Infrastructure
Go services that communicate over Connect-RPC, running on AWS (EKS), PostgreSQL, NATS, and Redis.
How it works
Credit orchestration: the path of an application
From intake to the final record, the application follows a single flow. The Workflow Engine runs the credit workflow, the Decision Engine decides, and the credit desk reviews whatever needs human eyes. Every step is recorded in the audit trail.
- 01
Intake
The application enters the credit workflow with its product, amount, term, and the applicant’s data, whether the applicant is an individual or a business, and gets a status and a timeline from the moment it is first recorded.
- 02
Orchestration
The Workflow Engine runs the journey designed in Workflow Studio, with automated steps and human tasks, in the order the institution has defined.
- 03
Decision
The Decision Engine runs the strategy, with rules, decision tables and decision trees, scorecards, and supported PMML models. The risk policy returns the verdict: approve, decline, or refer for manual review, with the reasons recorded.
- 04
Manual review
Whatever needs human eyes becomes a Case in a work queue. The analyst picks up the Case, reviews the application, and records the verdict in the audit trail.
- 05
Record
The audit trail keeps a record of the application’s path and builds its timeline.
Who it’s for
Credit platform for financial institutions
One decision core, built for institutions with different requirements. Fintech speed on bank discipline.
Tier-1 banks
Governance and auditability
For banks where every credit decision has to be explained to auditors and regulators: Kalliox records who did what and when, and keeps the reasons and trace of every automated decision.
- A queryable audit trail, with each application’s timeline read from that trail
- Risk policies, with the reasons for each decision recorded
- Corporate authentication via OpenID Connect, with token rotation and protected cookies
Specialty lenders
No-code agility for niche products
Auto, payroll-deductible, and agricultural loans each have their own rules, documents, and journeys. In the no-code studios, the business team designs and publishes each product, its journey, and its decision strategy, without writing code and without depending on IT.
- Product Studio to design and publish credit products
- Decision Studio with rules, tables, trees, scorecards, and supported PMML models
- Document rules per product and per stage
Digital finance
Automated underwriting, with the credit desk in the same flow
Digital operations call for automated decisions where policy allows and human review where policy requires it, without switching systems midway through an application.
- Automated decisioning and a human credit desk in the same flow
- Journeys with automated steps and human tasks, designed in Workflow Studio
- Portals in Portuguese, English, and Spanish
Governance and security
Explainable, auditable credit decisions
Rigid governance and dynamic decisioning, on the same platform. Explainability is not a separate report: it is a property of the decision. And when data is unreadable or a state is unexpected, access is refused and recorded, never granted by default.
Queryable audit trail
Actions are recorded in a queryable audit trail: who did what, when, and to what. Each decision keeps the reasons and trace behind it, and the application’s timeline is read from this trail.
Designed for the security requirements of CMN Res. 4,893 and the LGPD
The platform was built to support the cybersecurity requirements of Brazil’s CMN Resolution 4,893/2021 and General Data Protection Law (LGPD). This is not a certification: each institution’s compliance is still assessed by the institution itself and its auditors.
Manual review recorded in the trail
When the policy refers an application for manual review, the analyst picks up the Case and their verdict goes into the audit trail.
Per-tenant isolation and access control
Logical isolation per tenant across identity, data, and configuration. Access via OpenID Connect, with token rotation and protected cookies. A suspended tenant loses access to the portals.
Official launch coming soon
Get to know Kalliox before the official launch
Kalliox is in pre-launch. The official launch is coming soon; the date has not yet been announced. The core orchestration, decisioning, and audit trail capabilities can already be seen in a demo. If your institution wants to see the platform before launch, request a demo or express interest in early access.
Talk to the Kalliox teamFrequently asked questions
What is a credit decisioning platform?
It is the system in which a financial institution defines its credit policies, executes the decision on each application, and records how that decision was made. In Kalliox, the decision engine, journey orchestration, human review, and the audit trail sit on a single platform, and each decision keeps the reasons and trace behind it. It is the point of convergence between credit data, policy, and execution.
What is the difference between a credit decision engine and credit orchestration?
The credit decision engine executes the strategy (rules, decision tables and decision trees, scorecards, and models) and returns a verdict. Credit orchestration takes the application through the entire journey: the order of the steps, the human tasks, and the handoff to the credit desk when the policy calls for manual review. In Kalliox, the Decision Engine and the Workflow Engine work in the same flow.
Can the risk team change credit policy without depending on IT?
For designing and publishing, yes. Decision strategies, risk policies, products, and journeys are designed and published by the business team in the no-code studios, without writing code. Connecting the platform to the institution’s systems, and to each new data source, remains technical work.
How does isolation between institutions (tenants) work?
One instance serves multiple institutions, and each one is a tenant, with logical isolation across identity, data, and configuration. Access uses OpenID Connect, with token rotation and protected cookies. Tenant status is an admission criterion: a suspended tenant loses access to the portals.
Was Kalliox designed for CMN Resolution 4,893 and the LGPD?
The platform was designed to support the cybersecurity requirements of Brazil’s CMN Resolution 4,893/2021 and General Data Protection Law (LGPD), with logical isolation per tenant, authentication via OpenID Connect, and actions recorded in an audit trail. This is not a certification: each institution’s compliance is still assessed by the institution itself and its auditors.
When is the official launch?
The official launch of Kalliox is coming soon; the date has not yet been announced. The platform is in pre-launch, and the core orchestration, decisioning, and audit trail capabilities can already be seen in a demo. If your institution wants to get to know Kalliox before launch, use the form on this page to request a demo, express interest in early access, or propose a partnership, or write to contato@kalliox.com.
Contact
Talk to the Kalliox team
Request a demo, express interest in early access, or propose a partnership. Tell us what your institution wants to solve in credit decisioning; the team will reply to the email address you provide.