NVIDIA describes banking uses of open models in Europe. For luxury houses, these cases raise a precise question: which dependencies do you really want to control?
The model, the data and the hosting are not a single choice. The cases presented by NVIDIA on 21 October make it possible to examine them separately. According to the provider, Revolut runs PRAGMA in production for an initial population of 80 million customers, with an architecture designed for three times that capacity. This last indication is a sizing target, not a population already served.
bunq’s Finn assistant, for its part, runs on open-weight models on Nebius. NVIDIA reports quality comparable to that of closed models for a cost per answer equal to 60% of theirs. The release does not provide an independent protocol that would allow this comparison to be generalised.
Control is verified component by component
For a house that wishes to use its archives or product documentation, the interest of these examples lies in the decomposition of the system. Having a model’s weights is not enough to establish who can consult the documents, restore a service or change provider. The sovereignty claimed must be describable through concrete operations.
A management team can thus ask where the data is processed, which teams handle maintenance and what a change of hosting would force it to rebuild. These are examination criteria proposed by Luxsure, not certified properties of these deployments.
A cost per answer remains a partial indicator
The banking comparisons provide leads, without putting a figure on the cost of a system adapted to a house. Document integration, business controls and keeping the service running must enter the calculation. An open model can widen technical choices; its value then depends on the organisation’s ability to exercise those choices durably.
Also on Luxsure: Team Bots: deciding what a team can pool · Claude Sonnet 5.5: cost also depends on the work requested · Mistral in Munich: bringing research closer to industrial know-how · GPT-6.1 Sol: what the price of reused context changes
Cette publication est également disponible en :
