Supervised. Every layer of it.
Private banks, retail banks, asset managers and payment providers buy technology inside a perimeter drawn by their supervisor. Every model, every voice line, every migration and every campaign has to be explicable to a regulator, an auditor and a client who trusts the institution with more than money. Altuon builds for that perimeter from the first architecture review.

Worum es geht
The regulation is specific and it is enforced. In Switzerland, FINMA's circulars on outsourcing and operational risks decide what may be delegated, to whom, where the data may sit and what the institution must still be able to do itself; banking secrecy is a criminal matter, not a policy preference; and the revised Federal Act on Data Protection adds duties of its own. In the European Union, DORA turns operational resilience and third-party risk into supervised obligations. In Jordan, the central bank supervises technology and outsourcing arrangements as part of prudential oversight. In the United States, the model-risk management guidance issued by the Federal Reserve and the OCC governs how any model that touches a decision is validated and monitored. A vendor that cannot describe its work in those terms is a vendor the institution cannot use.
The cycle is long and the systems are old. A core banking platform, a policy engine or a client-record system was often built before the current regulation existed and before most of the people who run it joined. Replacing it cannot stop the business for a weekend, and the compatibility layer, the dual-running and the rehearsed rollback are not engineering preferences: they are the difference between a migration and an incident report.
The buyer is several people at once. The chief information officer wants an architecture that will still be defensible in ten years. The chief risk officer wants the model register, the evaluation evidence and the exit terms. The head of the client business wants a service line that answers in Swiss German, French and English without ever saying what the bank would not say. Procurement wants the sub-processor list, the residency commitment and the notice period. A proposal that answers one of them and not the others does not get past the second meeting.
Failure is public. A voice agent that resolves a transaction it should not have, a model that treats two clients differently without an explanation, a migration that loses a day of transactions, a campaign that makes a promotion the regulator has not approved — each is a supervisory finding before it is a business problem. The work has to be designed so that the failure mode is a handover to a person, a blocked release or a rollback, never a headline.
Relevante Practices
- Voice AgentsSignatur, wo Altuon führtClient service lines that verify identity to the level the transaction requires, resolve within written policy, record and retain calls the way the supervisor expects, and hand over to a relationship manager with the whole context of the call — in Swiss German, French, English and Arabic.
- Künstliche IntelligenzSignatur, wo Altuon führtModels for client, credit and compliance work with an owner, an evaluation set and a rollback path each, deployed inside the bank's own data plane, with the model register written in the form a validation function and a supervisor will ask for.
- Software EngineeringSignatur, wo Altuon führtCore banking migrations and integration layers carried out one consumer at a time behind a compatibility layer, with reconciliation, rehearsed rollback and the audit trail DORA and FINMA's outsourcing expectations require of a change to a critical system.
- TechnologieberatungSignatur, wo Altuon führtArchitecture and sourcing decisions written as supervisory evidence: the obligation register, the transition states, the exit terms of every outsourcing arrangement, and a programme governed by the case the board approved.
- Market IntelligenceSignatur, wo Altuon führtBoard-cadence intelligence on markets, rivals, supervisory change and technology, evidenced to the line, so a strategic decision can be shown to have been informed — and by what.
- Werbung und WachstumSignatur, wo Altuon führtFinancial promotions approved before publication, audiences excluded by rule, every claim traceable to its approver, and measurement expressed in accounts opened and assets gathered rather than clicks.
- Marke und IdentitätSignatur, wo Altuon führtIdentity systems for institutions and groups that must carry discretion across subsidiaries, booking centres and languages, and survive the renaming a merger or a succession brings.
Regionale Hinweise
- Europa und DACH
- Swiss institutions buy longevity and discretion. The data plane is Swiss unless there is a written reason for it not to be; the sub-processor list is short and read; every outsourcing arrangement is mapped to FINMA's expectations before it is signed, and the exit terms are negotiated as carefully as the price. German, French and Italian are working languages, not translations, and Swiss German is what the client service line hears.
- Naher Osten und Nordafrika
- Banks in Jordan and the Gulf are building at speed under supervisors who expect sovereignty: data held in-country, models that work in Arabic dialects as well as in English, and partners who are present in the room rather than on a call. Central-bank supervision of outsourcing and cloud use shapes the architecture, and a relationship with the institution's leadership is part of the mandate, not a preliminary to it.
- Nordamerika
- US institutions buy velocity under model-risk and privacy regimes that are examined rather than assumed. The model register, the validation evidence and the change control have to satisfy an examiner working from the Federal Reserve and OCC guidance; state privacy laws and the Gramm-Leach-Bliley safeguards decide how client data may be used in service and in marketing. The work has to move quickly and leave a documentary trail that moves with it.
Tätigkeitsregionen
Europa und DACH
Sitz
Turin, Italien
Repräsentatives Engagement
- Künstliche Intelligenz9. September 2026Sovereign AI and Swiss data residency for financial institutionsA Swiss bank can use frontier models without sending a byte of client data abroad. It requires an architecture decision, not a vendor promise, and the revised Data Protection Act is clearer on the point than most vendors are.
- Beschaffung9. September 2026Procurement's questions about AI vendors, answeredWho owns the model weights? Where is the training data? What happens to our prompts? Can we leave? The questions procurement teams ask AI vendors are the right ones. Here are the answers a serious firm should be able to give, and the ones that should end the conversation.
Fragen, die uns gestellt werden
Can our data and models stay in Switzerland, or in our own data centre?
Yes. The data plane is decided per system in the Define phase and recorded in the architecture register: a Swiss region, the European Union, the United States, your own premises or a national cloud. Speech, language and other models run inside that plane; the control plane holds policy, identity and metrics but never client data. For an on-premises deployment the proposal states what the institution provides — hardware, network, identity — and which model options fit that footprint, so the residency commitment is costed rather than assumed.
How do you work within FINMA's outsourcing expectations and DORA?
By treating them as design inputs. The obligation register written in the Discover phase lists every requirement that touches the engagement — the institution's right to audit, the supervisor's access, the location of data, the exit and continuity arrangements, the sub-processor chain — with an owner and the evidence that will show it is met. The agreement carries the audit and access rights the institution needs to include Altuon in its own outsourcing register. For EU entities, DORA's requirements on critical third-party arrangements, incident reporting and resilience testing are mapped in the same register.
What does model validation look like, and who owns the evidence?
Every model has an owner, a documented purpose and risk class, an evaluation set built from the institution's real cases and scored by its experts, a monitored baseline and a rollback version. The evidence is written in the form a validation function works from and an examiner recognises, and it belongs to the institution. Where the institution has its own model-risk framework, the register is mapped to it rather than duplicated beside it.
How is a voice agent kept from acting outside policy with a client?
Policy is enforced outside the language model: the model proposes, a policy engine decides what may be executed and at which verification level, and sensitive transactions require verification before any action. The permitted transactions, limits and verification levels are written with the compliance function and versioned like code. Adversarial testing for social engineering and prompt injection over voice is part of every release gate, and the handover to a person is available from every step with the full context of the call.
Who are your sub-processors, and how do we approve them?
The proposal lists every third party that could touch the institution's data — hosting, telephony, model and speech providers, observability tooling — by name, role and location. Each is approved by the institution before use, changes are notified in advance with the right to object, and for a fully on-premises or Swiss-sovereign deployment the list can be reduced to Altuon itself. The sub-processor agreement carries the audit and access rights the institution needs for its own supervisor.
How do you handle a first engagement with an institution that has never worked with you?
Usually with an executive briefing and a scoped project, priced fixed, with acceptance criteria written before work starts. Non-disclosure agreements are signed before any detail is exchanged; references are provided under those agreements, matched to the institution's business and region. The institution should expect to see the model register, the compliance design and the exit terms before it sees a demonstration.
Bring us the system your supervisor asks about.
Whether it is a service line, a model, a migration or a campaign, the Discover phase begins with your obligations and ends with a register you can put in front of your risk committee. Request a proposal, or book a briefing for the executives who will be asked to sign.

