Measured performance

What the engines actually do

Every number on this page was produced by timing a compiled binary during its build. Nothing is estimated, extrapolated or typed in by hand — the build writes the measurement to a file and this page reads that file back.

What these numbers are
  • Build-time benchmarks. Each figure is a mean over a fixed number of iterations of one named operation, taken on the machine that compiled that binary.
  • Not live traffic. Nothing here is sampled from a running system, and no figure on this page updates on its own.
  • Means, not percentiles. The figure in each row is a mean over the whole run. Engines benchmarked with the shared measure command also record p50, p95, p99 and max for that run; those live in prebuilt/<slug>/metrics.json and are not summarised here.
  • Not a league table. Each row times a different operation — a deal, a market tick, a support intake — so the unit measured is printed beside every figure. Comparing two rows to each other compares two different pieces of work.
  • Not your hardware. A different machine gives a different number, so the host that produced each row is printed beside it.
  • No customer data. Operator telemetry is opt-in, stays private to the vendor, and is not the source of anything shown here.
Engines measured
8 of 10
directories under prebuilt/ carrying a metrics.json
Quickest unit on record
0.23 µs
Trading Agent · one tick: book update + z-score + edge + risk check · mean of 400,000 iterations
At that rate
4.8M/sec
on win32-x64, 2026-10-11
EngineMean per unitRateUnit measuredIterationsWorkersHostMeasured
Trading Agent
sold as Cross-Venue Trade Flow Engine
0.23 µs4.8M/secone tick: book update + z-score + edge + risk check400,000not recordedwin32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
Real Estate Analyzer
sold as Lot Line Analyzer
2.99 µs334k/secone deal (amortise + evaluate, parse excluded)5,000not recordedwin32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
Lead Gen & Scraper
sold as VenueScan Lead Runner
3.68 µs271k/secone empty scheduler task (bot bench) — not a domain measurement50,00012win32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
Customer Support Agent3.84 µs260k/secone empty scheduler task (bot bench) — not a domain measurement50,00012win32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
SaaS Automation
sold as SaaS Automation Engine
4.07 µs246k/secone empty scheduler task (bot bench) — not a domain measurement50,00012win32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
Stock & Crypto Scanner
sold as Stock & Crypto Scanner
54 µs18k/secone full scan (22 indicators over 240 bars, file read excluded)5,000not recordedwin32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
File RAG Agent1.40 ms713/secone hybrid query (vector + BM25, top 5) over 6000 chunks1,000not recordedwin32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
Game Optimizer2.54 ms394/secone scheduled server frame (20,000 entities, 32 players)300not recordedwin32-x64
13th Gen Intel(R) Core(TM) i5-13420H · 12 threads
2026-10-11
Not yet measured

These engines ship a binary but carry no recorded measurement, so this page makes no performance claim about them. Listing them is the point: an absent benchmark is stated rather than filled in with a number from somewhere else.

webhook-engineworkflow-automation

How the architecture behind these numbers is put together: System Architecture & Pipeline Blueprint.