For financial institutions
AI does the work.Your team signs it.It stays on the record.
An external AI operations team for brokerages, wealth managers and compliance functions – with a portal where nothing happens unseen.
Keelra executes no trades and moves no money. Regulatory responsibility stays with you.
§ 01
Six modules.
Each one ends in a record entry. Select a module to see its scope.
Select a module to see its scope
A counterparty picture that does not go stale the day you sign.
Due diligence today is a photograph: expensive, taken once, out of date a week after closing. This module runs the search across the available sources in parallel, confirms material facts in at least two independent ones, and keeps watching for as long as the relationship lasts.
- Sources
- Company and insolvency registers, official publications, financial statements, sanctions and enforcement lists, court records – each in the form its operator makes available – plus the documents the entity handed you
- What it does
- Establishes identity, capital, ownership and authority to represent as at the date of signature, and computes the statutory calendar of corporate events
- Monitoring
- The entity stays under watch after the first pass: sources rechecked on a schedule, a weekly digest of changes, and an alert in the portal the moment something material moves
- Alerts on
- A drift between sources, a contradiction with the documents you were given, and a deadline that passed with no event
- Approval
- Every finding carries a source, a timestamp and a human signature before it counts
The client file is finished before anyone sits down.
The module assembles the documentation, checks that it hangs together, and names what is missing – instead of sending your people into three systems for the same scan.
- Sources
- Forms, identity and corporate documents, correspondence, your CRM
- What it does
- Collects the pack, reads the data off the documents, cross-checks it, and flags gaps and mismatches
- Boundary
- No AML duties are assumed – the obligated-institution role stays with you
- Approval
- The pack goes to your team for sign-off, never straight to the client
A document goes in as a file and comes out as data.
Contracts, statements and correspondence are read, typed and filed. The output is not another inbox to review – it is a record in the system you already use.
- Sources
- Mailboxes, shared drives, contract repositories
- What it does
- Recognises the document type, extracts the fields you actually use, names it and attaches it to the right case
- Output
- Records in your systems, plus the files where they are supposed to sit
- Approval
- Anything written back to a system of record waits for a person
Type
Custody agmt
Party
Redacted
Date
2026-03-12
Amount
41 806,20
Differences found before anyone posts them.
The module matches positions across sources, isolates the differences and explains each one. Not a discrepancy report – a list with an amount and a probable cause.
- Sources
- Custodian statements, ledgers, invoices, internal registers
- What it does
- Matches on hard keys first and on rules after; what it cannot match it reports instead of guessing
- Output
- An exception list with the amount, the side and the probable cause
- Approval
- Nothing is posted or corrected without approval
The same report, on the same day, from the same definitions.
A recurring report stops depending on who assembled it this month. The file comes with a record of what went into it.
- Sources
- The systems already connected to the workspace
- What it does
- Assembles the report to a fixed definition, on a fixed date, and compares it with the previous period
- Output
- The file, the distribution list, and the log of what it was built from
- Approval
- Distribution outside the firm waits for a signature
The reply is written and waiting. A human still sends it.
The module drafts the reply in your tone, attaches what it refers to, and proposes a priority. Nothing goes out without a click.
- Sources
- The client mailbox, your templates and tone of voice, the case history
- What it does
- Identifies the case, drafts the reply, attaches the documents, and sets a priority
- Output
- A draft in your outbox, not in somebody else's
- Approval
- Every send is a human action
- 09:02:14Ingest34 statements pulled from the custodian mailbox
- 09:02:51Classify34 documents typed and matched to clients
- 09:04:07Reconcile3 discrepancies across 1,204 positions
- 09:04:07HoldHeld – waiting for your approval
- 09:11:36ApproveM. Kowalska approved 3 of 3 exceptions
- 09:11:38WriteWritten to the system, report sent to 2 recipients
- Machine
- Waiting for a human
- Human-approved
Illustrative record
§ 02
Nothing sensitive leaves without a name next to it.
Approval is not a setting you can switch off. It is a step in the run: the work stops, a person sees what is proposed and why, and only their decision lets it continue.
Keelra executes no trades and moves no money, and assumes no AML obligations. Regulatory responsibility stays with you.
Entry 09:11:36 · Approval
- Proposed by
- Keelra · reconciliation run
- Item
- 3 exceptions · 41,806.20 PLN variance
- Decided by
- M. Kowalska · Head of Operations
- Decision
- Approved · 09:11:36 CET
The entry is written before the action, not after it. It cannot be edited later.
0
trades executed or payments made by AI
100%
of sensitive steps approved by your team
≥12 mo
of append-only log, exportable to your SIEM
§ 03
Six things your compliance team will ask about anyway.
Answered here so the questionnaire is a formality, not a discovery exercise.
01
Where the data actually sits
The application, the database and the automation engine run in Warsaw, on OVH infrastructure inside the EU. Model calls are a separate matter and we say so: they go to Anthropic in the United States, with identifiers masked before the call and the provider barred from retaining or training on the content. An EU-hosted model endpoint is available by arrangement. We separate the two because your compliance review will.
02
DPA available for signature
A data-processing agreement with SCCs for any non-EEA transfer, a maintained subprocessor list with 30-day notice of change, support for data-subject requests, and a 72-hour breach-notification commitment.
03
Masked, then discarded
Account numbers, national identifiers and card numbers are tokenised before any model call and restored after – the model never sees them raw. The provider is contractually barred from retaining the content or training on it.
04
A log nobody can edit
Authentication, role changes, every run, every approval and every export land in an append-only log, tenant-scoped and retained at least twelve months. It is a record of what happened, not a report assembled afterwards.
05
Outsourcing and ICT readiness
We are prepared to contract under the MiFID II outsourcing regime (Reg. (EU) 2017/565) and to supply DORA register data, incident-reporting deadlines, audit rights and a defined exit – with no sub-outsourcing without your consent. Readiness, stated as readiness: we claim no certification we have not obtained.
06
Isolation and encryption
Tenant isolation enforced by PostgreSQL row-level security rather than application checks alone, sessions bound to your own subdomain, TLS 1.2+ in transit and AES-256 for stored credentials.
The full security overview and the subprocessor list are available on request, and before signature.
§ 04
What this work costs you today.
Move the sliders. The figure is an estimate from your own inputs – the real one comes out of the call.
Per year, on work that can be taken over
378,788 PLN
175 h
recoverable per month
1.0
FTE (173 h/month)
An estimate from your inputs, assuming we take over 75% of that work. Not an audited figure.
§ 05
Two steps, in this order.
No retainer starts before the pilot numbers hold up.
Pilot
from 5,000 PLN
one-time · prepaid
One process, fixed scope, in production in 5–10 business days. You get the before and after numbers, and the record of every run behind them.
Retainer
from 8,000 PLN
per month
Keelra runs the process, adds the next ones, and reports monthly. It starts only once the pilot numbers hold up.
Prefer to start on your own? A self-serve workspace from $2,200 / month, billed in USD. Create an account
The pilot covers an audit and one narrowly scoped process – not a platform rollout. Scope and price are fixed on the call, against your processes.
§ 06
Direct questions, direct answers.
Does the AI decide anything?
No. It prepares work and stops before anything sensitive. It executes no trades, moves no money, and rejects nothing on its own. Every step that touches a client, a system of record or an outbound message waits for a person.
Where is the data processed?
In two places, and the difference matters. Your workspace, database and automation engine run in Warsaw, on European infrastructure; backups are encrypted and held in EU-jurisdiction storage. Model calls are the exception: they go to Anthropic in the United States, because that API offers global or US routing and no EU region at all. Prompt content therefore leaves the EEA under Standard Contractual Clauses, with identifiers masked beforehand and zero retention on the provider's side. If your mandate requires inference inside the EU, we can contract for an EU-hosted endpoint instead.
Does the model train on our data?
No. Identifiers are masked before the call, and the model provider is bound by zero-retention and no-training terms. We record token counts and cost, never the content of a prompt or a response.
How fast is the first result?
The first process runs in production 5–10 business days after pilot kickoff. That holds because the scope is deliberately narrow: one process, delivered end to end, rather than a platform programme that ships nothing for a quarter.
Is this outsourcing under supervisory rules?
It may be, and we are set up for it. We are prepared to contract under the MiFID II outsourcing regime (Reg. (EU) 2017/565) with audit rights, a defined exit, and no sub-outsourcing without your consent. How the arrangement is classified is your call and your counsel's – we supply what that assessment needs.
Do you replace people?
No. We take the repeatable handling off them and leave the decisions – those are the part that needs a signature. The hours come back to work that actually requires judgement.
Does the record replace what we are required to keep?
No. It is an operational trail of what Keelra did and who approved it. Your statutory record-keeping obligations remain yours, and the trail is built to feed them rather than to stand in for them.
What happens after the pilot?
A call on the before and after numbers. If they hold up, the process moves to a retainer and we scope the next one. If they do not, you keep what was built and the engagement ends there.
Thirty minutes and one process to name.
No slide deck. You leave the call with a named process, an estimated gain, and a pilot quote.
§ 07
Not a financial institution?
The way we work is the same anywhere repeatable handling eats hours. The vertical pack is not. Tell us what actually hurts and we will say whether it pays off.