Blog
Articles, guides, and insights on local artificial intelligence
Reading paths
Start here
The in-order path for newcomers to local AI: from basic concepts to installation and your first model.
Optimize performance
Pick the right hardware and get the most out of what you already own: CPU vs GPU, Mac, Raspberry Pi, and fast serving.
Data and privacy
What actually goes over the network with local AI: the data, the security, the compliance, and the control that stays in your hands.
Choosing hardware and model
How to pick the right hardware and the model suited to your use: VRAM, quantization, GPU or CPU and response speed.
6 articles
ML agents that run locally: MLExpert and EpochGo on Ollama, zero API costs
MLExpert raises the bar to 35B and a 72.7% medal rate; EpochGo runs three AutoML agents on 16 GB at zero API cost: what works today, the math and the limits.
MagpieTTS 357M: 12-language speech synthesis that runs on a laptop
NVIDIA releases MagpieTTS Multilingual, 364M parameters and 12 languages in one model: local text-to-speech with a 332 MB GGUF file, no GPU. The C++ runtime NeMo-Speech.cpp takes you from zero to first audio in three commands; the five voices are the same in every language, and for a natively Italian voice Piper is still ahead.
Decision models in local: JEV-35B and the 3B-active System 1
You don't need a big LLM to decide. JEV-35B (35B, 3B active) in NVFP4 on a 32GB GPU and ej (11.4MB) on CPU show how to do routing, classification and quality control without generating a single token.
Costs: local vs API, done with real numbers
How much does local really cost compared to a cloud API? Verified per-token prices, GPU amortization, electricity and the break-even point, calculated with real numbers.
Local AI for your business: 5 practical use cases
Five practical use cases of local AI for businesses: customer support, documents, internal search, CRM and generation — with the tools, minimum hardware and a 30-minute starting plan.
Privacy and GDPR: What Local AI Changes
Extra-EU transfers, sub-processors and Arts. 5, 25, 28, 32, 44: what the GDPR really says about cloud vs local, and what is still owed even with in-house AI.