Built for the people who audit you.
You answer to a regulator for every message that leaves your desk. So does BrokerOS. There is exactly one route from your systems to a write, a gate you control sits on it, and every action carries the evidence it acted on.
One path in. One gate on it.
This is the whole access model. Trace it and you have the answer to most of what a security review asks, because there is no second route and no exception to the gate.
- 01Your systems
Read credentials, scoped
Least privilege credentials to the trading platform, payment providers, ticketing and the ledger. Read scope only. No write permission is issued at this stage and none is required for anything that follows.
- 02Atlas
Into Atlas, per entity
Records are joined into the graph inside your region, held separately per licensed entity. Every read is scoped to one entity and logged with the agent that made it.
- 03Agent
An agent decides
The agent reads what it needs from the graph, never from your systems directly, and prepares an action with the records it relied on attached to it.
- 04Your control
The gate
The action is checked against the autonomy level and the amount you set for that function. Below the threshold at Autonomous it proceeds. At or above it, or at any lower level, it stops here and waits for a named person.
Nothing below this line happens without clearing it - 05Your systems
Write, narrowly
Only an action that cleared the gate is written, only to the system that owns that record, and only the field the action names. The write carries the approval and the evidence with it.
Every action leaves this. Not a sample of them.
An agent records what it read, why it acted and who released it. That record is more complete than the one a person leaves behind, which is usually the moment a compliance officer stops objecting and starts asking when they can have it.
- action
- partner.payout.hold
- verb and object, never free text
- agent
- Partners
- occurred_at
- 2026-09-18T06:41:12Z
- UTC, from the source system
- entity
- ENT-2
- the licence this ran under
- read
- partner:PTR-0412, agreement:AGR-0412-v3, trades:1240
- exactly what it saw, versioned
- reason
- Tier 2 applied. Signed agreement dated 4 March specifies Tier 3.
- why, in words a person can check
- amount
- USD 5040.00
- the sum at stake
- autonomy_level
- approval
- the level in force for this function
- outcome
- held, awaiting named approver
- approved_by
- not yet assigned
- filled on release, never by an agent
The controls, grouped the way you will ask about them.
Read only by default
Credentials issued to us are read scoped. Write access is granted per function, by you, and is revocable in one action.
No agent touches your systems to learn something
Agents read the graph. Only a cleared action reaches a source system, which means there is one path to audit rather than eight.
Least privilege, and logged
Every read is attributable to an agent, an entity and a moment. Access that is never used is removed.
Your entities stay separated
Separation is held in the graph itself, not applied as a filter over it. There is no query that returns another entity’s records and no report that can cross the boundary by accident.
Residency per entity
Records are held in the region the licence requires, set per entity and recorded in the order form. Nothing is moved for processing convenience.
Encrypted in transit and at rest
TLS in transit. Encryption at rest on every store holding your records, including backups.
Deletion you can trigger
On request or on termination, your data is returned in a structured format or deleted within thirty days, except where law requires us to retain it.
Five levels, set per function
Off, Observe, Recommend, Approval, Autonomous. Set per function rather than per product, and reversible at any time. Every function starts at Approval.
Your amount always wins
Above the threshold you set, a function asks a named person whatever its level. The threshold cannot be raised by an agent.
Money to a counterparty is never autonomous
At any level, in any configuration. This one is not a setting, and there is no combination of options that makes it one.
We are never in the payment path
BrokerOS holds no balances, receives no client money, and is not a party to any client agreement. It is not a payment institution and does not need to be one.
Breach notification without undue delay
You are told in time to meet your own notification deadlines, with the categories and records affected, the likely consequences and what we have done.
Sub-processors disclosed and objectable
The list is published. Thirty days notice before any addition, and a right to object on data protection grounds.
Your security review, answered before you send it.
These arrive as a spreadsheet. Here are the answers, including the two where the answer is not yet, because you would find that out anyway and we would rather you found it out from us.
- How is data encrypted?
- TLS for everything in transit. Encryption at rest on every store holding customer records, backups included.
- In place
- How do our people authenticate?
- Single sign on through your identity provider, with multi factor enforced by you. We do not want to be the system of record for your staff credentials.
- In place
- Where is our data hosted?
- In the region your licence requires, pinned per entity and written into the order form. Sub-processors and their regions are published.
- In place
- What does the audit trail contain?
- Every action, with the records it read, the reason in words, the autonomy level in force, the amount and the named approver. A specimen is above.
- In place
- How long is data retained?
- To your policy while the subscription is live. On termination, returned or deleted within thirty days unless law requires retention.
- In place
- Do you use our data to train models?
- No. Model providers are contracted on zero or shortest available retention and are prohibited from training on your data. Learning happens on your own book, inside your environment.
- In place
- Is there a data processing agreement?
- Published in full and written to be signed as it stands, including sub-processor objection rights, breach notification, audit and deletion.
- In place
- Do you carry a SOC 2 or ISO 27001 certificate?
- Not yet. The controls described on this page are in place and evidenced, and we will say plainly where we are in that process on a call rather than imply a certificate we do not hold.
- Not yet
- Is the platform penetration tested?
- Independent testing is scheduled rather than continuous today, and we will share the scope and the date of the most recent test under NDA.
- Not yet
Nothing changes on your side before you decide. No writes, no messages to clients, no work for your team beyond half a day of read credentials. You see the first list before anything is switched on, and every function is reversible in one action.
Bring your compliance officer to the first call.
Most brokers do. The audit trail is usually the part that ends the conversation rather than starting it.