Sheet 1 of 3·Failure modes
Agent systems fail in known ways: they reach data they shouldn't, invent a figure, run on, or act without asking. Each row names one failure, the control that stops it, and where on the path that control sits.
Each message is screened before the agent starts. Requests to run unrelated computation, look inside the sandbox or copy data out of it are refused.
Sheet 2 of 3·The wall
Run the Harness inside your network and the agent, your sign-in and the run record live there with it. When the agent needs market data, a tool call comes out to us carrying the tool, its parameters and your user ID. Before it leaves, the parameters are checked for personal data and the call is logged with its verdict. What comes back is inspected before the model reads it.
Sign in with SSO through your identity provider. Data is encrypted at rest with AES-256, and connections to the platform use TLS 1.2 or later. Credentials you connect are sealed with their own KMS data keys, and code the agent writes runs in its own microVM.
We don't train models on customer data, and under our DPA the model providers we use may not either. Run it inside your network and tool calls come out to us carrying the tool, its parameters and your user ID, screened for personal-data patterns before they leave and logged.
Answers are built from what the data tools return and cite it inline, back to the source documents. Where a deployment sets entitlements, a tool someone isn't entitled to is never built for their run. Every message is screened before the agent starts.
Our cloud is committed to 99.5% availability and runs across availability zones. If a model provider fails, the call moves automatically to the next model in line and the failed one sits out for 90 seconds. Scheduled reports are built before you open them. Every run has a step limit, and every data call a time limit.
An independent auditor's SOC 2 Type II report covers Security, Availability and Confidentiality from May 1 to July 31, 2026, with no exceptions noted. We hold ISO/IEC 27001 and ISO/IEC 42001 certification. Our DPA is written for regulated firms: GLBA and Reg S-P safeguards, 72-hour breach notice, and examination by your regulator where the law requires it. Every run is stored with its question, its answer, its sources and their citations.
Start hosted, or run the agent, your sign-in and the run record inside your network, with market data coming from us through checked, logged tool calls.
Hosted by us on AWS in the US, across availability zones. The fastest way to start.
The agent, your sign-in and the run record on your Kubernetes, from our Helm chart.
Model calls can go through your own gateway and contracts. Market data comes from us in tool calls, each screened and logged.
Sheet 3 of 3·The record
Each run is stored with its question, its answer, the sources the tools returned and the citations that tie them together. A change to your book waits on a card until you accept it, and a linked brokerage account can be read but not traded.
Each document as the tool returned it, with its as-of time and IDs.
Review and adjust the quantities and prices, then Accept. Nothing is committed until you do.
Reads holdings and transactions. Can't place an order.

On request: our SOC 2 Type II report, under NDA, and our DPA.