The run
You send an export
CSV or JSON, in as many files as you have. Columns and timestamps are detected on arrival. The agent works on the files, so it needs no connection to your production systems.
The agent writes, runs and scores
It writes a detection in Python, runs it in a sandbox on your data, scores the result without labelled cases and rewrites it. One run is up to 100 of these iterations.
You keep what scored
Your team reviews the rules that scored and chooses which ones run on new data. Each alert reaches Slack or a webhook with a draft report attached.
The agent runs on one GPU with a local model, or on a cloud model you choose, and your data is used for your rules alone. A model trained on your data, kept in your environment, is in development. See Fine-tuning.
Results
A cross-border remittance operator sent four exports, about 2.5 million rows, with no labelled cases. The agent ran 100 iterations in 5 hours 6 minutes, and the operator checked the five flagged accounts by hand.
What the kept rule keyed on
| Reversal rate | 27 times the peer median |
|---|---|
| Transactions per account-day | 3.08, against a population median of 0.04 |
| Sources | flagged accounts present in all four |
Across 51 runs on this data the agent wrote 2,037 rule versions, of which 12 were kept. There is no public benchmark yet.
Cost
| Open source | Free | The public detections, helpers and tests, under the MIT licence. |
|---|---|---|
| Self-serve | from $5,000 a year | Hosted by us. You send exports and the agent runs on them. |
| Platform | from $50,000 a year | Runs inside your environment, with draft reports, and fine-tuning when it ships. |
| First run on your export | No charge | One full run on one export. You keep every rule it produces. |
Transaction-monitoring platforms
Quoted to us for the same volume, 1.2 million transactions a year, at $42,000 to $107,573 a year on one- to three-year terms billed up front, after weeks of procurement and setup.
By hand
An analyst or consultant writes rules in a vendor’s builder, on the part of your data the builder can see, and revises them on a quarterly cycle.
Who it's for
Questions