Fits between your AI and your financial systems.
Okren runs as software inside your own environment. Your systems send it a proposed move. It sends back a decision. Your system executes only what is allowed.
One decision point, in front of execution.
Okren is attached to the move itself, not to one model, one agent framework or one payment provider.
Your AI or system
A model, an agent, an application or a person proposes a financial action.
OKREN
Runs inside your environment. Understands the move, applies your authority, returns a decision.
Your execution system
Carries out what is allowed. Your platform, your accounts, your control.
The outside world
A bank, payment system, venue or wallet. The money moves here.
Decision record
The decision, its reasons and what happened next are kept.
What crosses the line is small and stable.
Okren governs the proposed action. It does not depend on which model or framework produced it.
Change the model
Swap one AI provider for another. When the new one proposes the same kind of move in the same format, your rules and Okren's integration stay as they are.
Change the agent framework
Rebuild how your agents work. As long as moves still pass through Okren before they execute, the supervision holds.
Change where money moves
Add or replace an execution system. You connect it at the point where the move executes. The decision logic doesn't get rebuilt.
What goes in (illustrative)
- Who is asking
- Agent REBAL-02
- Type of move
- Withdrawal
- Amount
- $18,400
- Recipient
- Address not on the approved list
What comes back (illustrative)
- Answer
- Stop
- Why
- Recipient is not permitted
- Record
- Decision ID, limits version, time
- Then
- Your system does not execute
A genuinely new kind of move, or new fields, may need a policy or format update on our side. That is a small change, not a re-integration.
Okren supervises. It doesn't take over.
Stays with you
- Your platform and your systems
- Your accounts and your clients
- Your data
- Execution of every move
- The limits, and who may change them
What Okren does
- Understands each proposed move
- Applies your authority to it
- Returns Approve, Stop, Reduce or Ask
- Keeps the decision record
Okren is not a bank, a payment rail, an exchange, a wallet or your operating system. The way money moves can change. Okren's job stays the same.
Authority is set by rules. Not by a model's best guess.
Your AI can explore and propose in many ways. What it is allowed to do is set by a fixed set of rules you wrote.
The same facts and the same rule give the same answer, every time. Where a rule can't settle a move, a person does.
Illustration. Same facts, same rule, same answer.
Built so the AI can't approve itself.
Independent of the AI
Okren isn't part of the AI making the move. A mistaken or misbehaving agent meets the same limits as any other.
Held, not skipped
If Okren cannot answer, the action is held and not executed. Your systems should be set up to fail this way.
Silence is never approval
If a person is asked and doesn't answer, nothing happens. It doesn't turn into a yes, and it doesn't quietly turn into a no.
What Okren can supervise
Okren supervises moves that are routed through it. If a system is changed so a move can execute without reaching Okren, that move is outside its supervision. So we start by finding the point where moves execute, and putting Okren in front of it.
Your security review
Your security and vendor-risk teams will have questions. We answer them directly, including what is not yet in place. For example, SOC 2 is not yet complete.
A typical check takes under a millisecond in Okren's current environment. In Shadow we measure it on your own workflow.
Show us where your moves execute.
We'll show you where Okren would sit.