Okren is the financial supervisor that independently checks before AI moves money.
Phone view shows a short version. Open the full demo on a desktop to see everything.
Illustrative demo with sample data. Switch between Discover, Shadow and Enforce, and open Action, Limits and Record. Open the full demo
Works with any AI, bank, exchange or payment provider.
Okren sits in front of whatever executes the move, so changing the AI or the provider does not mean rebuilding Okren.
Swap the model or the provider. The check stays the same.
- ChatGPT
- Claude
- Grok
- Stripe
- Fireblocks
- Okta
- Microsoft
- Datadog
How do we safely trust AI to move money at AI speed?
- 1Slow it down. Safe, but you lose the advantage of AI speed.
- 2Trust AI. Fast, but AI should not authorize itself.
- 3RDOkren. Applies human supervision at AI speed while always staying in control.
Under 1 ms to check a move using Okren.
A teller creates the wire. The manager approves.
Okren is AI’s manager.
The teller
Opens the register and hands out the cash.
The manager
Signs off before the cash goes out.
The AI agent
The new teller. It can do the work, at machine speed.
Okren
Helps the human manager keep up with AI that moves money, checking every move before the money goes out.
Building towards super‑intelligence, our AI grew an account 3,300% in under 4 months.
Then someone asked: if I gave you $1 Billion in Bitcoin, could you guarantee the AI would not lose it or go off on its own?
Making the AI smarter will never answer that. Something separate has to decide what AI is allowed to do. That became Okren.
Read the full storyAI proposes.Okren supervises.Your financial system executes.
We give any company that moves money a scalable way to keep a human-in-the-loop while letting AI move money.
AI proposes
a financial move started by a person, a system or an AI agent.
Okren supervises
1 of 4 answers before the money moves.
Your financial system executes
what is allowed in your bank, payment system or trading venue.
Swap the model, agent or provider. The limits stay.
Inside your limits. It goes ahead.
Over a limit. Only the allowed amount goes.
Needs judgment. Held for a person you name.
Not allowed. It does not go.
AI should never authorize itself.
Okren sits outside the AI and outside the payment system. Whatever proposes a move cannot be the one that decides it is allowed.
Multiple systems, each with its own controls. Okren is the independent check across all of them, before money moves.
Different systems do different jobs. Okren is designed to apply the same limits whichever one carries out the move, independent of the AI and of the platform.
AI is missing
independent supervision
These systems can complement Okren. None of those responsibilities, by itself, is independent supervision of the whole proposed action before execution.
Outside the agent. Inside your system.
Okren doesn’t ask you to route decisions through a separate platform. It’s independent in how it decides, but it runs as an SDK inside the infrastructure you already have.
Okta, Entra, Auth0, StrongDM and Delinea control who can act and what they can reach.
They don’t decide whether this exact move is allowed.
They confirm who is acting; Okren decides whether this move is allowed.
Cerbos, Oso and Permit.io write down the rules and who controls them.
They don’t check each live move against the full situation.
They store the rules; Okren applies them to each move as it happens.
Microsoft and Faramesh protect systems from attack and misuse.
A secure system can still take a move nobody authorised.
They keep attackers out; Okren checks the moves that come from inside.
Sardine, Stripe Radar and Forter judge how risky or suspicious a move looks.
A low-risk move can still be outside your authority.
They score the risk; Okren decides whether the move is allowed.
ChatGPT, Claude and Grok focus on how the AI plans and acts.
They don’t independently approve what the AI helps produce.
They help the AI act; Okren independently approves the move before it happens.
Datadog, Splunk, New Relic, Vanta, Drata and AuditBoard show what is happening and what happened.
They don’t stop the wrong move before it becomes real.
They report what happened; Okren decides before it happens.
Stripe, bank APIs, exchanges, Fireblocks and Increase make the money move.
They don’t know whether your institution should make the move.
They carry out the move; Okren decides whether it should happen at all.
Is this exact agent move allowed, right now, given everything happening across the institution, under the authority it has set?
Okren is built to independently supervise AI agents, so humans are always in control of AI moving money.
Give it access. It builds the map on its own.
Okren is a control tower for your whole system. It watches everything inside it and learns how it works on its own, from the inside out.
ReadPayment requestAI agent$18,400
FoundRecipientSupplier
LinkedInvoiceBudgetPayment historyYour limits
MarkedWhere money leaves
LinkedOther agents that can pay the same supplier
MappedExisting controlsTheir logs
Okren understands the whole web. It only suggests the answer.
What it learns informs the check. Only the limits your people set decide it. Illustration using an example payment.
Okren sits alongside your controls. It replaces none of them.
Your first-line release authority and second-line monitoring stay where they are.
Stays with you
Nothing here moves to Okren- Sanctions and list screening
- Checking that an instruction is genuine
- Available balance and liquidity checks
- Your approval process: dual control, callbacks, who may release what
- Deciding on, and filing, suspicious-activity reports
What Okren adds
One independent layer on top- Independent by design. The AI cannot set its own limits, approve its own move, skip the check or rewrite the record.
- Checks the exact move, before it moves. The payment, order or transfer itself: not just who sent it, and not a report afterward.
- The same answer every time. Fixed limits your people set, applied the same way. Not a model’s guess.
- Works with any AI, system or rail. Swap the model, agent or provider. The limits stay.
- A record you can replay. Every answer is kept, with the limits that applied.
Separate on purpose. A control owned by the AI’s maker, or by one payment network, is not independent of it.
Okren does not judge what is suspicious.
Whether it’s $5 or $5 million, your limits apply every time.
See the full story behind every decision.
What was proposed. Which rules applied. What Okren answered. Why. And what happened next.
Built to answer the question asks later: why was this allowed to leave, or why was it held?
Phone view shows one decision. Open this page on a desktop to see the full record.
Example decisions with sample data.
Delegate work to AI. Keep human authority.
Let routine moves keep moving
Moves inside your limits go ahead without waiting in someone’s queue. Exceptions stay with people.
Keep one set of limits
The same limits apply whether a person, a system or an AI started the move.
Keep one record
Who asked, which limits applied, what Okren answered and what happened next.
Give AI more responsibility as confidence grows.
Start by watching. Okren shows what it would have answered, side by side with what your supervisors decided, and changes nothing until you say so.
Discover
Okren watches one workflow and keeps the record. Nothing changes.
Shadow
Okren records what it would have answered while your process runs unchanged.
Enforce
Its answers count, on a small scope first. You widen it as confidence grows.
Questions, answered plainly.
Does a person need to approve every transaction?
No. People set the limits and approve the exceptions. Routine moves continue inside the limits you set, and a person is involved when a move needs one.
Does Okren move the money?
No. Your financial system executes. Okren answers whether the move may go ahead.
What if Okren cannot answer?
The move is held, not executed. Who is alerted, and how a held payment is released, is something we agree with you before enforcement.
Can the AI go around Okren?
Okren checks every action routed through it. It cannot supervise a path that skips it, so we start by mapping where your moves execute and which paths do not pass through Okren.
Does Okren keep our private information in its logs?
It does not need to. Names, account numbers and other identifiers can be masked in Okren’s record and in exported logs. We recommend leaving that on, and your institution decides what is kept and where.
Who can change the limits?
Your institution owns the limits. Changing a limit is a privileged act, and how a change is approved is something we agree with you before enforcement.
How fast is it?
A typical check takes under a millisecond in Okren’s current environment. In Shadow we measure it on your own workflow.
Which path already moves money?
Show us one release path that already moves money. We will map where an independent check would sit against your authorization matrix and dual-control points.
One workflow. A fixed period. Pricing set with you.