Acoustic monitoring

MLPerf Tiny Anomaly Detection

A reference autoencoder for finding anomalies in machine sound: it learns only from recordings of a healthy unit and flags deviations. The system does not make a diagnosis, it gives you a reason to check the unit before it fails.

Developer
MLCommons, USA
First release
Jun 2021
Latest release
Aug 2026
Sizes
a tiny fully connected autoencoder sized for microcontrollers
License
Commercial use allowedApache 2.0 for the MLCommons reference implementation; the ONNX and TFLite builds on Hugging Face are MIT
Ready-made builds
8-bit
Running
On your own serverAlso runs without a GPU
Industries
Manufacturing and logistics, Software development, Science and research, Security

What it does

  • Listening to a machine tool, pump or conveyor
  • Flagging deviations from a unit usual noise
  • Training on your own recordings of healthy equipment
  • Running right on a board next to the equipment

Where it is used

Manufacturing and equipment maintenanceWarehouse and logisticsBuilding engineering servicesResearch and pilots

Hardware requirements

LaptopLaptop or regular PC, up to 8 GB of VRAM — smaller versions
fits
1 GPUOne GPU with 16–80 GB — mid-size versions
no versions
ClusterServer with several GPUs — flagship versions
no versions

Versions

  1. Сборки ONNX и TFLite, в том числе INT8
  2. Эталонный автоэнкодер в наборе MLPerf Tiny

How to run it

On your own serverWeights are downloaded from Hugging Face and served with vLLM (load and API) or llama.cpp (modest hardware). The model then runs in a closed network with no per-request fees.Hugging Face
How much hardware you needCalculate the VRAM for the model size, context length and number of concurrent requests.Open the hardware calculator

I can set this up end to end: pick the model size, deploy it on your server and connect it to your systems. Quantization compresses a model so it takes less video memory and runs on more modest hardware. Answers change slightly, so quality is checked on your own examples.

Frequently asked questions

Can MLPerf Tiny Anomaly Detection be used in a commercial project?

Yes. License: Apache 2.0 for the MLCommons reference implementation; the ONNX and TFLite builds on Hugging Face are MIT. It allows commercial use, but it is still worth having a lawyer review the license before launch.

What hardware does MLPerf Tiny Anomaly Detection need?

At minimum: Laptop or regular PC, up to 8 GB of VRAM — smaller versions. Some versions also run on an ordinary CPU, without a GPU. You can calculate the exact VRAM for your model size and context in the hardware calculator.

Does MLPerf Tiny Anomaly Detection support Russian?

Language does not matter for this model: it does not work with text.

Where can I download MLPerf Tiny Anomaly Detection and what does it cost?

The MLPerf Tiny Anomaly Detection weights are open and free to download. You only pay for the hardware it runs on and for the setup. Source links are at the bottom of this page.

How I deploy it for clients

  1. SelectionI pick the model size for your task and hardware and test it on your examples.
  2. DeploymentI deploy it on your server or in a closed network and provide an API.
  3. Fine-tuningI fine-tune it on your data (LoRA) or connect a knowledge base — whichever is cheaper for the task.
  4. IntegrationI connect it to your CRM, ERP, bot, website or team chat and set up monitoring.

Similar models

Source: huggingface.co/ketiswp/mlcommons-Deep-Autoencoder-DCASE2020-ToyCar-fp3. Data checked against the model card on 22 Sep 2026. Have a lawyer review the license before commercial launch.