Build1 distinct publisher3 min readPublished
The EdgeFirst Model Zoo ties every published result to the artifact, dataset and host that produced it. The arithmetic underneath is the actual argument against buying on peak throughput.
The Engineer · Build desk

Compiled by The EngineerSomething wrong?How this is made
The Apple row is where the argument gets sharp. EdgeFirst measured 1.80 milliseconds of inference for YOLOv8 Nano on an M2 Max Neural Engine inside a 5.26 millisecond end-to-end pipeline, then measured 791 FPS where a latency calculation implies roughly 190 [10]. Sustained 791 FPS is 1.26 milliseconds per frame [2]. Au-Zone's own profiler documentation attributes the gap to overlap: preprocessing, inference and postprocessing run on different frames, and the slowest stage sets sustained throughput [11]. Inference alone is about 42 percent longer than that 1.26 millisecond per-frame budget [3], so overlapping three stages cannot by itself produce the measured number. Either more than one inference is in flight at once, or 1.80 milliseconds is not what a frame costs on the sustained path. Both are ordinary engineering. Neither is legible from the two figures on their own, which is close to the complaint Au-Zone is making about everyone else's tables.
The accuracy numbers are less ambiguous and more immediately useful. On Qualcomm's Hexagon NPU, identical YOLOv8 Nano weights under an identical INT8 scheme scored 48.46 percent with a split decoder and 46.37 percent with a logical decoder [8], a spread of 2.09 points decided by where the graph was cut [1]. The distance from the published reference row for the same model to the better of those two Hexagon configurations is 2.03 points [6]. So one compile decision inside a single vendor's toolchain moved accuracy about as far as quantising and porting the model did.
A density check is worth doing before treating this as a corpus. 837 sessions across seven repositories at three model sizes is about 40 sessions per model variant, and spread over the eleven compute targets listed that is under four runs per target per variant [5]. Broad coverage, thin per cell. The value is the linkage, not the sample size: each row resolves to a session carrying the artifact, dataset lineage, converter settings, host kernel, accelerator and profiler version [2].
The board sweep is the part a buyer can act on soonest. The same eIQ Neutron NPU was run on boards from NXP, Toradex, Ezurio and PHYTEC, where the accelerator is fixed and memory, thermals and board support software are not [9]. That comparison exists because a TOPS figure describes theoretical integer throughput on a synthetic workload [15], and nothing in it survives contact with a thermally limited enclosure. Au-Zone is not a neutral party here. Sebastien Taylor, its VP of R&D, made the case in a Hugging Face Community Article [4]; the sessions browse without registration, and the trail leads back to EdgeFirst Studio [14]. The company has been building embedded vision software from Calgary since Brad Scott co-founded it in 2001, including machine-learning tooling work with NXP [3][16]. The pitch and the evidence point the same way, which is worth stating plainly rather than pretending the numbers arrived from nowhere.
Ranked by verification strength, evidence, and original report placement.
Au-Zone Technologies launched an EdgeFirst Model Zoo on August 24 with a direct challenge to how embedded AI hardware is sold: peak accelerator throughput is a poor guide to how a vision model will perform inside a finished device.
EdgeFirst says the release includes 837 validation sessions across seven YOLO detection and segmentation repositories, with each result connected to the model artifact, dataset version, test parameters, timing trace and host configuration that produced it; the session chain includes artifact, dataset lineage, converter settings, host kernel, accelerator and profiler version.
Au-Zone is a Calgary, Alberta developer led by co-founder and CEO Brad Scott, who co-founded the company in 2001.
Au-Zone vice president of research and development Sebastien Taylor, who has spent more than two decades developing embedded software products, laid out the argument in a Hugging Face Community Article.
The collection covers YOLOv5, YOLOv8, YOLO11 and YOLO26 for object detection, with YOLOv8, YOLO11 and YOLO26 also having instance-segmentation repositories; EdgeFirst publishes nano, small and medium variants in ONNX FP32 and INT8 alongside artifacts compiled for the accelerators it has tested.
Targets span NXP's i.MX and Ara hardware, a Raspberry Pi 5 paired with a Hailo-8L, NVIDIA's Jetson Orin Nano, Qualcomm's Hexagon NPU and Apple's Neural Engine, Metal GPU and CPU, with CUDA, x86 and Arm CPU measurements as additional reference points.
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Unusually specific but entirely vendor-reported and single-sourced
The factual density is high for a launch story: named session identifiers (v-e89), exact accuracy figures, explicit provenance chains and an enumerated target list. But every number originates with the party selling the measurement platform, only one publisher covers the cluster, no third party has reproduced any session, and the flagship throughput figure does not reconcile with its stated explanation. That combination supports 'well documented' but not 'independently verified'.
Artifacts shipped, no external uptake evidenced
There is a real, dated release with public artifacts and published benchmark sessions, so adoption is not zero at the publication layer. But the supplied material contains no third-party deployment, no named customer, no download or usage disclosure for EdgeFirst Studio, and parts of the guided experience are still marked in progress. Adoption is therefore vendor-side only.
Method claim outruns the published measurement base
The underlying argument — that TOPS does not predict a shipped pipeline, and that graph boundaries and board choice move real numbers — is directly supported by the vendor's own paired measurements, and the article is candid about unfinished cells and license obligations, which keeps the gap modest. The overstatement sits in the framing of scale and rigor: 837 sessions reads as exhaustive but thins to under four sessions per variant per target, the provenance-first pitch is delivered through self-published results with no independent replication, and the most quotable number (791 FPS) is presented as settled while its arithmetic does not close.
Benchmark publisher sells the benchmarking platform
Au-Zone publishes cross-vendor performance numbers while selling EdgeFirst Studio, the platform required to reproduce the process on private data, and the free model cards explicitly route to it. The critique of headline TOPS figures targets exactly the marketing practice of the silicon vendors whose parts are being ranked, and Au-Zone has a prior commercial relationship with one of those vendors, NXP. The published weights also carry AGPL-3.0 terms with a commercial Ultralytics Enterprise License requirement, adding a third-party licensing interest. None of this makes the measurements wrong; it does mean no disinterested party has confirmed them.
Moderate: detailed but unreplicated and single-publisher
Confidence is bounded by structure rather than vagueness. The specifics are checkable in principle and internally consistent apart from the throughput arithmetic, and the story is fresh and precisely dated. Against that: one publisher, one originating vendor post, no independent verification, no vendor rebuttal, and an unresolved inconsistency in a headline metric.
build
A browser video editor pays for its missing upload button in runtimes, caches and determinism1 distinct publisher
build
PyInstaller exits zero, then the real work starts: notarization traps that report success1 distinct publisher
build
Shanghai AI Lab's 397B science agent shipped in July; the paper explaining it landed August 131 distinct publisher
build
796 pages of semantic search with no vector database, and what it cost to skip one1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 24, 2026