Finance and accounting decision
Rust Trade Evaluator
A small, single-tenant evaluator to detect teaming/collusion is realistic for a capable developer to build and run in about a week, but the paid product likely adds proprietary data, polished UX, scale, and operational support that are non-trivial to fully replicate.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off38 h to build
$0/mo6 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Rust Trade Evaluator alternatives, with the arithmetic →
What a replacement has to do
- Ingest trade/match logs, compute collusion/teaming signals, store results, present findings in a web UI, and send alerts.
What it still won’t have
- Proprietary datasets or historical market telemetry the vendor may use
- Polished UI/UX and user support channels
- Operational scale and high-availability hosting
- Any proprietary detection models or closed-source analytics optimizations
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Rust Trade Evaluator does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal Rust-based Trade-Teaming Evaluator: use Actix-web for the backend, Postgres for storage, Diesel or SQLx for DB access, and a small React frontend. In scope: HTTP endpoints to upload trade/match logs (CSV/JSON), normalization into a canonical events table, implementation of several heuristic detectors (pairwise overlap, inter-trade timing correlation, suspicious repeated counterparties), scheduled batch worker (cron or background task) to run detectors on new data, APIs and dashboard pages to list flagged cases and drill into evidence, and email/webhook alerting for new flags. Out of scope: training ML models, multi-tenant billing, high-availability clustering, and proprietary data ingestion connectors. Include error handling, logging, environment-based config, DB migrations, and unit+integration tests for ingestion and detection logic.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productRust Trade Evaluator - Prevent teaming, trade fairly
- open sourcenautilus_trader
- open sourceSuperalgos
Integrity checks
What held up, and what did not.
