Okren helps a financial supervisor keep up with AI-speed transactions.
It applies the institution’s limits to every move routed through it before money moves, and keeps a record of every answer.
A supervisor does three things. Okren helps with each.
Understand
Know what is being asked
Knows who is asking, what for, how much, and where the money is going.
Brings the context of each proposed move together.
Apply authority
Check it against the limits
Checks the move against the limits the institution set, and signs off or sends it back.
Applies those limits the same way every time, at AI speed. Exceptions go to the person who owns them.
Remember
Keep the record
Writes down what was approved and why, so it can be explained later.
Keeps that record automatically.
Between whoever proposes and the system that executes.
Okren runs as software inside the institution’s own environment, in front of its execution system.
Your model, your agent framework and your execution system can change without rebuilding your rules.
1. The call
Before it executes, your system sends Okren the proposal: action, amount, recipient, account, intent, who or what is asking, and a trace ID.
2. The answer
Okren checks it against fixed rules, not a model’s guess, so the same input gets the same answer. It returns Approve, Reduce (with the permitted amount), Ask or Stop, the limit that applied, and a decision ID.
3. Held, not skipped
Your system executes only what comes back allowed. If Okren cannot answer, the move is held, not executed.
Your existing controls stay where they are
- Sanctions screening
- Authentication
- Balance checks
- Dual control and callbacks
- Reporting duties
Okren does not judge what is suspicious.
What goes in
- Started by
- PAY-AGENT-01 (AI agent)
- Type of move
- Supplier payment
- Amount
- $18,400
- Recipient
- Harbor Supply Co
What comes back
- Answer
- Reduce to $10,000
- Why
- Over the $10,000 payment limit
- Record
- Decision ID, time, the limit that applied
- Then
- Your system executes $10,000
Every move gets one of four plain answers.
| Answer | What happens to the move | Example |
|---|---|---|
| Approve | The move is inside what your institution allowed. It goes ahead under the authority you already set. | A $4,200 payment to a known supplier. |
| Reduce | Only the amount inside the limit goes ahead. The rest does not move, and the record shows both amounts. | An agent asks for $25,000. $10,000 goes out. |
| Ask | The move is held for a person you name. Nothing runs until they answer. Waiting is never approval. | A $120,000 wire, over the $50,000 wire limit. |
| Stop | The move does not go. The answer is recorded. | A payment to a recipient that was never approved. |
Examples are illustrative. Your institution sets the amounts and the rules.
The institution sets the limits. Okren applies them consistently.
Each person, system or AI that can start a move has a mandate: what it may move, to whom, and up to how much. Think of a signature card with a limit.
- How much a single move can be
- Who or what can receive the money
- Which accounts are in scope
- Which kinds of move are allowed
- Who or what is asking
- When a person must answer first
Example only. Not a recommended policy.
One dashboard, in your own environment.
Pick an area to see it in the demo.
Illustrative demo with sample data.
Know what was done with money, and what was allowed.
Built to answer the question a reviewer asks later: why was this allowed to leave?
Nothing proposing a move is the one writing its own history.
Example decisions with sample data.
Built so the control can’t be talked out of its job.
What your security and risk teams will ask. We would rather tell you first.
In place today
What Okren does now.
- Runs as software inside the institution’s own environment
- Independent of the system making the move: it cannot approve its own answer or define its own authority
- Approve, Reduce, Ask or Stop against your limits
- Every answer recorded and reconstructable
- Held, not executed, if Okren cannot answer
- Typical check under 1 ms (current environment)
Customized for the institution
What is specific to your organization, agreed before Enforce.
- Approvals started by your people, and who approves them
- Which of your systems and payment routes pass through Okren
- Who is alerted when a payment is held, and how it is released at a cutoff
- How a change to a limit is approved
- What data enters Okren, and where it is kept
Not yet
Stated plainly.
- SOC 2
- A full vendor-risk package
Okren supervises what is routed through it. A path that skips it is not supervised, so the first step is mapping where your moves execute.
Okren earns its authority in stages.
Nothing is switched on blind. You see what Okren would do before its answers are binding.
Discover
Map where money can move, and who starts each move. Okren watches. Nothing about execution changes.
Shadow
Okren records what it would have answered. Your existing process still runs the move. You compare the two.
Enforce
Okren’s answer is binding. Moves inside the limits proceed. Exceptions are stopped, reduced or held.
Shadow on one path is the easiest place to begin.
Run one workflow in Shadow for a fixed period, compare Okren’s answers with what actually happened, and decide from the evidence.
Moving from Shadow to Enforce is a risk decision, made by whoever owns your operational risk limits. It is not a settings change.
Two fair questions.
Why can’t an institution build it themselves?
The rule engine is the easy part. The hard parts are decision records you can reconstruct and test, state across systems, ongoing updates, and security and continuity evidence. A supervisor built inside the team it supervises is also never fully independent.
Why not rely on limits the institution (or its providers) already set?
Each provider’s limits stop at that provider’s edge. Okren holds one set of limits above all of them, separate from whichever AI is proposing the move.
See something we’ve missed? Please share.
Tell us what is unclear, what we got wrong, or how an approval process in your institution should work differently. A few lines is enough.
People move money. AI moves money. Okren supervises it.
Show us one release path that already moves money. We’ll map where an independent check would sit relative to your authorization matrix and dual-control points.