A June 7, 2026 r/LocalLLaMA thread asked a useful question: what non-LLM AI do people actually use every day? The answers were a reminder that practical AI is often smaller, narrower, and less glamorous than the frontier-model conversation suggests.

The strongest examples were task-specific vision systems. One commenter described a setup that reads water and electricity meters, tracks usage in real time, and flags leaks or outages. Another described a tiny YOLO model running on old security-camera footage to detect package deliveries. It was trained on roughly 200 manually labeled clips, runs on a Raspberry Pi 4, and reportedly beats cloud services because it is tuned to one household’s camera angle and failure modes.

The thread also turned into a defense of older machine-learning tools. LightGBM and XGBoost came up for tabular work, where gradient boosting remains fast, cheap, and predictable. For name matching and deduplication, commenters pointed to embedding similarity, Levenshtein distance, and other simple methods that can resolve easy cases before an LLM ever needs to enter the workflow.

Speech and document processing added another layer. Users mentioned NVIDIA Parakeet-based transcription and diarization tools, Coqui TTS pipelines for turning text collections into audio, OCR systems that process invoices, and targeted models for photo cleanup or object detection. These are not broad conversational systems, but they solve repeatable jobs with clearer cost and reliability boundaries.

The community angle matters because LocalLLaMA is often associated with running bigger local language models. This thread showed the quieter version of local AI: pick the model class that matches the job, keep it close to the data, and avoid paying a general model to do work a specialized one handles better.

The original discussion is on r/LocalLLaMA.

#yolo

LocalLLaMA’s best AI thread was not about LLMs