Fitting into the existing set-up, without replacing it.
Three entry levels, three deployment models, a controlled data chain, and an AI that stays local, for ALM and banking risk.
The bank chooses where RIALTO starts.
For the ALM modules, the entry level is chosen per scope and per entity. The same bank can have RIALTO generate the cash flows for one entity (level 1), supply its own cash flows for another (level 2), and pass on its already-computed metrics for a subsidiary (level 3).
A controlled data chain.
An intelligent ETL chain or flat files, as the bank chooses: mapping proposed to the target data model, validated by the business and reused at every reporting date, data quality checks and detection of missing data. Ingestion, calculations and reporting start as soon as extractions are available.
Your data is never sent to any external AI provider.
RIALTO Kernel is designed for the requirements of regulators and prudential bodies: bank data sovereignty, auditability and access control, by default.
Host
AI and calculations deployable on-premise, in the bank's private cloud or hosted by RIALTO. Layer isolation, encryption and control of external exchanges.
Govern
Role-based access, action logging, tracking of versions and assumptions, processing validation and vulnerability monitoring.
Reversibility
The bank's models are retained, analysis routines are configurable by the teams, skills transfer and reversibility terms are defined in the project.
Deterministic calculations
Figures come from the domain engines: the AI orchestrates and explains, it never improvises a figure. Reproducible, versioned, defensible.
100% local AI
The models run in the chosen deployment environment, on-premise, in the bank's private cloud or hosted by RIALTO. No data is sent to any external AI provider. The AI orchestrates the engines without accessing the data.
Access management
Centralised login, administrator and user roles, account creation and deactivation, real-time access monitoring.
Three configurations, constant sovereignty.
AI and calculations deployable on-premise, in the bank's private cloud or hosted by RIALTO.
On-premise
On-premise, in the bank's infrastructure. Data confidentiality, logs and infrastructure under the client's responsibility; support and maintenance provided by RIALTO.
RIALTO hosting
A dedicated environment operated by RIALTO: infrastructure, support, maintenance and logs under RIALTO's responsibility; the bank remains accountable for the confidentiality of its data.
Client cloud hosting
In the bank's cloud. Confidentiality, logs and infrastructure under the client's responsibility; RIALTO support and maintenance.
RACI, macro view: detailed split according to the chosen deployment. R = Responsible · A = Accountable.
| Responsibility | On-premise | RIALTO hosting | Client cloud hosting |
|---|---|---|---|
| Client data confidentiality | Client (R/A) | RIALTO (R) Client (A) | Client (R/A) |
| Auditability (client logs) | Client only (R/A) | RIALTO (R/A) | Client only (R/A) |
| Vendor logs | Client only (R/A) | RIALTO (R/A) | Client only (R/A) |
| Support & maintenance | RIALTO (R) Client (A) | RIALTO (R/A) | RIALTO (R) Client (A) |
| Infrastructure management | Client (R/A) | RIALTO (R/A) | Client (R/A) |
Seven steps, a timeline set at scoping.
Duration depends on scope, volumes and data to integrate. Stabilisation phase included. Support available: data needs, data quality, accounting consistency, group consolidation.
See RIALTO reason over your numbers.
We simulate a full analysis with your data types and the scenario of your choice.