Every module runs on the same data layer as the EBA Filler. Map your data once, then use it for stress testing, climate, capital and internal assessments, each with the same lineage and approvals.
Each hand-off is a file whose hash is on record at both ends, so a template value can be traced back to the scenario it came from. Scenario Creator and Model Studio read the same European macro library. The modules below are in development and will run on the same data layer, lineage and approvals.
Project the impact of supervisory and internal scenarios on your balance sheet, P&L and capital, on the same data that fills your EBA template.
Quantify transition and physical risk across your portfolio, and translate it into the credit and capital metrics supervisors ask about.
River flood depth for 1-in-10 to 1-in-500-year floods across Europe from the JRC maps the EBA refers to, postcode lookups for 31 countries, and the EBA 2027 flood class worked out on your own computer. Feeding it into Model Studio and Risk Reporting is planned.
Watch a climate stress test end to end, 12:45 →Forecast capital ratios and buffer headroom over the planning horizon, and see what every management action does to them.
Assemble your internal capital and liquidity assessments from figures that already reconcile, with ownership and sign-off tracked section by section.
The models behind every module. Agents work from the data your institution actually has; named people open every gate.
The macro scenarios every module starts from, built from public data and approved four-eyes before anyone uses them.
The credit-risk results of a stress test: losses, the CET1 walk and the commentary, signed off four-eyes with every figure traced to its file.
The rules you approve in the Filler feed every other module.
From source row to report figure, across modules.
Roles, approvals and versioning that work the same everywhere.
On-premise, private cloud or EU-hosted. Your choice.