Banking & fintech
The analyst opens the file, pulls the balance sheet, checks the credit bureau and writes the report by hand, while last month's queue of money-laundering alerts is still open. Inferana puts open models on all of that, inside your perimeter.
What each regulation in your sector requires, and which part of that the deployment solves.
Digital operational resilience and ICT third-party risk management.
Auditable EU provider, dedicated or on-premise deployment and OpenAI-compatible API.
Minimization, confidentiality and control over transfers of personal data.
Zero logs by design: prompts and responses are never stored or used to train models.
Traceability, data governance and human oversight for high-risk systems such as creditworthiness assessment (Annex III).
Open models with published model cards and licenses, with access controls and audit.
Payment services and open banking with security guarantees.
Isolated environments and data that never leaves your perimeter.
The same ones you already use, specific to your sector.
Nobody signed anything off, but the backlog does not wait and people solve it with whatever tab they have open. What follows is always the same:
We banned it, but I know they still use it from their phones.
ICT risk leadEvery new tool opens an international transfer I have to justify.
Data protection officerI cannot sign off what I cannot trace.
Internal auditLast month's alerts are still unreviewed and this month's are already coming in.
Anti-money launderingEvery file is hours of reading PDFs before I can give an opinion.
Credit riskComplaints pile up and the statutory deadline does not move.
Customer careThe core is in Cobol and two people understand it, both retiring.
Core banking systemsWherever you decide: on European infrastructure we manage, or in your own data centre, on-premise. In both cases prompts and responses are never stored or used to train models.
The service and deployment documentation: which functions it supports, where they run and with which dependencies. Filing it in your register of contractual arrangements and keeping it current remains the bank's job.
Yes, and it is written into the contract for the bank and for the competent authority. With an on-premise deployment you also audit your own infrastructure with the procedures you already have.
The models are open and the API is OpenAI-compatible, so your exit plan does not depend on us: you can take the weights with you and point the code elsewhere by changing a key. Your data and your indexes are exportable.
Classifying the system and taking on the high-risk obligations is the bank's responsibility. We provide open models with a published model card and license, access controls and a record of every interaction, which is what you need to document traceability and human oversight.
Yes, with the same key. There the query does go out to the model provider, so customer data is handled with the open models inside your perimeter. It is configured per team.
No. The API is OpenAI-compatible: swap the key and the endpoint and your code stays as it is.
Access control per user and per team, with a record of every query. Risk and internal audit can review who asked what and when, and export it.
In the demo we go through your case: which models you need, where they run and what it takes to meet the regulation that applies to you.
We reply within one business day.
