Private AI for a small financial firm: start with one workflow
For a thirty-person financial firm, the sensible first AI deployment is one internal workflow that answers DORA's two questions on day one: who is responsible, and where the data is processed.
A firm of thirty people has a short list of realistic AI work: internal document search, questions about its own policies, drafts of client communications, contract analysis, reporting, research and administrative automation. Private AI is for the part of that list where the data is sensitive and the dependency is documented.
What DORA puts on the financial entity
DORA does not forbid cloud AI. Article 28(1)(a) requires that financial entities using ICT services “shall, at all times, remain fully responsible for compliance with, and the discharge of, all obligations under this Regulation and applicable financial services law”.
Article 30(2)(b) then requires the contract to name “the locations, namely the regions or countries, where the contracted or subcontracted functions and ICT services are to be provided and where data is to be processed, including the storage location”, plus advance notice if the provider intends to change them.
Article 28(1)(b) makes the effort proportionate to “the nature, scale, complexity and importance of ICT-related dependencies”. A small firm is expected to know what it depends on, not to run a large institution's programme.
Where a local system helps, and where it does not
For workloads that stay internal, a local system lets staff work with the firm's own material without sending each document to an external inference endpoint. The register row is short, and the location does not move with a console setting.
Where a rented unit supports a critical or important function, DORA Article 28(8) requires an exit strategy. Bastion supplies the plan, and the entity tests it and owns it.
A local system does not make the firm compliant: under Article 28(1)(a) the responsibility does not transfer, to a cloud provider or to an appliance supplier.
The first workflow: a policy and procedure assistant
Start with an internal policy and procedure assistant, which reads approved internal documents and answers staff questions about them.
- The documents are already internal.
- The answers are checkable against a source.
- Nobody outside the firm is affected by a wrong answer.
- The value is immediate, because the questions are asked every week already.
Then expand deliberately: document summarisation, drafting, internal research, and only later anything that touches a customer outcome. Write the register entry for each workflow before it goes live.
With Bastion
What Bastion changes
Bastion is a private AI system delivered as one sealed box that runs inside your building. One monthly fee covers the hardware, the model, the hardened operating system and support, and nothing your team types leaves the building.
For the DORA register, a Bastion node gives a one-line answer to Article 30(2)(b): the service is provided and the data processed in one box at one address, the customer's own premises or a data centre that the contract names, with no outbound connectivity required.
Criticality, recovery objectives, access control and exit strategy stay with the entity.
Questions this article answers
- Where should a small financial firm start with AI?
- With one internal workflow, usually a policy and procedure assistant that answers staff questions from approved internal documents. The documents are already internal, the answers are checkable against a source, and no customer is affected by a wrong answer.
- Does a local AI system make a financial firm DORA compliant?
- No. Article 28(1)(a) states that the entity remains fully responsible at all times. A local system shortens the register row for the processing location; criticality, recovery objectives, access control and exit strategy stay with the entity.
- How much DORA work does a small firm have to do?
- Article 28(1)(b) makes the effort proportionate to the nature, scale, complexity and importance of the ICT dependencies. A small firm is not expected to run a large institution's programme, but it is expected to know what it depends on.
On the record
- 1
Read next
- DORA and AI: an assistant is an ICT dependency, not an experimentWhat Article 28 puts on the financial entity, what Article 30 requires in the contract, which questions an AI supplier has to answer in writing, and where a local appliance changes the dependency without removing the duty.
- How to evaluate an AI deployment: a checklist for 5 to 100 peopleTen questions about your own work, then four lists to put to any supplier: the technical specification, the data flow, the security architecture and the commercial terms. If a supplier cannot answer them, that is the answer.