<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/css" href="https://techfuelhq.com/feed.css"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>TechFuel HQ</title><link>https://techfuelhq.com/</link><description>Recent content on TechFuel HQ</description><generator>Hugo</generator><language>en-us</language><managingEditor>contact@techfuelhq.com (LK Wood IV)</managingEditor><lastBuildDate>Fri, 20 Nov 2026 20:00:00 +0000</lastBuildDate><atom:link href="https://techfuelhq.com/index.xml" rel="self" type="application/rss+xml"/><atom:link href="https://pubsubhubbub.appspot.com/" rel="hub"/><item><title>vLLM vs Ollama: Concurrent Serving vs Local GGUF Swaps</title><link>https://techfuelhq.com/self-hosted/vllm-vs-ollama-2026/</link><pubDate>Sat, 14 Nov 2026 10:35:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/vllm-vs-ollama-2026/</guid><atom:updated>2026-11-20T20:00:00Z</atom:updated><description>&lt;p>Comparing vLLM and Ollama as if one is simply a &amp;ldquo;faster&amp;rdquo; drop-in for the other misses why each project exists.&lt;/p>
&lt;p>They solve opposite problems. Ollama is a model appliance built around llama.cpp and GGUF weights: pull five models, chat with a 14B coder, switch to a vision model two minutes later, and watch your VRAM empty back out five minutes after you stop using it, so you can launch a game or compile shaders. vLLM is a serving engine built around PagedAttention and continuous batching: pin one model onto a Linux GPU, reserve the card&amp;rsquo;s free memory for a paged KV-cache pool when the server starts, and keep many simultaneous requests moving through one batch.&lt;/p>
&lt;p>Pick the wrong one and you feel it. Run vLLM on a 16GB daily-driver desktop and it holds nearly the whole card for as long as it runs. Run Ollama behind a multi-agent workflow firing ten parallel tool-calling loops and requests wait their turn: Ollama&amp;rsquo;s FAQ sets OLLAMA_NUM_PARALLEL to 1 by default, and raising it multiplies the context memory each model needs.&lt;/p>
&lt;h2 id="architecture-side-by-side">Architecture side by side&lt;/h2>
&lt;p>Every practical difference between the two servers traces back to KV-cache memory, weight formats and process lifetime. Versions read on November 18, 2026: vLLM 0.34.0 and Ollama 0.40.16.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Dimension&lt;/th>
&lt;th scope="col">vLLM&lt;/th>
&lt;th scope="col">Ollama&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Dimension">Core engine&lt;/td>
&lt;td data-label="vLLM">Python serving engine with &lt;strong>PagedAttention&lt;/strong>, continuous batching and optimized attention and GEMM kernels&lt;/td>
&lt;td data-label="Ollama">Go server with a &lt;strong>llama.cpp&lt;/strong> backend&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Target workload&lt;/td>
&lt;td data-label="vLLM">Concurrent API serving: batch pipelines, team endpoints, parallel agents&lt;/td>
&lt;td data-label="Ollama">Single-user or light-homelab chat, model switching, GPU plus CPU offload&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">VRAM on startup&lt;/td>
&lt;td data-label="vLLM">Reserves its KV cache at startup and holds it; on CUDA the default now sizes it from all memory free after warmup (&lt;code>gpu_memory_utilization&lt;/code> 1.0)&lt;/td>
&lt;td data-label="Ollama">Loads a model on first request and unloads it after 5 idle minutes by default (&lt;code>OLLAMA_KEEP_ALIVE&lt;/code>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Model switching&lt;/td>
&lt;td data-label="vLLM">&lt;strong>One model per server process&lt;/strong>; another model means a restart or a second instance&lt;/td>
&lt;td data-label="Ollama">&lt;strong>Loads on demand&lt;/strong>; up to 3 models per GPU stay resident if they fit (&lt;code>OLLAMA_MAX_LOADED_MODELS&lt;/code>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Weight formats&lt;/td>
&lt;td data-label="vLLM">Hugging Face Safetensors (BF16/FP16), &lt;strong>FP8 (W8A8)&lt;/strong>, &lt;strong>AWQ&lt;/strong>, &lt;strong>GPTQ&lt;/strong>; GGUF only through an experimental plugin&lt;/td>
&lt;td data-label="Ollama">&lt;strong>GGUF&lt;/strong> (Q4_K_M, Q5_K_M, Q6_K, Q8_0, IQ4_XS); Safetensors import&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Spilling into system RAM&lt;/td>
&lt;td data-label="vLLM">&lt;code>--cpu-offload-gb&lt;/code>, which the docs say needs a fast CPU-GPU interconnect because offloaded weights cross to the GPU on every forward pass&lt;/td>
&lt;td data-label="Ollama">Splits layers between VRAM and system RAM; &lt;code>ollama ps&lt;/code> shows the split&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Host operating systems&lt;/td>
&lt;td data-label="vLLM">&lt;strong>Linux&lt;/strong>; on Windows through WSL only; NVIDIA, AMD ROCm, Intel XPU and Apple Silicon builds&lt;/td>
&lt;td data-label="Ollama">Native &lt;strong>Windows&lt;/strong>, &lt;strong>macOS&lt;/strong> and &lt;strong>Linux&lt;/strong>, plus Docker&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Default OpenAI endpoint&lt;/td>
&lt;td data-label="vLLM">&lt;code>http://localhost:8000/v1&lt;/code>&lt;/td>
&lt;td data-label="Ollama">&lt;code>http://localhost:11434/v1&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">Authentication&lt;/td>
&lt;td data-label="vLLM">Optional &lt;code>--api-key&lt;/code>, which the docs say does not cover every endpoint&lt;/td>
&lt;td data-label="Ollama">None on the local API&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="why-pagedattention-matters-once-requests-overlap">Why PagedAttention matters once requests overlap&lt;/h2>
&lt;p>When a transformer generates tokens, every active conversation stores key and value (KV) tensors for every prior token in its prompt and reply. Servers that reserve one contiguous chunk of VRAM per request, sized for the longest context it might reach, waste most of it: in the &lt;a href="https://arxiv.org/abs/2309.06180" rel="noopener">SOSP 2023 PagedAttention paper&lt;/a> that launched vLLM, Kwon et al. profiled existing systems in which only 20.4% to 38.2% of KV-cache memory held actual token states. PagedAttention treats GPU memory like virtual memory in an operating system: it cuts the KV cache into small fixed-size blocks, maps each sequence onto blocks as it grows, and lets requests that share a prompt prefix share blocks. In the paper&amp;rsquo;s same comparison, vLLM used 96.3% of its KV-cache memory for token states, and current vLLM turns prefix caching on by default.&lt;/p>
&lt;p>Pair that with iteration-level continuous batching and watch what happens under parallel load:&lt;/p>
&lt;ol>
&lt;li>Request A is 1,800 tokens into decoding; request B arrives with a 500-token system prompt; request C finishes on the next token.&lt;/li>
&lt;li>Instead of waiting for request A to finish, vLLM frees request C&amp;rsquo;s KV blocks and schedules request B into the next forward pass.&lt;/li>
&lt;li>Generating one token at a time is memory-bound, as the paper puts it: it underuses the GPU&amp;rsquo;s compute while weights stream out of VRAM. Batching many active sequences reuses each weight read across all of them, which is where the paper&amp;rsquo;s 2-4x throughput gain over FasterTransformer and Orca, at the same latency, comes from.&lt;/li>
&lt;/ol>
&lt;p>Ollama can process parallel requests too. Its &lt;a href="https://docs.ollama.com/faq" rel="noopener">FAQ documents &lt;code>OLLAMA_NUM_PARALLEL&lt;/code>&lt;/a> (default 1) alongside &lt;code>OLLAMA_MAX_LOADED_MODELS&lt;/code>, and says the memory a model needs scales by OLLAMA_NUM_PARALLEL times OLLAMA_CONTEXT_LENGTH, so every extra slot on a 12GB or 16GB card costs a full context&amp;rsquo;s worth of KV cache. The engine underneath batches too: &lt;a href="https://github.com/ggml-org/llama.cpp/blob/master/tools/server/README.md" rel="noopener">llama.cpp&amp;rsquo;s server&lt;/a> enables continuous batching by default and can share one unified KV buffer across its slots. vLLM&amp;rsquo;s edge is the paged memory management above, built for many callers at once. Conversely, when one person types one prompt at a time, continuous batching has nothing to batch. In my RTX 5080 runs published in &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/">Ollama vs llama.cpp on an RTX 5080&lt;/a> and the &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>, Ollama &lt;code>0.32.1&lt;/code> already pushed &lt;code>319 tok/s&lt;/code> on Llama 3.2 3B and &lt;code>99.4 tok/s&lt;/code> on Qwen 2.5 14B (&lt;code>Q4_K_M&lt;/code>), landing within &lt;code>2–6%&lt;/code> of bare &lt;code>llama-server&lt;/code>. Solo chat hits human reading speed long before server overhead matters. For the desktop-app side of that choice, see &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/">Ollama vs LM Studio on the same card&lt;/a>.&lt;/p>
&lt;h2 id="weight-formats-and-the-12gb-24gb-vram-pinch">Weight formats and the 12GB-24GB VRAM pinch&lt;/h2>
&lt;p>Run your candidate model through our &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">LLM VRAM calculator&lt;/a> and &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">GPU VRAM sizing guide&lt;/a> before picking an engine. Both tools shop in different corners of Hugging Face.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Ollama&amp;rsquo;s GGUF comfort zone (12GB-24GB single GPUs):&lt;/strong> llama.cpp&amp;rsquo;s K-quants give fine-grained steps. Its &lt;a href="https://github.com/ggml-org/llama.cpp/blob/master/tools/quantize/README.md" rel="noopener">quantize README&lt;/a> lists Q4_K_M at about 4.89 bits per weight, Q5_K_M at 5.70 and IQ4_XS at 4.46, which puts a 14B model at roughly 8.6GB of weights in Q4_K_M and a 32B at roughly 19.6GB, leaving room for a single-user KV cache on a 16GB or 24GB card respectively. If a model does spill past your card, Ollama offloads layers to system RAM, slower but still running, and &lt;code>ollama ps&lt;/code> shows the CPU/GPU split.&lt;/li>
&lt;li>&lt;strong>vLLM&amp;rsquo;s BF16, FP8 and AWQ path:&lt;/strong> unquantized BF16 or FP16 weights cost 2 bytes per parameter, so an 8B model is about 16GB before a single token of KV cache. On a 16GB or 24GB card, running 14B-32B models in vLLM with room for concurrent context means 4-bit AWQ or GPTQ weights, or FP8 (W8A8) for 7B-14B models where your GPU supports it; &lt;a href="https://github.com/vllm-project/vllm/blob/v0.34.0/docs/features/quantization/README.md" rel="noopener">vLLM&amp;rsquo;s quantization table&lt;/a> lists FP8 W8A8 for Ada and Hopper cards. Set &lt;code>--max-model-len&lt;/code> explicitly as well: left unset, vLLM takes the context length from the model&amp;rsquo;s config, and &lt;code>auto&lt;/code> picks the largest length that fits in GPU memory.&lt;/li>
&lt;/ul>
&lt;p>Here is a practical single-GPU vLLM Docker launch on Linux or WSL2 (paired with NVIDIA Container Toolkit, covered in our &lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Docker GPU setup guide&lt;/a>) tuned so it coexists cleanly on a &lt;code>16GB&lt;/code> or &lt;code>24GB&lt;/code> homelab card:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker run -d --gpus all &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --name vllm-qwen &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --ipc&lt;span style="color:#f92672">=&lt;/span>host &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -p 127.0.0.1:8000:8000 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -v ~/.cache/huggingface:/root/.cache/huggingface &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> vllm/vllm-openai:v0.34.0 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --model Qwen/Qwen2.5-14B-Instruct-AWQ &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --served-model-name qwen2.5-14b &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --max-model-len &lt;span style="color:#ae81ff">16384&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --gpu-memory-utilization 0.85
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Four flags matter here. &lt;code>-p 127.0.0.1:8000:8000&lt;/code> binds the port to loopback only, so nothing else on your network can reach it; the official example publishes &lt;code>-p 8000:8000&lt;/code> with no host address. &lt;code>--gpu-memory-utilization 0.85&lt;/code> caps vLLM below its 1.0 default so the desktop, and anything you open after vLLM starts, keeps some memory: vLLM measures free memory once, after warmup, and &lt;a href="https://github.com/vllm-project/vllm/blob/v0.34.0/docs/configuration/optimization.md" rel="noopener">its tuning docs&lt;/a> call for a value below 1.0 when other processes share the GPU. &lt;code>--max-model-len 16384&lt;/code> bounds each request&amp;rsquo;s context so the KV pool holds several callers. &lt;code>--served-model-name&lt;/code> gives clients a short alias instead of the slash-separated repo path. The image tag is pinned to the release these flags were read against; &lt;code>latest&lt;/code> moves.&lt;/p>
&lt;p>&lt;strong>Before you open that port to anything but localhost:&lt;/strong> vLLM&amp;rsquo;s docs warn that &lt;code>--api-key&lt;/code> protects only the &lt;code>/v1&lt;/code>, &lt;code>/v2&lt;/code>, &lt;code>/inference&lt;/code> and &lt;code>/cohere&lt;/code> routes, not endpoints such as &lt;code>/invocations&lt;/code>, and recommend hardening such as a reverse proxy in front instead of relying on the key.&lt;/p>
&lt;h2 id="openai-v1chatcompletions-portability">OpenAI &lt;code>/v1/chat/completions&lt;/code> portability&lt;/h2>
&lt;p>Client code barely changes. Both engines speak the OpenAI Chat Completions wire format, as documented in &lt;a href="https://docs.vllm.ai/en/latest/serving/online_serving/openai_compatible_server/" rel="noopener">vLLM&amp;rsquo;s OpenAI-compatible server reference&lt;/a> and &lt;a href="https://docs.ollama.com/api/openai-compatibility" rel="noopener">Ollama&amp;rsquo;s OpenAI compatibility docs&lt;/a>, which means Open WebUI, Continue.dev, Roo/Cline, Home Assistant, and &lt;a href="https://techfuelhq.com/self-hosted/self-hosted-ai-agent-2026/">self-hosted AI agent stacks&lt;/a> can switch backends by changing &lt;code>base_url&lt;/code> and &lt;code>model&lt;/code>:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Ollama:&lt;/strong> &lt;code>OPENAI_BASE_URL=http://127.0.0.1:11434/v1&lt;/code>, with any placeholder key such as &lt;code>OPENAI_API_KEY=ollama&lt;/code>, which Ollama&amp;rsquo;s docs say is required by the client but ignored. The local API has no authentication of its own, so keep it on Ollama&amp;rsquo;s default 127.0.0.1 binding.&lt;/li>
&lt;li>&lt;strong>vLLM:&lt;/strong> &lt;code>OPENAI_BASE_URL=http://127.0.0.1:8000/v1&lt;/code>, with the key you passed to &lt;code>--api-key&lt;/code> if you set one, subject to the route limits above.&lt;/li>
&lt;/ul>
&lt;p>One behavior difference to watch during migration is structured output. vLLM constrains a reply to a JSON schema, regex, choice list or grammar through the &lt;code>structured_outputs&lt;/code> request field or the standard &lt;code>response_format&lt;/code>. If older client code sends &lt;code>guided_json&lt;/code>, &lt;code>guided_regex&lt;/code> or the other &lt;code>guided_*&lt;/code> fields, update it: &lt;a href="https://docs.vllm.ai/en/latest/features/structured_outputs/" rel="noopener">vLLM&amp;rsquo;s structured outputs docs&lt;/a> say those fields were removed in v0.12.0.&lt;/p>
&lt;h2 id="the-clear-decision-rule">The clear decision rule&lt;/h2>
&lt;p>Ignore benchmark tribalism. Decide on concurrency and VRAM residency instead:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Run Ollama&lt;/strong> if your GPU is a Windows desktop, a Mac, or a multipurpose 8GB-24GB homelab card where &lt;strong>one or two people&lt;/strong> alternate between a fast 3B or 8B autocomplete model, a 14B or 32B reasoning GGUF and an embedding model, and you want VRAM freed automatically after 5 idle minutes.&lt;/li>
&lt;li>&lt;strong>Run vLLM&lt;/strong> if you have a dedicated &lt;strong>Linux or WSL2 NVIDIA box&lt;/strong> holding &lt;strong>one primary AWQ, FP8 or BF16 model&lt;/strong> in VRAM around the clock to serve &lt;strong>parallel subagents, batch RAG indexing, evaluation harnesses or several simultaneous household or team users&lt;/strong>, where continuous batching turns memory-bandwidth stalls into parallel throughput.&lt;/li>
&lt;/ul>
&lt;p>Agents are the usual source of that concurrency: each MCP-connected agent loop is another caller, and the &lt;a href="https://techfuelhq.com/self-hosted/best-mcp-servers-homelab-2026/">MCP server benchmark&lt;/a> shows what the tooling side costs in RAM. For which model to serve, the &lt;a href="https://techfuelhq.com/articles/best-local-llm-coding-2026/">local coding model test&lt;/a> covers the 16GB tier, and &lt;a href="https://techfuelhq.com/articles/local-llm-70b-what-it-costs/">what a 70B model costs to run locally&lt;/a> covers the point where one consumer GPU stops being enough.&lt;/p>
&lt;p>If you&amp;rsquo;re weighing more than vLLM, the &lt;a href="https://techfuelhq.com/self-hosted/ollama-alternatives-2026/">full Ollama alternatives comparison&lt;/a> covers seven runtimes.&lt;/p></description></item><item><title>Self-Hosted AI Agent: What It Is and Which to Run (2026)</title><link>https://techfuelhq.com/self-hosted/self-hosted-ai-agent-2026/</link><pubDate>Sat, 12 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/self-hosted-ai-agent-2026/</guid><atom:updated>2026-11-20T20:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Self-hosted AI agent&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>An agent is three layers:&lt;/strong> a runtime (the loop, the tools it may call, the memory it keeps), a model, and the channels it lives in. Self-hosting means the runtime and the memory run on hardware you control.&lt;/li>
&lt;li>&lt;strong>The model is a separate choice.&lt;/strong> Fully local means an open-weight model on your GPU; the same runtime can also call a frontier model over an API. Both count as a self-hosted agent. A managed server someone else runs does not.&lt;/li>
&lt;li>&lt;strong>Start with the runtime that matches the job:&lt;/strong> OpenClaw for an assistant in your chats, OpenHands or a CLI agent for code, n8n's AI Agent node for automations. Pick the model by VRAM last.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Search for this phrase and you get two kinds of page. One is a ranked list of seven tools, rarely with any evidence that the writer runs them. The other is a vendor explaining why its platform is the answer. Neither starts with the question that decides everything: which parts of the agent run on your machine, and which do not. This page answers that first, then names the 2026 runtimes and which job each one fits.&lt;/p>
&lt;h2 id="what-self-hosted-means-for-an-agent-layer-by-layer">What self-hosted means for an agent, layer by layer&lt;/h2>
&lt;p>An LLM on its own answers a prompt. An agent is what wraps it. Strip any of the 2026 runtimes down and you find the same three layers.&lt;/p>
&lt;p>&lt;strong>The runtime.&lt;/strong> A loop that sends the model a goal, reads back a tool call, runs the tool, and feeds the result back until the goal is met. It owns the tool list, the permissions, and the memory that persists between runs. OpenClaw&amp;rsquo;s README describes its version of this as a Gateway, &amp;ldquo;the local control plane for sessions, tools, events, and channel connections.&amp;rdquo; This is the layer that touches your files, your shell, your accounts. It is the layer to self-host.&lt;/p>
&lt;p>&lt;strong>The model.&lt;/strong> The runtime does not care where the model lives. OpenClaw&amp;rsquo;s README puts it plainly. Models and agent harnesses, Claude, Codex and local models among them, &amp;ldquo;are plugins you can swap without changing anything else.&amp;rdquo; A local open-weight model on your GPU and a frontier model over an API plug into the same loop. The difference is where your prompts go, what it costs per token, and how smart the answers are.&lt;/p>
&lt;p>&lt;strong>The channels and tools.&lt;/strong> Chat platforms, a browser, a code editor, a database, MCP servers. OpenClaw&amp;rsquo;s README names Discord, iMessage, Slack, Teams, Telegram, WhatsApp, plus &amp;ldquo;20+ more.&amp;rdquo; Each connection is a credential the runtime holds on your behalf, and each MCP server is resident memory too: the site&amp;rsquo;s &lt;a href="https://techfuelhq.com/self-hosted/best-mcp-servers-homelab-2026/">MCP server benchmark&lt;/a> measured 178 to 422 MB per server.&lt;/p>
&lt;p>So the definition I use is short. A self-hosted AI agent is an agent runtime and its memory running on hardware you control. The model can be local or rented. If the runtime runs on a server someone else administers for you, it is hosted, whatever the marketing says; a managed OpenClaw box is a fine product and it is not this.&lt;/p>
&lt;h2 id="the-three-configurations-and-which-one-is-yours">The three configurations, and which one is yours&lt;/h2>
&lt;p>&lt;strong>Fully local.&lt;/strong> Runtime, memory, model, all on your box. Nothing leaves. The cost is a GPU with enough VRAM for a model good enough to drive tools reliably. On my RTX 5080, which has 16 GB, the site&amp;rsquo;s &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">throughput dataset&lt;/a> measured gpt-oss 20B decoding at 178 to 190 tokens per second with ollama 0.32.1, Qwen 2.5 14B at 94 to 97, and Llama 3.2 3B at 298 to 313, each the median of three runs. Those are comfortable speeds for an agent loop. The catch is quality: in the &lt;a href="https://techfuelhq.com/articles/best-local-llm-coding-2026/">coding eval on the same card&lt;/a>, gpt-oss 20B swept the eight tasks at the 16 GB tier, and that is the ceiling of what fits without spilling to system RAM. The &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">VRAM-tier guide&lt;/a> maps the rest.&lt;/p>
&lt;p>Which server runs that local model is its own choice. &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/">Ollama vs llama.cpp&lt;/a> and &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/">Ollama vs LM Studio&lt;/a> compare the common single-user options on the same card, and &lt;a href="https://techfuelhq.com/self-hosted/vllm-vs-ollama-2026/">vLLM vs Ollama&lt;/a> covers one model serving several agents at once. For a voice assistant on the same stack, see the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-local-llm-voice-2026/">Home Assistant local LLM guide&lt;/a>.&lt;/p>
&lt;p>&lt;strong>Local runtime, rented model.&lt;/strong> Runtime, memory, tool gates and credentials on your box; the model over an API. Your prompts leave, your files and keys do not, and you get frontier-model quality for tool use. It is the configuration most of the &amp;ldquo;self-hosted agent&amp;rdquo; tutorials quietly assume when they show an API key in the config.&lt;/p>
&lt;p>&lt;strong>Hosted, called self-hosted.&lt;/strong> A vendor&amp;rsquo;s cloud runs the runtime for you. Dify&amp;rsquo;s homepage is clear about its three options: Dify Cloud, &amp;ldquo;Hosted by Dify&amp;rdquo;; Enterprise, &amp;ldquo;Self-host or run in your VPC&amp;rdquo;; and a source-available Community Edition you &amp;ldquo;Self-host with Docker.&amp;rdquo; Ollama&amp;rsquo;s homepage now offers open models &amp;ldquo;locally or in the cloud,&amp;rdquo; with a pricing page beside the download. Read the deploy line before you believe the adjective.&lt;/p>
&lt;h2 id="the-runtimes-people-mean-in-2026">The runtimes people mean in 2026&lt;/h2>
&lt;p>Every row was re-read on 2026-11-18. The star count and version are what the pages showed that day.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Runtime&lt;/th>
&lt;th scope="col">What it is&lt;/th>
&lt;th scope="col">Model&lt;/th>
&lt;th scope="col">Self-hosting shape&lt;/th>
&lt;th scope="col">Source&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Runtime">OpenClaw&lt;/td>
&lt;td data-label="What it is">Personal assistant that lives in your chat apps; one Gateway plus native apps&lt;/td>
&lt;td data-label="Model">Plugins: Claude, Codex, local models&lt;/td>
&lt;td data-label="Self-hosting shape">Install script provisions Node.js (the npm package needs Node 24.16+ or 26.1+); about 395k GitHub stars; stewarded by the OpenClaw Foundation, an independent 501(c)(3) with no paid tier&lt;/td>
&lt;td data-label="Source">&lt;a href="https://github.com/openclaw/openclaw" rel="noopener">README&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">OpenHands&lt;/td>
&lt;td data-label="What it is">Coding-agent platform: the open-source Agent Canvas client, a Python Agent SDK, plus Cloud and Enterprise tiers&lt;/td>
&lt;td data-label="Model">Your choice via config&lt;/td>
&lt;td data-label="Self-hosting shape">Agent Canvas installs locally with npm, npx or Docker; Enterprise sells licensed self-hosting; its own June 2026 post ranks seven self-hosted coding agents&lt;/td>
&lt;td data-label="Source">&lt;a href="https://docs.openhands.dev/overview/introduction" rel="noopener">Docs&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">n8n AI Agent node&lt;/td>
&lt;td data-label="What it is">An agent step inside a visual workflow automation; it needs at least one tool sub-node&lt;/td>
&lt;td data-label="Model">Any connected chat model&lt;/td>
&lt;td data-label="Self-hosting shape">Runs wherever your n8n runs&lt;/td>
&lt;td data-label="Source">&lt;a href="https://docs.n8n.io/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.agent/" rel="noopener">Docs&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">Dify&lt;/td>
&lt;td data-label="What it is">&amp;ldquo;AI Agent Management Platform that Puts You in Control&amp;rdquo;&lt;/td>
&lt;td data-label="Model">Providers from its Marketplace or custom&lt;/td>
&lt;td data-label="Self-hosting shape">Dify Cloud, Enterprise (self-host or VPC), or the source-available Community Edition on Docker&lt;/td>
&lt;td data-label="Source">&lt;a href="https://dify.ai/" rel="noopener">Site&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">LangGraph&lt;/td>
&lt;td data-label="What it is">A &amp;ldquo;low-level orchestration framework and runtime for long-running, stateful agents&amp;rdquo;&lt;/td>
&lt;td data-label="Model">Any&lt;/td>
&lt;td data-label="Self-hosting shape">Code you host yourself&lt;/td>
&lt;td data-label="Source">&lt;a href="https://docs.langchain.com/oss/python/langgraph/overview" rel="noopener">Overview&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">CrewAI&lt;/td>
&lt;td data-label="What it is">Builds &amp;ldquo;collaborative AI agents, crews, and flows&amp;rdquo;&lt;/td>
&lt;td data-label="Model">Any&lt;/td>
&lt;td data-label="Self-hosting shape">Code you host yourself; the docs also describe an Enterprise console&lt;/td>
&lt;td data-label="Source">&lt;a href="https://docs.crewai.com/" rel="noopener">Docs&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">LocalAI&lt;/td>
&lt;td data-label="What it is">Open-source, MIT-licensed runtime, release 4.12.1, to &amp;ldquo;Run open models for chat, images, speech and video on your own machines&amp;rdquo;&lt;/td>
&lt;td data-label="Model">Local&lt;/td>
&lt;td data-label="Self-hosting shape">Your own hardware, behind an API in OpenAI and Anthropic formats&lt;/td>
&lt;td data-label="Source">&lt;a href="https://localai.io/" rel="noopener">Site&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Runtime">Ollama&lt;/td>
&lt;td data-label="What it is">The model runtime most of the above call for local inference; not an agent itself&lt;/td>
&lt;td data-label="Model">Local open-weight, or Ollama&amp;rsquo;s cloud&lt;/td>
&lt;td data-label="Self-hosting shape">Download for your OS; the &lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Docker-with-GPU tutorial&lt;/a> covers the Linux and WSL2 path&lt;/td>
&lt;td data-label="Source">&lt;a href="https://ollama.com/" rel="noopener">Site&lt;/a>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two things the table settles. Ollama and LocalAI are model layers rather than agents, and every agent runtime on the list can point at them. And OpenClaw is the one built for a person rather than a developer; its whole pitch is that the agent meets you in the chat you already use.&lt;/p>
&lt;h2 id="security-in-one-paragraph">Security in one paragraph&lt;/h2>
&lt;p>An agent that can run tools can run the wrong tool. OpenClaw&amp;rsquo;s README says it without softening: &amp;ldquo;Tools run on the host for the main session unless you configure sandboxing,&amp;rdquo; followed by a security guide, an exposure runbook and a sandboxing guide to read &amp;ldquo;before connecting other users or exposing the Gateway remotely.&amp;rdquo; The model layer needs the same care: Ollama&amp;rsquo;s documentation says its local API at localhost:11434 does not require authentication, so leave it on the default 127.0.0.1 binding rather than opening it to your network. Whatever you install, decide what it may touch before you hand it a credential, keep the control plane off the public internet, and treat every chat channel you connect as a door.&lt;/p>
&lt;h2 id="what-to-run-first">What to run first&lt;/h2>
&lt;p>Pick by the job rather than the star count.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>You want an assistant in Discord, Telegram or WhatsApp.&lt;/strong> OpenClaw. One install script that provisions Node.js for you, and it meets you in the chat you already use. Read its security guide first.&lt;/li>
&lt;li>&lt;strong>You want an agent that writes code in your repositories.&lt;/strong> OpenHands, or a CLI coding agent. The coding eval on this site says which local model is worth pointing it at on a 16 GB card.&lt;/li>
&lt;li>&lt;strong>You want automations that call a model as one step.&lt;/strong> n8n&amp;rsquo;s AI Agent node on a self-hosted n8n stack.&lt;/li>
&lt;li>&lt;strong>You are building something custom.&lt;/strong> LangGraph or CrewAI, and you host the result.&lt;/li>
&lt;li>&lt;strong>You want zero bytes leaving the house.&lt;/strong> Any of the above pointed at Ollama or LocalAI, sized by the &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">VRAM-tier guide&lt;/a>, on hardware from the &lt;a href="https://techfuelhq.com/articles/self-hosted-ai-stack-2026/">self-hosted AI stack&lt;/a> page.&lt;/li>
&lt;/ul>
&lt;p>Whichever you choose, the layer worth owning is the one that holds your keys and your memory. Host that. Rent the model until your GPU says otherwise.&lt;/p></description></item><item><title>LM Studio vs Ollama (2026): Measured Speed and RAM</title><link>https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/</link><pubDate>Wed, 26 Aug 2026 15:20:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/</guid><atom:updated>2026-11-20T20:00:00Z</atom:updated><description>&lt;p>Depending on which search result you trust, LM Studio is 46% faster than Ollama,
10-20% slower, or exactly the same speed. The Reddit thread that ranks first for
this query carries &amp;ldquo;3-4x faster&amp;rdquo; claims for Ollama, while a Stack Exchange question
a few results down asks why Ollama&amp;rsquo;s models run faster inside LM Studio.&lt;/p>
&lt;p>Those claims cannot all be true on the same computer, so I put both apps on mine: one RTX 5080.
For the two dense models, both loaded the same GGUF file. Hard-linked, sha256-verified, the same bytes on disk. The gpt-oss builds used different conversions.
I measured generation five times per configuration, at stock settings and again with settings matched.&lt;/p>
&lt;p>With settings matched, the decode rates stayed within 14% of each other. Moving
Ollama&amp;rsquo;s context slider cut the 3B model&amp;rsquo;s speed from 351 to 102 tokens per second.&lt;/p>
&lt;p>Everything here is Windows on an NVIDIA card. I have not tested a Mac or MLX, which is where the loudest &amp;ldquo;LM Studio is faster&amp;rdquo; claims come from.&lt;/p>
&lt;p>Every figure below is from August 26, 2026: Ollama 0.32.15 against LM Studio 0.4.21. On November 18, Ollama&amp;rsquo;s newest release was &lt;a href="https://github.com/ollama/ollama/releases" rel="noopener">0.40.16&lt;/a> and LM Studio&amp;rsquo;s &lt;a href="https://lmstudio.ai/download" rel="noopener">download page&lt;/a> offered 0.4.28. Neither newer version has been benchmarked here, so read the speed gaps as a dated snapshot. For the settings traps further down, Ollama&amp;rsquo;s &lt;a href="https://docs.ollama.com/context-length" rel="noopener">context-length docs&lt;/a> still describe the same app slider and the same 4k default for cards under 24 GiB.&lt;/p>
&lt;h2 id="the-verdict-by-use-case">The verdict, by use case&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">You want&lt;/th>
&lt;th scope="col">Run&lt;/th>
&lt;th scope="col">Why, measured&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="You want">A background service, API, scripting, Docker&lt;/td>
&lt;td data-label="Run">&lt;strong>Ollama&lt;/strong>&lt;/td>
&lt;td data-label="Why, measured">5-11% faster dense decode, 78-132 MB idle RAM, headless by design&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want">A GUI, model browser, per-model tuning&lt;/td>
&lt;td data-label="Run">&lt;strong>LM Studio&lt;/strong>&lt;/td>
&lt;td data-label="Why, measured">The interface is the product; decode within 5-11% of Ollama&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want">Fastest gpt-oss 20B on 16 GB&lt;/td>
&lt;td data-label="Run">&lt;strong>LM Studio + upstream GGUF&lt;/strong>&lt;/td>
&lt;td data-label="Why, measured">242.8 vs 213.7 t/s, engine and conversion differences both in play&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want">Long prompts, RAG, big context ingestion&lt;/td>
&lt;td data-label="Run">&lt;strong>LM Studio&lt;/strong>&lt;/td>
&lt;td data-label="Why, measured">Prefill 5-14% faster on every model tested&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want">Both at once&lt;/td>
&lt;td data-label="Run">&lt;strong>Fine&lt;/strong>&lt;/td>
&lt;td data-label="Why, measured">Ran simultaneously on ports 11434/1234, 7,000 MiB total VRAM with two 3Bs&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="how-long-until-the-first-short-reply">How long until the first short reply?&lt;/h2>
&lt;!-- timing-release:start -->
&lt;p>If you unload a model between jobs, count from before it loads. On Llama 3.2 3B, LM Studio spent 2.76 s loading and 0.07 s on the first request. The two rounded readings add to about 2.83 s. Ollama’s 2.38 s request already includes 2.27 s of loading.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Model and app&lt;/th>
&lt;th scope="col" style="text-align: right">Unloaded to first completed short reply&lt;/th>
&lt;th scope="col" style="text-align: right">Generating 256 tokens with model resident&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Model and app">Llama 3.2 3B · Ollama&lt;/td>
&lt;td style="text-align: right" data-label="Unloaded to first completed short reply">2.38 s, load included&lt;/td>
&lt;td style="text-align: right" data-label="Generating 256 tokens with model resident">0.73 s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model and app">Llama 3.2 3B · LM Studio&lt;/td>
&lt;td style="text-align: right" data-label="Unloaded to first completed short reply">2.76 + 0.07 ≈ 2.83 s&lt;/td>
&lt;td style="text-align: right" data-label="Generating 256 tokens with model resident">0.81 s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model and app">Qwen 2.5 14B · Ollama&lt;/td>
&lt;td style="text-align: right" data-label="Unloaded to first completed short reply">5.68 s, load included&lt;/td>
&lt;td style="text-align: right" data-label="Generating 256 tokens with model resident">2.50 s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model and app">Qwen 2.5 14B · LM Studio&lt;/td>
&lt;td style="text-align: right" data-label="Unloaded to first completed short reply">7.68 + 0.16 ≈ 7.84 s&lt;/td>
&lt;td style="text-align: right" data-label="Generating 256 tokens with model resident">2.62 s&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Both servers were already running, the filesystem cache was warm, and context was 4,096 tokens. I made one nonstreaming request per row, capped at eight output tokens. LM Studio used a separate CLI load before its chat request; no single timer spanned both stages. These times exclude app launch and cold disk reads.&lt;/p>
&lt;p>With Qwen resident, the gap was about 0.12 seconds per 256-token generation on this card. The right column takes the median of five runs, dividing the actual output count by each run’s decode rate. It excludes loading and prompt processing.&lt;/p>
&lt;p>For the first word to appear, time a streaming client. LM Studio reported resident server time to first token of 9.2 ms for Llama and 24.7 ms for Qwen. The Ollama capture has no matching reading; neither app measured first visible text.&lt;/p>
&lt;p>Download the &lt;a href="https://techfuelhq.com/data/lmstudio-ollama-startup-2026-08-26/observations.json" download type="application/json">four startup observations and 20 resident runs&lt;/a> and &lt;a href="https://techfuelhq.com/data/lmstudio-ollama-startup-2026-08-26/replay.py">offline replay&lt;/a> together. Run &lt;code>python replay.py&lt;/code> to reproduce the table. The extract supplies capture filenames and GGUF hashes; the &lt;a href="https://techfuelhq.com/data/llm-server-compare/">source dataset&lt;/a> is available under CC BY 4.0.&lt;/p>
&lt;p>&lt;strong>Timing export 1.0.0.&lt;/strong> Download the &lt;a href="https://techfuelhq.com/data/lmstudio-ollama-startup-2026-08-26/timing.csv" download type="text/csv">timing CSV&lt;/a> and &lt;a href="https://techfuelhq.com/data/lmstudio-ollama-startup-2026-08-26/timing.json" download type="application/json">JSON&lt;/a>. The &lt;a href="https://techfuelhq.com/data/evidence-releases/lmstudio-ollama-startup.json" download type="application/json">correction record&lt;/a> links the exact revision of both files and identifies the source measurements. The &lt;a href="https://techfuelhq.com/data/evidence-releases/index.json" download type="application/json">change register&lt;/a> lists other versioned corrections.&lt;/p>
&lt;!-- timing-release:end -->
&lt;h2 id="what-people-claim-vs-what-i-measured">What people claim vs what I measured&lt;/h2>
&lt;p>The top of this search results page disagrees with itself. The r/LocalLLaMA thread
that ranks first carries claims of Ollama being &amp;ldquo;3-4x&amp;rdquo; faster; a Medium post and
Codiste both say Ollama wins by 10-20%; atomic.chat says LM Studio generates 46%
faster; tech-insider.org titles its piece &amp;ldquo;Zero Performance Difference [Tested]&amp;rdquo;,
then prints Qwen 2.5 14B Q4_K_M at 25-30 tokens/sec on an RTX 4090, attributed to
community benchmarks.&lt;/p>
&lt;p>Every one of those pages is linked in the Sources block. My
RTX 5080 measures that exact model and quant at 97-102 t/s in both apps. Three to
four times their 4090 figure. A different machine and unknown settings on their
side, granted, and that is precisely the problem — this argument runs on numbers
nobody measured under stated conditions.&lt;/p>
&lt;p>With settings matched (context 4096, full GPU offload, temperature 0, seed 42, one
serving slot, medians of five fresh-prompt runs):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Model&lt;/th>
&lt;th scope="col">App&lt;/th>
&lt;th scope="col" style="text-align: right">Decode&lt;/th>
&lt;th scope="col" style="text-align: right">Prefill (~450 tok)&lt;/th>
&lt;th scope="col" style="text-align: right">GPU mem (MiB)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 3B&lt;/td>
&lt;td data-label="App">Ollama 0.32.15&lt;/td>
&lt;td style="text-align: right" data-label="Decode">&lt;strong>350.5 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Prefill (~450 tok)">17,862 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">3,760&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 3B&lt;/td>
&lt;td data-label="App">LM Studio 0.4.21&lt;/td>
&lt;td style="text-align: right" data-label="Decode">316.0 t/s&lt;/td>
&lt;td style="text-align: right" data-label="Prefill (~450 tok)">&lt;strong>20,337 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">3,808&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Qwen 2.5 14B&lt;/td>
&lt;td data-label="App">Ollama 0.32.15&lt;/td>
&lt;td style="text-align: right" data-label="Decode">&lt;strong>102.2 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Prefill (~450 tok)">5,038 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">10,356&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Qwen 2.5 14B&lt;/td>
&lt;td data-label="App">LM Studio 0.4.21&lt;/td>
&lt;td style="text-align: right" data-label="Decode">97.6 t/s&lt;/td>
&lt;td style="text-align: right" data-label="Prefill (~450 tok)">&lt;strong>5,567 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">10,405&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">gpt-oss 20B²&lt;/td>
&lt;td data-label="App">Ollama 0.32.15&lt;/td>
&lt;td style="text-align: right" data-label="Decode">213.7 t/s&lt;/td>
&lt;td style="text-align: right" data-label="Prefill (~450 tok)">9,187 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">13,570&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">gpt-oss 20B²&lt;/td>
&lt;td data-label="App">LM Studio 0.4.21&lt;/td>
&lt;td style="text-align: right" data-label="Decode">&lt;strong>242.8 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Prefill (~450 tok)">&lt;strong>9,618 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">12,533&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>² Different conversions of the same model, because they have to be: Ollama ships its
own gpt-oss blob and LM Studio runs the ggml-org upstream MXFP4 file. More on that
below.&lt;/p>
&lt;p>Ollama decodes faster on dense models, by 10.9% on the 3B and 4.7% on the 14B. LM Studio
prefills faster on everything I tested and wins the MoE outright.&lt;/p>
&lt;p>Each side wins one
event, which is the same shape my &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/">Ollama vs llama.cpp bench&lt;/a>
found six days earlier, and none of it justifies &amp;ldquo;3-4x&amp;rdquo; folklore. The per-run
decode arrays, VRAM, RAM, LM Studio TTFT medians, and load times are in the
&lt;a href="https://techfuelhq.com/data/llm-server-compare/">same-GPU compare dataset&lt;/a>, CC BY 4.0.&lt;/p>
&lt;h2 id="same-engine-underneath-same-process-name">Same engine underneath, same process name&lt;/h2>
&lt;p>The process tables captured with every run show the same thing on both sides: the
model being served by a &lt;code>llama-server.exe&lt;/code> process — Ollama&amp;rsquo;s from its install
directory, LM Studio&amp;rsquo;s from its backend extension directory. Both
apps are packaging around llama.cpp&amp;rsquo;s server, which is why the dense-model numbers
land within 11% of each other and why &amp;ldquo;which app is faster&amp;rdquo; is mostly a question
about versions and defaults.&lt;/p>
&lt;p>The versions matter more than the wrapper. Ollama 0.32.15 runs its vendored
llama.cpp at commit 9d77fa172; LM Studio 0.4.21 downloaded its llama.cpp runtime
2.29.1 on first launch. The installer shipped 2.28.2 engines, still on disk next to the newer one.&lt;/p>
&lt;p>The
app updated itself before I ran anything. Worth knowing
if you pin versions for reproducibility. Six days and fourteen patch-version
increments separate my two captures of Ollama on this rig, and its 3B decode moved
from 319 t/s (0.32.1, August 20) to 351 (0.32.15, August 26).&lt;/p>
&lt;p>Some of that is
engine updates. Some may be capture-window conditions, since the earlier run
predates the quiet-window discipline described in the method. By the time I
finished writing, Ollama had already promoted 0.33.0. Any LM-Studio-vs-Ollama
benchmark without version numbers is a screenshot of a moving target.&lt;/p>
&lt;h2 id="the-defaults-are-the-real-story">The defaults are the real story&lt;/h2>
&lt;p>The plan for this piece treated &amp;ldquo;defaults as installed&amp;rdquo; and &amp;ldquo;settings normalized&amp;rdquo;
as separate test conditions on the expectation that packaging differences would
show up in the numbers, and the dense models shrugged at every bit of it: Qwen 2.5
14B ran 98.2 t/s at LM Studio&amp;rsquo;s stock settings and 97.6 normalized while the 3B
moved about 1%. When the model fits comfortably, stock settings are fine. Stop
tuning.&lt;/p>
&lt;p>Two defaults are not fine, and both fail silently.&lt;/p>
&lt;p>&lt;strong>LM Studio&amp;rsquo;s automatic GPU offload quietly benched gpt-oss at 186 t/s&lt;/strong> — 23%
below the 243 the same app hits with settings tuned. Stock, LM Studio loads
models at 8,192 context across 4 parallel slots with GPU offload on &amp;ldquo;auto&amp;rdquo;, and
my first normalized pass changed all three at once. So I re-ran the stock
configuration changing only the offload slider, nothing else.&lt;/p>
&lt;p>Result: 244.9 t/s,
the entire gap, from one setting. Context length and slot count contributed
nothing measurable. On a 16 GB card, auto had chosen to hold part of the MoE&amp;rsquo;s
weights on the CPU, and no warning appears anywhere. Setting GPU offload to max
was worth 31% on this card.&lt;/p>
&lt;p>&lt;strong>Ollama&amp;rsquo;s context slider is a 3.4x foot-gun.&lt;/strong> Ollama&amp;rsquo;s documented default for a
16 GB card is a 4,096-token context, and at that default the 3B decodes at 351 t/s,
100% GPU-resident. This machine&amp;rsquo;s Ollama had its app-settings context slider at
256k from earlier use, a value Ollama clamps to this model&amp;rsquo;s 131,072-token
maximum. Still far past what fits.&lt;/p>
&lt;p>With nothing else changed, the same 2 GB model loaded
an 18 GB footprint, split 22%/78% across CPU and GPU, and decoded at 102 t/s. A
3.4x slowdown from one setting, and &lt;code>ollama ps&lt;/code> is the only place that shows you
why. I would bet money this explains a large share of the &amp;ldquo;Ollama was crawling for
me&amp;rdquo; posts in that Reddit thread; it is also presumably invisible to anyone
benchmarking only fresh installs.&lt;/p>
&lt;p>If one number from this page survives in your memory, make it this pair. The gap
between these two apps is at most 14%. The gap between a good and a bad memory
setting is 240%.&lt;/p>
&lt;h2 id="memory-vram-is-a-tie-ram-is-not">Memory: VRAM is a tie, RAM is not&lt;/h2>
&lt;p>Wherever both apps loaded the identical file, GPU memory matched within 50 MiB —
3,760 vs 3,808 on the 3B, 10,356 vs 10,405 on the 14B. Same bytes, same engine,
same memory.&lt;/p>
&lt;p>These are whole-card readings with the Windows desktop included. The
&lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download type="text/csv">capture CSV&lt;/a> records 1,053-1,122 MiB
in use before each load, against a 1,642 MiB desktop baseline in the
&lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/">llama.cpp comparison&lt;/a>. That is why the
same 3B reads 3,760 MiB on Ollama here and 4,343 MiB there: subtract each baseline and
the model&amp;rsquo;s own footprint is about 2,700 MiB both times. The gpt-oss row differs by 1,037 MiB because the conversions differ;
Ollama&amp;rsquo;s fork has allocated about a gigabyte more than upstream in every capture
I have run, on either engine.&lt;/p>
&lt;p>System RAM is where the apps genuinely part ways. Idle with no model, the Ollama
service tree held 78-132 MB across my checks; LM Studio&amp;rsquo;s GUI and server held
709-928 MB across the quiet-window observations (one transitional reading hit
3.1 GB mid-unload and is excluded as a non-idle state; it is in the raw JSON).&lt;/p>
&lt;p>Loaded, LM Studio&amp;rsquo;s runtime keeps the memory-mapped model file hot in its working
set. With gpt-oss resident, its process tree reported about 13 GB of RAM alongside
the 12.5 GB of VRAM, where Ollama&amp;rsquo;s runner released its mapping and sat near
2.1 GB.&lt;/p>
&lt;p>Mapped file pages are evictable cache, so this is not a hard requirement,
but on a machine with 16-32 GB of RAM running other work, Ollama is the lighter
tenant: five to six times lighter loaded, five to twelve times lighter idle.
tech-insider.org&amp;rsquo;s &amp;ldquo;5x Memory Gap&amp;rdquo; headline has the right direction and, at idle,
roughly the right magnitude; the spread depends mostly on what the Electron GUI
is doing.&lt;/p>
&lt;p>Load times were closer than I expected: 2.3-2.8s for the 3B on both apps, 5.5s vs
7.7s on the 14B, 8.1s vs 8.4s on gpt-oss, warm caches throughout.&lt;/p>
&lt;p>Those are the rounded model-load timers from the &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download type="text/csv">normalized rows in the original CSV&lt;/a>, in Ollama then LM Studio order. The gpt-oss files used different conversions. For the two matching dense models, the &lt;a href="#how-long-until-the-first-short-reply">first-reply comparison&lt;/a> separates loading from request time.&lt;/p>
&lt;h2 id="the-portability-catch-travels">The portability catch travels&lt;/h2>
&lt;p>My llama.cpp piece found that Ollama&amp;rsquo;s gpt-oss:20b blob declares architecture
&lt;code>gptoss&lt;/code>, which upstream llama.cpp rejects. LM Studio reproduces the refusal
verbatim: importing the blob works, the file indexes, and loading it dies with
&lt;code>unknown model architecture: 'gptoss'&lt;/code> from its 2.29.1 runtime. So the one model
Ollama co-launched still cannot leave Ollama, now confirmed against two external
consumers of the file.&lt;/p>
&lt;p>Everything else travels beautifully. &lt;code>lms import&lt;/code> took Ollama&amp;rsquo;s Llama 3.2 and
Qwen 2.5 blobs by path, and with the hard-link option both apps share one physical
copy of the weights. I verified it: each blob shows a link count of three (Ollama&amp;rsquo;s
store, my staging copy, LM Studio&amp;rsquo;s models directory all naming the same bytes),
and the files hash identically to Ollama&amp;rsquo;s own blob digests.&lt;/p>
&lt;p>The listings ship
with the raw evidence. In the other direction, Ollama
imports any GGUF with a one-line Modelfile (&lt;code>FROM /path/to/file.gguf&lt;/code> and
&lt;code>ollama create&lt;/code>), though it copies rather than links. Running both apps against
one model library costs you nothing but the gpt-oss exception.&lt;/p>
&lt;h2 id="which-one-belongs-on-your-machine">Which one belongs on your machine&lt;/h2>
&lt;p>Run Ollama when the model is infrastructure: a service that starts at boot, feeds
&lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Docker containers&lt;/a>, answers on 11434 from
&lt;a href="https://techfuelhq.com/articles/self-hosted-ai-stack-2026/">whatever stack you build on it&lt;/a>, and stays
out of RAM when idle. The local-LLM tutorials on this site ride on it for exactly
that reason, and its dense-decode edge is real if modest. If several agents or users
will hit one model at the same time, read &lt;a href="https://techfuelhq.com/self-hosted/vllm-vs-ollama-2026/">vLLM vs Ollama&lt;/a>
before you settle on either app.&lt;/p>
&lt;p>Run LM Studio when the model is an appliance: you want to browse Hugging Face
quants visually, flip a sampling parameter without editing a Modelfile, watch
token streams in a chat pane, and still get an OpenAI-compatible server on 1234
when an app needs one. Its per-model load settings are the granular control Ollama
hides behind environment variables, the same control that makes the auto-offload
default worth checking before you benchmark anything.&lt;/p>
&lt;p>Run both when the fits above split your week. They coexist on one card, share
model files one direction cleanly, and the second app costs you a few hundred
megabytes of idle RAM. Measured with both 3Bs resident: 7,000 MiB of total GPU
memory including the desktop&amp;rsquo;s ~1.1 GB baseline, and sequential requests answered
at 298 and 230 t/s.&lt;/p>
&lt;p>That is lower than the solo medians, though those coexistence
runs capped generation at 64 tokens, so they are not directly comparable to the
256-token table above. My &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">VRAM calculator&lt;/a>
and &lt;a href="https://techfuelhq.com/tools/llm-speed-calculator/">speed calculator&lt;/a> both apply unchanged to either
app, because underneath they are the same engine. That is the finding of this whole
exercise. Pick by workflow. Fix your settings. The
&lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">by-GPU model guide&lt;/a> covers what fits in
your VRAM either way, and the &lt;a href="https://techfuelhq.com/articles/best-local-llm-coding-2026/">local coding model test&lt;/a>
covers which model is worth loading on a 16 GB card.&lt;/p>
&lt;h2 id="method-and-limits">Method and limits&lt;/h2>
&lt;p>Both apps measured 2026-08-26 on the same box, an RTX 5080 16 GB on driver 610.88
under Windows 11. Ollama 0.32.15, upgraded from 0.32.1 the same morning — the
newest release at bench time, with 0.33.0 promoted while this was being written
and not tested here. LM Studio 0.4.21, installed fresh that morning, runtime
self-updated to llama.cpp-cuda12 2.29.1.&lt;/p>
&lt;p>Models: Llama 3.2 3B Q4_K_M (blob dde5aa3fc5ff…),
Qwen 2.5 14B Q4_K_M (blob 2049f5674b1e…), gpt-oss 20B MXFP4 — Ollama&amp;rsquo;s blob
e7b273f96360… on its side, ggml-org&amp;rsquo;s upstream file on LM Studio&amp;rsquo;s side, whose
sha256 27cd6c432c76… matches the hash Hugging Face publishes. Rates come from each
app&amp;rsquo;s own counters (Ollama&amp;rsquo;s eval fields; LM Studio&amp;rsquo;s /api/v0 stats), cross-checked
by wall-clock recomputation.&lt;/p>
&lt;p>Decode figures are medians of five runs, long-prefill
figures medians of three (a fourth warmup run is discarded), every run carrying a
unique prompt nonce to defeat prompt caches. The gpt-oss offload finding was
re-verified with a single-variable run — stock configuration, only the offload
slider moved — recorded with the rest of the raw JSON.&lt;/p>
&lt;p>LM Studio&amp;rsquo;s prefill rate is derived from
time-to-first-token minus one decoded token, because its API does not split prompt
evaluation out the way Ollama&amp;rsquo;s does; the long-prefill TTFTs live in the raw JSON
captures if you want to re-derive. One app under test at a time, the other fully killed, except in
the coexistence check.&lt;/p>
&lt;p>What I did not test: Mac and MLX (where the loudest &amp;ldquo;LM Studio is faster&amp;rdquo; claims
come from, and where nothing on this page applies), AMD cards, multi-GPU, LM
Studio&amp;rsquo;s chat UI as opposed to its server, concurrent multi-request serving, and
NVFP4 quantization — no NVFP4 conversion of this model set existed to test.&lt;/p>
&lt;p>Mid-capture I caught
a background indexing job on my own machine depressing 3B decode by 15%; it was
suspended and every published number re-measured on a quiet system, which is one
more reason to distrust any benchmark that does not say what else the box was
doing.&lt;/p>
&lt;p>All raw JSON captures live in the repo, and the
&lt;a href="https://techfuelhq.com/data/llm-server-compare/">dataset page&lt;/a> is the citable record. These numbers
carry version stamps because they moved 3-10% in two weeks on one of the apps
alone; date everything, including mine.&lt;/p></description></item><item><title>Self-Hosted SSO Tracker: Which Login Methods Cost Extra?</title><link>https://techfuelhq.com/self-hosted/self-hosted-sso-tax-2026/</link><pubDate>Wed, 26 Aug 2026 14:45:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/self-hosted-sso-tax-2026/</guid><atom:updated>2026-11-20T20:00:00Z</atom:updated><description>&lt;p>The &amp;ldquo;SSO tax&amp;rdquo; is the extra you pay for single sign-on (SSO). The &lt;a href="https://sso.tax/" rel="noopener">sso.tax list&lt;/a> describes vendors that &amp;ldquo;gate SSO behind an &amp;lsquo;Enterprise&amp;rsquo; paywall,&amp;rdquo; bundled with features you may not need or large minimum seat counts. Self-hosted software does it too: the free edition signs people in with local passwords, and SAML or OpenID Connect (OIDC) waits in a paid one. This tracker compares 17 self-hosted apps by edition and price.&lt;/p>
&lt;p>The short answer, from the November 4 rows:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Free routes:&lt;/strong> Zulip (SAML and OIDC on the free self-hosted plan), BookStack, Paperless-ngx, Vikunja and Vaultwarden (OIDC), and Nextcloud (a SAML app).&lt;/li>
&lt;li>&lt;strong>Edition or plan restrictions:&lt;/strong> Grafana, Mattermost, Metabase, Teleport, Passbolt, Bitwarden, n8n, Plane, OpenProject, PLANKA and Seafile. Seafile&amp;rsquo;s is the gentlest: its Pro edition is free for up to three users.&lt;/li>
&lt;li>&lt;strong>Changed since:&lt;/strong> Rocket.Chat 9.0.0, released November 10, moved LDAP, SAML and custom OAuth to premium plans. &lt;a href="#rocketchat-check-the-release-before-upgrading">Jump to the Rocket.Chat upgrade check&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>Before you pay for SSO, write down the protocol your identity provider needs. Grafana charges for &lt;a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-authentication/saml/" rel="noopener">self-managed SAML&lt;/a> and documents &lt;a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-authentication/generic-oauth/" rel="noopener">Generic OAuth in Open Source&lt;/a>. Those are two different answers to “does Grafana have free SSO?”&lt;/p>
&lt;p>Plane is easy to misread. When I checked &lt;a href="https://plane.so/pricing" rel="noopener">its pricing matrix&lt;/a>, it opened on Cloud, where the first tick for SAML or OpenID Connect (OIDC) sits under Business; choosing Self-hosted moves that tick to &lt;strong>Pro&lt;/strong> even though the URL and the feature names stay the same.&lt;/p>
&lt;p>Seafile is a different case. Its &lt;a href="https://manual.seafile.com/latest/config/saml2/" rel="noopener">SAML manual&lt;/a> says Pro. The &lt;a href="https://www.seafile.com/en/pricing/" rel="noopener">on-premises price table&lt;/a> supplies the missing detail: Pro is &lt;strong>free for up to three users&lt;/strong>. The &lt;a href="https://techfuelhq.com/data/self-hosted-sso-2026-08-25.csv" download type="text/csv">August table&lt;/a> missed both distinctions.&lt;/p>
&lt;h2 id="compare-the-self-hosted-editions">Compare the self-hosted editions&lt;/h2>
&lt;p>Start with the protocol. The filter matches the methods in the first column of the 11 edition comparisons and six included alternatives.&lt;/p>
&lt;p>Then count the seats.&lt;/p>
&lt;p>Suppose three people need SAML for their Seafile server and OpenID Connect for their password manager. The Seafile Pro allowance covers those three users, but if the same team chooses &lt;a href="https://www.passbolt.com/pricing/pro" rel="noopener">self-hosted Passbolt Pro&lt;/a> for its password manager, the ten-seat minimum applies even though seven seats go unused. At the displayed annual rate of $4.90 per user per month, that makes the license $588 a year. Hosting is separate.&lt;/p>
&lt;p data-sso-filter hidden>&lt;label for="sso-method">Compare by login method&lt;/label>
&lt;select id="sso-method" aria-controls="sso-rows-restricted sso-rows-included">&lt;option value="all">All tracked methods&lt;/option>&lt;option value="saml">SAML&lt;/option>&lt;option value="oidc">OpenID Connect (OIDC)&lt;/option>&lt;option value="ldap">LDAP&lt;/option>&lt;/select>
&lt;span role="status" data-sso-count>&lt;/span>
&lt;/p>&lt;script defer src="https://techfuelhq.com/js/sso-plan-comparison.min.f63bfbbc65de01e297aa90ba01a66dfdbf6325b34e5d8c7c0ed7d70d50d70d6b.js" integrity="sha256-9jv7vGXeAeKXqpC6AaZt/b9jJbNOXYx8DtfXDVDXDWs=">&lt;/script>
&lt;h3 id="sso-restricted">Edition and plan restrictions&lt;/h3>
&lt;section data-sso-group aria-labelledby="sso-restricted" id="sso-rows-restricted">
&lt;p data-sso-empty hidden>No apps in this section match that method. Choose another method above to see more.&lt;/p>
&lt;div data-sso-table class="table-wrap table-wrap--stack table-wrap--labels-above">&lt;table>
&lt;caption>Edition and plan restrictions, checked &lt;time datetime="2026-11-04">November 4, 2026&lt;/time>&lt;/caption>
&lt;thead>&lt;tr>&lt;th scope="col">App and method&lt;/th>&lt;th scope="col">What the plan includes&lt;/th>&lt;th scope="col">What to check&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>
&lt;tr id="sso-planka" data-sso-methods="oidc">&lt;td data-label="App and method">&lt;strong>PLANKA&lt;/strong>&lt;br>OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted Pro&lt;/strong>&lt;br>OIDC moved out of Community. Pro lists €7.20 per user per month on annual billing; one user minimum, before VAT.&lt;/td>&lt;td data-label="What to check">The €36 monthly figure shown by the calculator is for five seats. The offer is for organizations, not private consumers. Before a Community 2.2.0 upgrade, create a local admin and plan recovery of SSO-only accounts.
&lt;details>&lt;summary>Sources for PLANKA&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://github.com/plankanban/planka/releases/tag/v2.2.0">2.2.0 release notes&lt;/a>&lt;/li>&lt;li>&lt;a href="https://planka.app/pricing">Self-hosted price calculator&lt;/a>&lt;/li>&lt;li>&lt;a href="https://github.com/plankanban/planka/issues/1754">Maintainer announcement&lt;/a>&lt;/li>&lt;li>&lt;a href="https://github.com/plankanban/planka/issues/1759">Operator’s upgrade report&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-mattermost" data-sso-methods="saml">&lt;td data-label="App and method">&lt;strong>Mattermost&lt;/strong>&lt;br>SAML 2.0&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Professional and higher; Entry evaluation&lt;/strong>&lt;br>SAML is listed on Professional and higher plans. Professional directs buyers to sales.&lt;/td>&lt;td data-label="What to check">Entry also lists SAML. The pricing page limits this free edition to technical evaluation; it is not evidence of a free production entitlement.
&lt;details>&lt;summary>Sources for Mattermost&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://docs.mattermost.com/administration-guide/onboard/sso-saml">SAML plan list&lt;/a>&lt;/li>&lt;li>&lt;a href="https://mattermost.com/pricing/">Plan and evaluation terms&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-grafana" data-sso-methods="saml">&lt;td data-label="App and method">&lt;strong>Grafana&lt;/strong>&lt;br>SAML 2.0&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-managed Enterprise&lt;/strong>&lt;br>SAML is an Enterprise feature for self-managed Grafana.&lt;/td>&lt;td data-label="What to check">Generic OAuth is documented for Open Source. A requirement for external login is different from a requirement for SAML.
&lt;details>&lt;summary>Sources for Grafana&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-authentication/saml/">SAML editions&lt;/a>&lt;/li>&lt;li>&lt;a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-authentication/generic-oauth/">Generic OAuth editions&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-metabase" data-sso-methods="saml">&lt;td data-label="App and method">&lt;strong>Metabase&lt;/strong>&lt;br>SAML&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted Pro or Enterprise&lt;/strong>&lt;br>Pro starts at $575 per month on monthly billing, including the first ten users. Additional seats cost extra.&lt;/td>&lt;td data-label="What to check">The Open Source security guide recommends Google Sign-In or LDAP where practical. It would be incorrect to say the open edition has no external login.
&lt;details>&lt;summary>Sources for Metabase&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://www.metabase.com/docs/latest/people-and-groups/authenticating-with-saml">SAML plans&lt;/a>&lt;/li>&lt;li>&lt;a href="https://www.metabase.com/pricing">Pro pricing&lt;/a>&lt;/li>&lt;li>&lt;a href="https://www.metabase.com/docs/latest/installation-and-operation/security-best-practices-self-hosting">Open Source login options&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-teleport" data-sso-methods="saml oidc">&lt;td data-label="App and method">&lt;strong>Teleport&lt;/strong>&lt;br>SAML, OIDC, Active Directory&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Enterprise Self-Hosted&lt;/strong>&lt;br>The FAQ reserves these integrations for Enterprise Self-Hosted or Enterprise Cloud.&lt;/td>&lt;td data-label="What to check">Community has a GitHub connector. Its GitHub organization must not itself have external SSO enabled.
&lt;details>&lt;summary>Sources for Teleport&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://goteleport.com/docs/faq/">Enterprise authentication FAQ&lt;/a>&lt;/li>&lt;li>&lt;a href="https://goteleport.com/docs/zero-trust-access/sso/integrate-idp/github-sso/">Community GitHub connector&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-passbolt" data-sso-methods="oidc">&lt;td data-label="App and method">&lt;strong>Passbolt&lt;/strong>&lt;br>OIDC, Google SSO, Microsoft SSO&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted Pro&lt;/strong>&lt;br>Pro lists $4.90 per user per month billed annually, with a ten-user minimum.&lt;/td>&lt;td data-label="What to check">The setup guide confirms OpenID Connect. Ten seats make the published minimum $49 per month equivalent. LDAP provisioning is listed separately from SSO.
&lt;details>&lt;summary>Sources for Passbolt&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://www.passbolt.com/pricing/pro">Self-hosted Pro pricing&lt;/a>&lt;/li>&lt;li>&lt;a href="https://www.passbolt.com/docs/admin/authentication/sso/keycloak/">Pro OpenID Connect setup with Keycloak&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-bitwarden" data-sso-methods="saml oidc">&lt;td data-label="App and method">&lt;strong>Bitwarden&lt;/strong>&lt;br>SAML 2.0, OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Enterprise organization&lt;/strong>&lt;br>Enterprise lists $6 per user per month billed annually and includes self-hosting.&lt;/td>&lt;td data-label="What to check">An identity provider authenticates the member. Vault decryption is a separate choice; compare that step before switching password managers.
&lt;details>&lt;summary>Sources for Bitwarden&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://bitwarden.com/help/about-sso/">Enterprise SSO methods&lt;/a>&lt;/li>&lt;li>&lt;a href="https://bitwarden.com/pricing/business/">Business pricing&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-n8n" data-sso-methods="saml ldap">&lt;td data-label="App and method">&lt;strong>n8n&lt;/strong>&lt;br>SAML, LDAP&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted Business or Enterprise&lt;/strong>&lt;br>The Business plan lists €667 per month billed annually for 40,000 workflow executions.&lt;/td>&lt;td data-label="What to check">Community excludes SSO. The displayed Business offer is for companies with fewer than 100 employees; execution volume and eligibility matter.
&lt;details>&lt;summary>Sources for n8n&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://docs.n8n.io/deploy/host-n8n/community-edition-features">Community edition exclusions&lt;/a>&lt;/li>&lt;li>&lt;a href="https://n8n.io/pricing/">Business pricing&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-plane" data-sso-methods="saml oidc">&lt;td data-label="App and method">&lt;strong>Plane&lt;/strong>&lt;br>SAML, OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted Pro, Business or Enterprise&lt;/strong>&lt;br>The Self-hosted comparison includes both protocols starting at Pro. Free has neither. Paid self-hosted licenses require at least 10 seats.&lt;/td>&lt;td data-label="What to check">Select Self-hosted in the pricing matrix. On the default Cloud tab, the first checked column for both methods is Business. The paid license minimum does not apply to Community.
&lt;details>&lt;summary>Sources for Plane&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://plane.so/pricing">Pricing matrix: select Self-hosted&lt;/a>&lt;/li>&lt;li>&lt;a href="https://developers.plane.so/self-hosting/govern/authentication">Instance login options&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-openproject" data-sso-methods="saml oidc">&lt;td data-label="App and method">&lt;strong>OpenProject&lt;/strong>&lt;br>SAML, OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>On-premises Professional or higher&lt;/strong>&lt;br>The SSO row first appears in Professional: €10.95 per user per month at the displayed annual rate, minimum 25 users.&lt;/td>&lt;td data-label="What to check">Basic and Community do not include that SSO row. LDAP authentication has a separate row; do not count it as SAML or OIDC.
&lt;details>&lt;summary>Sources for OpenProject&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://www.openproject.org/pricing/">On-premises feature matrix&lt;/a>&lt;/li>&lt;li>&lt;a href="https://www.openproject.org/docs/system-admin-guide/authentication/openid-providers/">OIDC enterprise add-on&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-seafile" data-sso-methods="saml">&lt;td data-label="App and method">&lt;strong>Seafile&lt;/strong>&lt;br>SAML 2.0, AD FS&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Professional edition, including its free allowance&lt;/strong>&lt;br>SAML is Pro-only, but on-premises Pro is free for up to three users. The $100 annual total for nine users is a special offer for small businesses.&lt;/td>&lt;td data-label="What to check">The nine-user special license excludes basic email support. Community separately includes OAuth, Shibboleth and remote-user authentication.
&lt;details>&lt;summary>Sources for Seafile&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://manual.seafile.com/latest/config/saml2/">Pro SAML setup&lt;/a>&lt;/li>&lt;li>&lt;a href="https://manual.seafile.com/latest/config/single_sign_on/">Community and Pro methods&lt;/a>&lt;/li>&lt;li>&lt;a href="https://www.seafile.com/en/pricing/">On-premises license tiers&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>&lt;/tbody>
&lt;/table>&lt;/div>
&lt;/section>
&lt;h3 id="sso-included">Included self-hosted alternatives&lt;/h3>
&lt;section data-sso-group aria-labelledby="sso-included" id="sso-rows-included">
&lt;p data-sso-empty hidden>No apps in this section match that method. Choose another method above to see more.&lt;/p>
&lt;div data-sso-table class="table-wrap table-wrap--stack table-wrap--labels-above">&lt;table>
&lt;caption>Included self-hosted alternatives, checked &lt;time datetime="2026-11-04">November 4, 2026&lt;/time>&lt;/caption>
&lt;thead>&lt;tr>&lt;th scope="col">App and method&lt;/th>&lt;th scope="col">What the plan includes&lt;/th>&lt;th scope="col">What to check&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>
&lt;tr id="sso-zulip" data-sso-methods="saml oidc">&lt;td data-label="App and method">&lt;strong>Zulip&lt;/strong>&lt;br>SAML, OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Free self-hosted server&lt;/strong>&lt;br>Both methods appear in the Free self-hosted column.&lt;/td>&lt;td data-label="What to check">The wrench in that column means you configure and maintain the integration yourself. Cloud plan columns are different.
&lt;details>&lt;summary>Sources for Zulip&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://zulip.com/plans/">Self-hosted feature matrix&lt;/a>&lt;/li>&lt;li>&lt;a href="https://zulip.readthedocs.io/en/stable/production/authentication-methods.html">Self-hosted authentication guide&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-bookstack" data-sso-methods="oidc">&lt;td data-label="App and method">&lt;strong>BookStack&lt;/strong>&lt;br>OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted open-source edition&lt;/strong>&lt;br>OIDC can serve as the primary login method.&lt;/td>&lt;td data-label="What to check">It replaces the default email/password login. Plan how existing accounts will match the identity provider before enabling it.
&lt;details>&lt;summary>Sources for BookStack&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://www.bookstackapp.com/docs/admin/oidc-auth/">OIDC setup&lt;/a>&lt;/li>&lt;li>&lt;a href="https://www.bookstackapp.com/">Project and licensing&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-paperless" data-sso-methods="oidc">&lt;td data-label="App and method">&lt;strong>Paperless-ngx&lt;/strong>&lt;br>OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted community project&lt;/strong>&lt;br>The project documents OIDC through django-allauth, including a Keycloak example.&lt;/td>&lt;td data-label="What to check">Follow the existing-account linking instructions rather than assuming a new provider sign-in will reuse the right user.
&lt;details>&lt;summary>Sources for Paperless-ngx&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://github.com/paperless-ngx/paperless-ngx/blob/fc29f3511f427e365a7d6fe19b232c13445b9343/docs/advanced_usage.md#openid-connect-and-social-authentication">Project’s OIDC instructions&lt;/a>&lt;/li>&lt;li>&lt;a href="https://github.com/paperless-ngx/paperless-ngx">Project repository&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-vikunja" data-sso-methods="oidc">&lt;td data-label="App and method">&lt;strong>Vikunja&lt;/strong>&lt;br>OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted project&lt;/strong>&lt;br>The project documents external OIDC providers, including authentik and Keycloak.&lt;/td>&lt;td data-label="What to check">The documentation identifies the claims the provider must supply. Test with a non-admin account before migrating a team.
&lt;details>&lt;summary>Sources for Vikunja&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://vikunja.io/docs/openid/">OpenID Connect guide&lt;/a>&lt;/li>&lt;li>&lt;a href="https://vikunja.io/">Self-hosted project&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-vaultwarden" data-sso-methods="oidc">&lt;td data-label="App and method">&lt;strong>Vaultwarden&lt;/strong>&lt;br>OIDC&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted community server&lt;/strong>&lt;br>The project documents OIDC authentication.&lt;/td>&lt;td data-label="What to check">A master password is still required to unlock the vault. Vaultwarden is a separate project from Bitwarden Enterprise.
&lt;details>&lt;summary>Sources for Vaultwarden&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect">OIDC and vault unlock&lt;/a>&lt;/li>&lt;li>&lt;a href="https://github.com/dani-garcia/vaultwarden">Community server project&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>
&lt;tr id="sso-nextcloud" data-sso-methods="saml">&lt;td data-label="App and method">&lt;strong>Nextcloud&lt;/strong>&lt;br>SAML&lt;/td>&lt;td data-label="What the plan includes">&lt;strong>Self-hosted server with user_saml app&lt;/strong>&lt;br>Nextcloud’s app store and the app repository provide the SSO &amp;amp; SAML app.&lt;/td>&lt;td data-label="What to check">Match the app release to your server version; installing an incompatible release is not a plan entitlement problem.
&lt;details>&lt;summary>Sources for Nextcloud&lt;/summary>&lt;ul>&lt;li>&lt;a href="https://apps.nextcloud.com/apps/user_saml">Nextcloud app listing&lt;/a>&lt;/li>&lt;li>&lt;a href="https://github.com/nextcloud/user_saml">App code and license&lt;/a>&lt;/li>&lt;/ul>&lt;/details>
&lt;/td>&lt;/tr>&lt;/tbody>
&lt;/table>&lt;/div>
&lt;/section>
&lt;h2 id="rocketchat-check-the-release-before-upgrading">Rocket.Chat: check the release before upgrading&lt;/h2>
&lt;p>Rocket.Chat &lt;a href="https://github.com/RocketChat/Rocket.Chat/releases/tag/9.0.0" rel="noopener">9.0.0&lt;/a> shipped as a stable release on November 10, 2026. Its release notes make LDAP, SAML and custom OAuth premium features (Starter, Commercial, Government and Defense plans) and remove the Drupal, Facebook, LinkedIn, Meteor, X, WordPress and Dolphin logins. A Community workspace that uses any of them has to change plan or move those users to a supported login before updating, or they will not be able to sign in. The &lt;a href="https://github.com/RocketChat/Rocket.Chat/pull/41643" rel="noopener">LDAP/SAML&lt;/a> and &lt;a href="https://github.com/RocketChat/Rocket.Chat/pull/42477" rel="noopener">custom OAuth&lt;/a> changes are the two pull requests behind it.&lt;/p>
&lt;p>For a Community workspace moving to 9.0, the &lt;a href="https://docs.rocket.chat/docs/prepare-for-authentication-changes-in-9-0-0" rel="noopener">migration guide&lt;/a> gives two paths. Keep LDAP, SAML or custom OAuth on an eligible &lt;strong>free Starter&lt;/strong> workspace (up to 50 users, one workspace per organization), or choose a paid plan. To stay on Community, move affected accounts to a supported login first: local passwords, or the built-in Google, GitHub, GitLab, Apple and Nextcloud logins. A custom OAuth connection to your own provider is a different method.&lt;/p>
&lt;p>Test a local administrator in a separate browser session. An open tab proves little. Sign out of that test session and sign back in with the local credentials before touching the upgrade. If you already upgraded and lost access, the same guide documents the recovery: sign in with local credentials, restore the login form with the &lt;code>OVERWRITE_SETTING_Accounts_ShowFormLogin=true&lt;/code> environment variable, and, as a last resort after a database backup, reset an administrator&amp;rsquo;s password in MongoDB. Check the &lt;a href="https://github.com/RocketChat/Rocket.Chat/releases" rel="noopener">release history&lt;/a> and &lt;a href="https://docs.rocket.chat/docs/our-plans" rel="noopener">plan terms&lt;/a> against your target version.&lt;/p>
&lt;h2 id="planka-a-real-upgrade-consequence">PLANKA: a real upgrade consequence&lt;/h2>
&lt;p>The &lt;a href="https://github.com/plankanban/planka/releases/tag/v2.2.0" rel="noopener">Community 2.2.0 release&lt;/a> on August 9 removed OIDC, deactivating accounts that relied on it; its notes say OIDC/SSO is now part of PLANKA Pro. An &lt;a href="https://github.com/plankanban/planka/issues/1759" rel="noopener">operator running a family installation&lt;/a> described an automatic update that deactivated their accounts. That report establishes what happened to one installation; the release notes give the recovery procedure. Make a local administrator first, then assign passwords and reactivate affected users if you stay on Community.&lt;/p>
&lt;p>The &lt;a href="https://github.com/plankanban/planka/issues/1754" rel="noopener">maintainers’ announcement&lt;/a> explains their support costs. The &lt;a href="https://planka.app/pricing" rel="noopener">pricing calculator&lt;/a> shows why our old price needed correcting: €36 per month at the displayed annual rate buys &lt;strong>five&lt;/strong> self-hosted seats. The stated minimum is one seat. The page also says the offer is for organizations, not private consumers. A family installation should establish eligibility before treating the plan as an escape route.&lt;/p>
&lt;h2 id="set-up-an-included-alternative">Set up an included alternative&lt;/h2>
&lt;p>For team chat, compare &lt;a href="https://zulip.readthedocs.io/en/stable/production/authentication-methods.html" rel="noopener">Zulip’s self-hosted authentication options&lt;/a> with the protocol your organization uses. The &lt;a href="https://techfuelhq.com/articles/self-hosted-discord-alternatives-2026/">self-hosted Discord alternatives guide&lt;/a> covers Zulip and Rocket.Chat beyond login.&lt;/p>
&lt;p>For a password manager, ask what happens after the identity provider says you&amp;rsquo;re signed in: if your organization wants a successful OIDC login to open the vault as well, &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect" rel="noopener">Vaultwarden’s master-password requirement&lt;/a> matters more than the tick in a feature matrix. The &lt;a href="https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/">Vaultwarden on Proxmox guide&lt;/a> covers the install itself.&lt;/p>
&lt;p>For an app with no free SSO at all, an identity check in front of it is the other route: the &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale vs Cloudflare Tunnel comparison&lt;/a> covers Cloudflare Access, whose &lt;a href="https://developers.cloudflare.com/cloudflare-one/access-controls/policies/" rel="noopener">policies&lt;/a> check a login through your identity provider, an emailed one-time PIN or a service token before a request reaches the app.&lt;/p>
&lt;p>On the identity-provider side, authentik publishes integration guides for several of the included apps. The vendor and project sources above establish plan inclusion; these are implementation guides:&lt;/p>
&lt;ul>
&lt;li>Team chat and tasks: &lt;a href="https://integrations.goauthentik.io/chat-communication-collaboration/zulip/" rel="nofollow noopener">Zulip SAML&lt;/a> and &lt;a href="https://integrations.goauthentik.io/chat-communication-collaboration/vikunja/" rel="nofollow noopener">Vikunja OIDC&lt;/a>.&lt;/li>
&lt;li>Documents and wikis: &lt;a href="https://integrations.goauthentik.io/documentation/paperless-ngx/" rel="nofollow noopener">Paperless-ngx OIDC&lt;/a> and &lt;a href="https://integrations.goauthentik.io/documentation/bookstack/" rel="nofollow noopener">BookStack OIDC/SAML&lt;/a>.&lt;/li>
&lt;li>Vaults and files: &lt;a href="https://integrations.goauthentik.io/security/vaultwarden/" rel="nofollow noopener">Vaultwarden OIDC&lt;/a> and &lt;a href="https://integrations.goauthentik.io/chat-communication-collaboration/nextcloud/" rel="nofollow noopener">Nextcloud setup&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>Our &lt;a href="https://techfuelhq.com/tutorials/paperless-ngx-docker-setup-2026/">Paperless-ngx setup guide&lt;/a>, &lt;a href="https://techfuelhq.com/tutorials/nextcloud-aio-docker-setup-2026/">Nextcloud AIO walkthrough&lt;/a> and &lt;a href="https://techfuelhq.com/articles/self-hosted-apps-replace-saas-2026/">self-hosted starter list&lt;/a> cover deployment choices beyond login.&lt;/p>
&lt;h2 id="download-cite-or-correct-a-row">Download, cite or correct a row&lt;/h2>
&lt;p>The &lt;a href="https://techfuelhq.com/data/self-hosted-sso-2026-11-04.json" download type="application/json">November 4 evidence file (JSON)&lt;/a> records each app’s edition and protocol alongside its billing conditions and the time the source was checked. Its Rocket.Chat entry predates the November 10 stable release; the section above has the current status. The &lt;a href="https://techfuelhq.com/data/self-hosted-sso-2026-08-25.csv" download type="text/csv">August 25 archive (CSV)&lt;/a> preserves the original observations and prices. At the end of the JSON are three older notes: Rocket.Chat’s previous release status and two changes unrelated to login, at MinIO and Cal.com. They do not count toward the 17 comparisons.&lt;/p>
&lt;p>Read the source through &lt;code>url&lt;/code>. For the GitHub releases in this file, the address you need to check the saved response is &lt;code>retrieved_url&lt;/code>, because the public release page is HTML and the GitHub API that supplied our evidence returned JSON. Those bytes differ.&lt;/p>
&lt;p>Cite the dated file you used. TechFuel HQ’s observations are available under &lt;a href="https://creativecommons.org/licenses/by/4.0/" rel="noopener">CC BY 4.0&lt;/a>; vendor material remains with its publisher.&lt;/p>
&lt;p>If a row no longer fits your deployment, &lt;a href="https://techfuelhq.com/contact/">send a correction&lt;/a> with the app, self-hosted edition, exact version, protocol and the release note or plan row that changed. A redacted test result is useful when documentation and behavior disagree. Leave out account names, tokens and identity-provider configuration secrets.&lt;/p></description></item><item><title>Ollama vs llama.cpp on an RTX 5080: Measured (2026)</title><link>https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/</link><pubDate>Thu, 20 Aug 2026 01:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/</guid><atom:updated>2026-11-20T20:00:00Z</atom:updated><description>&lt;p>The argument shows up in every local-AI thread: Ollama is &amp;ldquo;just a wrapper&amp;rdquo; and real
performance lives in bare llama.cpp. Nobody arguing it ever posts numbers from the same
machine. So I ran both servers on the same RTX 5080, loading the same GGUF bytes,
with generation pinned to temperature 0, seed 42, and fresh prompts every run.&lt;/p>
&lt;p>The answer surprised me, because I went in expecting to confirm the forum consensus
and instead measured something smaller, stranger, and more useful. &lt;strong>The wrapper costs
almost nothing, and each side wins one event.&lt;/strong>&lt;/p>
&lt;p>Decode goes to llama.cpp. Prefill goes to Ollama. Nobody wins big.&lt;/p>
&lt;h2 id="llamacpp-vs-ollama-what-each-one-is">llama.cpp vs Ollama: what each one is&lt;/h2>
&lt;p>llama.cpp is the engine. Its &lt;a href="https://github.com/ggml-org/llama.cpp" rel="noopener">README&lt;/a> calls it &amp;ldquo;LLM inference in C/C++&amp;rdquo;: C/C++ code that ships a command-line tool and an OpenAI-compatible server, and both can download a GGUF model straight from Hugging Face. Ollama wraps an engine in model management. It fetches and runs models by name from its own library at ollama.com/library, and serves a REST API on port 11434; &lt;a href="https://github.com/ollama/ollama" rel="noopener">its README&lt;/a> lists llama.cpp as a supported backend. So the real choice is how much of the machinery you want to run yourself. Speed barely enters into it on dense models, as the table below shows.&lt;/p>
&lt;h2 id="the-measured-table">The measured table&lt;/h2>
&lt;p>Ollama 0.32.1 versus llama.cpp b10507 (llama-server), full GPU offload, 4096 context,
256-token generations, decode medians of five runs. Prefill measured at real prompt
length (~420 tokens), median of three fresh runs with a discarded warmup. The short
version of why the prompt length matters is below.&lt;/p>
&lt;p>These are August 20, 2026 numbers. On November 18 the newest releases were
&lt;a href="https://github.com/ollama/ollama/releases" rel="noopener">Ollama 0.40.16&lt;/a> and
&lt;a href="https://github.com/ggml-org/llama.cpp/releases/tag/v1.0.0" rel="noopener">llama.cpp v1.0.0&lt;/a> from
November 13, with numbered llama.cpp builds up to b12498. Neither has been benchmarked
here, so read the percentages as a dated snapshot. Per-run arrays for every row are in
the &lt;a href="https://techfuelhq.com/data/llm-server-compare/">same-GPU compare dataset&lt;/a>.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Model&lt;/th>
&lt;th scope="col">Server&lt;/th>
&lt;th scope="col" style="text-align: right">Decode&lt;/th>
&lt;th scope="col" style="text-align: right">Prefill&lt;/th>
&lt;th scope="col" style="text-align: right">GPU mem (MiB)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 3B&lt;/td>
&lt;td data-label="Server">Ollama&lt;/td>
&lt;td style="text-align: right" data-label="Decode">319 t/s&lt;/td>
&lt;td style="text-align: right" data-label="Prefill">17,444 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">4,343&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 3B&lt;/td>
&lt;td data-label="Server">llama.cpp&lt;/td>
&lt;td style="text-align: right" data-label="Decode">&lt;strong>338 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Prefill">16,809 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">4,339&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Qwen 2.5 14B&lt;/td>
&lt;td data-label="Server">Ollama&lt;/td>
&lt;td style="text-align: right" data-label="Decode">99.4 t/s&lt;/td>
&lt;td style="text-align: right" data-label="Prefill">5,004 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">10,941&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Qwen 2.5 14B&lt;/td>
&lt;td data-label="Server">llama.cpp&lt;/td>
&lt;td style="text-align: right" data-label="Decode">&lt;strong>101.4 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Prefill">4,697 t/s&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">10,942&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">gpt-oss 20B&lt;/td>
&lt;td data-label="Server">Ollama&lt;/td>
&lt;td style="text-align: right" data-label="Decode">195.8 t/s&lt;/td>
&lt;td style="text-align: right" data-label="Prefill">—&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">14,152&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">gpt-oss 20B&lt;/td>
&lt;td data-label="Server">llama.cpp²&lt;/td>
&lt;td style="text-align: right" data-label="Decode">&lt;strong>222-238 t/s&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Prefill">—&lt;/td>
&lt;td style="text-align: right" data-label="GPU mem (MiB)">13,037&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>² Upstream GGUF (the Ollama blob refuses to load; see the portability catch below).&lt;/p>
&lt;p>gpt-oss is a mixture-of-experts model and its decode rate on upstream llama.cpp is
prompt-dependent: a fixed prompt held a tight 232-242 t/s (median 238.5), while varied
prompts were bimodal, mostly ~230-243 with a ~176 slow path — range 175-243,
varied-prompt median 235.3. The published 222 median also carries a cold first run at
186. Ollama&amp;rsquo;s fork ran a flat 195.7-196.3 under the same nonce scheme. The gpt-oss
prefill cells are dashed because the long-prompt pass was not run on this model.&lt;/p>
&lt;p>Desktop baseline was 1,642 MiB of GPU memory; subtract it for the models&amp;rsquo; own
footprints. Wall-clock recomputation agreed with each server&amp;rsquo;s self-reported rates
within 2% on every run but one — the first gpt-oss run on llama-server landed 3.6% off,
a cold-start artifact. Wherever both servers loaded the same file, VRAM matched within
7 MiB. Same weights, same memory. The gpt-oss row is the exception, and it is carrying
two different conversions of the model, not a wrapper difference. These figures also
run 2-7% above our earlier &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 throughput dataset&lt;/a>
for the same models, because that capture used 500-1,650-token prompts where this one
uses short ones; both pages state their regime.&lt;/p>
&lt;p>llama.cpp decodes 2-6% faster on the dense models, more on the MoE below.
Ollama prefills 4-7% faster at real prompt sizes.
Neither gap changes what a model feels like to use, and neither survives a driver
update, an engine release, or a quantization change as the deciding factor in a
purchase or a migration.&lt;/p>
&lt;h2 id="the-overhead-ladder">The overhead ladder&lt;/h2>
&lt;p>One more instrument completes the picture. llama.cpp ships llama-bench, which times
the raw engine loop with no server in front of it. On Llama 3.2 3B:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Instrument&lt;/th>
&lt;th scope="col">What it measures&lt;/th>
&lt;th scope="col" style="text-align: right">Decode&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Instrument">llama-bench&lt;/td>
&lt;td data-label="What it measures">bare engine loop&lt;/td>
&lt;td style="text-align: right" data-label="Decode">367 t/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Instrument">llama-server&lt;/td>
&lt;td data-label="What it measures">+ HTTP serving, sampling pipeline&lt;/td>
&lt;td style="text-align: right" data-label="Decode">338 t/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Instrument">Ollama&lt;/td>
&lt;td data-label="What it measures">+ model management, its serving stack&lt;/td>
&lt;td style="text-align: right" data-label="Decode">319 t/s&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Each layer costs single-digit percent, and that is the entire &amp;ldquo;wrapper tax&amp;rdquo;: 13% from
the bare engine loop to the most convenient tool in the stack, most of it spent on
serving machinery that any usable setup needs anyway, whichever side of the argument
you started on. Forum threads promise dramatic slowdowns. None reproduced here.&lt;/p>
&lt;p>That is the whole controversy, measured.&lt;/p>
&lt;h2 id="how-my-first-measurement-lied-to-me">How my first measurement lied to me&lt;/h2>
&lt;p>The first pass of this bench used a short, ~40-token prompt, and it showed Ollama&amp;rsquo;s
prefill rates landing 32-55% above llama-server&amp;rsquo;s — a gap that turned out to be an
artifact, because at tiny
prompt sizes &amp;ldquo;prefill tokens per second&amp;rdquo; is dominated by fixed per-request overhead
rather than compute, which means it measures which server shuffles a request faster
rather than which one ingests your context faster, and re-measured at ~420 prompt
tokens, llama-server&amp;rsquo;s prefill jumped from ~5,300 to ~16,800 t/s on the 3B while the
gap collapsed to single digits. The flags people credit for prefill speed did nothing
here either: flash attention on or off, micro-batch 512 or 2048, all within noise at
real prompt length on this card. Flags were not the story. Prompt length was.&lt;/p>
&lt;p>So treat one-line-prompt prefill numbers as request plumbing, not throughput.&lt;/p>
&lt;h2 id="the-portability-catch">The portability catch&lt;/h2>
&lt;p>Ollama stores weights as standard GGUF blobs, and &lt;code>ollama show &amp;lt;model&amp;gt; --modelfile&lt;/code>
prints the path. Point llama-server at it and both tools share one copy of the weights.
That worked perfectly for Llama 3.2 3B and Qwen 2.5 14B.&lt;/p>
&lt;p>It failed for gpt-oss:20b, and the failure is worth knowing about. llama.cpp refused
the blob with &lt;code>unknown model architecture: 'gptoss'&lt;/code>, and the server died on the spot. Ollama&amp;rsquo;s conversion tags the
architecture with its own name, while upstream llama.cpp expects &lt;code>gpt-oss&lt;/code> — so the
one model Ollama co-launched is the one whose Ollama download you cannot carry to the
upstream engine, so its download does not travel. The fix is downloading the
&lt;a href="https://huggingface.co/ggml-org/gpt-oss-20b-GGUF" rel="noopener">upstream GGUF&lt;/a> separately, at the
cost of a second ~12GB copy on disk. The upstream copy then decoded 13-22% faster than
Ollama&amp;rsquo;s fork on most prompts and allocated 1.1GB less GPU memory at the same context,
so the annoyance bought something real, about 1.09 GiB of it.&lt;/p>
&lt;h2 id="which-one-should-you-run">Which one should you run?&lt;/h2>
&lt;p>Run Ollama when you want model management to be someone else&amp;rsquo;s problem: pulls, updates,
memory eviction, an OpenAI-style API on 11434, and every tutorial on the internet
assuming you have it. If the real question is a GUI desktop app rather than a second
server engine, that is a different comparison — I benched it separately in
&lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/">Ollama vs LM Studio on the same card&lt;/a>. Our &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 throughput dataset&lt;/a>
and the &lt;a href="https://techfuelhq.com/tutorials/self-host-local-llm-rtx-5060-2026/">RTX 5060 local LLM guide&lt;/a> both
ride on it for exactly that reason.&lt;/p>
&lt;p>Run llama-server when you want the newest engine the day it ships, exact control over
batching, context, and sampling, or the last few percent of decode speed. For these
models the engines share llama.cpp lineage; Ollama&amp;rsquo;s &lt;a href="https://github.com/ollama/ollama" rel="noopener">README&lt;/a>
lists llama.cpp among its supported backends, and the gpt-oss arch tag shows its
conversions can diverge from upstream. You are choosing how much of the engine&amp;rsquo;s surface to touch. Throughput is the wrong reason to switch in either direction — 2-6% is
less than the gain from one quantization step or one driver update.&lt;/p>
&lt;p>If the plan is one model answering several agents or users at once,
&lt;a href="https://techfuelhq.com/self-hosted/vllm-vs-ollama-2026/">vLLM vs Ollama&lt;/a> covers the engine built for
concurrent serving. For the Ollama side of the setup, the
&lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Docker-with-GPU tutorial&lt;/a> covers the install, the
&lt;a href="https://techfuelhq.com/articles/best-local-llm-coding-2026/">local coding model test&lt;/a> covers which model to
load, and the &lt;a href="https://techfuelhq.com/tools/llm-speed-calculator/">LLM speed calculator&lt;/a> estimates decode rates
on other GPUs.&lt;/p>
&lt;h2 id="method-and-limits">Method and limits&lt;/h2>
&lt;p>Both servers ran the same sha256-identical GGUF blobs from Ollama&amp;rsquo;s own store (except
the gpt-oss case above), one server resident at a time, fresh process per model, with
&lt;code>ollama stop&lt;/code> and process-tree kills between runs. Every request used a unique prompt
nonce; llama-server additionally got &lt;code>cache_prompt: false&lt;/code>. Generation pinned to
temperature 0, seed 42, 256 tokens (64 for the long-prefill pass), context 4096 on
both. Rates come from each server&amp;rsquo;s own timing counters, cross-checked by wall-clock
recomputation (within 2% throughout) and by llama-bench as a third instrument.&lt;/p>
&lt;p>The box is the same RTX 5080 desktop as the
&lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/">LM Studio comparison&lt;/a>, whose August 26
capture records Windows 11 and NVIDIA driver 610.88; the August 12
&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">throughput dataset&lt;/a> on this card records the same driver
and a Ryzen 7 7800X3D.&lt;/p>
&lt;p>The limits, named. One GPU, one box, three models, servers on default flags. Token counts for identical prompt text differed slightly between servers (433
vs 407 on the long prompt) because Ollama applies its chat template to /api/generate
while llama-server&amp;rsquo;s /completion takes the prompt raw — rates are per-token, so the
comparison holds, but byte-identical inputs produce slightly different token streams.
Ollama builds on llama.cpp, the backend its README lists, so some of the decode gap is
simply engine version lag, and it will move with every release on both sides. Date everything;
this page says 2026-08-20.&lt;/p></description></item><item><title>Best MCP Servers for a Homelab: 11 Measured (2026)</title><link>https://techfuelhq.com/self-hosted/best-mcp-servers-homelab-2026/</link><pubDate>Wed, 19 Aug 2026 23:58:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/best-mcp-servers-homelab-2026/</guid><atom:updated>2026-11-20T20:00:00Z</atom:updated><description>&lt;p>All four &amp;ldquo;favorite MCP servers&amp;rdquo; roundups I could find share one gap. None publishes a
single number. No memory footprint, no startup time, no latency. Enumerate and vibe is
the format. So I wrote a small benchmark, pointed it at eleven of the most-recommended
MCP servers, and measured what they actually cost to keep resident on a homelab box.&lt;/p>
&lt;p>The headline: &lt;strong>each server holds 178-422MB of RAM&lt;/strong>, and the popular advice to &amp;ldquo;just
connect everything&amp;rdquo; costs about &lt;strong>1GB for five servers&lt;/strong>, because I measured 961.6MB for
a real concurrent stack, two independent measurement paths agreed on it to the decimal,
and that is a gigabyte gone before a single model or container starts, spent on tooling
I touch a few times a day. Nobody mentions this. RAM is the quiet bill.&lt;/p>
&lt;p>MCP servers are the tool layer of an agent: the runtime calls them to read files, fetch pages or work a repository. Where they sit beside the model and the memory is on the &lt;a href="https://techfuelhq.com/self-hosted/self-hosted-ai-agent-2026/">self-hosted AI agent&lt;/a> page, and every run behind the table below is on the &lt;a href="https://techfuelhq.com/data/mcp-server-bench/">dataset page&lt;/a>.&lt;/p>
&lt;h2 id="the-measured-table">The measured table&lt;/h2>
&lt;p>Fresh spawn per iteration, warm package cache, five iterations per server (three for
GitHub and Qdrant, benched later the same evening — the iterations column in the CSV
says which), medians reported. RSS covers the full process tree, because npx and uvx
both spawn children, and measuring only the parent undercounts 18x. Raw data ships as
&lt;a href="https://techfuelhq.com/data/mcp-server-bench-2026-08.csv" download type="text/csv">CSV&lt;/a> with a
&lt;a href="https://techfuelhq.com/data/mcp-server-bench/">versioned dataset page&lt;/a>, CC BY 4.0.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Server&lt;/th>
&lt;th scope="col">Version&lt;/th>
&lt;th scope="col" style="text-align: right">Ready&lt;/th>
&lt;th scope="col" style="text-align: right">RSS&lt;/th>
&lt;th scope="col" style="text-align: right">Tools&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Server">GitHub (legacy npm)&lt;/td>
&lt;td data-label="Version">0.6.2&lt;/td>
&lt;td style="text-align: right" data-label="Ready">547ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">178MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">26&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Playwright&lt;/td>
&lt;td data-label="Version">1.63.0-alpha-2026-08-05&lt;/td>
&lt;td style="text-align: right" data-label="Ready">618ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">227MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">24&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Time (Python)&lt;/td>
&lt;td data-label="Version">1.29.0¹&lt;/td>
&lt;td style="text-align: right" data-label="Ready">619ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">181MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">2&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Sequential-thinking&lt;/td>
&lt;td data-label="Version">0.2.0&lt;/td>
&lt;td style="text-align: right" data-label="Ready">666ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">186MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">1&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Memory&lt;/td>
&lt;td data-label="Version">0.6.3&lt;/td>
&lt;td style="text-align: right" data-label="Ready">667ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">187MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">9&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Filesystem&lt;/td>
&lt;td data-label="Version">0.2.0&lt;/td>
&lt;td style="text-align: right" data-label="Ready">692ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">188MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">14&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Git (Python)&lt;/td>
&lt;td data-label="Version">1.29.0¹&lt;/td>
&lt;td style="text-align: right" data-label="Ready">699ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">185MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">12&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Fetch (Python)&lt;/td>
&lt;td data-label="Version">1.29.0¹&lt;/td>
&lt;td style="text-align: right" data-label="Ready">717ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">220MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">1&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Context7&lt;/td>
&lt;td data-label="Version">4.0.2&lt;/td>
&lt;td style="text-align: right" data-label="Ready">815ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">214MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">2&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Desktop Commander&lt;/td>
&lt;td data-label="Version">0.2.47&lt;/td>
&lt;td style="text-align: right" data-label="Ready">1,705ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">275MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">26&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Server">Qdrant (Python, 3.12 pin)&lt;/td>
&lt;td data-label="Version">1.29.0¹&lt;/td>
&lt;td style="text-align: right" data-label="Ready">1,881ms&lt;/td>
&lt;td style="text-align: right" data-label="RSS">422MB&lt;/td>
&lt;td style="text-align: right" data-label="Tools">2&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>¹ The four Python servers self-report the version string 1.29.0 via serverInfo, a
framework string rather than each package&amp;rsquo;s own release number.&lt;/p>
&lt;p>The versions are the ones measured on August 19, 2026, and most of these servers have
shipped since. On November 18, npm listed filesystem 2.3.0, memory 2.1.1,
sequential-thinking 2.1.1, Playwright MCP 0.0.85, Context7 4.7.3 and Desktop Commander
0.3.3, and PyPI listed the time, git and fetch servers at 2026.11.11. The Qdrant server&amp;rsquo;s
latest release is still 0.8.1, and the legacy GitHub package has had no release since
April 2025 because it is archived (more below). Memory figures can move with any of those releases.&lt;/p>
&lt;p>Controls matter here. A bare Node process idles at 52MB and bare Python at 15MB on the
same box, so the gap between those floors and the table is frameworks plus dependencies.
Your tool code is nearly free. Tool count barely predicts weight. The 26-tool GitHub
server is the lightest thing I measured, while the 1-tool sequential-thinking server
still costs 186MB. The framework is the payload.&lt;/p>
&lt;p>Two findings surprised me. Python servers land as heavy as Node ones, since uvx resolves
an environment and spawns its own interpreter chain; fetch holds 220MB for a single tool.
And the whole startup-cost worry is mostly noise for homelab use. Everything except
Desktop Commander and Qdrant is ready in under a second warm, and a persistent client
like Claude Code spawns servers once per session anyway.&lt;/p>
&lt;h2 id="the-tiers-with-the-criteria-stated">The tiers, with the criteria stated&lt;/h2>
&lt;p>I ranked on four things I can defend: measured cost, utility per megabyte, install
friction, and whether the server works standalone or needs a service running behind it.&lt;/p>
&lt;h3 id="tier-1-connect-these-first">Tier 1, connect these first&lt;/h3>
&lt;p>&lt;strong>Filesystem&lt;/strong> (188MB, 14 tools), &lt;strong>Fetch&lt;/strong> (220MB, 1 tool), and &lt;strong>Git&lt;/strong> (185MB,
12 tools). These are the hands and eyes of any local AI setup. They read and edit real
files, pull real web pages, and work actual repository history. Every workflow I run
daily leans on at least two of the three, so their megabytes never idle.&lt;/p>
&lt;h3 id="tier-2-worth-it-when-the-use-exists">Tier 2, worth it when the use exists&lt;/h3>
&lt;p>&lt;strong>GitHub&lt;/strong> (178MB, 26 tools) earns a slot if your work lives in issues and PRs. The npm
package I measured is the legacy implementation; GitHub&amp;rsquo;s current
&lt;a href="https://github.com/github/github-mcp-server" rel="noopener">first-party server&lt;/a> ships as a Go binary
and a hosted remote endpoint, so treat 178MB as the worst case.
npm now marks that legacy package deprecated: &amp;ldquo;Archived and unmaintained; no security
guarantees.&amp;rdquo; Use the current server, remote or local, for anything new.
&lt;strong>Playwright&lt;/strong> (227MB, 24 tools) puts an agent behind a real browser, and the 227MB is
just the idle server, so budget for the browser on top. &lt;strong>Memory&lt;/strong> (187MB, 9 tools)
gives an agent a persistent knowledge graph across sessions, which pays off once you
have sessions worth remembering. &lt;strong>Desktop Commander&lt;/strong> (275MB, 26 tools) is the heaviest
Node server, and at 1.7s only Qdrant starts slower. It earns that by being a full
terminal-and-editor surface. Run it where you would trust an agent with a shell, and
nowhere else. Its own README says its guardrails are &amp;ldquo;not a sandbox&amp;rdquo; and offers a Docker
install for isolation; use that when the agent does not need your real files.&lt;/p>
&lt;h3 id="tier-3-think-twice">Tier 3, think twice&lt;/h3>
&lt;p>Sequential-thinking is the worst utility-per-megabyte in the table. It holds 186MB for
one tool that restates a reasoning pattern current models handle natively. Context7
(214MB, 2 tools) pulls current library docs into context, which helps coding agents and
duplicates a client that already fetches the web. Qdrant is the heaviest measured at
422MB, and bare uvx failed to install it outright on this machine — the resolver picked
a pydantic-core it had to source-build, which dies without a Rust toolchain. Pin it with
&lt;code>uvx --python 3.12 mcp-server-qdrant&lt;/code> and it starts fine, then holds its FastEmbed
embedding model (all-MiniLM-L6-v2 by default) inside that 422MB. Run it if you already run Qdrant for something else.&lt;/p>
&lt;h2 id="the-service-bound-layer-i-did-not-measure">The service-bound layer I did not measure&lt;/h2>
&lt;p>The service-bound servers the homelab press centers on need their platform running to
mean anything. Proxmox MCP is the consensus pick, covered by three of the four
roundups I checked, with one author counting 200+ exposed tools. Kubernetes MCP and
Docker Desktop&amp;rsquo;s MCP Toolkit round out that set. This bench box runs
neither Docker nor Proxmox, so those numbers would have been theater, and I left them
out. The pattern from the measured set almost certainly transfers. Expect the runtime
floor plus dependencies, call it 200-400MB per server, and measure on your own box
before trusting anyone&amp;rsquo;s table, including mine.&lt;/p>
&lt;p>Home Assistant is the exception that needs no separate server. Since 2025.2 it ships a
&lt;a href="https://www.home-assistant.io/integrations/mcp_server/" rel="noopener">Model Context Protocol integration&lt;/a>
that makes Home Assistant itself an MCP server. Its device-control set reaches only the
entities you expose to voice assistants, the full set requires an administrator account,
and a read-only mode hides every tool that changes anything. Start with device control in
read-only mode. The &lt;a href="https://techfuelhq.com/tutorials/home-assistant-local-llm-voice-2026/">Home Assistant local LLM guide&lt;/a>
covers pairing it with a model that stays on your network.&lt;/p>
&lt;p>For options beyond the eleven measured here, &lt;a href="https://hol.org/plugins" rel="nofollow noopener">HOL&amp;rsquo;s catalog of MCP servers and plugins&lt;/a> shows static scan results and trust scores. HOL itself says a scan is not a safety guarantee.&lt;/p>
&lt;h2 id="configs-beyond-cursor">Configs beyond Cursor&lt;/h2>
&lt;p>Three of the four roundups I read assume Cursor, and the fourth stays client-agnostic.
Two clients they skip matter in a homelab. Claude Code
wires a server in one line.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem C:/lab
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That hands the agent read and write access to &lt;code>C:/lab&lt;/code>. The filesystem server can touch
only the directories you pass it, so name one working folder, never a drive root or your
home directory, and add the &lt;code>--read-only&lt;/code> flag its README documents when the agent only
needs to read.&lt;/p>
&lt;p>LM Studio and Claude Desktop take the same JSON shape in &lt;code>mcp.json&lt;/code>.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-json" data-lang="json">&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;mcpServers&amp;#34;&lt;/span>: {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;filesystem&amp;#34;&lt;/span>: {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;command&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;npx&amp;#34;&lt;/span>,
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;args&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;-y&amp;#34;&lt;/span>, &lt;span style="color:#e6db74">&amp;#34;@modelcontextprotocol/server-filesystem&amp;#34;&lt;/span>, &lt;span style="color:#e6db74">&amp;#34;C:/lab&amp;#34;&lt;/span>]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Swap &lt;code>npx -y &amp;lt;package&amp;gt;&lt;/code> for &lt;code>uvx &amp;lt;package&amp;gt;&lt;/code> on the Python servers, and remember the
Qdrant interpreter pin from the table above.&lt;/p>
&lt;h2 id="what-to-run-this-on">What to run this on&lt;/h2>
&lt;p>The RAM math is friendly. A five-server stack costs about 1GB resident, so any
&lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">N100-class mini PC&lt;/a> with 16GB handles the tooling
layer without noticing. The real constraint is whatever model or services run beside it.
If the same box also hosts a local LLM, size memory for the model first; the
&lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Ollama in Docker with GPU guide&lt;/a> covers that setup, and
the &lt;a href="https://techfuelhq.com/homelab/komodo-vs-portainer-vs-dockge-2026/">Komodo vs Portainer vs Dockge comparison&lt;/a>
covers managing the containers around it. Our
&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 throughput dataset&lt;/a> and the
&lt;a href="https://techfuelhq.com/tutorials/self-host-local-llm-rtx-5060-2026/">local LLM on an RTX 5060 guide&lt;/a> carry the
VRAM numbers. Mine are measured on this bench. The 5060 guide&amp;rsquo;s come from published
benchmarks for those cards. With &lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 prices where they are&lt;/a>,
over-provisioning system RAM is the cheapest insurance in the build. Where those servers sit in a full agent, and which layers of one you host, is on the &lt;a href="https://techfuelhq.com/self-hosted/self-hosted-ai-agent-2026/">self-hosted AI agent&lt;/a> page.&lt;/p>
&lt;h2 id="method-including-the-traps">Method, including the traps&lt;/h2>
&lt;p>The bench script (in our repo) spawns each server fresh,
speaks MCP JSON-RPC over stdio with an initialize handshake followed by a tools/list
call, and samples RSS across the full descendant process tree 0.4s after the listing
returns. Five iterations per server, three for the two late additions. One discarded
warmup spawn keeps npm and uv package caches warm, because the documented condition is a configured homelab, and never a first
install. Run-to-run ready-time spread stayed under 7% for eight of eleven servers; the Python
time and fetch servers carried first-iteration outliers up to 17%, visible in the
published arrays. RSS spread stayed within 8MB worst case.&lt;/p>
&lt;p>The instrument hit traps, so yours does not have to. Measuring only the spawned npx parent
reports 10.3MB while the full process tree holds 189.3MB — an 18x undercount, recorded
in the evidence set. Sum the tree.
My first Git-server runs timed out because I pointed the repository flag at a plain
directory, and the server waits silently. The Qdrant failure looked like a hang until
stderr showed the build dying: &amp;ldquo;Failed to build pydantic-core==2.33.2 &amp;hellip; Rust not
found, installing into a temporary directory&amp;rdquo;. Bare uvx had resolved a pinned
pydantic-core and fallen back to a source build; the 3.12 interpreter pin sidesteps it.&lt;/p>
&lt;p>For the five-stack figure the components were memory 189.8, filesystem 187.1, fetch
221.7, git 184.5, and GitHub 178.5, totaling 961.6MB by psutil; an independent
PowerShell WorkingSet64 walk over the same process trees returned 961.6MB, exact
agreement. Those come from the one concurrent five-server run, so they differ by a few MB
from the per-server medians in the table.&lt;/p>
&lt;p>Limitations, named. One Windows 11 machine. Warm caches. Stdio transport only. I
measured readiness and listing, and never per-tool-call latency under load. The GitHub
entry is the legacy npm package rather than the current Go binary. Linux numbers will
differ, likely lower on the Node floor, and that comparison is a natural v2 alongside
the service-bound servers once this lab runs Docker.&lt;/p></description></item><item><title>Docker Exit Code 137: Prove OOMKilled Before Raising Memory</title><link>https://techfuelhq.com/tutorials/docker-exit-code-137-oomkilled-2026/</link><pubDate>Sat, 03 Oct 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/docker-exit-code-137-oomkilled-2026/</guid><atom:updated>2026-11-18T07:30:00Z</atom:updated><description>&lt;p>&lt;strong>Exit code 137 means the container&amp;rsquo;s main process was killed with &lt;code>SIGKILL&lt;/code>.&lt;/strong> Under &lt;a href="https://www.gnu.org/software/bash/manual/html_node/Exit-Status.html" rel="noopener">GNU Bash&amp;rsquo;s exit-status rules&lt;/a>, a command terminated by fatal signal &lt;em>N&lt;/em> is reported as 128 + &lt;em>N&lt;/em>, and Linux &lt;a href="https://man7.org/linux/man-pages/man7/signal.7.html" rel="noopener">lists &lt;code>SIGKILL&lt;/code> as signal 9&lt;/a>. The most common sender is the kernel&amp;rsquo;s out-of-memory killer, because the container hit its own memory limit or because the host (or the Docker Desktop VM) ran out.&lt;/p>
&lt;p>It is not proof of memory, though. &lt;a href="https://docs.docker.com/engine/containers/run/#exit-status" rel="noopener">Docker returns the container command&amp;rsquo;s exit status&lt;/a>, so a command can return &lt;code>137&lt;/code> itself, and Docker has two non-memory ways to send &lt;code>SIGKILL&lt;/code>: &lt;a href="https://docs.docker.com/reference/cli/docker/container/kill/" rel="noopener">&lt;code>docker kill&lt;/code> uses it by default&lt;/a>, and &lt;a href="https://docs.docker.com/reference/cli/docker/container/stop/" rel="noopener">&lt;code>docker stop&lt;/code> escalates to it&lt;/a> when the process has not exited after the timeout, 10 seconds by default for Linux containers. The four steps below tell those apart in a few minutes, from least to most disruptive.&lt;/p>
&lt;p>This page is written against Docker Engine 29.10.0, the current release on November 18, 2026.&lt;/p>
&lt;p>&lt;strong>Before you restart or recreate anything:&lt;/strong> a container&amp;rsquo;s next start resets its exit code and OOM flag, and a recreated container is a different object. Run step 1 first.&lt;/p>
&lt;h2 id="1-ask-docker-whether-it-recorded-an-oom-kill">1. Ask Docker whether it recorded an OOM kill&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker inspect --type&lt;span style="color:#f92672">=&lt;/span>container &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --format &lt;span style="color:#e6db74">&amp;#39;exit={{.State.ExitCode}} oom_killed={{.State.OOMKilled}} limit={{.HostConfig.Memory}} finished={{.State.FinishedAt}} restarts={{.RestartCount}}&amp;#39;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> CONTAINER_NAME_OR_ID
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;ul>
&lt;li>&lt;code>oom_killed=true&lt;/code>: Docker recorded an out-of-memory kill. Go to step 2.&lt;/li>
&lt;li>&lt;code>limit=0&lt;/code>: Docker set no per-container hard limit, so any OOM kill came from the host, a parent cgroup or the Docker Desktop VM, not from a container limit. Giving this container &amp;ldquo;more memory&amp;rdquo; has nothing to raise.&lt;/li>
&lt;li>&lt;code>oom_killed=false&lt;/code>: memory is not ruled out, but it is not shown either. Step 3 checks the kernel&amp;rsquo;s own record.&lt;/li>
&lt;li>&lt;code>restarts&lt;/code> above zero or a &lt;code>finished&lt;/code> time after the incident: this is a later run, and its flags describe that run, not the one that died. Use the &lt;a href="#when-the-quick-check-is-not-enough">full capture&lt;/a> instead.&lt;/li>
&lt;/ul>
&lt;p>This rules out guessing. It does not yet say which boundary was hit.&lt;/p>
&lt;h2 id="2-watch-memory-against-the-limit">2. Watch memory against the limit&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker stats --no-stream
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>MEM USAGE / LIMIT&lt;/code> is what each container is using and what it is allowed. A container sitting close to its limit under normal load will be killed again under a burst. Run it a few times while the workload is busy, or drop &lt;code>--no-stream&lt;/code> to watch it live. If no limit is set, the limit column shows what the container can see, usually the host&amp;rsquo;s or the VM&amp;rsquo;s memory.&lt;/p>
&lt;p>This tells you whether the limit is plausibly too small for the workload. It does not show host pressure from other processes.&lt;/p>
&lt;h2 id="3-read-the-kernels-record-of-the-kill">3. Read the kernel&amp;rsquo;s record of the kill&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo journalctl -k --since &lt;span style="color:#e6db74">&amp;#34;2 hours ago&amp;#34;&lt;/span> --no-pager &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> | grep -Ei &lt;span style="color:#e6db74">&amp;#39;out of memory|oom-kill|killed process|memory cgroup&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>journalctl&lt;/code> accepts relative times such as &lt;code>2 hours ago&lt;/code>; narrow the window to the incident. A line naming the killed process and a memory cgroup points at a cgroup limit; an out-of-memory line with no container limit set points at the host. No line at all, together with &lt;code>oom_killed=false&lt;/code>, points away from memory: go to &amp;ldquo;Not memory&amp;rdquo; in step 4.&lt;/p>
&lt;p>This step separates a container limit from host pressure. If the incident happened before the last reboot, use the boot-selection commands in the &lt;a href="#when-the-quick-check-is-not-enough">full capture&lt;/a>.&lt;/p>
&lt;h2 id="4-fix-the-cause-the-evidence-points-to">4. Fix the cause the evidence points to&lt;/h2>
&lt;p>&lt;strong>The container&amp;rsquo;s own limit was hit.&lt;/strong> Measure the workload&amp;rsquo;s peak first (step 2), then raise the limit with headroom for non-heap memory and bursts. In Compose, set it on the service:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">worker&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">mem_limit&lt;/span>: &lt;span style="color:#ae81ff">1g&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>or under &lt;code>deploy.resources.limits.memory&lt;/code>; Docker&amp;rsquo;s &lt;a href="https://docs.docker.com/reference/compose-file/services/" rel="noopener">Compose reference&lt;/a> says the two must agree if you set both. &lt;code>memswap_limit&lt;/code> controls swap: left unset, a container with a memory limit can use as much swap again as its limit if the host has swap.&lt;/p>
&lt;p>&lt;strong>Warning:&lt;/strong> &lt;code>docker compose up -d&lt;/code> applies the change by stopping and recreating the container. Volumes are kept, but anything written inside the container&amp;rsquo;s own filesystem rather than to a volume is lost. Capture what you need from the old container first.&lt;/p>
&lt;p>&lt;strong>The application, not the limit, is the problem.&lt;/strong> Runtimes that size their heap by themselves need telling about the limit. For Node.js, &lt;code>--max-old-space-size&lt;/code> sets the V8 old-space size in MiB and is allowed in &lt;code>NODE_OPTIONS&lt;/code>, so it can go in the service&amp;rsquo;s &lt;code>environment:&lt;/code> (for example &lt;code>NODE_OPTIONS=--max-old-space-size=768&lt;/code> under a 1 GB limit). For Java, &lt;code>-XX:MaxRAMPercentage&lt;/code> sets the heap as a percentage of available memory (default 25), passed through &lt;code>JDK_JAVA_OPTIONS&lt;/code>. A database cache, shared memory and native allocations also count against the limit; &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">Compose environment variables&lt;/a> covers getting those settings into the container.&lt;/p>
&lt;p>&lt;strong>The host ran out.&lt;/strong> With no container limit and an out-of-memory line in the kernel log, raising one container&amp;rsquo;s limit is not a fix. Docker warns that when the host runs out, the kernel can kill any process, including Docker itself. Inventory what runs on the host, set limits so one container cannot take everything, and add RAM if the total does not fit; the &lt;a href="https://techfuelhq.com/tools/docker-ram-planner/">Docker RAM planner&lt;/a> estimates a stack&amp;rsquo;s needs and the &lt;a href="https://techfuelhq.com/homelab/proxmox-hardware-requirements-2026/">Proxmox hardware requirements guide&lt;/a> covers host sizing. If Docker runs inside a Proxmox VM or LXC, that guest&amp;rsquo;s own memory is the ceiling: size it with the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">capacity planner&lt;/a>, and see how limits differ in &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM&lt;/a>. Docker&amp;rsquo;s own advice includes being mindful with swap: slower than memory, but a buffer against running out.&lt;/p>
&lt;p>&lt;strong>Docker Desktop&amp;rsquo;s VM ran out.&lt;/strong> On Docker Desktop the containers share one VM&amp;rsquo;s memory. With the Hyper-V backend, and on Mac and Linux, raise &lt;strong>Memory limit&lt;/strong> under Settings, Resources, Advanced; it defaults to 50% of the host&amp;rsquo;s memory. With the WSL 2 backend, Docker Desktop points you to the WSL utility VM instead: set &lt;code>memory=&lt;/code> under &lt;code>[wsl2]&lt;/code> in &lt;code>%UserProfile%\.wslconfig&lt;/code> (default: 50% of Windows memory), then run &lt;code>wsl --shutdown&lt;/code> so the VM restarts with the new size.&lt;/p>
&lt;p>&lt;strong>Not memory: a stop timeout.&lt;/strong> If Docker&amp;rsquo;s events show a stop or restart just before the kill (see the &lt;a href="#when-the-quick-check-is-not-enough">full capture&lt;/a>), the process ignored &lt;code>SIGTERM&lt;/code> for the whole grace period. A common cause, &lt;a href="https://docs.docker.com/reference/cli/docker/container/kill/" rel="noopener">per Docker&lt;/a>: a shell-form &lt;code>ENTRYPOINT&lt;/code> or &lt;code>CMD&lt;/code> runs under &lt;code>/bin/sh -c&lt;/code>, which does not pass signals on, so the real process never hears the stop. Fix the signal handling, or give a slow-stopping service more time with &lt;code>stop_grace_period&lt;/code> in Compose. Do not change memory because the final number happened to be 137.&lt;/p>
&lt;p>&lt;strong>Not memory: someone or something killed it.&lt;/strong> A &lt;code>docker kill&lt;/code>, an orchestrator, or an automation script sends &lt;code>SIGKILL&lt;/code> by default. Trace the actor from the daemon, scheduler or automation log. The container behaved as instructed.&lt;/p>
&lt;p>&lt;strong>Stop here&lt;/strong> if none of the four steps shows memory evidence, a stop or a kill. Do not edit limits by guesswork: keep the container, run the full capture below, and wait for a second occurrence with better records. If the image belongs to a project, its issue tracker is the next stop, with your capture attached.&lt;/p>
&lt;h2 id="when-the-quick-check-is-not-enough">When the quick check is not enough&lt;/h2>
&lt;p>The quick check reads the container&amp;rsquo;s current state. For an incident that has to be explained properly, or one where the service has already restarted, bind every observation to the &lt;strong>same container ID and time window&lt;/strong>. Capture first. Change one thing only after the evidence names a cause.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">Hardware Diagnostic Workbench&lt;/a> can hold that container ID, time window, configured limits, event sequence, kernel or daemon evidence, cgroup counters, and each later test. It records; it does not interpret exit 137 as an OOM verdict.&lt;/p>
&lt;h3 id="the-four-records-to-save-first">The four records to save first&lt;/h3>
&lt;p>First, find the &lt;strong>historical container ID&lt;/strong> on the daemon that ran the failing service. A name such as &lt;code>worker-1&lt;/code> can already belong to its replacement. Set a narrow interval that has &lt;strong>already ended&lt;/strong>; use UTC or an explicit offset. The example times below are placeholders.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>SINCE&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;2026-10-03T18:20:00-05:00&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>UNTIL&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;2026-10-03T18:30:00-05:00&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">(&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> set -C
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> docker events --since &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$SINCE&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --until &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$UNTIL&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --filter type&lt;span style="color:#f92672">=&lt;/span>container &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --format &lt;span style="color:#e6db74">&amp;#39;{{json .}}&amp;#39;&lt;/span> &amp;gt; docker-137-events.jsonl
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">)&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Run that from a private local folder. &lt;code>set -C&lt;/code> prevents Bash from overwriting an existing capture. Keep the file private: event attributes can contain names and labels for other containers on this daemon. &lt;a href="https://docs.docker.com/reference/cli/docker/system/events/" rel="noopener">Docker returns only the last 256 events&lt;/a>; an empty window is not proof that no container died. If the command fails, fix the capture error before interpreting the file.&lt;/p>
&lt;p>Find the &lt;code>die&lt;/code> line whose &lt;code>exitCode&lt;/code> is &lt;code>137&lt;/code> at the incident time. In that line&amp;rsquo;s &lt;code>Actor&lt;/code> object, copy the full &lt;code>ID&lt;/code>. If several exits match, keep them separate. The remaining commands use that ID, even if the name now points somewhere else.&lt;/p>
&lt;p>Second, inspect that exact container. Set &lt;code>CONTAINER&lt;/code> to the ID you copied; the placeholder below is intentionally not a valid ID.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>CONTAINER&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;paste-the-full-64-character-ID-from-the-die-event&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker inspect --type&lt;span style="color:#f92672">=&lt;/span>container &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --format &lt;span style="color:#e6db74">&amp;#39;id={{.Id}} name={{.Name}} state={{.State.Status}} image={{.Config.Image}} exit={{.State.ExitCode}} oom_killed={{.State.OOMKilled}} started={{.State.StartedAt}} finished={{.State.FinishedAt}} error={{json .State.Error}} memory={{.HostConfig.Memory}} reservation={{.HostConfig.MemoryReservation}} memory_swap={{.HostConfig.MemorySwap}} oom_kill_disable={{json .HostConfig.OomKillDisable}} restart_count={{.RestartCount}}&amp;#39;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CONTAINER&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If inspection says &lt;strong>No such object&lt;/strong>, save that result and continue with the historical events and host logs. Do not replace &lt;code>CONTAINER&lt;/code> with the service name. If the ID still exists, compare &lt;code>StartedAt&lt;/code> and &lt;code>FinishedAt&lt;/code> with the incident. State from a run that started &lt;strong>after&lt;/strong> the failure cannot explain the earlier exit. Even when the ID matches, a later run&amp;rsquo;s exit code, OOM flag or current memory setting is not a historical reading.&lt;/p>
&lt;p>Third, if the original ID still exists, save its application output from the same interval. This can show an orderly shutdown request, an application-level allocation failure, or the last completed operation. If the object is gone, use any existing external logs for that ID. Missing logs do not prove a kernel kill.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker logs --timestamps --since &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$SINCE&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --until &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$UNTIL&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CONTAINER&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Fourth, check the host kernel and Docker daemon around those timestamps. &lt;code>journalctl&lt;/code> accepts &lt;a href="https://www.freedesktop.org/software/systemd/man/255/journalctl.html#-S%20TIME" rel="noopener">space-separated date and time values&lt;/a> for &lt;code>--since&lt;/code> and &lt;code>--until&lt;/code>; the separate UTC values below describe the same interval as the Docker variables above and work on systemd releases that do not accept that RFC 3339 form. These read-only queries explicitly select the current boot:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>JOURNAL_SINCE&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;2026-10-03 23:20:00 UTC&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>JOURNAL_UNTIL&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;2026-10-03 23:30:00 UTC&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>journalctl -k --boot&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">0&lt;/span> --since &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$JOURNAL_SINCE&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --until &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$JOURNAL_UNTIL&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --no-pager &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> | grep -Ei &lt;span style="color:#e6db74">&amp;#39;out of memory|oom-kill|killed process|memory cgroup&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>journalctl -u docker.service --boot&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">0&lt;/span> --since &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$JOURNAL_SINCE&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --until &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$JOURNAL_UNTIL&lt;span style="color:#e6db74">&amp;#34;&lt;/span> --no-pager
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If the incident occurred before the current boot, run &lt;a href="https://www.freedesktop.org/software/systemd/man/255/journalctl.html#--list-boots" rel="noopener">&lt;code>journalctl --list-boots&lt;/code>&lt;/a>, choose the boot ID whose recorded interval contains the incident, and replace &lt;code>--boot=0&lt;/code> in both commands with &lt;code>--boot=THE_32_CHARACTER_BOOT_ID&lt;/code>. If the host does not use systemd, use its actual kernel and daemon log mechanism. Do not substitute an unbounded &lt;code>dmesg | tail&lt;/code> and then assume the last message belongs to this incident.&lt;/p>
&lt;h3 id="restart-or-replacement">Same name, different run&lt;/h3>
&lt;p>&lt;a href="https://docs.docker.com/reference/cli/docker/compose/up/" rel="noopener">Docker Compose can recreate a container&lt;/a> when its image or configuration changes. A restart poses a different problem: the ID can stay the same, while &lt;a href="https://github.com/moby/moby/blob/b3b7197adfc8f056dd50b74317ed3c26d1abb82f/daemon/container/state.go#L272-L280" rel="noopener">the Engine resets the exit code and OOM flag when the container starts&lt;/a>. Neither a healthy replacement nor &lt;code>OOMKilled=false&lt;/code> on a later run clears an earlier incident. Match the individual &lt;code>die&lt;/code> event by time and full ID, not by name.&lt;/p>
&lt;p>To practise reading a capture, save the &lt;a href="https://techfuelhq.com/downloads/docker-137-window.py">Python 3 timeline reader&lt;/a> and the &lt;a href="https://techfuelhq.com/downloads/docker-137-synthetic.jsonl">synthetic event file&lt;/a> in one folder. &lt;strong>The file is a practice incident&lt;/strong>, not an outage recorded on this site: two exits on one ID, then a replacement with the same name. The reader only opens the local file you name; it does not connect to Docker or need extra packages.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>python3 docker-137-window.py docker-137-synthetic.jsonl
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>python3 docker-137-window.py docker-137-synthetic.jsonl --name worker-1
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>python3 docker-137-window.py docker-137-synthetic.jsonl --id a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>For your own incident, substitute &lt;code>docker-137-events.jsonl&lt;/code> and the full ID from your own output. A &lt;a href="https://github.com/moby/moby/issues/40613" rel="noopener">Moby user&amp;rsquo;s incident report&lt;/a> shows &lt;code>ExitCode: 137&lt;/code> and &lt;code>OOMKilled: false&lt;/code> together; that is a useful counterexample, not a diagnosis of your host.&lt;/p>
&lt;h3 id="read-the-evidence-as-a-set">Read the evidence as a set&lt;/h3>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you captured&lt;/th>
&lt;th scope="col">What it establishes&lt;/th>
&lt;th scope="col">What it does not establish&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you captured">Exit code &lt;code>137&lt;/code> only&lt;/td>
&lt;td data-label="What it establishes">The container command reported 137&lt;/td>
&lt;td data-label="What it does not establish">Who or what chose that value&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">&lt;code>State.OOMKilled=true&lt;/code>&lt;/td>
&lt;td data-label="What it establishes">Docker recorded an OOM-killed state&lt;/td>
&lt;td data-label="What it does not establish">Which memory boundary caused it, or how much memory is safe&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">Docker &lt;code>oom&lt;/code> event in the same window&lt;/td>
&lt;td data-label="What it establishes">Docker emitted an OOM event for that container&lt;/td>
&lt;td data-label="What it does not establish">Whether the configured limit is simply too small, the host is overcommitted, or the workload is leaking&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">&lt;code>kill&lt;/code> followed by &lt;code>die&lt;/code>, with the signal and matching time&lt;/td>
&lt;td data-label="What it establishes">A signal was sent in Docker&amp;rsquo;s event sequence&lt;/td>
&lt;td data-label="What it does not establish">Who initiated it unless the surrounding daemon/orchestrator record says so&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">Kernel OOM record naming the victim/cgroup&lt;/td>
&lt;td data-label="What it establishes">The kernel selected a process under memory pressure&lt;/td>
&lt;td data-label="What it does not establish">That blindly raising this container&amp;rsquo;s limit protects the host&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">The exact cgroup&amp;rsquo;s local &lt;code>oom&lt;/code> counter increased&lt;/td>
&lt;td data-label="What it establishes">An allocation in that cgroup was about to fail because of that cgroup&amp;rsquo;s memory limit&lt;/td>
&lt;td data-label="What it does not establish">Which process was selected, or how much memory is safe&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">cgroup &lt;code>oom_kill&lt;/code> counter increase&lt;/td>
&lt;td data-label="What it establishes">An OOM killer killed a process in that cgroup&lt;/td>
&lt;td data-label="What it does not establish">Which cgroup supplied the limiting boundary, or that the killed process was the container&amp;rsquo;s PID 1&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you captured">&lt;code>State.OOMKilled=false&lt;/code> and no memory evidence&lt;/td>
&lt;td data-label="What it establishes">No OOM cause has been demonstrated&lt;/td>
&lt;td data-label="What it does not establish">That memory pressure is impossible&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>That last row prevents a reasoning error. A false flag is not permission to declare &amp;ldquo;not memory,&amp;rdquo; just as a &lt;code>137&lt;/code> is not permission to declare &amp;ldquo;memory.&amp;rdquo; Keep the cause unknown until another record closes the gap.&lt;/p>
&lt;h3 id="separate-a-container-boundary-from-host-pressure">Separate a container boundary from host pressure&lt;/h3>
&lt;p>The &lt;code>memory&lt;/code> value in the inspect record is the hard memory limit in bytes. A zero means Docker did not configure a per-container hard limit. It does not mean the host, VM, systemd unit, parent cgroup, or orchestrator is unlimited.&lt;/p>
&lt;p>&lt;a href="https://docs.docker.com/engine/containers/resource_constraints/" rel="noopener">Docker&amp;rsquo;s resource documentation&lt;/a> distinguishes a hard &lt;code>--memory&lt;/code> limit from a softer &lt;code>--memory-reservation&lt;/code>. It also warns that without constraints a container can use as much memory as the host kernel scheduler allows, and that host OOM can select processes when the machine cannot perform essential work.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>A nonzero container limit and matching Docker &lt;code>oom&lt;/code> event do not identify the limiting boundary by themselves.&lt;/strong> A kernel OOM record naming that cgroup as the limiting boundary, or a same-window increase in &lt;code>oom&lt;/code> from that exact cgroup&amp;rsquo;s &lt;code>memory.events.local&lt;/code>, corroborates the container boundary. An &lt;code>oom_kill&lt;/code> increase alone only says a process in the cgroup was killed by an OOM killer.&lt;/li>
&lt;li>&lt;strong>No container hard limit plus a host kernel OOM record&lt;/strong> points to host or parent-boundary pressure. Giving one container more memory is not a fix; it has no private boundary to raise.&lt;/li>
&lt;li>&lt;strong>A &lt;code>kill&lt;/code> or stop-timeout sequence with no correlated memory evidence&lt;/strong> points away from an OOM diagnosis. Docker documents that &lt;code>docker stop&lt;/code> sends the configured stop signal first and forcibly sends &lt;code>SIGKILL&lt;/code> after the timeout.&lt;/li>
&lt;li>&lt;strong>No correlated record&lt;/strong> stays unresolved. Preserve the worksheet, increase observability, and wait for a second incident rather than editing limits by guesswork.&lt;/li>
&lt;/ol>
&lt;h3 id="read-cgroup-counters-only-where-the-host-exposes-them">Read cgroup counters only where the host exposes them&lt;/h3>
&lt;p>Do not paste a path from someone else&amp;rsquo;s machine. Docker&amp;rsquo;s cgroup driver, systemd integration, parent cgroup and cgroup version determine the location. Locate the container&amp;rsquo;s cgroup through that host&amp;rsquo;s runtime configuration, replace the placeholder assignment below with the path you verified, then read the files that actually exist there. These commands only read those files.&lt;/p>
&lt;p>For &lt;strong>cgroup v2&lt;/strong>, read the following &lt;a href="https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files" rel="noopener">Linux kernel memory-interface files&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>CGROUP_PATH&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;/replace/with/verified/container-cgroup-path&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.max&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.high&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.events&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.events.local&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>memory.max&lt;/code> is the hard limit. &lt;code>memory.high&lt;/code> applies reclaim pressure but does not itself invoke the OOM killer. In &lt;code>memory.events&lt;/code>, &lt;code>oom&lt;/code> counts occasions when allocation was about to fail at the limit, while &lt;code>oom_kill&lt;/code> counts processes in the cgroup killed by an OOM killer. The regular file is hierarchical; &lt;code>memory.events.local&lt;/code> is local to that cgroup.&lt;/p>
&lt;p>For a host still using &lt;strong>cgroup v1&lt;/strong>, the &lt;a href="https://docs.kernel.org/admin-guide/cgroup-v1/memory.html" rel="noopener">kernel documents&lt;/a> the older files below. The same documentation marks the v1 soft-limit and OOM-control interfaces deprecated, so read them as legacy evidence rather than advice for new configuration.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>CGROUP_PATH&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;/replace/with/verified/container-cgroup-path&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.limit_in_bytes&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.usage_in_bytes&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.failcnt&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$CGROUP_PATH&lt;span style="color:#e6db74">/memory.oom_control&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If the container was removed or its cgroup disappeared, say that the counters were unavailable. Do not replace missing evidence with a guessed path or a counter from a new container.&lt;/p>
&lt;h3 id="incident-worksheet">Incident worksheet&lt;/h3>
&lt;p>Copy this before changing anything, and fill it in from the records above:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>Docker exit-137 incident
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Observed at (timestamp + timezone):
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Host name / VM:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Docker Engine version:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Container name:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Full container ID:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Incident die timestamp (UTC):
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Any later start for the same ID, or replacement ID using the same name?:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Image + immutable digest if available:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Compose project / service or launcher:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>State
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> ExitCode:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> OOMKilled:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> StartedAt:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> FinishedAt:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> RestartCount:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> State.Error:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Configured boundary (bytes as reported by inspect)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Memory:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> MemoryReservation:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> MemorySwap:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> OomKillDisable:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Parent/orchestrator limit, if separately proven:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Same-window evidence
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Docker oom event: yes / no / unavailable
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Docker kill event + signal:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Docker die event + exitCode:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Stop/restart event immediately before death:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Kernel OOM record naming process/cgroup: yes / no / unavailable
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> cgroup version and exact path:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> memory.events(.local) before change, if retained:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Application&amp;#39;s last timestamped log line:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Classification
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> [ ] container/parent OOM is correlated
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> [ ] host OOM is correlated
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> [ ] stop timeout or external signal is correlated
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> [ ] application returned 137 without proven SIGKILL
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> [ ] unknown: preserve evidence and observe again
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>One change to test next:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Result and timestamp:
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The empty boxes matter. &amp;ldquo;Unavailable&amp;rdquo; is evidence quality; it is not a &amp;ldquo;no.&amp;rdquo;&lt;/p>
&lt;h2 id="what-i-verified-and-what-i-did-not">What I verified and what I did not&lt;/h2>
&lt;p>I verified the command syntax and field semantics against Docker&amp;rsquo;s current documentation and the cgroup file meanings against current Linux kernel documentation on 2026-10-03. I did not run an OOM experiment on a Docker host for this article, so none of the worksheet values or branches is presented as a TechFuelHQ measurement.&lt;/p>
&lt;p>The downloadable practice capture exercises the local event reader with two exits on the same container and another container reusing its name. It is not a live Docker or OOM test.&lt;/p>
&lt;p>The article also does not assume Kubernetes. Pod eviction, Kubernetes &lt;code>OOMKilled&lt;/code> status, pod limits and node-pressure decisions add another control plane and need their own evidence path.&lt;/p>
&lt;hr>
&lt;p>&lt;em>If the incident is actually disk pressure rather than memory pressure, the &lt;a href="https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/">Docker cleanup guide&lt;/a> separates disposable cache and images from volumes that can contain the only copy of data.&lt;/em>&lt;/p></description></item><item><title>How to Check CPU Temp in Windows 11 (2026)</title><link>https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/</link><pubDate>Sun, 13 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/</guid><atom:updated>2026-11-18T07:20:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · How to check CPU temp&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Any Intel or AMD PC:&lt;/strong> Core Temp for a quick per-core number. HWiNFO, a free download, for several readings side by side.&lt;/li>
&lt;li>&lt;strong>A desktop Ryzen:&lt;/strong> AMD's Ryzen Master shows the current CPU temperature.&lt;/li>
&lt;li>&lt;strong>No software:&lt;/strong> the BIOS shows CPU temperature, but only while the PC sits in firmware. It is an idle number.&lt;/li>
&lt;li>&lt;strong>Which reading on AMD:&lt;/strong> I watch CPU (Tctl/Tdie). HWiNFO's author says the Die (average) value always runs somewhat lower.&lt;/li>
&lt;li>&lt;strong>GPU temperature:&lt;/strong> Task Manager's Performance tab shows it for a dedicated card. On NVIDIA, nvidia-smi prints it in one line.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Windows shows your graphics card&amp;rsquo;s temperature and hides your processor&amp;rsquo;s. How-To Geek&amp;rsquo;s long-running guide puts it flatly: &amp;ldquo;Neither Windows 10 nor Windows 11 has a built-in way to see your computer&amp;rsquo;s CPU temperature, so you&amp;rsquo;ll need a third-party program for this.&amp;rdquo;&lt;/p>
&lt;p>I checked what my own desktop exposes, a Ryzen 7 7800X3D and RTX 5080 on Windows 11 Home 25H2. One command printed the GPU at 60 C. The two thermal sources Windows offers to scripts came back empty.&lt;/p>
&lt;p>So the CPU number has to come from the firmware or from a tool that reads the chip&amp;rsquo;s sensors. This page covers the four routes that work and which reading to trust. It also covers two commands that came back empty on my desktop. Already have a number and want to know if it is too hot? The &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe CPU temperature guide&lt;/a> has the ranges by chip. If it is too hot, &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating&lt;/a> sorts out the cause by when it happens.&lt;/p>
&lt;h2 id="how-to-check-cpu-and-gpu-temperature-in-windows-11-or-10">How to check CPU and GPU temperature in Windows 11 or 10&lt;/h2>
&lt;p>Windows does not put CPU temperature in Task Manager. For a quick CPU reading, restart into the BIOS or open a sensor tool such as Core Temp. On a supported desktop Ryzen processor, AMD&amp;rsquo;s &lt;a href="https://docs.amd.com/r/en-US/68886-ryzen-master-user-guide/Gauges" rel="noopener">Ryzen Master gauges&lt;/a> show the current CPU temperature and its maximum. Use HWiNFO when you need CPU package and per-core readings beside motherboard, storage, or GPU sensors.&lt;/p>
&lt;p>For a dedicated GPU, open &lt;strong>Task Manager &amp;gt; Performance &amp;gt; GPU&lt;/strong> and read Temperature. That GPU field does not expose the processor temperature. Windows 10 and Windows 11 have the same split: Task Manager for the supported GPU reading, firmware or a hardware monitor for the CPU. Check idle first, then leave the monitor open while you repeat the workload that made you concerned. That gives the temperature context instead of one unexplained number.&lt;/p>
&lt;h2 id="which-number-to-watch">Which number to watch&lt;/h2>
&lt;p>Open a serious monitoring tool and you get several CPU temperatures. HWiNFO&amp;rsquo;s author explained why on his forum in June 2024, answering a 7800X3D owner who could not tell which to trust: &amp;ldquo;There are dozens of various temperature sensors inside the CPU (CCD or IOD) and each of those values takes a different set of sensors into account and uses a different evaluation formula.&amp;rdquo; He added that &amp;ldquo;AMD doesn&amp;rsquo;t fully disclose all details about the exact meaning.&amp;rdquo;&lt;/p>
&lt;p>Two tools reading different sensors can disagree. That alone does not mean one is broken.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>On a Ryzen, I watch CPU (Tctl/Tdie).&lt;/strong> The author labels Tctl the control temperature. HWiNFO shows that single CPU (Tctl/Tdie) line when the two values are the same. On a chip with an offset it lists Tctl and Tdie separately, and in 2018 he put a Ryzen 7 2700X&amp;rsquo;s gap at 10 C, with Tdie as the real temperature.&lt;/li>
&lt;li>&lt;strong>Expect CPU Die (average) to read lower.&lt;/strong> In the author&amp;rsquo;s words it &amp;ldquo;is the average value among multiple sensors during a certain period. So it will always be somewhat lower than the instant (max) value.&amp;rdquo;&lt;/li>
&lt;li>&lt;strong>On Intel,&lt;/strong> users on HWiNFO&amp;rsquo;s forum describe a CPU Package reading next to the per-core values.&lt;/li>
&lt;li>&lt;strong>Judge idle and load separately.&lt;/strong> A number means little until you know what the PC was doing.&lt;/li>
&lt;/ul>
&lt;h2 id="method-1-the-bios-no-software-needed">Method 1: the BIOS, no software needed&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s own route from Windows 11 starts in Settings. Select System, choose Recovery and select Restart now under Advanced startup. On the next screen select Troubleshoot. Choose Advanced options. Select UEFI Firmware Settings and choose Restart. The PC reboots straight into the firmware.&lt;/p>
&lt;p>Where the temperature sits depends on the board maker. Check your manual. On ASUS boards that stop at boot with a CPU Over Temperature Error, the company&amp;rsquo;s support page tells owners to &amp;ldquo;Press [F1] to enter into BIOS Setup EZ Mode,&amp;rdquo; where the current CPU temperature is shown in EZ Mode, in red when it is too high. How-To Geek&amp;rsquo;s Windows 11 guide says you &amp;ldquo;might find your CPU&amp;rsquo;s current temperature next to the &amp;lsquo;CPU Core Temperature&amp;rsquo; or a similar option.&amp;rdquo;&lt;/p>
&lt;p>The catch is what the PC is doing at that moment. Nothing.&lt;/p>
&lt;p>The same guide notes that &amp;ldquo;this method shows your CPU temp when Windows 11 isn&amp;rsquo;t loaded,&amp;rdquo; so it is good for spotting a cooler that is not mounted and useless for judging how the chip runs in a game.&lt;/p>
&lt;h2 id="method-2-ryzen-master-on-an-amd-cpu">Method 2: Ryzen Master on an AMD CPU&lt;/h2>
&lt;p>AMD&amp;rsquo;s own utility is the first thing I would open on a desktop Ryzen. AMD&amp;rsquo;s user guide lists desktop processors on the AM4 and AM5 sockets, plus SP6. AMD describes it as offering &amp;ldquo;real-time monitoring of per-core clock rates, temperature and voltages including average and peak readings,&amp;rdquo; and says that for the CPU &amp;ldquo;you can monitor individual CCDs.&amp;rdquo; The current download covers Ryzen 5000 processors and later, with separate builds for older generations. I have Ryzen Master 3.1.0.5185 installed on my desktop.&lt;/p>
&lt;p>Read it while the load is still running.&lt;/p>
&lt;p>A CPU&amp;rsquo;s temperature falls quickly once a load stops, as the Reddit example further down shows. AMD&amp;rsquo;s user guide defines the CPU Temperature gauge as the current processor temperature, so after twenty minutes of play the number you see when you alt-tab out has already started to fall. Keep the window on a second screen while the game runs.&lt;/p>
&lt;h2 id="method-3-core-temp-the-quick-check">Method 3: Core Temp, the quick check&lt;/h2>
&lt;p>Core Temp does one job. Its maker calls it &amp;ldquo;a compact, no fuss, small footprint, yet powerful program to monitor processor temperature and other vital information,&amp;rdquo; and says it is &amp;ldquo;capable of displaying a temperature of each individual core of every processor in your system.&amp;rdquo; It reads the processor&amp;rsquo;s digital thermal sensor, which the site says &amp;ldquo;provides more accurate and higher resolution temperature readings than conventional onboard thermal sensors.&amp;rdquo; It supports both Intel and AMD processors. The current release is 1.20.1, dated May 2, 2026.&lt;/p>
&lt;h2 id="method-4-hwinfo-every-reading-at-once">Method 4: HWiNFO, every reading at once&lt;/h2>
&lt;p>HWiNFO is what I would use to settle an argument between two tools. It lists the instant and averaged CPU readings side by side. Its site offers it as a free download and describes it as &amp;ldquo;Comprehensive Hardware Analysis, Monitoring and Reporting for Windows and DOS.&amp;rdquo; On a Ryzen whose Tctl and Tdie match, CPU (Tctl/Tdie) and CPU Die (average) sit together in its sensor readings. The gap between them is the averaging the author described. I have not installed HWiNFO or Core Temp on this desktop, so the details for both come from their makers and from the HWiNFO author&amp;rsquo;s forum answers.&lt;/p>
&lt;h2 id="method-5-msi-afterburner-in-a-game-overlay">Method 5: MSI Afterburner in a game overlay&lt;/h2>
&lt;p>Use the CPU entry by name.&lt;/p>
&lt;p>MSI&amp;rsquo;s &lt;a href="https://www.msi.com/blog/msi-afterburner-on-screen-display/" rel="noopener">Afterburner monitoring guide&lt;/a>
documents CPU temperature as an on-screen statistic. Install the bundled &lt;strong>RivaTuner
Statistics Server&lt;/strong> as well; MSI says RTSS supplies the on-screen display.&lt;/p>
&lt;p>Open Afterburner,
choose &lt;strong>Settings &amp;gt; Monitoring&lt;/strong>, find &lt;strong>CPU temperature&lt;/strong>, enable its check mark, select it,
then enable &lt;strong>Show in On-Screen Display&lt;/strong> and choose Apply. Leave Afterburner and RTSS running
while the game is open.&lt;/p>
&lt;p>The entry still depends on Afterburner exposing a supported CPU sensor on that machine. If
CPU temperature is absent, stuck, or does not move when the workload changes, the overlay has
not produced a trustworthy processor reading. Do not select &lt;strong>GPU temperature&lt;/strong> and relabel it;
that is the graphics card. Use HWiNFO or Core Temp above for the CPU instead. The overlay is a
display route, not a reason to change Afterburner&amp;rsquo;s clock, voltage, power or fan controls.&lt;/p>
&lt;h2 id="gpu-temperature-task-manager-and-nvidia-smi">GPU temperature: Task Manager and nvidia-smi&lt;/h2>
&lt;p>Task Manager does show one temperature. Microsoft added it in August 2019: &amp;ldquo;If you have a dedicated GPU card, we will now bubble up the current temperature next to its listing in the Performance Tab.&amp;rdquo; It needs a graphics driver &amp;ldquo;which supports version 2.4 (or higher) of WDDM.&amp;rdquo; To check yours, Microsoft says to &amp;ldquo;press WIN+R and enter dxdiag. Under the Display tab, it will say your WDDM version next to Driver Model.&amp;rdquo; The value is shown in Celsius only.&lt;/p>
&lt;p>On an NVIDIA card the driver&amp;rsquo;s own tool is faster. I ran this in a terminal:&lt;/p>
&lt;pre tabindex="0">&lt;code>nvidia-smi --query-gpu=name,driver_version,temperature.gpu,utilization.gpu,power.draw --format=csv
&lt;/code>&lt;/pre>&lt;p>It printed my RTX 5080 at 60 C on driver 616.56, at 99 percent utilization and 350.20 W. The &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">safe GPU temperature guide&lt;/a> shows how to compare that reading with the exact limit reported by a supported NVIDIA card.&lt;/p>
&lt;p>If your card reaches its limit under a similar load, the &lt;a href="https://techfuelhq.com/articles/gpu-overheating-2026/">GPU overheating guide&lt;/a> is the next stop.&lt;/p>
&lt;h2 id="the-commands-that-came-back-empty-on-my-desktop">The commands that came back empty on my desktop&lt;/h2>
&lt;p>Search results still hand out a PowerShell or Command Prompt query of MSAcpi_ThermalZoneTemperature as the no-download answer. On the day I checked, Bing&amp;rsquo;s answer box told readers to run the Command Prompt version as administrator. On my desktop the PowerShell version, run without administrator rights, answered &amp;ldquo;Not supported.&amp;rdquo; Windows&amp;rsquo; own Thermal Zone Information performance counter did no better: &amp;ldquo;The specified instance is not present.&amp;rdquo; I did not run either one elevated. I would not send anyone down that route when the four above work.&lt;/p>
&lt;h2 id="check-that-the-reading-is-real">Check that the reading is real&lt;/h2>
&lt;p>A real CPU temperature moves. It drops within seconds of the PC going idle and climbs as soon as a load starts. A poster on r/techsupport shared exactly that shape this month, reading a Ryzen 7 5800X on a 240 mm AIO: 34.1 C doing nothing, 60 C when Firefox opened before it &amp;ldquo;quickly returns to 35,&amp;rdquo; and 83.2 C during a game. Does your number barely change whatever you do? Then you are probably watching the wrong sensor.&lt;/p>
&lt;p>Then compare the load number with your chip&amp;rsquo;s limit. On my 7800X3D that ceiling is about 89 C, lower than most Ryzen chips. The &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe temperature guide&lt;/a> lists the rest. If the peak climbs toward the limit on a light load, old paste is a common culprit, and the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> covers the repaste. On an X3D chip already near its limit, the &lt;a href="https://techfuelhq.com/articles/9800x3d-undervolt-guide-2026/">9800X3D undervolt guide&lt;/a> can buy back a few degrees on its efficiency path, though the guide says neither result is guaranteed on your chip.&lt;/p>
&lt;h2 id="temperature-monitoring-benchmarks-and-ssd-checks">Temperature monitoring, benchmarks and SSD checks&lt;/h2>
&lt;p>A sensor reading and a benchmark score answer different questions.&lt;/p>
&lt;p>Name the sensor. Record the workload and time with each temperature; then compare the exact CPU&amp;rsquo;s limit in the &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">temperature guide&lt;/a>. For GPU temperature, use the Task Manager or &lt;code>nvidia-smi&lt;/code> method above. MSI also documents selecting &lt;strong>CPU temperature&lt;/strong> under Afterburner&amp;rsquo;s &lt;strong>Settings &amp;gt; Monitoring&lt;/strong> in its &lt;a href="https://www.msi.com/blog/msi-afterburner-on-screen-display/" rel="noopener">monitoring guide&lt;/a>; available readings depend on hardware support.&lt;/p>
&lt;p>For a CPU performance test, &lt;a href="https://www.maxon.net/en/cinebench" rel="noopener">Maxon&amp;rsquo;s free Cinebench&lt;/a> measures rendering performance and provides current platform requirements. For a gaming graphics benchmark, &lt;a href="https://benchmarks.ul.com/en/3dmark/download" rel="noopener">UL&amp;rsquo;s official 3DMark download page&lt;/a> directs users to the Steam demo. Use the same test version and preset for comparisons. Neither result is an FPS forecast for every game, and a temperature utility does not produce either score.&lt;/p>
&lt;p>SSD health is another check. The &lt;a href="https://techfuelhq.com/articles/ssd-health-check-2026/">SSD health guide&lt;/a> explains Windows&amp;rsquo; NVMe health fields and temperature, with a recorded example. &lt;a href="https://crystalmark.info/en/software/crystaldiskmark/" rel="noopener">CrystalDiskMark&lt;/a> measures storage performance; its publisher warns that results depend on test size, file position and other conditions. A speed result cannot substitute for a health log or prove that important data is safe. Back up before investigating a drive showing errors.&lt;/p>
&lt;p>To investigate a CPU fan, compare its reported RPM with the cooler manual and the actual temperature trend. A reading of zero needs context: the wrong header, a supported fan-stop mode or a missing tachometer signal can differ from a stopped cooler. Follow the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">cooler wiring and fan-warning checks&lt;/a> and power off before inspecting connections. Do not use a stress benchmark as the first test of a cooler suspected of failing.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://www.howtogeek.com/1035/ever-wonder-what-temperature-your-cpu-is-running-at/" rel="noopener">How-To Geek, How to Monitor Your Computer&amp;rsquo;s CPU Temperature (Whitson Gordon and Chris Hoffman, updated January 31, 2022)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.geeksforgeeks.org/techtips/check-your-cpu-temperature-on-windows-11/" rel="noopener">GeeksforGeeks, How to Check Your CPU Temperature on Windows 11 (updated February 2, 2026)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.howtogeek.com/884911/how-to-check-your-cpu-temperature-on-windows-11/" rel="noopener">How-To Geek, How to Check Your CPU Temperature on Windows 11 (Mahesh Makvana, updated November 11, 2023)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://blogs.windows.com/windows-insider/2019/08/16/announcing-windows-10-insider-preview-build-18963/" rel="noopener">Windows Insider Blog, Announcing Windows 10 Insider Preview Build 18963 (August 16, 2019; GPU temperature in Task Manager)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/security/devicesecurity/windows-11-and-secure-boot" rel="noopener">Microsoft Support, Windows 11 and Secure Boot (steps to UEFI Firmware Settings)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.asus.com/support/faq/1043819/" rel="noopener">ASUS Support FAQ 1043819, CPU Over Temperature Error occurs after bootup (updated 2025-11-25)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.amd.com/en/products/software/ryzen-master.html" rel="noopener">AMD, Ryzen Master utility&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.alcpu.com/CoreTemp/" rel="noopener">Core Temp (ALCPU), version 1.20.1&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.hwinfo.com/" rel="noopener">HWiNFO&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.hwinfo.com/forum/threads/is-cpu-tctl-value-is-still-a-tdie-value-on-ryzen.4977/" rel="noopener">HWiNFO Forum, Is CPU Tctl value is still a Tdie value on Ryzen? (replies by the HWiNFO author, May 25, 2018)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://docs.amd.com/r/en-US/68886-ryzen-master-user-guide/Gauges" rel="noopener">AMD Ryzen Master User Guide 3.1.0, Gauges&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://docs.amd.com/r/en-US/68886-ryzen-master-user-guide/Supported-Platforms" rel="noopener">AMD Ryzen Master User Guide 3.1.0, Supported Platforms&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.hwinfo.com/forum/threads/tctl-tdie-vs-tdie-which-should-i-be-referring-to.9808/" rel="noopener">HWiNFO Forum, Tctl/Tdie vs Tdie (replies by the HWiNFO author, June 20, 2024)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.hwinfo.com/forum/threads/cpu-package-temperature-different-for-intel-dts-sensor-and-enhanced-sensor.9140/" rel="noopener">HWiNFO Forum, CPU Package Temperature Different For Intel DTS Sensor And Enhanced Sensor (September 1, 2023)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.reddit.com/r/techsupport/comments/1wdmpm3/postbuild_my_pc_is_giving_off_a_lot_of_heat/" rel="noopener">Reddit r/techsupport, Post-Build: My PC is giving off a lot of heat during gaming (September 2026)&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Beelink EQ14 vs GMKtec G3 Plus: Which N150 Mini PC?</title><link>https://techfuelhq.com/homelab/beelink-eq14-vs-gmktec-g3-plus/</link><pubDate>Sun, 04 Oct 2026 23:45:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/beelink-eq14-vs-gmktec-g3-plus/</guid><atom:updated>2026-11-18T07:00:00Z</atom:updated><description>&lt;p>For a small host with one wired connection, I would start with the G3 Plus. Buy the EQ14 for two Ethernet ports. Both use the same entry-level processor; the choice comes down to which network version you order, the drives you want to fit and what the complete machine costs. Specifications checked October 4, 2026.&lt;/p>
&lt;h2 id="which-one-should-you-buy">Which one should you buy?&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Your requirement&lt;/th>
&lt;th scope="col">Starting choice&lt;/th>
&lt;th scope="col">Check before ordering&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Your requirement">Two physical wired connections&lt;/td>
&lt;td data-label="Starting choice">EQ14&lt;/td>
&lt;td data-label="Check before ordering">Select the intended gigabit or 2.5GbE version&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Your requirement">One 2.5GbE connection and a small host&lt;/td>
&lt;td data-label="Starting choice">G3 Plus&lt;/td>
&lt;td data-label="Check before ordering">Confirm the listing names Intel I226-V&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Your requirement">Reuse an M.2 2242 SATA drive&lt;/td>
&lt;td data-label="Starting choice">G3 Plus&lt;/td>
&lt;td data-label="Check before ordering">Match SATA protocol as well as the 2242 length&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Your requirement">Install two M.2 2280 drives&lt;/td>
&lt;td data-label="Starting choice">EQ14&lt;/td>
&lt;td data-label="Check before ordering">Confirm the exact unit&amp;rsquo;s supported drive protocols&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Your requirement">A workload that definitely requires 32GB&lt;/td>
&lt;td data-label="Starting choice">Compare a higher-capacity platform first&lt;/td>
&lt;td data-label="Check before ordering">Resolve the system-vendor/CPU-vendor support difference before paying&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Your requirement">A basic desktop or small service host&lt;/td>
&lt;td data-label="Starting choice">Whichever complete configuration fits for less&lt;/td>
&lt;td data-label="Check before ordering">Include RAM, SSD, network version and delivered cost&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Your requirement">A Frigate NVR&lt;/td>
&lt;td data-label="Starting choice">Not the EQ14&lt;/td>
&lt;td data-label="Check before ordering">Frigate&amp;rsquo;s hardware page says the EQ14 &amp;ldquo;has some known compatibility issues, so you should avoid that model for now&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The processor does not break the tie. Both systems use the four-core, four-thread N150; Intel specifies a single memory channel and 6W processor base power. Budget electricity from whole-system power instead. That 6W processor rating excludes the rest of the computer. &lt;a href="https://www.intel.com/content/www/us/en/products/sku/241636/intel-processor-n150-6m-cache-up-to-3-60-ghz/specifications.html" rel="noopener">Intel specifications&lt;/a>.&lt;/p>
&lt;p>Still choosing a processor class? Start with the broader &lt;a href="https://techfuelhq.com/homelab/n150-mini-pc-2026/">N150 buying guide&lt;/a> or our &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">mini-PC shortlist&lt;/a>. For Frigate hardware, see &lt;a href="https://techfuelhq.com/homelab/best-hardware-frigate-nvr-2026/">best hardware for Frigate NVR&lt;/a>; for Home Assistant, the &lt;a href="https://techfuelhq.com/homelab/best-mini-pc-home-assistant-2026/">mini PC for Home Assistant&lt;/a> guide.&lt;/p>
&lt;h2 id="the-configuration-differences-that-matter">The configuration differences that matter&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col">Beelink EQ14&lt;/th>
&lt;th scope="col">GMKtec NucBox G3 Plus&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">Processor&lt;/td>
&lt;td data-label="Beelink EQ14">Intel N150&lt;/td>
&lt;td data-label="GMKtec NucBox G3 Plus">Intel N150&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory slot&lt;/td>
&lt;td data-label="Beelink EQ14">DDR4 SO-DIMM&lt;/td>
&lt;td data-label="GMKtec NucBox G3 Plus">One DDR4-3200 SO-DIMM&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">System vendor&amp;rsquo;s published maximum&lt;/td>
&lt;td data-label="Beelink EQ14">16GB&lt;/td>
&lt;td data-label="GMKtec NucBox G3 Plus">32GB; Intel specifies 16GB for N150&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Wired networking&lt;/td>
&lt;td data-label="Beelink EQ14">Two gigabit RTL8111H ports &lt;strong>or&lt;/strong> two 2.5GbE I226-V ports&lt;/td>
&lt;td data-label="GMKtec NucBox G3 Plus">One 2.5GbE I226-V port&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Storage listed by manufacturer&lt;/td>
&lt;td data-label="Beelink EQ14">Two M.2 2280 PCIe 3.0 slots; supplied drive is SATA III&lt;/td>
&lt;td data-label="GMKtec NucBox G3 Plus">One M.2 2280 PCIe slot plus one M.2 2242 SATA slot&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Power arrangement&lt;/td>
&lt;td data-label="Beelink EQ14">Built-in power supply&lt;/td>
&lt;td data-label="GMKtec NucBox G3 Plus">External 12V/3A adapter&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Sources: &lt;a href="https://www.bee-link.com/products/beelink-eq14-n150" rel="noopener">Beelink EQ14 configuration/specification page&lt;/a>, &lt;a href="https://www.gmktec.com/products/nucbox-g3-plus-enhanced-performance-mini-pc-with-intel-n150-processor" rel="noopener">GMKtec G3 Plus specification table&lt;/a>.&lt;/p>
&lt;h3 id="ethernet-decide-how-many-physical-ports-you-need">Ethernet: decide how many physical ports you need&lt;/h3>
&lt;p>One connection to your switch? The G3 Plus is my pick. If you want separate physical connections for an upstream network and an isolated test network, the EQ14&amp;rsquo;s second port gives you a reason to choose it instead.&lt;/p>
&lt;p>Get the right EQ14 version. The gigabit model uses RTL8111H controllers; the 2.5GbE model uses I226-V. The product name alone leaves that unresolved, and the &lt;a href="https://techfuelhq.com/reviews/beelink-eq14-review-2026/">EQ14 review&lt;/a> covers how to tell them apart. Beelink&amp;rsquo;s &lt;a href="https://techfuelhq.com/reviews/beelink-mini-s13-review-2026/">Mini S13&lt;/a> is another N150 box with the same version question. For a router build, map the connections with the &lt;a href="https://techfuelhq.com/tutorials/opnsense-mini-pc-setup-2026/">OPNsense mini-PC setup guide&lt;/a> before ordering.&lt;/p>
&lt;h3 id="storage-match-the-drive-to-the-slot">Storage: match the drive to the slot&lt;/h3>
&lt;p>The G3 Plus makes this choice straightforward: one 2280 PCIe slot and one 2242 SATA slot. Match both length and protocol. A spare 2242 SATA drive gives you a specific reason to choose this box.&lt;/p>
&lt;p>The EQ14 needs a closer look. Beelink lists PCIe-capable slots but says the supplied SSD is SATA, and Notebookcheck&amp;rsquo;s January 2025 review tested a 512GB SATA configuration. That review identifies the installed drive in its sample; it does not settle which upgrade belongs in the unit on sale today. Ask for the supported drive protocols before buying two 2280 drives for it. &lt;a href="https://www.notebookcheck.net/Beelink-EQ14-mini-PC-review-Ready-to-go-HTPC-for-under-200.939127.0.html" rel="noopener">Notebookcheck&amp;rsquo;s tested configuration&lt;/a>.&lt;/p>
&lt;p>Use the &lt;a href="https://techfuelhq.com/tools/nvme-expansion-checker/">NVMe expansion checker&lt;/a> to organize the slot and lane requirements for your planned drives. Enter the exact machine&amp;rsquo;s specifications.&lt;/p>
&lt;h3 id="ram-budget-the-guests-before-buying">RAM: budget the guests before buying&lt;/h3>
&lt;p>Start with the guests you intend to keep. Put their allocations and the host reserve into the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox capacity planner&lt;/a>. Our &lt;a href="https://techfuelhq.com/homelab/proxmox-hardware-requirements-2026/">Proxmox hardware guide&lt;/a> supplies workload starting points.&lt;/p>
&lt;p>If that budget already presses against 16GB, I would price a higher-capacity platform. GMKtec advertises 32GB, while Intel publishes 16GB for the N150; buying around the higher figure means getting an exact supported module and support terms from GMKtec first. There is only one RAM slot in the G3 Plus. You cannot add a second module later. For a workload comfortably inside 16GB, choose on ports and total cost.&lt;/p>
&lt;h2 id="published-power-tests-and-what-they-mean-for-your-bill">Published power tests and what they mean for your bill&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Tested computer&lt;/th>
&lt;th scope="col" style="text-align: right">Reported idle result&lt;/th>
&lt;th scope="col">Source and context&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Tested computer">Beelink EQ14, N150&lt;/td>
&lt;td style="text-align: right" data-label="Reported idle result">8.91W average&lt;/td>
&lt;td data-label="Source and context">Notebookcheck, January 27, 2025; one-minute external-monitor test, 16GB RAM, 512GB SATA and dual gigabit Ethernet configuration&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tested computer">GMKtec G3 Plus, N150&lt;/td>
&lt;td style="text-align: right" data-label="Reported idle result">9.3W at the wall&lt;/td>
&lt;td data-label="Source and context">Jeff Geerling&amp;rsquo;s January 2025 test record; Ubuntu 24.04, replacement SSD; the record also describes cooling changes and a High Performance BIOS profile&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>These measurements belong to &lt;a href="https://www.notebookcheck.net/Beelink-EQ14-mini-PC-review-Ready-to-go-HTPC-for-under-200.939127.0.html" rel="noopener">Notebookcheck&lt;/a> and &lt;a href="https://github.com/geerlingguy/sbc-reviews/issues/64" rel="noopener">Jeff Geerling&lt;/a>. Their configurations and test conditions differ, so I would use the figures to budget running costs and choose neither machine on that small idle-power difference.&lt;/p>
&lt;p>For budgeting, use watts ÷ 1,000 × 8,760 hours × your electricity rate. At EIA&amp;rsquo;s August 2026 US residential average of &lt;strong>18.16 cents per kWh&lt;/strong>, a constant 10W system uses 87.6kWh a year and costs &lt;strong>$15.91&lt;/strong>; a constant 15W system uses 131.4kWh and costs &lt;strong>$23.86&lt;/strong>. Notebookcheck&amp;rsquo;s 8.91W EQ14 figure works out to 78.05kWh and &lt;strong>$14.17 a year&lt;/strong>, and Geerling&amp;rsquo;s 9.3W G3 Plus figure to 81.47kWh and &lt;strong>$14.79&lt;/strong>: a 62-cent gap between two different tests. Active work raises the annual average.&lt;/p>
&lt;p>Put your tariff into the &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">Power &amp;amp; Cost Calculator&lt;/a>, then compare the annual difference with the purchase difference. A tiny power saving is a poor reason to pay much more upfront. The &lt;a href="https://techfuelhq.com/homelab/24-7-homelab-idle-power-costs-2026/#mini-pc--sff-nodes-proxmox-hosts">published mini-PC power references&lt;/a> keep each measurement with its tested configuration.&lt;/p>
&lt;h2 id="compare-the-complete-machine-then-buy">Compare the complete machine, then buy&lt;/h2>
&lt;p>Compare complete machines. A barebone offer still needs memory and storage, and a cheaper EQ14 offer may be the other network variant. Write down the seller, exact configuration, installed RAM and SSD (model, capacity and protocol), Ethernet speed and controller, the upgrades you still need, the delivered total and the return window for each offer. With the needed ports and capacity covered, buy the lower delivered total. Save the final configuration and planned workloads in &lt;a href="https://techfuelhq.com/tools/hardware-projects/">Hardware Projects&lt;/a> for later upgrades, and follow the &lt;a href="https://techfuelhq.com/articles/proxmox-mini-pc-setup/">Proxmox mini-PC setup&lt;/a> once it arrives.&lt;/p>
&lt;p>Newegg&amp;rsquo;s product catalogue on November 17, 2026 listed neither the EQ14 nor the G3 Plus, so this page carries no paired retailer links. The makers&amp;rsquo; own product pages for the &lt;a href="https://www.bee-link.com/products/beelink-eq14-n150" rel="noopener">EQ14&lt;/a> and the &lt;a href="https://www.gmktec.com/products/nucbox-g3-plus-enhanced-performance-mini-pc-with-intel-n150-processor" rel="noopener">G3 Plus&lt;/a> show the configurations; whichever store you use, confirm the network version, RAM and SSD in the listing before you pay.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://www.intel.com/content/www/us/en/products/sku/241636/intel-processor-n150-6m-cache-up-to-3-60-ghz/specifications.html" rel="noopener">Intel N150 specifications&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://www.bee-link.com/products/beelink-eq14-n150" rel="noopener">Beelink EQ14 manufacturer specifications and variants&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://www.gmktec.com/products/nucbox-g3-plus-enhanced-performance-mini-pc-with-intel-n150-processor" rel="noopener">GMKtec G3 Plus manufacturer specification table&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://www.notebookcheck.net/Beelink-EQ14-mini-PC-review-Ready-to-go-HTPC-for-under-200.939127.0.html" rel="noopener">Notebookcheck&amp;rsquo;s January 2025 EQ14 review and power tests&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://github.com/geerlingguy/sbc-reviews/issues/64" rel="noopener">Jeff Geerling&amp;rsquo;s G3 Plus test record&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://www.eia.gov/electricity/monthly/epm_table_grapher.php?t=epmt_5_6_a" rel="noopener">EIA Electric Power Monthly, Table 5.6.A: average residential price, August 2026&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://docs.frigate.video/frigate/hardware/" rel="noopener">Frigate recommended hardware (EQ14 note)&lt;/a>.&lt;/li>
&lt;/ul></description></item><item><title>Docker Compose Environment Variables: .env vs env_file</title><link>https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/</link><pubDate>Sat, 15 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/</guid><atom:updated>2026-11-18T07:00:00Z</atom:updated><description>&lt;p>Drop a &lt;code>.env&lt;/code> file next to &lt;code>compose.yaml&lt;/code>, fill it with application settings, run &lt;code>docker compose up -d&lt;/code>, and exec into the container to inspect &lt;code>env&lt;/code>.&lt;/p>
&lt;p>Nothing from &lt;code>.env&lt;/code> is inside the container.&lt;/p>
&lt;p>If that is why you are here, this is the fix. Either pass each value through by name:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">app&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">TZ=${TZ} &lt;/span> &lt;span style="color:#75715e"># .env fills ${TZ}; environment: puts it in the container&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>or hand the whole file to the container, so every &lt;code>KEY=VALUE&lt;/code> line in it becomes a container variable:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">app&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./.env&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then run &lt;code>docker compose up -d&lt;/code> again: Compose recreates a container whose configuration changed. &lt;code>docker compose restart&lt;/code> does not pick up changed environment variables. The rest of this page explains why, and which value wins when the same name is set twice. It is written against Docker Compose 5.8.0, released November 17, 2026.&lt;/p>
&lt;p>That single surprise wastes more homelab debugging hours than almost anything else in Docker. It happens because two Compose features share nearly identical names while operating at completely separate stages of container startup:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Phase 1 — YAML Interpolation (&lt;code>.env&lt;/code> and &lt;code>--env-file&lt;/code>):&lt;/strong> Substitutes &lt;code>${VAR}&lt;/code> text placeholders &lt;strong>inside &lt;code>compose.yaml&lt;/code> itself&lt;/strong> before Docker creates anything. By itself, &lt;code>.env&lt;/code> injects zero variables into any container.&lt;/li>
&lt;li>&lt;strong>Phase 2 — Container Runtime Injection (&lt;code>env_file:&lt;/code> and &lt;code>environment:&lt;/code>):&lt;/strong> Passes key-value variables &lt;strong>into the running container process&lt;/strong>, and is never consulted to fill &lt;code>${VAR}&lt;/code> placeholders in &lt;code>compose.yaml&lt;/code>.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/envvars-precedence/" rel="noopener">Docker&amp;rsquo;s official precedence documentation&lt;/a> states that distinction outright: the Host OS environment and &lt;code>.env&lt;/code> file do not put a variable inside a container on their own unless &lt;code>compose.yaml&lt;/code> explicitly references or passes them through.&lt;/p>
&lt;h2 id="yaml-interpolation-env-vs-runtime-injection-env_file">YAML interpolation (&lt;code>.env&lt;/code>) vs runtime injection (&lt;code>env_file:&lt;/code>)&lt;/h2>
&lt;p>Before looking at precedence conflicts, separate the two mechanisms side by side. Mixing them up causes two silent bugs. Names look alike; directions stay opposite.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Property&lt;/th>
&lt;th scope="col">Project &lt;code>.env&lt;/code> (or CLI &lt;code>--env-file&lt;/code>)&lt;/th>
&lt;th scope="col">Service &lt;code>env_file:&lt;/code> attribute&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Property">&lt;strong>When Compose reads it&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;strong>Phase 1:&lt;/strong> Parsing &lt;code>compose.yaml&lt;/code>&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>Phase 2:&lt;/strong> Creating the container runtime environment&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Fills &lt;code>${VAR}&lt;/code> in &lt;code>compose.yaml&lt;/code>?&lt;/strong> (&lt;code>image:&lt;/code>, &lt;code>ports:&lt;/code>, &lt;code>volumes:&lt;/code>)&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>No — completely ignored during YAML interpolation&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Injects variables into the container?&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;strong>No&lt;/strong> (unless wired into &lt;code>environment:&lt;/code>)&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>Yes — every &lt;code>KEY=VAL&lt;/code> line enters the container&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Relative path base directory&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;code>--env-file&lt;/code> resolves from &lt;strong>your current shell working directory&lt;/strong>; default &lt;code>.env&lt;/code> lives in the project directory&lt;/td>
&lt;td data-label="Service env_file: attribute">Resolves from &lt;strong>&lt;code>compose.yaml&lt;/code>&amp;rsquo;s parent folder&lt;/strong>, regardless of your shell &lt;code>pwd&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>If the file is missing&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">Default &lt;code>.env&lt;/code>: &lt;strong>silent no-op&lt;/strong>; explicit &lt;code>--env-file&lt;/code>: &lt;strong>hard error&lt;/strong>&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>Hard error&lt;/strong> by default (unless &lt;code>required: false&lt;/code> on Compose 2.24+)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Visible in &lt;code>docker compose config&lt;/code>?&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">Shows interpolated values inside the rendered YAML&lt;/td>
&lt;td data-label="Service env_file: attribute">Expands and merges &lt;code>env_file:&lt;/code> keys into the service&amp;rsquo;s rendered &lt;code>environment:&lt;/code> block&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Here are both failure directions in ten lines of YAML:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># .env (Phase 1: YAML interpolation source ONLY)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">POSTGRES_TAG=17-alpine&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># compose.yaml&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">postgres:${POSTGRES_TAG} &lt;/span> &lt;span style="color:#75715e"># Works: .env turns this into postgres:17-alpine&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">./app.env # Works&lt;/span>: &lt;span style="color:#ae81ff">every line in app.env enters the container&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">TZ=America/Chicago # Works&lt;/span>: &lt;span style="color:#ae81ff">TZ enters the container&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>In that file, &lt;code>POSTGRES_TAG&lt;/code> never enters the &lt;code>db&lt;/code> container&amp;rsquo;s &lt;code>env&lt;/code> output. Now look at the mirror-image mistake:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">web&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;nginx:${NGINX_TAG}&amp;#34;&lt;/span> &lt;span style="color:#75715e"># BROKEN: env_file is NOT read for ${NGINX_TAG}!&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./web.env &lt;/span> &lt;span style="color:#75715e"># Even if NGINX_TAG=1.27 is inside web.env, image becomes &amp;#34;nginx:&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Listing &lt;code>./web.env&lt;/code> (or even &lt;code>./.env&lt;/code>) under &lt;code>env_file:&lt;/code> dumps every key into the container process at runtime, while &lt;code>${NGINX_TAG}&lt;/code> on the &lt;code>image:&lt;/code> line still evaluates before &lt;code>env_file:&lt;/code> is ever opened.&lt;/p>
&lt;h2 id="complete-6-level-docker-compose-variable-precedence-table">Complete 6-level Docker Compose variable precedence table&lt;/h2>
&lt;p>When the same variable name appears in more than one place, &lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/envvars-precedence/" rel="noopener">Docker&amp;rsquo;s environment variable precedence specification&lt;/a> resolves what actually lands &lt;strong>inside the container&lt;/strong> from &lt;strong>Level 1 (highest)&lt;/strong> down to &lt;strong>Level 6 (lowest)&lt;/strong>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Priority&lt;/th>
&lt;th scope="col">Mechanism&lt;/th>
&lt;th scope="col">Example&lt;/th>
&lt;th scope="col">Critical edge case to watch&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>1 (Highest)&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>&lt;code>docker compose run -e&lt;/code> CLI flag&lt;/strong>&lt;/td>
&lt;td data-label="Example">&lt;code>docker compose run --rm -e APP_ENV=cli_run web env&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">Applies only to &lt;code>docker compose run&lt;/code> one-off containers (&lt;code>docker compose up&lt;/code> has no &lt;code>-e&lt;/code> flag). Bare &lt;code>-e VAR&lt;/code> pulls from host shell.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>2&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Interpolated value&lt;/strong> in &lt;code>environment:&lt;/code> or &lt;code>env_file:&lt;/code> (from your shell, &lt;code>.env&lt;/code> or &lt;code>--env-file&lt;/code>)&lt;/td>
&lt;td data-label="Example">&lt;code>APP_ENV=host_shell docker compose up -d&lt;/code> with &lt;code>environment: [APP_ENV]&lt;/code> or &lt;code>APP_ENV=${APP_ENV}&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">Host shell beats &lt;code>.env&lt;/code> during &lt;code>${VAR}&lt;/code> interpolation AND beats &lt;code>env_file:&lt;/code> when bare &lt;code>environment: - APP_ENV&lt;/code> is listed. Unexported shell vars are invisible!&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>3&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Literal value under &lt;code>environment:&lt;/code>&lt;/strong> in &lt;code>compose.yaml&lt;/code>&lt;/td>
&lt;td data-label="Example">&lt;code>environment: [APP_ENV=compose_attr]&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">&lt;strong>Beats &lt;code>env_file:&lt;/code> even when empty!&lt;/strong> A stray &lt;code>APP_ENV=&lt;/code> or &lt;code>APP_ENV: &amp;quot;${UNSET}&amp;quot;&lt;/code> under &lt;code>environment:&lt;/code> wipes out a valid &lt;code>APP_ENV&lt;/code> in &lt;code>env_file:&lt;/code>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>4&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Service &lt;code>env_file:&lt;/code> attribute&lt;/strong> in &lt;code>compose.yaml&lt;/code>&lt;/td>
&lt;td data-label="Example">&lt;code>env_file: [./base.env, ./local.env]&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">Evaluated top-to-bottom when multiple files are listed; &lt;strong>the last file in the &lt;code>env_file:&lt;/code> list wins&lt;/strong> (&lt;code>local.env&lt;/code> beats &lt;code>base.env&lt;/code>).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>5&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Container image &lt;code>Dockerfile&lt;/code> &lt;code>ENV&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Example">&lt;code>ENV APP_ENV=image_default&lt;/code> baked into image layers&lt;/td>
&lt;td data-label="Critical edge case to watch">Pure fallback. Evaluates &lt;strong>only&lt;/strong> if Levels 1–4 have zero entry for &lt;code>APP_ENV&lt;/code>. Any Compose entry replaces it completely.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>6 (Lowest)&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Unset / undefined&lt;/strong>&lt;/td>
&lt;td data-label="Example">Variable omitted everywhere&lt;/td>
&lt;td data-label="Critical edge case to watch">Absent from container &lt;code>env&lt;/code>. If referenced via unguarded &lt;code>${VAR}&lt;/code> in YAML, silently becomes empty string &lt;code>&amp;quot;&amp;quot;&lt;/code>!&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Keep &lt;strong>Phase 1 YAML interpolation precedence&lt;/strong> distinct in your head too (&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/variable-interpolation/" rel="noopener">variable interpolation docs&lt;/a>). When Compose fills &lt;code>${VAR}&lt;/code> inside &lt;code>compose.yaml&lt;/code>, it checks three sources in order:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Host OS shell environment&lt;/strong> (&lt;code>export VAR=...&lt;/code> or inline &lt;code>VAR=... docker compose ...&lt;/code>)&lt;/li>
&lt;li>&lt;strong>CLI &lt;code>--env-file&lt;/code> file(s)&lt;/strong> (or &lt;code>COMPOSE_ENV_FILES&lt;/code>; with several &lt;code>--env-file&lt;/code> options, Compose reads them in order and later files override earlier ones)&lt;/li>
&lt;li>&lt;strong>Default &lt;code>.env&lt;/code> file&lt;/strong> in the project directory (unless disabled via &lt;code>COMPOSE_DISABLE_ENV_FILE=1&lt;/code>)&lt;/li>
&lt;/ol>
&lt;h2 id="verify-levels-1-to-4-yourself-with-docker-compose-config">Verify levels 1 to 4 yourself with &lt;code>docker compose config&lt;/code>&lt;/h2>
&lt;p>Never guess what Compose resolved. Never test with live database passwords either. Create a disposable lab directory with distinct, non-secret marker strings (&lt;code>FROM_DOTENV&lt;/code>, &lt;code>FROM_ENV_FILE&lt;/code>, &lt;code>FROM_COMPOSE_ENV&lt;/code>, &lt;code>FROM_HOST_SHELL&lt;/code>, &lt;code>FROM_RUN_CLI&lt;/code>) and inspect the merged model using &lt;a href="https://docs.docker.com/reference/cli/docker/compose/config/" rel="noopener">&lt;code>docker compose config&lt;/code>&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir -p /tmp/compose-env-lab &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> cd /tmp/compose-env-lab
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; .env &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">IMAGE_TAG=3.20
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_INTERPOLATED=FROM_DOTENV
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; runtime.env &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_FILE_ONLY=FROM_ENV_FILE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_CONFLICT=FROM_ENV_FILE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_EMPTY_TRAP=GOOD_VALUE_IN_ENV_FILE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; compose.yaml &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">services:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> probe:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> image: alpine:${IMAGE_TAG}
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> env_file:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> - ./runtime.env
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> environment:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> TEST_CONFLICT: FROM_COMPOSE_ENV
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> TEST_SHELL_BRIDGE: ${TEST_INTERPOLATED}
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> TEST_EMPTY_TRAP: &amp;#34;&amp;#34;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Run &lt;code>docker compose config&lt;/code> before starting any container. It only parses the file, resolves the variables and prints the result in canonical form; it starts nothing:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker compose config
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Look at the rendered &lt;code>environment:&lt;/code> block Compose prints for &lt;code>probe&lt;/code>:&lt;/p>
&lt;ul>
&lt;li>&lt;code>image&lt;/code> resolved to &lt;code>alpine:3.20&lt;/code>, while &lt;code>IMAGE_TAG&lt;/code> itself is &lt;strong>absent&lt;/strong> from &lt;code>environment:&lt;/code> (proving &lt;code>.env&lt;/code> alone stays out of the container).&lt;/li>
&lt;li>&lt;code>TEST_FILE_ONLY&lt;/code> equals &lt;code>FROM_ENV_FILE&lt;/code> (Level 4).&lt;/li>
&lt;li>&lt;code>TEST_CONFLICT&lt;/code> equals &lt;code>FROM_COMPOSE_ENV&lt;/code> (Level 3 beat Level 4).&lt;/li>
&lt;li>&lt;code>TEST_SHELL_BRIDGE&lt;/code> equals &lt;code>FROM_DOTENV&lt;/code> (Level 2: an &lt;code>environment:&lt;/code> value interpolated from &lt;code>.env&lt;/code>).&lt;/li>
&lt;li>&lt;code>TEST_EMPTY_TRAP&lt;/code> equals &lt;code>&amp;quot;&amp;quot;&lt;/code> (an empty string in Level 3 wiped out &lt;code>GOOD_VALUE_IN_ENV_FILE&lt;/code> from Level 4 with zero warnings!).&lt;/li>
&lt;/ul>
&lt;p>Now watch Levels 2 and 1 override that same stack without editing a file. These two commands do start short-lived containers, so they need the Docker daemon and pull &lt;code>alpine:3.20&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Level 2: Host shell overrides .env interpolation -&amp;gt; prints TEST_SHELL_BRIDGE=FROM_HOST_SHELL&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>TEST_INTERPOLATED&lt;span style="color:#f92672">=&lt;/span>FROM_HOST_SHELL docker compose run --rm probe sh -c &lt;span style="color:#e6db74">&amp;#39;env | grep ^TEST_ | sort&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Level 1: run -e beats everything -&amp;gt; prints TEST_CONFLICT=FROM_RUN_CLI&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose run --rm -e TEST_CONFLICT&lt;span style="color:#f92672">=&lt;/span>FROM_RUN_CLI probe sh -c &lt;span style="color:#e6db74">&amp;#39;env | grep ^TEST_ | sort&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Clean up the scratch folder when finished&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>rm -rf /tmp/compose-env-lab
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The lab stops at Level 4. Level 5 (an &lt;code>ENV&lt;/code> baked into the image) and Level 6 (unset) only show up when nothing above them sets the variable, so &lt;code>docker compose config&lt;/code> has nothing to print for them; check them inside the container with &lt;code>docker compose run --rm probe env&lt;/code>.&lt;/p>
&lt;p>Whenever a stack behaves strangely on your server (whether managed from the CLI or via &lt;a href="https://techfuelhq.com/tutorials/dockge-docker-compose-manager-2026/">Dockge&lt;/a>), &lt;code>docker compose config&lt;/code> shows the exact post-interpolation truth in two seconds, and &lt;code>docker compose config --environment&lt;/code> prints the variables Compose used for interpolation. Keep &lt;code>docker compose config&lt;/code> output out of public GitHub issues or screenshots if real credentials sit in your env files, because Compose prints every resolved value inline!&lt;/p>
&lt;h2 id="env_file-multi-file-layering-required-false-and-format-raw">&lt;code>env_file:&lt;/code> multi-file layering, &lt;code>required: false&lt;/code>, and &lt;code>format: raw&lt;/code>&lt;/h2>
&lt;p>Compose 2.24.0 and later (&lt;a href="https://docs.docker.com/reference/compose-file/services/#env_file" rel="noopener">services &lt;code>env_file&lt;/code> reference&lt;/a>) support a structured mapping syntax under &lt;code>env_file:&lt;/code> that solves two classic parser headaches:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">webapp&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./defaults.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">path&lt;/span>: &lt;span style="color:#ae81ff">./local-overrides.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">required: false # Compose 2.24.0+&lt;/span>: &lt;span style="color:#ae81ff">silent skip if missing&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">path&lt;/span>: &lt;span style="color:#ae81ff">./literal-hashes.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">format: raw # Compose 2.30.0+&lt;/span>: &lt;span style="color:#66d9ef">no&lt;/span> &lt;span style="color:#ae81ff">quote stripping or $ expansion!&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pay close attention to &lt;code>format: raw&lt;/code> (added in Compose &lt;code>2.30.0&lt;/code>). In standard &lt;code>.env&lt;/code> and &lt;code>env_file&lt;/code> syntax, double-quoted and unquoted values are interpolated, and Compose reads any &lt;code>$&lt;/code> followed by a letter or &lt;code>_&lt;/code> as a variable. A bcrypt password hash like &lt;code>$2a$12$R9h/cIPz0gi...&lt;/code> therefore loses its &lt;code>$R9h&lt;/code> segment to an empty variable unless you wrap it in single quotes (&lt;code>'$2a$12...'&lt;/code>) or load the file with &lt;code>format: raw&lt;/code>. Inside &lt;code>compose.yaml&lt;/code> itself, write a literal dollar sign as &lt;code>$$&lt;/code>. Also watch inline comments: &lt;code>PORT=8080 # web&lt;/code> sets &lt;code>8080&lt;/code>, whereas &lt;code>PORT=8080# web&lt;/code> (missing the space before &lt;code>#&lt;/code>) sets the literal string &lt;code>8080# web&lt;/code>.&lt;/p>
&lt;h2 id="guarding-defaults-var-default-vs-var-default-vs-varerror">Guarding defaults: &lt;code>${VAR:-default}&lt;/code> vs &lt;code>${VAR-default}&lt;/code> vs &lt;code>${VAR:?error}&lt;/code>&lt;/h2>
&lt;p>Never leave critical image tags or database usernames as bare &lt;code>${VAR}&lt;/code> placeholders. An unset &lt;code>${POSTGRES_VERSION}&lt;/code> turns &lt;code>postgres:${POSTGRES_VERSION}&lt;/code> into &lt;code>postgres:&lt;/code>, producing a cryptic registry parse error instead of telling you which variable was missing.&lt;/p>
&lt;p>The colon inside parameter expansion controls whether &lt;strong>empty strings (&lt;code>VAR=&amp;quot;&amp;quot;&lt;/code>)&lt;/strong> trigger the fallback alongside &lt;strong>unset&lt;/strong> variables:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Syntax&lt;/th>
&lt;th scope="col">Variable is &lt;strong>unset&lt;/strong>&lt;/th>
&lt;th scope="col">Variable is &lt;strong>empty (&lt;code>VAR=&lt;/code>)&lt;/strong>&lt;/th>
&lt;th scope="col">Variable is &lt;strong>&lt;code>VAR=custom&lt;/code>&lt;/strong>&lt;/th>
&lt;th scope="col">Best use in &lt;code>compose.yaml&lt;/code>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR:-default}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;code>&amp;quot;default&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;code>&amp;quot;default&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Safe defaults for image tags, ports, and optional settings&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR-default}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;code>&amp;quot;default&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;code>&amp;quot;&amp;quot;&lt;/code> (stays empty!)&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Rare cases where an explicit empty string is intentional&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR:?error msg}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;strong>Fails fast with &lt;code>error msg&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;strong>Fails fast with &lt;code>error msg&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Required paths, hostnames, and non-default usernames&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR?error msg}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;strong>Fails fast with &lt;code>error msg&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;code>&amp;quot;&amp;quot;&lt;/code> (allowed!)&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Required key that is allowed to be blank&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;postgres:${POSTGRES_VERSION:-17}&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_DB&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;${DB_NAME:-app}&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_USER&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;${DB_USER:?Set DB_USER in .env before starting}&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Also note the warning difference on pass-through lines: writing bare &lt;code>- DEBUG&lt;/code> under &lt;code>environment:&lt;/code> emits &lt;strong>zero warning&lt;/strong> when &lt;code>DEBUG&lt;/code> is unset in your shell, whereas writing &lt;code>- DEBUG=${DEBUG}&lt;/code> makes Compose print a warning that &lt;code>DEBUG&lt;/code> is not set and substitute an empty string. Use the explicit &lt;code>${VAR:?...}&lt;/code> or &lt;code>${VAR:-...}&lt;/code> forms so missing &lt;code>.env&lt;/code> files on a new server fail loud at &lt;code>docker compose up&lt;/code> time rather than half-starting a broken container.&lt;/p>
&lt;h2 id="keep-real-secrets-out-of-environment-variables">Keep real secrets out of environment variables&lt;/h2>
&lt;p>Everything injected via &lt;code>environment:&lt;/code> or &lt;code>env_file:&lt;/code> is stored in container metadata and returned in plaintext by &lt;code>docker inspect&lt;/code>. On Linux, &lt;a href="https://techfuelhq.com/tutorials/add-user-to-docker-group-2026/">anyone in the &lt;code>docker&lt;/code> group&lt;/a> can inspect every running container—and crashed apps routinely dump &lt;code>process.env&lt;/code> or &lt;code>os.environ&lt;/code> into stack traces. Build-time &lt;code>ARG&lt;/code> tokens are even worse, remaining baked into &lt;code>docker history&lt;/code> image metadata unless handled via BuildKit secret mounts.&lt;/p>
&lt;p>Where official images support the &lt;code>_FILE&lt;/code> convention (&lt;code>postgres&lt;/code>, &lt;code>mariadb&lt;/code>, &lt;code>mysql&lt;/code>, &lt;code>wordpress&lt;/code>, &lt;code>authelia&lt;/code>, &lt;code>vaultwarden&lt;/code> admin tokens), mount file-based Compose secrets into &lt;code>/run/secrets/&amp;lt;name&amp;gt;&lt;/code> as recommended in &lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/best-practices/" rel="noopener">Docker&amp;rsquo;s environment-variable best practices&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">postgres:17&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_USER&lt;/span>: &lt;span style="color:#ae81ff">appuser&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_PASSWORD_FILE&lt;/span>: &lt;span style="color:#ae81ff">/run/secrets/db_password&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">secrets&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">db_password&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">secrets&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db_password&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">file&lt;/span>: &lt;span style="color:#ae81ff">./secrets/db_password.txt &lt;/span> &lt;span style="color:#75715e"># chmod 600 on host, gitignored&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="my-three-rule-house-standard">My three-rule house standard&lt;/h2>
&lt;p>After getting burned once at 1 a.m. by an empty &lt;code>environment:&lt;/code> key overriding a valid &lt;code>env_file:&lt;/code> entry, I stick to three non-negotiable habits on every homelab stack:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>.env&lt;/code> shapes &lt;code>compose.yaml&lt;/code> only:&lt;/strong> Pinned image versions (&lt;code>IMMICH_VERSION&lt;/code>), published host ports, and host bind-mount paths (&lt;code>UPLOAD_LOCATION&lt;/code>) live in &lt;code>.env&lt;/code>, guarded by &lt;code>:-&lt;/code> defaults or &lt;code>:?&lt;/code> checks.&lt;/li>
&lt;li>&lt;strong>&lt;code>env_file:&lt;/code> feeds application config:&lt;/strong> App-internal flags go into a dedicated &lt;code>./app.env&lt;/code> (with &lt;code>chmod 600&lt;/code>), while actual credentials use &lt;code>/run/secrets/&lt;/code> &lt;code>_FILE&lt;/code> mounts wherever supported.&lt;/li>
&lt;li>&lt;strong>Never define the same variable name in both &lt;code>environment:&lt;/code> and &lt;code>env_file:&lt;/code>:&lt;/strong> Precedence tables are for diagnosing bugs—not for intentionally defining conflicting values across two files and hoping future-you remembers Level 3 beats Level 4. While tidying up old stacks, check unused volumes and dangling images with our &lt;a href="https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/">Docker disk-space cleanup guide&lt;/a>.&lt;/li>
&lt;/ol>
&lt;p>To practise on a real stack, the &lt;a href="https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/">Immich migration guide&lt;/a> builds its &lt;code>.env&lt;/code> from the release&amp;rsquo;s &lt;code>example.env&lt;/code>, and the &lt;a href="https://techfuelhq.com/tutorials/paperless-ngx-docker-setup-2026/">Paperless-ngx&lt;/a>, &lt;a href="https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/">Vaultwarden&lt;/a> and &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">Jellyfin&lt;/a> guides each start from a compose file you can check with &lt;code>docker compose config&lt;/code>.&lt;/p></description></item><item><title>PTM7950 vs Thermal Paste: Which Lasts and When</title><link>https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/</guid><atom:updated>2026-11-18T06:55:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · PTM7950 vs thermal paste&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>PTM7950 is the right answer for a bare die that keeps pumping paste out&lt;/strong>, and for anything you do not want to open again. It holds its bond line through thermal cycling and Honeywell's sheet claims no pump-out, bleed-out or dry-out.&lt;/li>
&lt;li>&lt;strong>Paste is the right answer for a flat cold plate you might remove&lt;/strong>, for a quick remount, and for anything where you want to adjust mounting pressure by feel. Kryonaut is silicone-based, does not cure, and is easy to clean off.&lt;/li>
&lt;li>&lt;strong>Pressure decides the result.&lt;/strong> Honeywell wants 30 to 40 psi for PTM7950, with 10 psi as the minimum for a significant reduction in bond-line thickness. If you can't be sure your mount gets there, paste is the safer choice.&lt;/li>
&lt;li>&lt;strong>The conductivity labels are not comparable.&lt;/strong> PTM7950 is rated 8.5 W/m·K; Thermal Grizzly has not published a W/m·K figure since 2020. Buy on measured thermal resistance, not on the number on the tube.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Thermal paste is a suspension of thermally conductive particles in a carrier fluid. PTM7950 is a phase-change material: a thin, firm sheet that is solid at room temperature and turns into a viscous, conformal layer once it passes about 45 °C. They are used in the same place, and they fail in different ways, which is the entire decision.&lt;/p>
&lt;p>I have re-pasted enough coolers to have an opinion, but the numbers below are Honeywell&amp;rsquo;s, Thermal Grizzly&amp;rsquo;s and Igor&amp;rsquo;s Lab&amp;rsquo;s, not my own bench results. What follows is what each material is specified to do, where the published figures are not comparable, and the two conditions that decide which one you should buy.&lt;/p>
&lt;h2 id="side-by-side">Side by side&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Honeywell PTM7950 (pad)&lt;/th>
&lt;th scope="col">Thermal Grizzly Kryonaut (paste)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">What it is&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">Phase-change pad; Solstice lists a 45 °C phase change&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">Silicone-based thermal grease that works without curing&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Rated conductivity&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">8.5 W/m·K (ASTM D5470, 125 W, 40 psi)&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">None published since the end of 2020&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Published resistance&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">0.04 °C·cm²/W thermal impedance&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">0.0032 K/W thermal resistance&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Measured by Igor&amp;rsquo;s Lab&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">6.374 W/(m·K) effective, ASTM D5470-17&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">Not tested in that article&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Pressure&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">30 to 40 psi needed; 10 psi minimum to thin the bond line&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">No figure published&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Pump-out&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">Honeywell claims no pump-out, bleed-out or dry-out&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">Thermal Grizzly says temperature changes can gradually displace it&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Thickness&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">Pads at 0.2, 0.25, 0.3, 0.4 and 0.5 mm&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">Spread to the layer you apply&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Handling&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">The second protective film is hard to peel without damage; Igor calls pre-assembled versions the safest route&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">Remove with a dry cloth, then isopropyl alcohol, per Thermal Grizzly&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Newegg, November 17, 2026&lt;/td>
&lt;td data-label="Honeywell PTM7950 (pad)">No listing that names Honeywell&lt;/td>
&lt;td data-label="Thermal Grizzly Kryonaut (paste)">5.55 g tube (TG-K-015-R) at $23.99&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The resistance figures use different units, °C·cm²/W against K/W, so they can&amp;rsquo;t be compared directly.&lt;/p>
&lt;h2 id="what-each-material-actually-is">What each material actually is&lt;/h2>
&lt;p>PTM7950 is silicone-free and supplied as a sheet in 0.2, 0.25, 0.3, 0.4 and 0.5 mm thicknesses (&lt;a href="https://prod-edam.solstice.com/content/dam/honeywell-edam/pmt/oneam/en-us/electronic-materials/thermal-interface-materials/documents/9020001-esm-sls-choose-your-phase-change-mtl-ltr-en.pdf" rel="noopener">Solstice selection chart&lt;/a>; &lt;a href="https://prod-edam.solstice.com/content/dam/honeywell-edam/pmt/oneam/en-us/electronic-materials/thermal-interface-materials/documents/100600-esm-tds-ptm7950-pcm-ltr-en.pdf" rel="noopener">Honeywell TDS&lt;/a>). Its selling point is a property list rather than a single number: no pump-out, no bleed-out, no dry-out. That is a direct claim about the failure modes that kill paste on hot, small dies.&lt;/p>
&lt;p>Kryonaut is a silicone-based paste with no curing step. Thermal Grizzly publishes its viscosity at 130 to 170 Pa·s, density at 3.7 g/cm³, operating range from −250 °C to +350 °C, and thermal resistance at 0.0032 K/W (&lt;a href="https://www.thermal-grizzly.com/media/56/c8/6a/1700224682/TG-Datasheet-Kryonaut-EN.pdf" rel="noopener">Kryonaut datasheet&lt;/a>). It is a conventional product, well understood, and it behaves the way paste is supposed to behave.&lt;/p>
&lt;p>The mechanical difference is what matters. Paste is applied as a blob or a line and spreads under mounting pressure until it fills the microscopic gaps between two surfaces. The pad is already a sheet of a known thickness, and it thins as it heats and is compressed. A pad is a manufactured bond line; a paste is a bond line you create on the day.&lt;/p>
&lt;h2 id="the-conductivity-numbers-are-not-comparable">The conductivity numbers are not comparable&lt;/h2>
&lt;p>This is where most comparisons go wrong, so it is worth being precise.&lt;/p>
&lt;p>Honeywell rates PTM7950 at 8.5 W/m·K with a thermal impedance of 0.04 °C·cm²/W, both by ASTM D5470 at 125 W and 40 psi with no shim. Thermal Grizzly does not publish a W/m·K figure at all. Its product page states that the company &amp;ldquo;has not published general W/(m·K) ratings since the end of 2020&amp;rdquo; (&lt;a href="https://www.thermal-grizzly.com/en/kryonaut/s-tg-k-100-r" rel="noopener">Thermal Grizzly&lt;/a>). Its reason is that a single conductivity value doesn&amp;rsquo;t allow a reliable comparison of cooling performance, because the test method, temperature, mounting pressure and contact surfaces all affect the result.&lt;/p>
&lt;p>Igor&amp;rsquo;s Lab measured PTM7950 with ASTM D5470-17 on their TIMA5 tester and reported 6.374 W/(m·K), with thermal resistance falling from 0.41913 cm²K/W to 0.03427 cm²K/W as the bond line was compressed (&lt;a href="https://www.igorslab.de/en/overhyped-solstice-ptm7950-in-lab-test-and-as-game-changer-for-graphics-cards/" rel="noopener">Igor&amp;rsquo;s Lab&lt;/a>). They also state that ordinary pastes &amp;ldquo;cannot achieve much more than 4 to 5 W/(m-K) under the usual conditions on a GPU or CPU.&amp;rdquo;&lt;/p>
&lt;p>Two things follow. First, Igor&amp;rsquo;s 6.374 is an effective conductivity measured through a real layer, and his table lists the bulk figure as not available, so it isn&amp;rsquo;t the same kind of number as Honeywell&amp;rsquo;s rated 8.5. Second, the comparison that matters is roughly 6.4 against 4 to 5. That is a gap in effective conductivity under pressure, not in the number printed on the box.&lt;/p>
&lt;h2 id="pressure-is-the-deciding-variable">Pressure is the deciding variable&lt;/h2>
&lt;p>Honeywell is explicit that pressure drives performance. Its datasheet states that 30 to 40 psi is needed, and that &amp;ldquo;a minimum pressure of 10 psi is needed to observe a significant reduction in bondline thickness.&amp;rdquo; Below that, you are not getting the material the datasheet describes.&lt;/p>
&lt;p>That is a harder requirement than it sounds. Most CPU coolers use spring-loaded screws that bottom out against a standoff, and the actual pressure depends on the spring rate and how far it compresses. Most mounts are designed to work with paste, which needs far less pressure to spread. If your cooler is a stock boxed unit with plastic push-pins, or a laptop heatsink held by four small screws into a thin chassis, you may never reach the pressure Honeywell specifies. If you are still choosing the cooler itself, the &lt;a href="https://techfuelhq.com/articles/air-cooler-vs-aio-2026/">air cooler vs AIO comparison&lt;/a> covers that decision.&lt;/p>
&lt;p>There is no published number from Thermal Grizzly for Kryonaut&amp;rsquo;s required pressure, which is the point. Paste is forgiving of a mediocre mount. PTM7950 is not. If you cannot control or verify the mounting pressure, paste is the lower-risk choice, and the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> covers how to tell whether the mount is the problem in the first place.&lt;/p>
&lt;h2 id="pump-out-drying-and-the-long-haul">Pump-out, drying, and the long haul&lt;/h2>
&lt;p>Pump-out is the mechanism that makes a good paste go bad. Thermal Grizzly describes it on its &lt;a href="https://www.thermal-grizzly.com/en/kryonaut/s-tg-k-100-r" rel="noopener">Kryonaut page&lt;/a>: temperature changes can gradually displace paste from the contact area, and a thin, even layer with a correct cooler installation reduces the risk but can&amp;rsquo;t eliminate it in every configuration. Its guidance is to replace the paste if temperatures show a confirmed deterioration or if the cooler has been removed.&lt;/p>
&lt;p>A phase-change material is sold on surviving that cycle. Honeywell&amp;rsquo;s sheet lists long service life under thermal cycling and superior wetting at operating temperature among its claims, and its reliability data is aimed squarely at this: a 150 °C bake for 1,000 hours, a Double 85 test for 1,000 hours, and 1,000 temperature cycles between −55 °C and +125 °C, with thermal impedance staying at or below 0.045 °C·cm²/W throughout (&lt;a href="https://prod-edam.solstice.com/content/dam/honeywell-edam/pmt/oneam/en-us/electronic-materials/thermal-interface-materials/documents/100600-esm-tds-ptm7950-pcm-ltr-en.pdf" rel="noopener">TDS&lt;/a>).&lt;/p>
&lt;p>Igor&amp;rsquo;s Lab&amp;rsquo;s real-world result is consistent with that. On a Manli RTX 4080 Gallardo in its July 2024 test, temperatures settled at 66 to 67 °C after burn-in, the same level as the card&amp;rsquo;s original paste in its factory state when new. After six months, though, that factory paste had let the hotspot climb to 103 °C against 79 °C at delivery (&lt;a href="https://www.igorslab.de/en/overhyped-solstice-ptm7950-in-lab-test-and-as-game-changer-for-graphics-cards/5/" rel="noopener">page 5&lt;/a>). That is a single card and a single test, not a universal claim, and I would not quote it as a temperature win over paste on your specific card. It is evidence that the material performs in a real mount.&lt;/p>
&lt;p>The trade-off is handling. Igor says the hard part is peeling the second protective film off without destroying the pad, notes that chilling it to help makes it firm but brittle, and calls the pre-assembled versions with adhesive strips the safest route (&lt;a href="https://www.igorslab.de/en/overhyped-solstice-ptm7950-in-lab-test-and-as-game-changer-for-graphics-cards/" rel="noopener">page 1&lt;/a>). Paste does not have that problem. It has the opposite problem: it is easy to apply badly and easy to apply too much.&lt;/p>
&lt;h2 id="where-each-one-belongs">Where each one belongs&lt;/h2>
&lt;p>Buy PTM7950 for a bare die with a small contact area that runs hot and cycles constantly: a graphics card, a laptop, a handheld. Buy it for a machine you do not want to open again, and for any mount where you have already seen paste pump out once. Skip it where you can&amp;rsquo;t be sure the mount reaches the pressure in the section above. On a graphics card, the &lt;a href="https://techfuelhq.com/articles/gpu-overheating-2026/">GPU overheating guide&lt;/a> covers what to rule out before you open the cooler at all.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Honeywell&amp;#43;PTM7950&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ptm7950-vs-thermal-paste-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DHoneywell%2BPTM7950" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ptm7950-vs-thermal-paste-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Buy the pad from a listing that names the Honeywell part and the thickness, because the data sheet&amp;rsquo;s figures belong to that product. On November 17, 2026, none of the PTM7950 listings in Newegg&amp;rsquo;s catalogue named Honeywell, so read the seller&amp;rsquo;s details before you buy; that is why the links above are searches rather than a single listing.&lt;/p>
&lt;p>Buy paste for a desktop CPU under a tower cooler with a proper spring mount, for a cold plate you expect to remove within a year, and for any situation where you want to adjust the mount and try again. Kryonaut&amp;rsquo;s published properties are unremarkable in a good way: it works without curing and cleans up with isopropyl alcohol, and Thermal Grizzly says to replace it whenever you remove the cooler. Newegg listed the 5.55 g tube (TG-K-015-R) at $23.99 on November 17, 2026.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Thermal&amp;#43;Grizzly&amp;#43;Kryonaut&amp;#43;TG-K-015-R&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ptm7950-vs-thermal-paste-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fthermal-grizzly-tg-k-015-r-5-5g%2Fp%2F2SA-000B-00001%3Fitem%3D9SIA2W0DNS1844" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ptm7950-vs-thermal-paste-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="what-i-would-check-before-buying">What I would check before buying&lt;/h2>
&lt;p>Four checks, and the first two decide most of the answer.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Can you apply real pressure?&lt;/strong> Spring screws with standoffs, a proper backplate, and a cooler that is not held by push-pins. If the answer is no, paste is the safer choice regardless of the conductivity numbers.&lt;/li>
&lt;li>&lt;strong>Has this mount already pumped out once?&lt;/strong> If you have re-pasted the same card twice and the temperatures fell again both times, that is the signature case for a phase-change pad.&lt;/li>
&lt;li>&lt;strong>Is the die bare or under a heat spreader?&lt;/strong> A bare GPU die with a small contact patch is the strongest case for PTM7950, and it is the case Igor&amp;rsquo;s Lab tested. None of the sources here compares the two under a CPU heat spreader, so there paste is the easier choice to apply, remove and redo.&lt;/li>
&lt;li>&lt;strong>What does your sensor actually say?&lt;/strong> Measure before you change anything. The &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/">CPU temperature check&lt;/a> covers the tools, the &lt;a href="https://techfuelhq.com/articles/gpu-hotspot-temperature-2026/">GPU hotspot temperature guide&lt;/a> explains the core-to-hotspot gap people repaste for, and the &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">GPU hotspot delta census&lt;/a> collects readings of that split.&lt;/li>
&lt;/ol>
&lt;p>If the temperatures are already fine, neither product will help. Repasting a healthy cooler is how people end up with a worse result than they started with. The &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling fix guide&lt;/a> is the place to start when the machine is actually throttling, because airflow, fan curves and mount pressure all come before the material choice.&lt;/p></description></item><item><title>Best Wi-Fi 7 Routers (2026): Five Picks by Budget, Ports and Coverage</title><link>https://techfuelhq.com/networking/best-wifi-7-router-2026/</link><pubDate>Tue, 18 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/best-wifi-7-router-2026/</guid><atom:updated>2026-11-18T06:50:00Z</atom:updated><description>&lt;h2 id="the-picks-at-a-glance">The picks at a glance&lt;/h2>
&lt;p>Choose the band layout first, then count the ports. The giant aggregate speed on the box comes last, because no single client receives it.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Pick&lt;/th>
&lt;th scope="col">Best for&lt;/th>
&lt;th scope="col">Radio layout&lt;/th>
&lt;th scope="col">Useful wired I/O&lt;/th>
&lt;th scope="col" style="text-align: right">Newegg, Nov. 17, 2026&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Pick">&lt;strong>&lt;a href="#rt-be92u">ASUS RT-BE92U&lt;/a>&lt;/strong>&lt;/td>
&lt;td data-label="Best for">Most homes&lt;/td>
&lt;td data-label="Radio layout">Tri-band: 2.4 + 5 + 6GHz&lt;/td>
&lt;td data-label="Useful wired I/O">1× 10G WAN/LAN, 1× 2.5G WAN/LAN, 3× 2.5G LAN&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;strong>$285.99&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pick">&lt;strong>&lt;a href="#archer-be230">TP-Link Archer BE230&lt;/a>&lt;/strong>&lt;/td>
&lt;td data-label="Best for">Under $100&lt;/td>
&lt;td data-label="Radio layout">Dual-band: 2.4 + 5GHz; no 6GHz&lt;/td>
&lt;td data-label="Useful wired I/O">1× 2.5G WAN, 1× 2.5G LAN, 3× 1G LAN&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;strong>$99.99&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pick">&lt;strong>&lt;a href="#deco-be63">TP-Link Deco BE63, 2-pack&lt;/a>&lt;/strong>&lt;/td>
&lt;td data-label="Best for">Large or multi-floor homes&lt;/td>
&lt;td data-label="Radio layout">Tri-band: 2.4 + 5 + 6GHz&lt;/td>
&lt;td data-label="Useful wired I/O">4× 2.5G per unit&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;strong>$449.99&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pick">&lt;strong>&lt;a href="#rt-be88u">ASUS RT-BE88U&lt;/a>&lt;/strong>&lt;/td>
&lt;td data-label="Best for">Wired-first router and switch replacement&lt;/td>
&lt;td data-label="Radio layout">Dual-band: 2.4 + 5GHz; &lt;strong>no 6GHz&lt;/strong>&lt;/td>
&lt;td data-label="Useful wired I/O">10G SFP+, 10G WAN/LAN, 4× 2.5G, 4× 1G&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;strong>$349.99&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pick">&lt;strong>&lt;a href="#gt-be98-pro">ASUS GT-BE98 Pro&lt;/a>&lt;/strong>&lt;/td>
&lt;td data-label="Best for">Dual-6GHz AiMesh and dense networks&lt;/td>
&lt;td data-label="Radio layout">Quad-band: 2.4 + 5 + 6 + 6GHz&lt;/td>
&lt;td data-label="Useful wired I/O">2× 10G, 4× 2.5G, 1× 1G&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;strong>$684.99&lt;/strong>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Every price is the listing sold by Newegg itself in Newegg&amp;rsquo;s catalogue on November 17, 2026. Prices move daily in Black Friday week, so check the listing before you buy.&lt;/p>
&lt;p>Before comparing models, answer four questions: does the router need 6GHz (yes, if 320MHz channels are the point), what speed feeds it, what wired gear sits behind it, and can one box cover the home. The best router is the least expensive one that serves those four answers.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. &lt;/em>&lt;/p>
&lt;h2 id="rt-be92u">1. ASUS RT-BE92U: the pick for most homes&lt;/h2>
&lt;p>The RT-BE92U has the wireless and wired sides a mainstream Wi-Fi 7 upgrade needs. ASUS lists 2.4GHz, 5GHz and 6GHz radios with 20 to 320MHz channel widths, so the 6GHz band and its 320MHz channels are there. The wired side is one 10G WAN/LAN port, one 2.5G WAN/LAN port and three 2.5G LAN ports, plus a USB 3.2 Gen1 port.&lt;/p>
&lt;p>That combination keeps a fast Wi-Fi client from being pinched behind a gigabit port on the way to a multi-gig NAS, lets a 5Gbps fiber service enter through the 10G port, and saves many homes a small multi-gig switch.&lt;/p>
&lt;p>TP-Link&amp;rsquo;s Archer BE550 Pro has nearly the same layout, tri-band with 320MHz on 6GHz, one 10G WAN and four 2.5G LAN ports, and it was this page&amp;rsquo;s main pick in August. Newegg&amp;rsquo;s catalogue did not list it on November 17, 2026, so it has no buy link here.&lt;/p>
&lt;p>Check two details at checkout: the exact model name and regional version, and whether the phone, laptop or desktop you want to speed up supports 6GHz Wi-Fi 7. A router cannot add a radio to the client.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=ASUS&amp;#43;RT-BE92U&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fasus-rt-be92u-ieee-802-11a-ieee-802-11b-ieee-802-11g-wifi-4-wifi-5-wifi-6-wifi-6e-wifi-7-ipv4-ipv6%2Fp%2FN82E16833320608" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="archer-be230">2. TP-Link Archer BE230: the pick under $100&lt;/h2>
&lt;p>The Archer BE230 is how Wi-Fi 7 gets under $100: TP-Link rates it BE3600 dual-band, 5GHz and 2.4GHz, with Multi-Link Operation. There is no 6GHz radio, so no 320MHz channels. The wired side is better than the price suggests: a 2.5G WAN port, a 2.5G LAN port and three gigabit LAN ports, plus USB 3.0.&lt;/p>
&lt;p>Buy it for a gigabit or 2.5G internet plan in an apartment or a small home, or when your clients do not have 6GHz radios yet. Skip it if wide-channel 6GHz speed is the reason you are upgrading; that is what the RT-BE92U&amp;rsquo;s extra money buys.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=TP-Link&amp;#43;Archer&amp;#43;BE230&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Ftp-link-archer-be230-ieee-802-11be-ax-ac-n-a-5-ghz-ieee-802-11be-ax-n-g-b-2-4-ghz%2Fp%2FN82E16833704758" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="deco-be63">3. TP-Link Deco BE63: the mesh pick&lt;/h2>
&lt;p>When one box cannot cover the house, a mesh kit is a different purchase, and the Deco BE63 keeps the 6GHz band that makes Wi-Fi 7 worth it. TP-Link rates it BE10000 tri-band, 2.4GHz, 5GHz and 6GHz, with 320MHz channels on 6GHz only and MLO. Each unit has four 2.5G ports that auto-sense WAN or LAN, and TP-Link supports optional Ethernet backhaul between units. It rates the two-pack for up to 5,800 square feet.&lt;/p>
&lt;p>Wire the units together with 2.5G Ethernet if you can; a wired backhaul leaves every radio free for clients. If you cannot, place the second unit where it still has a strong link to the first rather than at the edge of the dead zone.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=TP-Link&amp;#43;Deco&amp;#43;BE63&amp;#43;2-pack&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Ftp-link-deco-be63%2Fp%2FN82E16833704722" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="rt-be88u">4. ASUS RT-BE88U: the wired-first exception&lt;/h2>
&lt;p>The RT-BE88U is an unusual recommendation because its strongest feature is also the reason many Wi-Fi 7 buyers should skip it.&lt;/p>
&lt;p>ASUS lists only 5GHz and 2.4GHz. There is no 6GHz radio, so there are no 320MHz 6GHz channels; ASUS lists channel widths up to 160MHz. Put that fact above every marketing number.&lt;/p>
&lt;p>The wired layout is excellent:&lt;/p>
&lt;ul>
&lt;li>one 10G SFP+ port&lt;/li>
&lt;li>one 10G WAN/LAN port&lt;/li>
&lt;li>one 2.5G WAN/LAN port and three 2.5G LAN ports&lt;/li>
&lt;li>four gigabit LAN ports&lt;/li>
&lt;/ul>
&lt;p>For a homelab or fiber gateway, that can replace both a consumer router and a separate multi-gig switch. The SFP+ port is especially useful when the existing core already speaks DAC or fiber; the &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE budget guide&lt;/a> covers the cards and cables on the other end. At $349.99, the extra $64 over the RT-BE92U can be cheaper than buying a managed switch.&lt;/p>
&lt;p>For a wireless-first buyer, the logic reverses. Spending more while losing 6GHz makes no sense when the reason for the upgrade is wide-channel Wi-Fi. This is the port-density pick. Nothing else.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=ASUS&amp;#43;RT-BE88U&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fasus-rt-be88u-ieee-802-11a-ieee-802-11b-ieee-802-11g-wifi-4-wifi-5-wifi-6-wifi-6e-wifi-7-ipv4-ipv6%2Fp%2FN82E16833320598" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="gt-be98-pro">5. ASUS GT-BE98 Pro: the flagship&lt;/h2>
&lt;p>The GT-BE98 Pro carries four radios: 2.4GHz and 5GHz plus two separate 6GHz bands, each with 320MHz support. ASUS&amp;rsquo;s spec page lists one 10G WAN/LAN port, one 2.5G WAN/LAN port, one 10G LAN port, three 2.5G LAN ports and one gigabit LAN port, plus AiMesh.&lt;/p>
&lt;p>The second 6GHz radio is the feature that can justify the price. In an AiMesh deployment, one 6GHz band can carry wireless backhaul while the other serves clients. In a dense single-router deployment, the extra radio can divide high-end clients instead of placing them all on one 6GHz channel set.&lt;/p>
&lt;p>Most homes will never turn that capability into a visible result. A single laptop cannot consume four bands. A gigabit internet plan cannot saturate the wired uplink. If the second 6GHz radio has no backhaul or client-density job, the $684.99 price is a $399 premium over the RT-BE92U for idle capacity.&lt;/p>
&lt;p>Buy it for a named topology: dual-6GHz AiMesh, multiple current Wi-Fi 7 clients, 10G core networking, or a flagship gaming network where cost is secondary. It is the strongest wireless platform here. It is not the default.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=ASUS&amp;#43;ROG&amp;#43;Rapture&amp;#43;GT-BE98&amp;#43;Pro&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fasus-gt-be98-pro%2Fp%2FN82E16833320588" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/best-wifi-7-router-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="why-6ghz-changes-the-ranking">Why 6GHz changes the ranking&lt;/h2>
&lt;p>Wi-Fi 7 features are not one indivisible package. MLO and 4K-QAM can operate without 6GHz. The headline 320MHz channels cannot; in the United States they live in the 6GHz band.&lt;/p>
&lt;p>That creates three product classes:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Class&lt;/th>
&lt;th scope="col">What it gives you&lt;/th>
&lt;th scope="col">What it misses&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Class">&lt;strong>Dual-band Wi-Fi 7&lt;/strong>&lt;/td>
&lt;td data-label="What it gives you">MLO/4K-QAM on 2.4 and 5GHz, often strong wired I/O&lt;/td>
&lt;td data-label="What it misses">6GHz and 320MHz channels&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Class">&lt;strong>Tri-band Wi-Fi 7&lt;/strong>&lt;/td>
&lt;td data-label="What it gives you">The full mainstream feature set: 2.4, 5, 6GHz&lt;/td>
&lt;td data-label="What it misses">A dedicated second 6GHz backhaul/client radio&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Class">&lt;strong>Quad-band dual-6GHz&lt;/strong>&lt;/td>
&lt;td data-label="What it gives you">Extra capacity or dedicated 6GHz mesh backhaul&lt;/td>
&lt;td data-label="What it misses">Value, unless the topology uses it&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>This is why the RT-BE92U leads and the RT-BE88U stays a specialist. The RT-BE92U delivers the feature most buyers mean when they say &amp;ldquo;upgrade to Wi-Fi 7.&amp;rdquo; The Archer BE230 and the RT-BE88U are both dual-band: one trades 6GHz for price, the other for ports.&lt;/p>
&lt;h2 id="port-topology-beats-a-30gbps-box-number">Port topology beats a 30Gbps box number&lt;/h2>
&lt;p>Router marketing adds every radio&amp;rsquo;s theoretical maximum and prints the sum. That number is access-point capacity under ideal conditions. It is not a laptop speed test.&lt;/p>
&lt;p>Read the physical ports instead:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>RT-BE92U:&lt;/strong> one 10G port and four 2.5G ports, the cleanest layout for a multi-gig home.&lt;/li>
&lt;li>&lt;strong>Archer BE230:&lt;/strong> 2.5G in and one 2.5G out; the rest is gigabit.&lt;/li>
&lt;li>&lt;strong>Deco BE63:&lt;/strong> four 2.5G ports on every unit, so wired backhaul and wired rooms share the same speed.&lt;/li>
&lt;li>&lt;strong>RT-BE88U:&lt;/strong> best wired density and the only SFP+ option here.&lt;/li>
&lt;li>&lt;strong>GT-BE98 Pro:&lt;/strong> two 10G paths plus four 2.5G ports.&lt;/li>
&lt;/ul>
&lt;p>For a NAS and workstation, map the whole chain. A 10G router feeding a gigabit switch is still a gigabit network. A Wi-Fi 7 access point wired back through 1GbE is still limited to one gigabit of backhaul. A 2.5G or 10G run through a wall is a cable decision too; &lt;a href="https://techfuelhq.com/networking/cat6-vs-cat6a-2026/">Cat6 vs Cat6A&lt;/a> covers which to pull.&lt;/p>
&lt;h2 id="standalone-router-or-mesh">Standalone router or mesh?&lt;/h2>
&lt;p>Choose standalone when:&lt;/p>
&lt;ul>
&lt;li>the router can sit near the center of the usable space&lt;/li>
&lt;li>one access point already covers the home&lt;/li>
&lt;li>Ethernet can feed a separate access point later&lt;/li>
&lt;/ul>
&lt;p>Choose mesh when:&lt;/p>
&lt;ul>
&lt;li>floors, dense walls, or distance create repeatable dead zones&lt;/li>
&lt;li>one central location cannot cover the house&lt;/li>
&lt;li>you can wire at least the main satellite with 2.5GbE or faster&lt;/li>
&lt;/ul>
&lt;p>A larger antenna count does not repair a bad access-point location. Spend on topology before flagship hardware: if the upstairs devices stay weak because the router is in a basement corner, a second wired access point or a mesh node fixes it, and a bigger standalone router does not. If you would rather run a separate firewall and access points than a consumer router, &lt;a href="https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/">UniFi vs an OPNsense build&lt;/a> covers that route, and the &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">homelab VLAN guide&lt;/a> covers splitting IoT and guest devices onto their own network. Cheaper wired gear for the rest of the network is in &lt;a href="https://techfuelhq.com/articles/best-homelab-networking-gear-under-200/">homelab networking gear under $200&lt;/a>.&lt;/p>
&lt;h2 id="do-not-upgrade-to-solve-a-fault">Do not upgrade to solve a fault&lt;/h2>
&lt;p>A router that disconnects clients, reboots, or loses WAN under load may need replacement. It may also have a channel, firmware, heat, power, or ISP problem. Rule those out before using a new wireless generation as a repair strategy.&lt;/p>
&lt;p>The same rule applies to speed. Test a wired client first. If Ethernet is slow, the radio is innocent.&lt;/p>
&lt;h2 id="lag-under-load">Lag under load is a queue, not a radio&lt;/h2>
&lt;p>If the complaint is lag rather than speed, test before you buy. A line that measures 900 Mbps idle can still spike a game&amp;rsquo;s ping the moment a console pulls an update or a phone uploads its photo library, because packets pile up in a buffer at the slowest link, often the modem or the router&amp;rsquo;s upload. The IETF working draft on network responsiveness says significant queueing &amp;ldquo;only happens on entry to the lowest-capacity&amp;rdquo; hop on the path. A Wi-Fi 7 router does not move that hop when the bottleneck is the cable modem&amp;rsquo;s upstream.&lt;/p>
&lt;p>Run the test on the router you already own. Plug a PC in with Ethernet and open &lt;a href="https://www.waveform.com/tools/bufferbloat" rel="noopener">Waveform&amp;rsquo;s bufferbloat test&lt;/a>. It measures idle latency, then latency during a download and during an upload, and grades the larger increase: A+ under 5 ms added, A under 30, B under 60, C under 200, D under 400, F at 400 ms or more. By Waveform&amp;rsquo;s own scale, anything worse than a B may affect video calls and gaming.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Wired result&lt;/th>
&lt;th scope="col">Where the queue is&lt;/th>
&lt;th scope="col">What fixes it&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Wired result">Latency jumps during the upload phase&lt;/td>
&lt;td data-label="Where the queue is">Modem or router upstream&lt;/td>
&lt;td data-label="What fixes it">Smart queue management (SQM) on the router: CAKE or fq_codel, shaped a little below the measured upload speed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Wired result">Latency jumps during the download phase&lt;/td>
&lt;td data-label="Where the queue is">Upstream of your router, on the ISP side of the line&lt;/td>
&lt;td data-label="What fixes it">SQM shaping on the download side as well&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Wired result">Ethernet is clean, Wi-Fi jumps&lt;/td>
&lt;td data-label="Where the queue is">The wireless hop&lt;/td>
&lt;td data-label="What fixes it">Access-point placement and the 5GHz or 6GHz band before a new Wi-Fi generation&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Shaping is a router feature, not a Wi-Fi standard. OpenWrt&amp;rsquo;s SQM guide sets the shaper to 90% of your tested speed and warns that slower devices may not keep up with a full-speed line, because SQM runs on the router&amp;rsquo;s CPU. MLO, Wi-Fi 7&amp;rsquo;s multi-link feature, works on the Wi-Fi hop only, and a 2023 experimental study found it can cut latency sharply when both links are equally busy but can increase it when they are not.&lt;/p>
&lt;h2 id="the-60-second-checkout-audit">The 60-second checkout audit&lt;/h2>
&lt;ol>
&lt;li>If lag under load is the complaint, run a wired bufferbloat test on the current router first.&lt;/li>
&lt;li>Match the exact model and item number.&lt;/li>
&lt;li>Count the bands. Look for 6GHz explicitly.&lt;/li>
&lt;li>Confirm the WAN port speed and whether it can become LAN.&lt;/li>
&lt;li>Count 10G, 2.5G, and 1G LAN ports separately.&lt;/li>
&lt;li>Check whether your clients support Wi-Fi 7 and 6GHz.&lt;/li>
&lt;li>Decide standalone versus mesh before ordering.&lt;/li>
&lt;li>Confirm seller, warranty, return window, and regional version.&lt;/li>
&lt;li>Screenshot the final price and configuration.&lt;/li>
&lt;/ol>
&lt;p>For most buyers, the answer is the RT-BE92U. It buys the radio that makes Wi-Fi 7 different and the ports that keep it from being trapped behind gigabit.&lt;/p></description></item><item><title>Docker Cleanup: Which Prune Command Eats Your Data (2026)</title><link>https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/</link><pubDate>Sat, 15 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/</guid><atom:updated>2026-11-18T06:45:00Z</atom:updated><description>&lt;p>The received wisdom is simple. &lt;code>docker system prune -a --volumes&lt;/code> eats databases, so never run it.&lt;/p>
&lt;p>That fear is aimed at the wrong command. Docker&amp;rsquo;s own &lt;a href="https://docs.docker.com/reference/cli/docker/system/prune/" rel="noopener">options table&lt;/a> describes &lt;code>--volumes&lt;/code> as &lt;strong>&amp;ldquo;Prune anonymous volumes&amp;rdquo;&lt;/strong>, and the confirmation prompt spells out what it will remove: all anonymous volumes not used by at least one container. A named volume is not anonymous. If your Postgres data lives in a volume you named in a compose file, &lt;code>docker system prune -a --volumes&lt;/code> is not the thing that will take it.&lt;/p>
&lt;p>The command that removes named volumes is this one.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker volume prune --all
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Docker &lt;a href="https://docs.docker.com/reference/cli/docker/volume/prune/" rel="noopener">documents&lt;/a> that by default &lt;code>docker volume prune&lt;/code> only removes anonymous volumes, and that &lt;code>--all&lt;/code> removes all unused volumes, not just anonymous ones, behind an API 1.42 gate. Read those two sentences next to each other and the asymmetry is obvious: the destructive option is a four-character flag on a command whose name sounds like it only touches leftovers.&lt;/p>
&lt;p>So the scary-sounding command is narrower than its reputation. The mild-sounding one is the loaded gun. That inversion (feared command safe, safe-sounding command dangerous) is the whole reason this page exists.&lt;/p>
&lt;p>&lt;strong>All of that depends on your Engine version.&lt;/strong> The anonymous-only default arrived with Docker Engine 23.0 in February 2023: its &lt;a href="https://docs.docker.com/engine/release-notes/23.0/" rel="noopener">release notes&lt;/a> say only anonymous volumes are now pruned by default on API 1.42 and later. On an older daemon, &lt;code>docker volume prune&lt;/code> and &lt;code>docker system prune --volumes&lt;/code> also removed unused named volumes. Check before you prune anything with volumes in it:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker version --format &lt;span style="color:#e6db74">&amp;#39;{{.Server.Version}}&amp;#39;&lt;/span> &lt;span style="color:#75715e"># 23.0 or later for the behaviour above&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This page is written against Docker Engine 29.10.0, the current release on November 18, 2026.&lt;/p>
&lt;p>One caveat before you act on any of it. Everything above is read from Docker&amp;rsquo;s current documentation, not from a test I ran on this machine. I have no Docker daemon here. The optional demonstration at the end requires an entirely disposable daemon. Inspect mounts on your real host without running a prune as a test.&lt;/p>
&lt;h2 id="what-each-command-removes">What each command removes&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Command&lt;/th>
&lt;th scope="col">What it removes&lt;/th>
&lt;th scope="col">Volumes&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker builder prune&lt;/code>&lt;/td>
&lt;td data-label="What it removes">Dangling build cache; &lt;code>-a&lt;/code> takes all unused build cache&lt;/td>
&lt;td data-label="Volumes">Never&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker container prune&lt;/code>&lt;/td>
&lt;td data-label="What it removes">All stopped containers, writable layers included&lt;/td>
&lt;td data-label="Volumes">Never&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker image prune&lt;/code>&lt;/td>
&lt;td data-label="What it removes">Dangling images; &lt;code>-a&lt;/code> takes every image no container uses&lt;/td>
&lt;td data-label="Volumes">Never&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker system prune&lt;/code>&lt;/td>
&lt;td data-label="What it removes">Stopped containers, unused networks, dangling images, unused build cache&lt;/td>
&lt;td data-label="Volumes">Not by default&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker system prune -a&lt;/code>&lt;/td>
&lt;td data-label="What it removes">The same, plus every unused image and all build cache&lt;/td>
&lt;td data-label="Volumes">Not by default&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker system prune --volumes&lt;/code>&lt;/td>
&lt;td data-label="What it removes">Adds unused anonymous volumes&lt;/td>
&lt;td data-label="Volumes">Anonymous only on 23.0+; named too on older engines&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker volume prune&lt;/code>&lt;/td>
&lt;td data-label="What it removes">Unused anonymous volumes&lt;/td>
&lt;td data-label="Volumes">Anonymous only on 23.0+; named too on older engines&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Command">&lt;code>docker volume prune --all&lt;/code>&lt;/td>
&lt;td data-label="What it removes">Every unused volume, named ones included&lt;/td>
&lt;td data-label="Volumes">Named and anonymous&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>A dangling image (one that no tag points at any more) is typically what is left after rebuilding under the same tag. &amp;ldquo;Unused&amp;rdquo; in &lt;code>-a&lt;/code> means no container is associated with the image, tagged or not. On a homelab where you keep images around for things you run occasionally, &lt;code>-a&lt;/code> removes them and you will pull them again over your home connection at the least convenient moment. It is safe for your data. It is expensive for your time.&lt;/p>
&lt;p>Current docs add one detail for &lt;code>docker system prune&lt;/code>: build cache is always eligible, including BuildKit cache mounts created with &lt;code>RUN --mount=type=cache&lt;/code>.&lt;/p>
&lt;h2 id="step-1-look-before-you-sweep">Step 1: Look before you sweep&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker system df
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker system df -v
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The first breaks usage into images, containers, local volumes and build cache, with a reclaimable column. The second lists every image, container and volume with its own size. Run them first. Every time.&lt;/p>
&lt;p>I push this because &amp;ldquo;reclaim disk space&amp;rdquo; is usually the wrong framing, and running a prune before you have looked at &lt;code>docker system df&lt;/code> is how people end up re-pulling forty gigabytes of images to solve a problem that was one container writing an unbounded log file the whole time. The question is what filled the disk, and the answer changes the fix entirely. Build cache on a machine that builds often is a different problem from forty pulled images you never run, which is different again from one container writing an unbounded log. Only one of those is solved by pruning.&lt;/p>
&lt;p>Check the logs in the same pass. Docker&amp;rsquo;s default &lt;code>json-file&lt;/code> logging driver performs no rotation at all, and Docker&amp;rsquo;s own &lt;a href="https://docs.docker.com/engine/logging/configure/" rel="noopener">logging page&lt;/a> warns that it can exhaust the disk for containers that generate much output:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker info --format &lt;span style="color:#e6db74">&amp;#39;{{.LoggingDriver}}&amp;#39;&lt;/span> &lt;span style="color:#75715e"># json-file unless someone changed it&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo du -h &lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>docker inspect --format&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;{{.LogPath}}&amp;#39;&lt;/span> CONTAINER_NAME&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>And check the right directory. On Linux the daemon keeps its data in &lt;code>/var/lib/docker&lt;/code>, but on fresh Docker Engine 29 installs, which use the containerd image store, image contents and container snapshots live in &lt;code>/var/lib/containerd&lt;/code> instead:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo du -sh /var/lib/docker /var/lib/containerd 2&amp;gt;/dev/null
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-2-clear-the-build-cache">Step 2: Clear the build cache&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker builder prune &lt;span style="color:#75715e"># dangling build cache&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker builder prune -a --filter &lt;span style="color:#66d9ef">until&lt;/span>&lt;span style="color:#f92672">=&lt;/span>24h &lt;span style="color:#75715e"># all unused cache older than a day&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Build cache is the safest thing here to delete, because it is reproducible by definition. On a machine that builds regularly it is also often the entire problem. &lt;code>--keep-storage&lt;/code> lets you keep a set amount of cache instead of emptying it.&lt;/p>
&lt;h2 id="step-3-remove-stopped-containers-and-dangling-images">Step 3: Remove stopped containers and dangling images&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker system prune &lt;span style="color:#75715e"># stopped containers, unused networks, dangling images, unused build cache&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Before you run it, save anything needed from stopped containers: pruning removes their writable layers too. A stopped container can still hold your only copy of a file.&lt;/p>
&lt;p>To be narrower, prune one type and only what is older than a cutoff:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker container prune --filter &lt;span style="color:#66d9ef">until&lt;/span>&lt;span style="color:#f92672">=&lt;/span>24h
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-4-remove-old-unused-images-if-you-accept-re-pulling">Step 4: Remove old unused images, if you accept re-pulling&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker image prune -a --filter &lt;span style="color:#e6db74">&amp;#34;until=240h&amp;#34;&lt;/span> &lt;span style="color:#75715e"># unused images created more than 10 days ago&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;code>until&lt;/code> filter takes a timestamp or a duration such as &lt;code>240h&lt;/code>, computed on the daemon&amp;rsquo;s clock. This is the step that costs bandwidth later, so it is the one to skip on a slow or metered connection.&lt;/p>
&lt;h2 id="step-5-cap-container-logs">Step 5: Cap container logs&lt;/h2>
&lt;p>Do not delete or edit the log files by hand: Docker&amp;rsquo;s &lt;a href="https://docs.docker.com/engine/logging/drivers/json-file/" rel="noopener">json-file page&lt;/a> says they are meant to be accessed only by the daemon, and outside tools can interfere with its logging. Set rotation instead. Docker recommends the &lt;a href="https://docs.docker.com/engine/logging/drivers/local/" rel="noopener">&lt;code>local&lt;/code> driver&lt;/a>, which rotates by default (20 MB files, five of them, compressed: about 100 MB per container). Put this in &lt;code>/etc/docker/daemon.json&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-json" data-lang="json">&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;log-driver&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;local&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Or keep &lt;code>json-file&lt;/code> and give it limits. The values in &lt;code>log-opts&lt;/code> must be quoted strings:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-json" data-lang="json">&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;log-driver&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;json-file&amp;#34;&lt;/span>,
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;log-opts&amp;#34;&lt;/span>: {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;max-size&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;10m&amp;#34;&lt;/span>,
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;max-file&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;3&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then restart the daemon:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo systemctl restart docker
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Warning:&lt;/strong> by default, when the Docker daemon stops it shuts down running containers. Unless you have &lt;a href="https://docs.docker.com/engine/daemon/live-restore/" rel="noopener">live restore&lt;/a> enabled, do this when a brief outage is acceptable; containers with a restart policy come back with the daemon.&lt;/p>
&lt;p>The new settings only apply to containers created afterwards. Existing containers keep the options they were created with, so recreate them, for example with &lt;code>docker compose up -d --force-recreate&lt;/code> in each project. To set limits for one service instead of the whole daemon, use the Compose &lt;code>logging&lt;/code> key:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">app&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">logging&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">driver&lt;/span>: &lt;span style="color:#ae81ff">json-file&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">options&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">max-size&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;10m&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">max-file&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;3&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-6-volumes-only-by-name">Step 6: Volumes, only by name&lt;/h2>
&lt;p>Volumes are the one thing on this page that might be the only copy of something. Look at each one before removing it, and remove it by name. The commands are in the routine below. If what you actually need is more room rather than less clutter, size the host&amp;rsquo;s disk properly: the &lt;a href="https://techfuelhq.com/homelab/proxmox-hardware-requirements-2026/">Proxmox hardware requirements guide&lt;/a> covers that for a homelab box.&lt;/p>
&lt;h2 id="the-trap-that-is-genuinely-real">The trap that is genuinely real&lt;/h2>
&lt;p>Here is the case where you can genuinely lose data to anonymous-volume pruning. It is not the one people worry about.&lt;/p>
&lt;p>Some official images declare a &lt;code>VOLUME&lt;/code> in their Dockerfile. Postgres declares one at its data directory. When you start such an image without giving it a named volume or a bind mount, Docker satisfies that declaration by creating an anonymous volume. It has a long hex name you never chose. It holds your actual database.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># creates an anonymous volume holding real data&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker run -d postgres:17
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># creates a named volume you control&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker run -d -v pgdata:/var/lib/postgresql/data postgres:17
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Stop that first container and the anonymous volume is now unused, and squarely in scope for &lt;code>--volumes&lt;/code>.&lt;/p>
&lt;p>So the failure mode is not &amp;ldquo;prune ate my named volume&amp;rdquo;. It is &amp;ldquo;I never named the volume, so Docker quietly named it for me, that autogenerated name made it anonymous by definition, and anonymous is precisely the category the flag I ran was documented to remove&amp;rdquo;. The fix is upstream of any prune command: name your volumes. A compose file with a top-level &lt;code>volumes:&lt;/code> block gets this right by default, which is one more reason to run things through compose rather than long &lt;code>docker run&lt;/code> lines; the &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">Compose environment variables guide&lt;/a> covers the rest of a tidy compose file. And a volume you would miss belongs in a &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">backup&lt;/a> before any of these commands come near it.&lt;/p>
&lt;h2 id="what-i-run-weekly">What I run weekly&lt;/h2>
&lt;p>Weekly, on a homelab Docker host, with the reasoning attached:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker system df &lt;span style="color:#75715e"># look first&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker builder prune &lt;span style="color:#75715e"># cache is reproducible&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker system prune &lt;span style="color:#75715e"># stopped containers, unused networks, dangling images&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>I add &lt;code>-a&lt;/code> only when I have decided I am willing to re-pull, which on a metered or slow connection is a real cost rather than a theoretical one.&lt;/p>
&lt;p>I never run &lt;code>docker volume prune --all&lt;/code> on a schedule. A volume is the one thing here that might be the only copy. When I want a specific volume gone, I look at it first and then remove it by name, which is slower in exactly the way that a command capable of destroying the only copy of something ought to be:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker volume ls
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker volume inspect &amp;lt;name&amp;gt;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker volume rm &amp;lt;name&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Slower. It also makes me say what I mean.&lt;/p>
&lt;h2 id="optional-demonstration-on-a-disposable-daemon">Optional demonstration on a disposable daemon&lt;/h2>
&lt;p>&lt;code>docker system prune&lt;/code> acts across its target daemon. Creating two test volumes does not restrict it to those volumes. On your real host, inspect &lt;code>docker system df -v&lt;/code> and the relevant container mounts; do not run a global prune just to test what it deletes.&lt;/p>
&lt;p>To see the behaviour for yourself, use a separate empty Linux VM whose entire Docker storage you can lose, and a Docker context named &lt;code>prune-lab&lt;/code> that points only at it (&lt;a href="https://docs.docker.com/engine/manage-resources/contexts/" rel="noopener">Docker&amp;rsquo;s context documentation&lt;/a>). A context name alone proves nothing about its target, so confirm the endpoint first and stop if that daemon holds any real workload:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker context inspect prune-lab
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab info --format &lt;span style="color:#e6db74">&amp;#39;{{.Name}}&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab ps -a
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab volume ls
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then, naming the context on every command (the containers are created but never started):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker --context prune-lab pull alpine
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab volume create keepme
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab create --name anon-test -v /data alpine
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab create --name named-test -v keepme:/data alpine
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab rm anon-test named-test
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab volume ls
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab system prune -a --volumes
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker --context prune-lab volume ls
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>On Engine 23.0 or later, the &lt;a href="https://docs.docker.com/engine/manage-resources/pruning/" rel="noopener">documented prune behavior&lt;/a> predicts that the unused anonymous volume disappears and &lt;code>keepme&lt;/code> remains. Compare the before and after lists. This experiment can delete resources across the whole disposable daemon. Keep it off your active host.&lt;/p>
&lt;h2 id="what-i-have-not-tested">What I have not tested&lt;/h2>
&lt;p>I have not run any of this on a live daemon during this write-up, for the reason given at the top. Every behavioural claim here traces to Docker&amp;rsquo;s current CLI documentation.&lt;/p>
&lt;p>I have not checked how an older daemon behaves, and this is the gap I would most want closed before anyone runs these commands on a long-lived box that has not been updated in a couple of years. &lt;code>--all&lt;/code> on &lt;code>docker volume prune&lt;/code> carries an API 1.42 gate, which implies the pre-1.42 behaviour differed, and I have not established what a new CLI does against an old daemon. If you are on something long-lived and unpatched, test rather than assume. Docker&amp;rsquo;s Engine 23.0 release notes, read on November 18, 2026, settle the daemon side: anonymous-only pruning by default arrived with API 1.42 in Engine 23.0, so a daemon older than that removes unused named volumes too.&lt;/p>
&lt;p>I have not measured how much any of this reclaims in practice. That number is a property of your machine, and quoting mine would tell you nothing.&lt;/p>
&lt;h2 id="what-getting-it-wrong-costs">What getting it wrong costs&lt;/h2>
&lt;p>Pruning images costs you a download. Pruning build cache costs one slow build. Both are annoyances with a known price.&lt;/p>
&lt;p>Pruning a volume costs you whatever was in it, and the price is only discovered later, usually when something tries to read data that is no longer there and fails in a way that does not obviously say &amp;ldquo;your volume is gone&amp;rdquo;. If that data mattered, the real lesson is not about prune flags at all. It is that a volume you would miss should be &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">backed up&lt;/a>, because a wrong flag is only one of many ways to lose it.&lt;/p>
&lt;p>If the container died rather than the disk filling, the &lt;a href="https://techfuelhq.com/tutorials/docker-exit-code-137-oomkilled-2026/">exit code 137 guide&lt;/a> covers the memory side.&lt;/p></description></item><item><title>Home Assistant Connect ZBT-2: Buy It, or a Sonoff? (2026)</title><link>https://techfuelhq.com/homelab/home-assistant-connect-zbt-2-2026/</link><pubDate>Sat, 12 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/home-assistant-connect-zbt-2-2026/</guid><atom:updated>2026-11-18T06:40:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Connect ZBT-2&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Buy it&lt;/strong> for a first Zigbee network on a Home Assistant box that sits where the stick can sit, or for a Thread border router you can switch to later. $49 MSRP, cable and antenna in the box, ZHA, Zigbee2MQTT and OpenThread all supported.&lt;/li>
&lt;li>&lt;strong>It is one radio.&lt;/strong> Zigbee or Thread, never both at once, and no Bluetooth or Z-Wave. Both networks means two sticks.&lt;/li>
&lt;li>&lt;strong>Skip it&lt;/strong> when the Home Assistant machine lives in a rack or closet and the radio needs to live in the house: the SMLIGHT SLZB-06 goes on Ethernet with PoE. Skip it for Z-Wave; that is the ZWA-2.&lt;/li>
&lt;li>&lt;strong>Owners of a ZBT-1 or SkyConnect&lt;/strong> keep using it. Discontinued, still updated, same hardware under both names.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Home Assistant&amp;rsquo;s own Zigbee stick got a second generation in November 2025.&lt;/p>
&lt;p>The question is whether it is the right radio for the machine and the house it is going into, and that turns on a few things the product page will not decide for you. I have no ZBT-2 on my bench. This page is built from the vendor documents and the owner threads, and the verdict is my position on them.&lt;/p>
&lt;h2 id="the-deciders-that-matter-ranked">The deciders that matter, ranked&lt;/h2>
&lt;p>&lt;strong>1. One radio runs one protocol.&lt;/strong> Nabu Casa&amp;rsquo;s specification page says it plainly: &amp;ldquo;Home Assistant Connect ZBT-2 supports either the Zigbee or Thread protocol. You can choose the protocol during setup and also switch later, if needed.&lt;/p>
&lt;p>Running Zigbee and Thread at the same time on the same adapter is not supported.&amp;rdquo; The product page says the same in fewer words: &amp;ldquo;Connect ZBT-2 cannot do both Zigbee and Thread simultaneously.&amp;rdquo; So the ZBT-2 is a Zigbee coordinator or a Thread border router, and if you want Zigbee devices and Matter-over-Thread devices in the same house you need two radios.&lt;/p>
&lt;p>The same Nabu Casa page adds that Home Assistant&amp;rsquo;s ZHA integration &amp;ldquo;is single instance only&amp;rdquo; and that &amp;ldquo;you cannot run 2 Home Assistant Connect ZBT-2 adapters with the Zigbee Home Automation integration at once.&amp;rdquo; That limit is ZHA&amp;rsquo;s, not the stick&amp;rsquo;s. Two ZBT-2s on ZHA is out; one on ZHA and one on Thread is the documented pair.&lt;/p>
&lt;p>&lt;strong>2. Where the radio can physically sit.&lt;/strong> The ZBT-2 is a USB stick.&lt;/p>
&lt;p>Home Assistant ships it with a 1.5 m USB-C cable and a 164 mm external antenna precisely because the ZHA documentation tells you to keep the radio away from the computer: &amp;ldquo;Avoid USB 3.0 ports/computers/peripherals as they are known culprits of RFI/EMI/EMF disruption,&amp;rdquo; &amp;ldquo;only connect the Zigbee USB adapter to a USB 2.0 port,&amp;rdquo; and &amp;ldquo;use a long USB extension cable and place Zigbee Coordinator away from interference and obstacles.&amp;rdquo; A cable solves that for a Home Assistant Green on a shelf.&lt;/p>
&lt;p>It does not solve it for a Proxmox host in a basement rack, and that is the case where a network-attached coordinator wins. SMLIGHT&amp;rsquo;s SLZB-06 models take 802.3af PoE, so check the switch with the &lt;a href="https://techfuelhq.com/tools/poe-budget-calculator/">PoE budget calculator&lt;/a>, and give the coordinator a port on your &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">IoT VLAN&lt;/a> if you run one.&lt;/p>
&lt;p>The top reply in the r/homeassistant thread makes the same cut: the ZBT-2 &amp;ldquo;is great if you&amp;rsquo;re using ZHA and have a good place to put it,&amp;rdquo; and &amp;ldquo;isn&amp;rsquo;t great if you want to connect it over something other than USB, for instance ethernet.&amp;rdquo; The &lt;a href="https://techfuelhq.com/homelab/best-mini-pc-home-assistant-2026/">mini PC for Home Assistant&lt;/a> page covers the USB 3 interference trap in detail.&lt;/p>
&lt;p>&lt;strong>3. Which Zigbee software you run.&lt;/strong> Nabu Casa lists ZHA, Zigbee2MQTT and OpenThread Border Router as supported, and the product page answers the Zigbee2MQTT question directly: &amp;ldquo;Yes, Connect ZBT-2 is being used by many people with Zigbee2MQTT, and they are seeing great results.&amp;rdquo; Nabu Casa&amp;rsquo;s Getting started with Zigbee section carries migration guides from Zigbee2MQTT, deCONZ and an existing ZHA network onto the ZBT-2, so moving a network is a documented path rather than a re-pair.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/tutorials/home-assistant-zigbee-zwave-2026/">Zigbee and Z-Wave tutorial&lt;/a> is the setup walk-through for either path.&lt;/p>
&lt;p>&lt;strong>4. Z-Wave is a different stick.&lt;/strong> The ZBT-2 &amp;ldquo;does not support Bluetooth or Z-Wave.&amp;rdquo; Home Assistant&amp;rsquo;s Z-Wave radio is the Connect ZWA-2, a Silicon Labs ZG23 800-series stick that its product page prices at $69 / 59€ and that runs &amp;ldquo;Z-Wave and Z-Wave Long Range networks simultaneously.&amp;rdquo; If your devices are Z-Wave, the ZBT-2 does nothing for you.&lt;/p>
&lt;p>&lt;strong>5. Price against the cheap dongle.&lt;/strong> The ZBT-2&amp;rsquo;s recommended price is $49 USD / €45. ITead lists the Sonoff Zigbee 3.0 USB Dongle Plus, the ZBDongle-P, at $19.90 with a CC2652P, +20 dBm output and an SMA antenna. Both work with ZHA and Zigbee2MQTT. ITead sells the ZBDongle-P as a Zigbee 3.0 coordinator, and its product page says nothing about Thread, so plan on a different radio for a Thread border router. If Thread is never coming to your house, the price gap buys nothing.&lt;/p>
&lt;p>&lt;strong>6. The radio itself.&lt;/strong> The generation change is real. Home Assistant&amp;rsquo;s announcement says the ZBT-2 moves from the MG21 to the Silicon Labs MG24, takes the chip&amp;rsquo;s serial link to the host from 115,200 to 460,800 baud, which is the link speed and not radio range, and grows the antenna from &amp;ldquo;safety pin-sized&amp;rdquo; to &amp;ldquo;tablespoon-sized.&amp;rdquo; It also puts an ESP32-S3 on the stick as the USB bridge, which the blog frames as room for future firmware work.&lt;/p>
&lt;p>None of that changes the one-protocol rule.&lt;/p>
&lt;h2 id="side-by-side">Side by side&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Connect ZBT-2&lt;/th>
&lt;th scope="col">Connect ZBT-1 (SkyConnect)&lt;/th>
&lt;th scope="col">Sonoff ZBDongle-P&lt;/th>
&lt;th scope="col">SMLIGHT SLZB-06&lt;/th>
&lt;th scope="col">Connect ZWA-2&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Protocols&lt;/td>
&lt;td data-label="Connect ZBT-2">Zigbee 3.0 or Thread, one at a time&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">Zigbee or Thread (an experimental multiprotocol firmware exists; Home Assistant does not recommend it)&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">Zigbee 3.0&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">Zigbee 3.0 or Thread (SMLIGHT: Thread on every SLZB-06 model)&lt;/td>
&lt;td data-label="Connect ZWA-2">Z-Wave and Z-Wave Long Range&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Radio&lt;/td>
&lt;td data-label="Connect ZBT-2">Silicon Labs MG24 + ESP32-S3 bridge&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">Silicon Labs MG21&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">TI CC2652P + CP2102(N)&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">TI CC2652P + ESP32 (the 06M, 06MG24, 06P7 and 06P10 use other chips)&lt;/td>
&lt;td data-label="Connect ZWA-2">Silicon Labs ZG23 + ESP32-S3 bridge&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Link&lt;/td>
&lt;td data-label="Connect ZBT-2">USB-C, 1.5 m cable and external antenna in the box; 460,800 baud host link&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">USB, 115,200 baud host link&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">USB-A, SMA antenna, +20 dBm&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">Ethernet with PoE (802.3af) or USB-C; a Wi-Fi mode per SMLIGHT&lt;/td>
&lt;td data-label="Connect ZWA-2">USB-C, 5 V 1 A&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Software&lt;/td>
&lt;td data-label="Connect ZBT-2">ZHA, Zigbee2MQTT, OpenThread Border Router&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">ZHA, Zigbee2MQTT, OpenThread&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">ZHA, Zigbee2MQTT&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">ZHA, Zigbee2MQTT, OpenThread Border Router&lt;/td>
&lt;td data-label="Connect ZWA-2">Z-Wave JS&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Bluetooth&lt;/td>
&lt;td data-label="Connect ZBT-2">No (Nabu Casa)&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">No&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">Not offered (ships Zigbee firmware)&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">BLE through the ESP32 with ESPHome firmware (SMLIGHT)&lt;/td>
&lt;td data-label="Connect ZWA-2">Antenna present but inactive&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Price on the vendor page&lt;/td>
&lt;td data-label="Connect ZBT-2">$49 / €45 MSRP (USD before tax, EUR with tax, per the product page)&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">Discontinued&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">$19.90&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">Not listed; set by resellers&lt;/td>
&lt;td data-label="Connect ZWA-2">$69 / 59€ (same tax note)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Availability, read 2026-09-12&lt;/td>
&lt;td data-label="Connect ZBT-2">Shipping since November 19, 2025&lt;/td>
&lt;td data-label="Connect ZBT-1 (SkyConnect)">Out of production, still receives software updates&lt;/td>
&lt;td data-label="Sonoff ZBDongle-P">Listed&lt;/td>
&lt;td data-label="SMLIGHT SLZB-06">Listed&lt;/td>
&lt;td data-label="Connect ZWA-2">Listed&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Specifications and prices are from the vendor pages cited in the sources below; the Bluetooth cells for the two CC2652P sticks, the availability row and the parentheticals are my reading of those pages, not vendor statements. I measured none of it.&lt;/p>
&lt;p>&lt;strong>Where to buy.&lt;/strong> Newegg&amp;rsquo;s product catalogue on November 17, 2026 had no Connect ZBT-2 listing, so the ZBT-2 gets no paired retailer links here; Home Assistant&amp;rsquo;s &lt;a href="https://www.home-assistant.io/connect/zbt-2/" rel="noopener">product page&lt;/a> lists its sellers by region. ITead sells the ZBDongle-P directly at $19.90. Newegg&amp;rsquo;s SLZB-06 rows that day were third-party listings at $149.98 under a reseller&amp;rsquo;s brand, and its Sonoff Dongle Plus rows did not name the ZBDongle-P, so neither gets a buy link either. If you need more than one radio at once, SMLIGHT&amp;rsquo;s overview describes its SLZB-MR models as running Zigbee and Thread at the same time on two separate chips.&lt;/p>
&lt;h2 id="what-i-would-run-and-why">What I would run, and why&lt;/h2>
&lt;p>I have no ZBT-2 on the bench, and no Zigbee stick is part of the hardware this site documents as mine. Read this as a position. Not a report.&lt;/p>
&lt;p>For a first Zigbee network on a Home Assistant Green, Yellow, or a mini PC on a shelf, I would buy the ZBT-2 and run it on ZHA with the cable, antenna vertical, away from any USB 3 port. It is the stick Home Assistant&amp;rsquo;s own docs list first, it is the one the migration guides are written for, and if Matter-over-Thread devices arrive later it can become the border router while a $20 Sonoff takes over Zigbee.&lt;/p>
&lt;p>For a Home Assistant VM on a Proxmox box in a closet, I would buy the SLZB-06 and put it on a PoE port in the middle of the house, because the radio&amp;rsquo;s location matters more than the radio&amp;rsquo;s chip and the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/">Proxmox setup&lt;/a> already has enough USB passthrough in it. The ZBT-2 on a 1.5 m cable does not reach the middle of a house from a rack.&lt;/p>
&lt;p>For a house that already runs a Sonoff dongle without dropouts, I would change nothing. The owners in the r/homeassistant thread who report the ZBT-1 running &amp;ldquo;a handful of Zigbee devices (~30 or so?)&amp;rdquo; with no problems are describing the normal case, and Home Assistant says the ZBT-1 keeps getting updates. Spend the $49 when you have a reason: Thread, a dying stick, or a coordinator too far from the devices it serves.&lt;/p>
&lt;h2 id="the-bottom-line">The bottom line&lt;/h2>
&lt;p>The ZBT-2 is the right default Zigbee radio for a Home Assistant machine the stick can sit next to, and the right Thread border router for the same machine. Not both at the same time. Decide the protocol first, then the room the radio lives in, and the choice between the ZBT-2, a Sonoff and an SLZB-06 makes itself. Z-Wave is a different stick. A working ZBT-1 is not a reason to buy anything. Once the stick is running, the &lt;a href="https://techfuelhq.com/homelab/home-assistant-door-sensor-2026/">door sensor guide&lt;/a> covers which contact sensors fit a Zigbee or Thread setup.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://support.nabucasa.com/hc/en-us/articles/31313065259421-About-Home-Assistant-Connect-ZBT-2" rel="noopener">Nabu Casa Support, About Home Assistant Connect ZBT-2 (one protocol at a time; no Bluetooth or Z-Wave; MG24 and ESP32-S3; ZHA single instance)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.nabucasa.com/hc/en-us/articles/31368700350109-Home-Assistant-Connect-ZBT-2-status-light-LEDs" rel="noopener">Nabu Casa Support, Home Assistant Connect ZBT-2 status light (LEDs)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.nabucasa.com/hc/en-us/sections/29400567268253-Getting-started-with-Zigbee" rel="noopener">Nabu Casa Support, Getting started with Zigbee (the migration guides)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/connect/zbt-2/" rel="noopener">Home Assistant, Connect ZBT-2 product page (cable, antenna, MSRP, supported integrations)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/blog/2025/11/19/home-assistant-connect-zbt-2/" rel="noopener">Home Assistant blog, The best gets better - Home Assistant Connect ZBT-2, November 19, 2025 (MG21 to MG24, 115,200 to 460,800 baud, antenna, ZBT-1 production ended)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/connectzbt1/" rel="noopener">Home Assistant, Connect ZBT-1 product page (no longer in production, still updated; formerly SkyConnect)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/connect/zwa-2/" rel="noopener">Home Assistant, Connect ZWA-2 product page (ZG23, Z-Wave plus Long Range, $69 / 59€)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/integrations/zha/" rel="noopener">Home Assistant, Zigbee Home Automation integration documentation (USB 3.0 interference and extension-cable guidance; recommended radios)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus/" rel="noopener">ITead, SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P (CC2652P, +20 dBm, $19.90)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://smlight.tech/manual/slzb-06/" rel="noopener">SMLIGHT, SLZB-06 series manual (CC2652P, Ethernet, Wi-Fi, USB, PoE)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://smlight.tech/manual/slzb-06/guide/slzb-models-overview/" rel="noopener">SMLIGHT, SLZB models overview (chip per SLZB-06 model, Thread and Bluetooth support, SLZB-MR dual radio)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.reddit.com/r/homeassistant/comments/1phsj5c/is_the_connect_zbt2_the_way_to_go_for_a_zigbee/" rel="noopener">Reddit r/homeassistant, Is the Connect ZBT-2 the way to go for a Zigbee bridge? (owner reports)&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>How to Tell If Your AIO Pump Is Working (2026)</title><link>https://techfuelhq.com/articles/how-to-tell-if-aio-pump-is-working-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/how-to-tell-if-aio-pump-is-working-2026/</guid><atom:updated>2026-11-18T06:30:00Z</atom:updated><description>&lt;p>A failed AIO pump is the quietest hardware failure in a PC. The fans keep spinning, the lighting stays on, nothing beeps, and the machine boots normally. The only thing that changes is that the processor starts running hot, and by the time most people notice, they have already blamed the paste, the case, or the weather.&lt;/p>
&lt;p>The good news is that the pump is not a mystery component. It reports its own speed, and that number is either inside the manufacturer&amp;rsquo;s range or it is not. Everything else on this page is about making sure you are reading the right number.&lt;/p>
&lt;h2 id="the-pump-tach-is-the-whole-diagnosis">The pump tach is the whole diagnosis&lt;/h2>
&lt;p>Every pump on a modern AIO has a tachometer output on its control connector. That is the third pin on a standard fan-type header, and it is what the motherboard reads to show you an RPM figure. If the pump is turning, the number is non-zero. If the number is zero or absent on the correct header, the pump is not turning or not reporting.&lt;/p>
&lt;p>Know what the range should be before you judge the reading:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Cooler&lt;/th>
&lt;th scope="col">Pump speed specification&lt;/th>
&lt;th scope="col">Connector&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Cooler">ARCTIC Liquid Freezer III 360&lt;/td>
&lt;td data-label="Pump speed specification">800–2800 rpm, PWM controlled, 12 V DC, 0.35 A&lt;/td>
&lt;td data-label="Connector">4-pin PWM&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Cooler">NZXT Kraken Plus (2026)&lt;/td>
&lt;td data-label="Pump speed specification">1,200–3,200 rpm ±300, Asetek Gen 9&lt;/td>
&lt;td data-label="Connector">4-pin PWM&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Cooler">NZXT Kraken Core (2025)&lt;/td>
&lt;td data-label="Pump speed specification">3,100 rpm ±310&lt;/td>
&lt;td data-label="Connector">3-pin DC fan header&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Those figures come straight from the manufacturers: Arctic&amp;rsquo;s &lt;a href="https://www.arctic.de/media/16/63/19/1708429821/Spec_Sheet_Liquid_Freezer_III_360_Black_EN.pdf" rel="noopener">Liquid Freezer III 360 specification sheet&lt;/a>, NZXT&amp;rsquo;s &lt;a href="https://support.nzxt.com/hc/en-us/articles/58318166453659-What-are-the-specs-of-the-pump-in-the-Kraken-Plus-2026" rel="noopener">Kraken Plus pump article&lt;/a>, and NZXT&amp;rsquo;s &lt;a href="https://support.nzxt.com/hc/en-us/articles/41097983638299-Kraken-Core-2025-Specs" rel="noopener">Kraken Core (2025) spec sheet&lt;/a>. Read yours before you test, because &amp;ldquo;500 rpm&amp;rdquo; means something different on a pump rated at 3,100 rpm than on one with an 800 rpm floor.&lt;/p>
&lt;p>One Arctic detail trips people up. Arctic&amp;rsquo;s spec sheet shows the Liquid Freezer III&amp;rsquo;s single all-in-one connector carrying the radiator fan tachometer on its signal pin, and Arctic&amp;rsquo;s product page says that connection outputs the speed of the radiator fans. To read the pump itself, use the pump connector on the splitter cable. The &lt;a href="https://techfuelhq.com/reviews/arctic-liquid-freezer-iii-360-review-2026/">Liquid Freezer III 360 review&lt;/a> covers the rest of that cooler.&lt;/p>
&lt;p>A pump reading in range does not prove the loop is healthy, and a pump reading zero does not always mean the pump is dead. That is why the next two sections exist.&lt;/p>
&lt;h2 id="read-the-header-before-you-touch-the-tubes">Read the header before you touch the tubes&lt;/h2>
&lt;p>People squeeze the tubes first. It feels like evidence. It is not.&lt;/p>
&lt;p>The supply tube carries hot coolant away from the block, and the return tube warms partly by conduction along the fitting and the rubber even when the water inside is barely moving. A warm tube tells you the block is hot. It does not tell you the impeller is turning.&lt;/p>
&lt;p>Read the header instead. On an ASUS AM5 board the fan settings live in Advanced Mode (F7) under Monitor, then Q-Fan Configuration, per ASUS&amp;rsquo;s &lt;a href="https://dlcdnets.asus.com/pub/ASUS/mb/Socket%20AM5/ROG_STRIX_X670E-E_GAMING_WIFI/E20544_ROG_STRIX_X670E_Series_BIOS_manual_EM_WEB.pdf" rel="noopener">ROG STRIX X670E Series BIOS manual&lt;/a>. The same Monitor menu lists each header&amp;rsquo;s speed in RPM, including AIO PUMP Speed, which is exactly the reading you need. ASUS notes the menu varies by board, so check your own manual for the names.&lt;/p>
&lt;p>Which header should the pump be on? If the board has a dedicated pump header, that is the one. ASUS&amp;rsquo;s manual for the &lt;a href="https://dlcdnets.asus.com/pub/ASUS/mb/Socket%20AM5/ROG%20STRIX%20B650-A%20GAMING%20WIFI/E20268_ROG_STRIX_B650-A_GAMING_WIFI_UM_WEB.pdf" rel="noopener">ROG STRIX B650-A Gaming WiFi&lt;/a> says to connect a water-cooling kit&amp;rsquo;s pump connector to the AIO_PUMP header, and its header table shows that AIO_PUMP defaults to full speed while CPU_FAN and CPU_OPT are Q-Fan controlled. NZXT&amp;rsquo;s guidance for the Kraken Plus points the same direction: use CPU_FAN or AIO_PUMP, and not a CAM-powered controller.&lt;/p>
&lt;p>Two settings readings look like a dead pump. ASUS&amp;rsquo;s manual says a header with nothing connected shows N/A, and a speed set to Ignore in the Monitor menu is hidden rather than displayed. Check which one you are looking at before you blame the hardware; it costs nothing to rule out.&lt;/p>
&lt;h2 id="match-the-header-mode-to-the-connector">Match the header mode to the connector&lt;/h2>
&lt;p>This is the step that catches the most false alarms, and it is also the step most guides skip.&lt;/p>
&lt;p>Fan and pump headers can run in PWM mode or DC (voltage) mode. ASUS&amp;rsquo;s AM5 BIOS manual gives the AIO Pump Q-Fan Control setting three choices: Auto Detect, DC Mode for a 3-pin fan or pump, and PWM Mode for a 4-pin one. Pick the wrong one and the header either cannot modulate the device or cannot read it properly.&lt;/p>
&lt;p>That matters because AIO pumps are not uniform. The Arctic Liquid Freezer III and the NZXT Kraken Plus use 4-pin PWM connectors. The NZXT Kraken Core (2025) uses a 3-pin DC fan header. A 3-pin pump on a header configured for PWM has no control line to talk to, so check the mode against the connector before you decide anything is broken.&lt;/p>
&lt;p>While you are in that page, look at the low-speed warning setting. The same ASUS manual lists AIO Pump Speed Low Limit options of Ignore or 200 to 600 RPM and says a warning appears when the pump reaches the limit. If your pump can legitimately idle below the limit you pick, the warning will fire on a healthy cooler. If your pump should never drop that low, the warning is a useful alarm you should leave on.&lt;/p>
&lt;h2 id="coolers-that-report-through-usb-and-their-own-app">Coolers that report through USB and their own app&lt;/h2>
&lt;p>Some AIOs split the job across several leads. NZXT&amp;rsquo;s &lt;a href="https://support.nzxt.com/hc/en-us/articles/43715888947611-Is-my-Kraken-cooler-failing" rel="noopener">Kraken failure guide&lt;/a> lists three to check on the Kraken Elite, Kraken (2023), Kraken Z and Kraken X: SATA power from the power supply, a 3-pin Pump Sense lead to the motherboard&amp;rsquo;s CPU_FAN header, and a USB 9-pin lead to the motherboard. The Pump Sense lead is what reports RPM, so the BIOS reading still works on these coolers even though NZXT&amp;rsquo;s CAM software controls them. On the Kraken Core, Kraken 120 and Kraken M22, NZXT says the 3-pin pump lead goes to AIO_PUMP, CPU_OPT or a similar header.&lt;/p>
&lt;p>If that header shows 0 RPM or N/A, NZXT says to check those connections and set the header to 100% fixed speed in the BIOS. If the reading is still 0 or N/A, NZXT treats it as a possible failed or seized pump. For a noisy pump, NZXT says to keep the pump cap below the highest point of the radiator so air does not collect in it.&lt;/p>
&lt;p>Other brands that run their pumps through a USB controller and their own software have their own wiring; follow the cooler manual for which lead carries the pump&amp;rsquo;s speed.&lt;/p>
&lt;h2 id="is-it-the-pump-the-mount-or-the-firmware">Is it the pump, the mount, or the firmware?&lt;/h2>
&lt;p>Three different faults produce the same headline symptom: a hot CPU. Separate them with the table below.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you observe&lt;/th>
&lt;th scope="col">Most likely cause&lt;/th>
&lt;th scope="col">First check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM zero, CPU hot within seconds of load&lt;/td>
&lt;td data-label="Most likely cause">Pump not powered or failed&lt;/td>
&lt;td data-label="First check">Pump power lead and header assignment&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM in range, CPU still hot&lt;/td>
&lt;td data-label="Most likely cause">Mounting, contact, or airflow&lt;/td>
&lt;td data-label="First check">Cold plate contact and radiator airflow&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM correct but drops to zero under load&lt;/td>
&lt;td data-label="Most likely cause">Header curve or power delivery&lt;/td>
&lt;td data-label="First check">Header mode, profile, and pump lead seating&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM normal, temps changed after a BIOS flash&lt;/td>
&lt;td data-label="Most likely cause">Firmware reset header settings&lt;/td>
&lt;td data-label="First check">Monitor &amp;gt; Q-Fan Configuration&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Gurgling or intermittent RPM after moving the case&lt;/td>
&lt;td data-label="Most likely cause">Air trapped at the impeller&lt;/td>
&lt;td data-label="First check">Cooler manual&amp;rsquo;s orientation guidance&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The first row is the one that ends in a warranty claim. The second row is the one that ends in a remount or repaste. If the pump is turning and the radiator is getting hot, the loop is moving heat; the problem is that heat is not getting into the loop efficiently, or not leaving the radiator. NZXT&amp;rsquo;s guide suggests checking contact by removing the pump and seeing whether the paste spread across the CPU, and the &lt;a href="https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/">PTM7950 vs thermal paste comparison&lt;/a> covers the material if you redo it.&lt;/p>
&lt;p>The fourth row is worth dwelling on. A BIOS update or a CMOS clear can return fan and pump headers to defaults. A header you had set to full speed can come back on a quiet profile, and the pump slows without any hardware change. If your temperatures changed on the same day you flashed firmware, check the fan configuration page before you order parts; the &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update guide&lt;/a> covers what a flash resets.&lt;/p>
&lt;h2 id="ordered-checks-that-survive-a-reboot">Ordered checks that survive a reboot&lt;/h2>
&lt;p>Work top to bottom. The first four cost nothing and take minutes.&lt;/p>
&lt;h3 id="1-boot-into-the-bios-and-open-the-fan-page">1. Boot into the BIOS and open the fan page&lt;/h3>
&lt;p>Advanced Mode (F7), then Monitor, then Q-Fan Configuration on ASUS boards. Write down the pump header&amp;rsquo;s RPM and mode. A number inside the pump&amp;rsquo;s rated range rules out a dead pump straight away.&lt;/p>
&lt;h3 id="2-confirm-the-header-assignment">2. Confirm the header assignment&lt;/h3>
&lt;p>Pump on AIO_PUMP if the board has one, otherwise CPU_FAN; on a USB-linked Kraken, the Pump Sense lead on CPU_FAN. Check that the reading is not set to Ignore. This rules out reading the wrong header.&lt;/p>
&lt;h3 id="3-match-the-mode-to-the-connector">3. Match the mode to the connector&lt;/h3>
&lt;p>PWM for 4-pin pumps, DC for 3-pin pumps, or Auto Detect where the board offers it. This rules out a header that cannot drive or read the pump.&lt;/p>
&lt;h3 id="4-set-the-pump-header-to-full-speed-and-re-read">4. Set the pump header to full speed and re-read&lt;/h3>
&lt;p>On the B650-A the AIO_PUMP header already defaults to full speed, and NZXT asks for 100% fixed speed on its Kraken headers, so a pump that still reads zero or N/A after this has a power or hardware problem. This rules out a fan curve that slowed the pump.&lt;/p>
&lt;h3 id="5-check-the-pumps-own-power-lead">5. Check the pump&amp;rsquo;s own power lead&lt;/h3>
&lt;p>Some coolers take power from a separate connector or SATA lead in addition to the tach header; NZXT&amp;rsquo;s Kraken Elite, Kraken (2023), Kraken Z and Kraken X use SATA power plus a USB 9-pin lead. Seat both ends of each. This rules out a pump that is fine but unpowered.&lt;/p>
&lt;h3 id="6-watch-the-temperature-response">6. Watch the temperature response&lt;/h3>
&lt;p>If the pump is genuinely dead, the CPU climbs toward its limit quickly under light load. AMD lists 95 °C as the maximum operating temperature for the &lt;a href="https://www.amd.com/en/products/processors/desktops/ryzen/9000-series/amd-ryzen-7-9800x3d.html" rel="noopener">Ryzen 7 9800X3D&lt;/a> and 89 °C for the &lt;a href="https://www.amd.com/en/products/processors/desktops/ryzen/7000-series/amd-ryzen-7-7800x3d.html" rel="noopener">Ryzen 7 7800X3D&lt;/a>; a chip pinned there in a browser is not a fan-curve problem. This separates a pump that reports oddly from one that isn&amp;rsquo;t moving heat.&lt;/p>
&lt;h3 id="7-confirm-the-radiator-fans-separately">7. Confirm the radiator fans separately&lt;/h3>
&lt;p>They can run while the pump is still. On the Arctic unit the split cable lets you control pump, VRM fan, and radiator fans independently, which makes this easy to check and easy to misread. This rules out mistaking healthy fans for a healthy pump.&lt;/p>
&lt;h3 id="8-save-your-readings">8. Save your readings&lt;/h3>
&lt;p>A written record of header, mode, RPM, and temperature survives a reboot. Your memory of a number you saw once does not.&lt;/p>
&lt;p>Two things survive a reboot and one does not. A change you make in the BIOS fan page persists. A record you saved to a file persists. A Windows-only fan utility curve may not survive a clean boot or a driver update, which is why I prefer to settle the pump question in firmware before involving software.&lt;/p>
&lt;p>If you want the temperature side in more depth, the &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/">CPU temperature check guide&lt;/a> covers the tools and the &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe CPU temperature guide&lt;/a> covers the ceilings by model. The &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling guide&lt;/a> explains how to confirm the chip is actually being slowed rather than merely warm. If the machine also stops producing a picture, that is a separate fault: start with &lt;a href="https://techfuelhq.com/articles/pc-wont-post-2026/">PC won&amp;rsquo;t POST&lt;/a> or &lt;a href="https://techfuelhq.com/articles/monitor-no-signal-2026/">monitor says no signal&lt;/a>. The &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> covers the cooling side from the top.&lt;/p>
&lt;h2 id="when-to-stop">When to stop&lt;/h2>
&lt;p>Stop troubleshooting and use the warranty when the evidence is unambiguous.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Zero pump RPM with the lead seated and the header configured correctly.&lt;/strong> That is a failed pump, not a settings problem.&lt;/li>
&lt;li>&lt;strong>Pump RPM outside its rated range and a CPU that still overheats.&lt;/strong> The impeller may be turning without moving coolant. Either way, the unit is not doing its job.&lt;/li>
&lt;li>&lt;strong>Repeated air-lock symptoms after you have followed the cooler manual&amp;rsquo;s orientation and tilt guidance.&lt;/strong> Do not keep power-cycling a loop that will not prime.&lt;/li>
&lt;li>&lt;strong>Any leak, smell, or audible grinding from the pump housing.&lt;/strong> Stop using the machine. Do not open the pump.&lt;/li>
&lt;li>&lt;strong>A pump that works and a CPU that still overheats.&lt;/strong> That is a mounting or airflow problem, and replacing the cooler without fixing contact will reproduce the symptom. Read the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> before you buy anything.&lt;/li>
&lt;/ul>
&lt;p>If the pump has failed and you are choosing a replacement, the &lt;a href="https://techfuelhq.com/articles/air-cooler-vs-aio-2026/">air cooler vs AIO comparison&lt;/a> covers whether to replace it with another AIO or a tower air cooler.&lt;/p>
&lt;p>If you are still uncertain after the checks above, the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> lets you log each step and the reading beside it, so the next person to look at the machine starts from evidence instead of a description.&lt;/p></description></item><item><title>Dynamic DNS for a Homelab: CGNAT, Cloudflare, and IPv6</title><link>https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/</link><pubDate>Sat, 14 Nov 2026 10:35:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/</guid><atom:updated>2026-11-18T06:25:00Z</atom:updated><description>&lt;p>Dynamic DNS only solves one narrow problem: rewriting an &lt;code>A&lt;/code> or &lt;code>AAAA&lt;/code> record after your ISP hands your router a new address, which helps only when unsolicited packets from the outside world can reach your WAN interface in the first place. It never punches through carrier-grade NAT. If an upstream ISP translator swallows inbound packets before they reach your home router, your updater container will happily log &lt;code>SUCCESS&lt;/code> every five minutes while every outside connection times out in silence.&lt;/p>
&lt;p>Whenever I wire remote access on a residential circuit, DNS comes second. Proving the WAN address is routable comes first.&lt;/p>
&lt;h2 id="step-0-run-the-cgnat-and-ipv6-check-before-touching-dns">Step 0: Run the CGNAT and IPv6 check before touching DNS&lt;/h2>
&lt;p>Log into your router or firewall status screen and read the IPv4 address assigned to its WAN interface. Do not rely on an external &amp;ldquo;what is my IP&amp;rdquo; site yet. Read the interface itself.&lt;/p>
&lt;p>Now fetch what the public internet sees from a shell on the same LAN (&lt;code>curl -4 https://1.1.1.1/cdn-cgi/trace&lt;/code>) and compare the &lt;code>ip=&lt;/code> line against your router&amp;rsquo;s WAN status page. Three distinct outcomes show up on residential lines:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Router WAN IPv4&lt;/th>
&lt;th scope="col">Matches external IP check?&lt;/th>
&lt;th scope="col">What is happening&lt;/th>
&lt;th scope="col">Will IPv4 DDNS + port forward work?&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Router WAN IPv4">Public range (e.g., &lt;code>71.x.x.x&lt;/code>)&lt;/td>
&lt;td data-label="Matches external IP check?">Yes&lt;/td>
&lt;td data-label="What is happening">Direct routable dynamic IPv4&lt;/td>
&lt;td data-label="Will IPv4 DDNS &amp;#43; port forward work?">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Router WAN IPv4">&lt;code>100.64.0.0&lt;/code> – &lt;code>100.127.255.255&lt;/code>&lt;/td>
&lt;td data-label="Matches external IP check?">No&lt;/td>
&lt;td data-label="What is happening">ISP CGNAT (&lt;code>100.64.0.0/10&lt;/code>)&lt;/td>
&lt;td data-label="Will IPv4 DDNS &amp;#43; port forward work?">&lt;strong>No&lt;/strong> (use IPv6, overlay VPN, or tunnel)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Router WAN IPv4">&lt;code>192.168.x.x&lt;/code>, &lt;code>10.x.x.x&lt;/code>, &lt;code>172.16-31.x.x&lt;/code>&lt;/td>
&lt;td data-label="Matches external IP check?">No&lt;/td>
&lt;td data-label="What is happening">Double NAT behind ISP combo gateway&lt;/td>
&lt;td data-label="Will IPv4 DDNS &amp;#43; port forward work?">Only after bridging the ISP gateway&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>If your WAN address lands anywhere between &lt;code>100.64.0.1&lt;/code> and &lt;code>100.127.255.254&lt;/code>, stop before installing any IPv4 updater. &lt;a href="https://www.rfc-editor.org/rfc/rfc6598.html" rel="noopener">IETF RFC 6598&lt;/a> allocates &lt;code>100.64.0.0/10&lt;/code> as Shared Address Space specifically so service providers can number the link between a carrier-grade NAT translator and customer-premises routers. Dozens of households sit behind the same public IPv4 address. None of the inbound ports on that public address belong to your router, which is also the first gate in our &lt;a href="https://techfuelhq.com/networking/port-forwarding-2026/">port forwarding troubleshooting checklist&lt;/a>.&lt;/p>
&lt;p>Check IPv6 next before giving up on direct ingress. Many fiber, cable, and 5G home gateways that put IPv4 behind &lt;code>100.64.0.0/10&lt;/code> still delegate a globally routable &lt;code>/56&lt;/code> or &lt;code>/60&lt;/code> IPv6 prefix (&lt;code>2000::/3&lt;/code>).&lt;/p>
&lt;p>With IPv6, NAT disappears. Your Linux host or reverse proxy holds its own global &lt;code>2xxx:...&lt;/code> address, and your firewall opens a targeted IPv6 pinhole to that host rather than translating a WAN port. One detail trips people up here: modern operating systems rotate RFC 8981 privacy extensions (&lt;code>Temporary IPv6 Address&lt;/code>) daily for outbound browsing. Always run your &lt;code>AAAA&lt;/code> DDNS updater on the target server itself—or bind its stable SLAAC/DHCPv6 interface identifier—so the published &lt;code>AAAA&lt;/code> record matches the exact host address your firewall allows.&lt;/p>
&lt;p>A pinhole lets anyone on the internet reach that one port on that host, so open only the port the service needs; deleting the firewall rule closes it again.&lt;/p>
&lt;h2 id="create-a-single-zone-cloudflare-api-token">Create a single-zone Cloudflare API token&lt;/h2>
&lt;p>Years ago, scripts authenticated to Cloudflare with an account email and the Global API Key. Retire that habit. One leaked Global API Key exposes every domain, Worker, tunnel, and billing setting inside your account at once.&lt;/p>
&lt;p>Cloudflare&amp;rsquo;s &lt;a href="https://developers.cloudflare.com/fundamentals/api/get-started/create-token/" rel="noopener">API token workflow&lt;/a> and &lt;a href="https://developers.cloudflare.com/fundamentals/api/reference/template/" rel="noopener">token template reference&lt;/a> ship a purpose-built &lt;strong>Edit zone DNS&lt;/strong> template that restricts automated updaters to the single domain they actually need to touch:&lt;/p>
&lt;ol>
&lt;li>Open &lt;strong>My Profile → API Tokens → Create Token&lt;/strong> in the Cloudflare dashboard and choose &lt;strong>Edit zone DNS&lt;/strong>.&lt;/li>
&lt;li>Set &lt;strong>Permissions&lt;/strong> to &lt;strong>Zone → DNS → Edit&lt;/strong>. Leave account-level permissions empty.&lt;/li>
&lt;li>Under &lt;strong>Zone Resources&lt;/strong>, select &lt;strong>Include → Specific zone → &lt;code>example.com&lt;/code>&lt;/strong> so a leaked &lt;code>.env&lt;/code> file on one homelab host cannot touch any other domain you own.&lt;/li>
&lt;li>Create the initial &lt;code>A&lt;/code> record (such as &lt;code>vpn.example.com&lt;/code> pointing to &lt;code>192.0.2.1&lt;/code>) in the Cloudflare DNS tab first if your chosen client expects an existing record to update, and leave &lt;strong>Proxy status&lt;/strong> set to &lt;strong>DNS only&lt;/strong> (grey cloud) for non-HTTP protocols or direct ACME validation.&lt;/li>
&lt;/ol>
&lt;p>That single-zone token is what favonia/cloudflare-ddns and OPNsense&amp;rsquo;s native client expect. ddclient asks for more; Option 3 has the details.&lt;/p>
&lt;p>Test the token once from a terminal before burying it inside a daemon config:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>curl -sS &lt;span style="color:#e6db74">&amp;#34;https://api.cloudflare.com/client/v4/user/tokens/verify&amp;#34;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -H &lt;span style="color:#e6db74">&amp;#34;Authorization: Bearer YOUR_SCOPED_CF_API_TOKEN&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>When the JSON reply prints &lt;code>&amp;quot;status&amp;quot;:&amp;quot;active&amp;quot;&lt;/code>, the credential works.&lt;/p>
&lt;h2 id="three-reliable-ways-to-update-cloudflare-dns">Three reliable ways to update Cloudflare DNS&lt;/h2>
&lt;p>Cloudflare&amp;rsquo;s &lt;a href="https://developers.cloudflare.com/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses/" rel="noopener">dynamic IP documentation&lt;/a> points to API clients, &lt;code>ddclient&lt;/code>, and tunnels depending on where your edge lives. Pick the updater that sits closest to the interface you actually want published.&lt;/p>
&lt;h3 id="option-1-stateless-docker-container-favoniacloudflare-ddns">Option 1: Stateless Docker container (&lt;code>favonia/cloudflare-ddns&lt;/code>)&lt;/h3>
&lt;p>If your homelab runs Docker on Debian, Ubuntu, or a Proxmox VM and you want zero config files on disk, &lt;a href="https://github.com/favonia/cloudflare-ddns" rel="noopener">favonia/cloudflare-ddns&lt;/a> is a small, single-purpose updater. Its README suggests the &lt;strong>Edit zone DNS&lt;/strong> token template, reads the token from &lt;code>CLOUDFLARE_API_TOKEN&lt;/code> or a Docker secret file, and manages both &lt;code>A&lt;/code> and &lt;code>AAAA&lt;/code> records. This compose file follows the README&amp;rsquo;s example (v1.18.0):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">cloudflare-ddns&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">favonia/cloudflare-ddns:1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">cloudflare-ddns&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">network_mode&lt;/span>: &lt;span style="color:#ae81ff">host&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">user&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;1000:1000&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">read_only&lt;/span>: &lt;span style="color:#66d9ef">true&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">cap_drop&lt;/span>: [&lt;span style="color:#ae81ff">all]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">security_opt&lt;/span>: [&lt;span style="color:#66d9ef">no&lt;/span>-&lt;span style="color:#ae81ff">new-privileges:true]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">CLOUDFLARE_API_TOKEN=YOUR_SCOPED_CF_API_TOKEN&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">DOMAINS=vpn.example.com,home.example.com&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">PROXIED=false&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">TZ=America/Chicago&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;code>1&lt;/code> tag tracks the latest 1.x release; the README advises against &lt;code>latest&lt;/code> in production because it can pull in a future major version. The older &lt;code>CF_API_TOKEN&lt;/code> name still works but is marked for deprecation in version 2.0.0.&lt;/p>
&lt;p>As written, the container publishes both an &lt;code>A&lt;/code> and an &lt;code>AAAA&lt;/code> record, because &lt;code>IP4_PROVIDER&lt;/code> and &lt;code>IP6_PROVIDER&lt;/code> both default to &lt;code>cloudflare.trace&lt;/code>. &lt;code>network_mode: host&lt;/code> is what lets it see the host&amp;rsquo;s global IPv6 address; on a default Docker bridge without IPv6, it cannot. For IPv4 only, add &lt;code>- IP6_PROVIDER=none&lt;/code> under &lt;code>environment&lt;/code>; behind CGNAT with a routed IPv6 prefix, add &lt;code>- IP4_PROVIDER=none&lt;/code> instead so it stops managing the &lt;code>A&lt;/code> record; it leaves an existing &lt;code>A&lt;/code> record in place, so delete that one by hand.&lt;/p>
&lt;h3 id="option-2-opnsense-at-the-router-edge-os-ddclient">Option 2: OPNsense at the router edge (&lt;code>os-ddclient&lt;/code>)&lt;/h3>
&lt;p>When you run an &lt;a href="https://techfuelhq.com/tutorials/opnsense-mini-pc-setup-2026/">OPNsense mini-PC firewall&lt;/a> at the perimeter, IPv4 DDNS belongs on the router itself because OPNsense already owns the WAN interface.&lt;/p>
&lt;p>According to the &lt;a href="https://docs.opnsense.org/manual/dynamic_dns.html" rel="noopener">OPNsense Dynamic DNS manual&lt;/a>, install &lt;code>os-ddclient&lt;/code> under &lt;strong>System → Firmware → Plugins&lt;/strong>, then open &lt;strong>Services → Dynamic DNS → Settings&lt;/strong>. In &lt;strong>General Settings&lt;/strong>, pick &lt;code>native&lt;/code> as the backend; OPNsense wrote it in Python as ddclient development winds down, and advises trying it when your service is supported. Add an account with these fields:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Service:&lt;/strong> &lt;code>Cloudflare&lt;/code>&lt;/li>
&lt;li>&lt;strong>Username:&lt;/strong> &lt;code>token&lt;/code> (the manual&amp;rsquo;s value when you authenticate with an API token)&lt;/li>
&lt;li>&lt;strong>Password:&lt;/strong> your &lt;code>Zone:DNS:Edit&lt;/code> API token, scoped to the specific zone&lt;/li>
&lt;li>&lt;strong>Zone:&lt;/strong> &lt;code>example.com&lt;/code> (the zone name, not its zone ID)&lt;/li>
&lt;li>&lt;strong>Hostname(s):&lt;/strong> &lt;code>vpn.example.com&lt;/code>&lt;/li>
&lt;li>&lt;strong>Check ip method:&lt;/strong> &lt;code>Interface&lt;/code>, with the interface set to &lt;code>WAN&lt;/code> (when your WAN holds a real public IPv4)&lt;/li>
&lt;/ul>
&lt;p>Reading the interface directly avoids hitting external IP echo servers every five minutes and prevents a LAN VPN policy-routing rule from accidentally publishing your commercial VPN exit IP as your home address. For an &lt;code>AAAA&lt;/code> record too, the manual&amp;rsquo;s pattern is a second account with an IPv6 check method.&lt;/p>
&lt;h3 id="option-3-bare-metal-linux-daemon-ddclient">Option 3: Bare-metal Linux daemon (&lt;code>ddclient&lt;/code>)&lt;/h3>
&lt;p>On a minimal Debian or Proxmox host where you prefer distro packages over an extra container, &lt;a href="https://github.com/ddclient/ddclient" rel="noopener">ddclient&lt;/a> has supported Cloudflare API tokens since version 3.10.0; the current release is 4.0.0 (January 19, 2025). Check your version first, because two things changed along the way:&lt;/p>
&lt;ul>
&lt;li>The &lt;code>usev4&lt;/code> and &lt;code>webv4&lt;/code> options in the example below arrived in 3.11.0. Ubuntu 24.04&amp;rsquo;s package is ddclient 3.10.0, which only has the older &lt;code>use&lt;/code> option.&lt;/li>
&lt;li>ddclient&amp;rsquo;s README lists a 3.10.0 bug that spams Cloudflare with updates when &lt;code>use&lt;/code> is set, fixed in 3.11.2. On 3.10.0, install 3.11.2 or newer before pointing it at Cloudflare, or use Option 1.&lt;/li>
&lt;/ul>
&lt;p>ddclient&amp;rsquo;s sample configuration (3.10.0 through 4.0.0) says an API token needs both &lt;strong>Zone - DNS - Edit&lt;/strong> and &lt;strong>Zone - Zone - Read&lt;/strong>, with Zone Resources set to &lt;strong>All zones&lt;/strong>, and &lt;code>login=token&lt;/code> in the config. That is broader than the single-zone token above, so give ddclient its own token. Edit &lt;code>/etc/ddclient.conf&lt;/code> with &lt;code>0600&lt;/code> root-only permissions:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-ini" data-lang="ini">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">daemon&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">300&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">syslog&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">yes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">ssl&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">yes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">usev4&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">webv4, webv4=https://1.1.1.1/cdn-cgi/trace, webv4-skip=&amp;#39;ip=&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">protocol&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">cloudflare, \&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">zone&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">example.com, \&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">ttl&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">1, \&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">login&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">token, \&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">password&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;YOUR_DDCLIENT_CF_API_TOKEN&amp;#39; \&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">vpn.example.com&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>daemon=300&lt;/code> tells ddclient to check every 300 seconds. In Cloudflare&amp;rsquo;s API, &lt;code>ttl=1&lt;/code> means &amp;ldquo;Automatic&amp;rdquo; (which Cloudflare serves as &lt;code>300&lt;/code> seconds on unproxied records), or you can pass an explicit integer from &lt;code>60&lt;/code> upward. Run &lt;code>sudo ddclient -daemon=0 -debug -verbose -noquiet&lt;/code> once during setup to watch the exact HTTPS request and verify &lt;code>&amp;quot;success&amp;quot;:true&lt;/code> in real time.&lt;/p>
&lt;h2 id="cloudflare-ddns-vs-duckdns">Cloudflare DDNS vs DuckDNS&lt;/h2>
&lt;p>Not every homelab needs a custom domain on day one. &lt;a href="https://www.duckdns.org/spec.jsp" rel="noopener">DuckDNS&lt;/a> remains popular because its entire update protocol is a single HTTPS GET request (&lt;code>https://www.duckdns.org/update?domains=yourname&amp;amp;token=YOUR_UUID&amp;amp;ip=&lt;/code>) that runs from a one-line &lt;code>cron&lt;/code> job with &lt;code>curl&lt;/code> on almost any busybox router.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Factor&lt;/th>
&lt;th scope="col">Cloudflare DDNS (own domain)&lt;/th>
&lt;th scope="col">DuckDNS (&lt;code>*.duckdns.org&lt;/code>)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Factor">Annual domain cost&lt;/td>
&lt;td data-label="Cloudflare DDNS (own domain)">Standard TLD renewal (~$10–$15/yr)&lt;/td>
&lt;td data-label="DuckDNS (*.duckdns.org)">Free subdomain&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Auth isolation&lt;/td>
&lt;td data-label="Cloudflare DDNS (own domain)">Scoped &lt;code>Zone:DNS:Edit&lt;/code> token per zone&lt;/td>
&lt;td data-label="DuckDNS (*.duckdns.org)">One account token for every subdomain on the account&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">TLS certificates&lt;/td>
&lt;td data-label="Cloudflare DDNS (own domain)">Full DNS-01 ACME (&lt;code>*.home.example.com&lt;/code>)&lt;/td>
&lt;td data-label="DuckDNS (*.duckdns.org)">DNS-01 through DuckDNS&amp;rsquo;s TXT update API, which it says can prove ownership to Let&amp;rsquo;s Encrypt&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Custom records&lt;/td>
&lt;td data-label="Cloudflare DDNS (own domain)">&lt;code>MX&lt;/code>, &lt;code>SRV&lt;/code>, &lt;code>CAA&lt;/code>, &lt;code>TXT&lt;/code>, multiple &lt;code>A&lt;/code>/&lt;code>AAAA&lt;/code>&lt;/td>
&lt;td data-label="DuckDNS (*.duckdns.org)">&lt;code>A&lt;/code>, &lt;code>AAAA&lt;/code>, and one &lt;code>TXT&lt;/code> record per subdomain, shared by its sub-subdomains&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>My rule is straightforward. Pick by TLS needs. Use DuckDNS when you want a zero-dollar hostname for a single &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">self-hosted WireGuard endpoint&lt;/a> tonight, then move to an inexpensive domain on Cloudflare the moment you deploy &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">Caddy, Nginx Proxy Manager, or Traefik&lt;/a> and want valid Let&amp;rsquo;s Encrypt DNS-01 wildcard certificates across internal LAN services without ever exposing port &lt;code>80&lt;/code> to the public internet. A &lt;a href="https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/">Vaultwarden instance on Proxmox&lt;/a> is a typical service that needs exactly that hostname and certificate.&lt;/p>
&lt;h2 id="ttl-math-how-long-an-ip-change-stalls-access">TTL math: how long an IP change stalls access&lt;/h2>
&lt;p>People routinely blame their DDNS container when reconnects stall for forty minutes after a modem reboot. Usually the container updated Cloudflare in two minutes. Cached DNS records did the rest.&lt;/p>
&lt;p>Worst-case cutover lag equals two timers added together:&lt;/p>
&lt;p>&lt;strong>Maximum stale window = polling interval + DNS record TTL&lt;/strong>&lt;/p>
&lt;p>Suppose your client polls every &lt;code>300&lt;/code> seconds (5 minutes) and your &lt;code>A&lt;/code> record carries a legacy &lt;code>3600&lt;/code>-second (1 hour) TTL. If a recursive resolver caches your old IP ten seconds before your ISP forces a new DHCP lease during an overnight maintenance window, clients behind that resolver can keep dialing the dead IP for up to &lt;strong>65 minutes&lt;/strong>. Drop the record TTL to &lt;code>120&lt;/code> or &lt;code>300&lt;/code> seconds while keeping a &lt;code>300&lt;/code>-second poll interval, and the worst-case stale window shrinks to &lt;strong>7 to 10 minutes&lt;/strong> without hammering Cloudflare&amp;rsquo;s API.&lt;/p>
&lt;h2 id="when-to-skip-ddns-and-port-forwarding-altogether">When to skip DDNS and port forwarding altogether&lt;/h2>
&lt;p>Even with a clean public IPv4 and a 60-second TTL, opening router ports is no longer the default answer for every homelab workload.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Private admin access (Proxmox UI, SSH, SMB, RDP, Home Assistant):&lt;/strong> Skip public DNS and inbound ports if only your own phones and laptops connect. An outbound mesh VPN works through CGNAT, hotel Wi-Fi, and double NAT with zero firewall holes; see our &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale vs WireGuard breakdown&lt;/a> for when raw kernel WireGuard still wins on throughput and battery life, or &lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a> if you want to run that mesh&amp;rsquo;s control server yourself.&lt;/li>
&lt;li>&lt;strong>Public HTTPS apps behind CGNAT:&lt;/strong> When family or webhooks need browser access without installing VPN client apps—and your ISP locks you inside &lt;code>100.64.0.0/10&lt;/code>—an outbound &lt;code>cloudflared&lt;/code> daemon publishes the web service through Cloudflare&amp;rsquo;s edge without a public WAN IP. Check the privacy and media-streaming tradeoffs in &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale vs Cloudflare Tunnel&lt;/a> before routing video over it; the &lt;a href="https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/">Jellyfin remote access guide&lt;/a> covers that case.&lt;/li>
&lt;li>&lt;strong>Self-hosted WireGuard on a real public IP:&lt;/strong> Here Dynamic DNS shines. Pair &lt;code>vpn.example.com&lt;/code> (grey-clouded, &lt;code>TTL 120&lt;/code>) with UDP port &lt;code>51820&lt;/code> on your router, add &lt;code>PersistentKeepalive = 25&lt;/code> on road-warrior peers, and you hold an encrypted path back to your rack with zero third-party relay servers in the middle. That forward exposes UDP 51820 to the whole internet; delete the forward on the router to close it.&lt;/li>
&lt;/ul></description></item><item><title>Size a Frigate NVR by Bitrate, Not Megapixels</title><link>https://techfuelhq.com/homelab/frigate-nvr-sizing-bitrate-2026/</link><pubDate>Mon, 07 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/frigate-nvr-sizing-bitrate-2026/</guid><atom:updated>2026-11-18T06:20:00Z</atom:updated><description>&lt;p>Reolink&amp;rsquo;s &lt;a href="https://reolink.com/us/product/rlc-520a/" rel="noopener">RLC-520A&lt;/a> is a 5MP camera. Its &lt;a href="https://reolink.com/us/product/rlc-811a/" rel="noopener">RLC-811A&lt;/a> is 4K: 3840×2160 against the 520A&amp;rsquo;s 2560×1920, about seventy percent more pixels. Reolink&amp;rsquo;s own spec pages give both the same mainstream default: &lt;strong>6144 kbps.&lt;/strong>&lt;/p>
&lt;p>That shared default is the whole lesson. Frigate&amp;rsquo;s storage bill is set by the average bitrate it records and how long it keeps it; resolution matters only where it moves that bitrate. This page is about picking the right input. For which machine to buy once you have the number, see &lt;a href="https://techfuelhq.com/homelab/best-hardware-frigate-nvr-2026/">best hardware for Frigate NVR&lt;/a>.&lt;/p>
&lt;h2 id="use-my-recording-figures">Use my recording figures&lt;/h2>
&lt;p>Four cameras averaging 4,096 kbps continuously for 30 days write &lt;strong>5.31 TB&lt;/strong> before any allowance. Reserving 20% of capacity raises the target to &lt;strong>6.64 TB&lt;/strong>. Which starting point matches what you know?&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;a href="https://techfuelhq.com/tools/frigate-nvr-storage-calculator/?start=observed#recording-worksheet">I have recording observations&lt;/a>.&lt;/strong> Use the size of unique segments retained during a representative interval, or actual day and night averages for the recording stream. Note the Frigate version, dates and retention rules. Free space can stay flat while old recordings expire even though new video is being written.&lt;/li>
&lt;li>&lt;strong>&lt;a href="https://techfuelhq.com/tools/frigate-nvr-storage-calculator/?start=assumed#recording-worksheet">I only have a configured bitrate&lt;/a>.&lt;/strong> Treat that rate as a scenario: a setting of 4,096 kbps means 4.096 Mbps, not what a busy night will actually write.&lt;/li>
&lt;/ul>
&lt;p>For a mixed policy, count each segment once. If you keep all footage for two days and motion footage for five, only the &lt;strong>three older days&lt;/strong> add motion storage. &lt;a href="https://docs.frigate.video/configuration/record/#understanding-storage-usage" rel="noopener">Frigate&amp;rsquo;s storage notes&lt;/a> explain why the usage Frigate reports will not exactly match what &lt;code>df&lt;/code> or &lt;code>du&lt;/code> shows.&lt;/p>
&lt;h2 id="frigate-copies-the-stream-so-the-camera-sets-the-size">Frigate copies the stream, so the camera sets the size&lt;/h2>
&lt;p>Frigate&amp;rsquo;s &lt;a href="https://docs.frigate.video/configuration/record/" rel="noopener">recording documentation&lt;/a> states that recordings are &amp;ldquo;written directly from your camera stream without re-encoding.&amp;rdquo; So the recorded streams&amp;rsquo; average bitrate is the footage estimate; add audio, container overhead, other stored data and free-space reserve on top.&lt;/p>
&lt;p>That collapses the whole storage question to one multiplication. One megabit per second of continuous recording is 86,400 megabits a day, which is &lt;strong>10.8 GB/day&lt;/strong>. Everything else (resolution, frame rate, codec) matters only because it moves the bitrate.&lt;/p>
&lt;p>Here is the Reolink mainstream range, converted:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Mainstream bitrate&lt;/th>
&lt;th scope="col" style="text-align: right">Per camera/day&lt;/th>
&lt;th scope="col" style="text-align: right">4 cameras, 14 days&lt;/th>
&lt;th scope="col" style="text-align: right">4 cameras, 30 days&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Mainstream bitrate">1024 kbps (RLC-520A floor)&lt;/td>
&lt;td style="text-align: right" data-label="Per camera/day">11.1 GB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 14 days">0.62 TB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 30 days">1.33 TB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mainstream bitrate">2048 kbps&lt;/td>
&lt;td style="text-align: right" data-label="Per camera/day">22.1 GB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 14 days">1.24 TB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 30 days">2.65 TB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mainstream bitrate">&lt;strong>4096 kbps&lt;/strong> (RLC-811A floor)&lt;/td>
&lt;td style="text-align: right" data-label="Per camera/day">&lt;strong>44.2 GB&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 14 days">&lt;strong>2.48 TB&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 30 days">&lt;strong>5.31 TB&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mainstream bitrate">6144 kbps (both defaults)&lt;/td>
&lt;td style="text-align: right" data-label="Per camera/day">66.4 GB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 14 days">3.72 TB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 30 days">7.96 TB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mainstream bitrate">8192 kbps (both ceilings)&lt;/td>
&lt;td style="text-align: right" data-label="Per camera/day">88.5 GB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 14 days">4.95 TB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras, 30 days">10.62 TB&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Bitrate ranges from the Reolink &lt;a href="https://reolink.com/us/product/rlc-520a/" rel="noopener">RLC-520A&lt;/a> and &lt;a href="https://reolink.com/us/product/rlc-811a/" rel="noopener">RLC-811A&lt;/a> specification pages, read 2026-11-18. The table assumes those rates are sustained averages during continuous recording, in decimal gigabytes, before overhead. A configured limit is not a measured average, which is why the same camera can land anywhere in this table.&lt;/p>
&lt;p>The same spec pages cap both cameras&amp;rsquo; substreams at 512 kbps against the mainstream&amp;rsquo;s 8192 kbps ceiling, a sixteen-fold gap that matters in the next section. The &lt;a href="https://techfuelhq.com/tools/frigate-nvr-storage-calculator/">Frigate storage worksheet&lt;/a> handles camera groups with different recorded rates and retention periods; group cameras only if they cover distinct footage.&lt;/p>
&lt;h2 id="what-megapixels-actually-cost-the-detect-stream">What megapixels actually cost: the detect stream&lt;/h2>
&lt;p>Resolution is not free. It just does not bill you where people look.&lt;/p>
&lt;p>Frigate&amp;rsquo;s &lt;a href="https://docs.frigate.video/frigate/camera_setup/" rel="noopener">camera setup guide&lt;/a> describes the detect stream as &amp;ldquo;the only stream that Frigate will decode for processing,&amp;rdquo; and the record stream as &amp;ldquo;the resolution you wish to store for reference.&amp;rdquo; Two different streams, two different budgets. The 4K stream goes to disk untouched. The substream is what gets decoded, buffered and inspected.&lt;/p>
&lt;p>You can see the split in shared memory. Frigate&amp;rsquo;s &lt;a href="https://docs.frigate.video/frigate/installation/" rel="noopener">installation calculator&lt;/a>, checked November 18, 2026, uses &lt;code>(width × height × 1.5 + 270480) / 1048576 × 25&lt;/code> per camera, computed on the &lt;strong>detect&lt;/strong> resolution, and adds room for two cameras added while Frigate runs plus 50 MB for logs and cache. The documentation labels the result MB; the divisor is 2²⁰ bytes. The table follows that calculator and rounds the combined allowance upward:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Detect resolution&lt;/th>
&lt;th scope="col" style="text-align: right">Per camera, 25 frames&lt;/th>
&lt;th scope="col" style="text-align: right">4 cameras + 2 spare + logs/cache&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Detect resolution">640×480&lt;/td>
&lt;td style="text-align: right" data-label="Per camera, 25 frames">17.44 MB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras &amp;#43; 2 spare &amp;#43; logs/cache">155 MB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detect resolution">&lt;strong>1280×720&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Per camera, 25 frames">&lt;strong>39.41 MB&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras &amp;#43; 2 spare &amp;#43; logs/cache">&lt;strong>287 MB&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detect resolution">1920×1080&lt;/td>
&lt;td style="text-align: right" data-label="Per camera, 25 frames">80.61 MB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras &amp;#43; 2 spare &amp;#43; logs/cache">534 MB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detect resolution">2560×1440&lt;/td>
&lt;td style="text-align: right" data-label="Per camera, 25 frames">138.28 MB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras &amp;#43; 2 spare &amp;#43; logs/cache">880 MB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detect resolution">3840×2160&lt;/td>
&lt;td style="text-align: right" data-label="Per camera, 25 frames">303.08 MB&lt;/td>
&lt;td style="text-align: right" data-label="4 cameras &amp;#43; 2 spare &amp;#43; logs/cache">1869 MB&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Add another 8 MB if Birdseye restream is enabled. The same page gives its own example, about 210MB for two cameras detecting at 720p, against Docker&amp;rsquo;s 64MB default. The calculator targets 25 frames, a little above the 20-frame minimum Frigate warns below; Frigate keeps up to 50 when there is room. This shared-memory budget is separate from total machine RAM.&lt;/p>
&lt;p>A higher detect resolution raises this budget fast; a separate 4K record stream does not touch it. Treat a 1280×720 detect substream as a starting point to test against the distance of the objects you need to recognize, and match its aspect ratio to the record stream, which Frigate&amp;rsquo;s guide asks for the best experience in its UI.&lt;/p>
&lt;h2 id="the-detector-budget-is-frames-not-cameras">The detector budget is frames, not cameras&lt;/h2>
&lt;p>The third budget is inference, and Frigate publishes the arithmetic for one accelerator. From the &lt;a href="https://docs.frigate.video/frigate/hardware/" rel="noopener">recommended hardware page&lt;/a>: &amp;ldquo;With an inference speed of 10, your Coral will top out at &lt;code>1000/10=100&lt;/code>, or 100 frames per second.&amp;rdquo; The same page now says the Coral &amp;ldquo;is no longer recommended for new Frigate installations, except in deployments with particularly low power requirements or hardware incapable of utilizing alternative AI accelerators,&amp;rdquo; and that a pipelined MemryX MX3&amp;rsquo;s limit &amp;ldquo;cannot be calculated as 1/latency.&amp;rdquo; So inverse latency applies to a Coral you already own; for an MX3, Frigate says to use its published total-FPS figures instead.&lt;/p>
&lt;p>Nor does 100 inferences per second mean twenty cameras at 5 fps: Frigate&amp;rsquo;s &lt;a href="https://docs.frigate.video/frigate/video_pipeline/" rel="noopener">video pipeline&lt;/a> analyzes motion regions, so camera frames and model invocations are not one-to-one. The camera guide calls 5 detect fps correct for most scenes, raising it toward 10 only when objects cross the whole frame in about a second. A faster detector also does nothing for CPU decoding and motion processing.&lt;/p>
&lt;p>Frigate&amp;rsquo;s &lt;a href="https://docs.frigate.video/configuration/object_detectors/" rel="noopener">object detector docs&lt;/a> note that &amp;ldquo;when using many cameras one detector may not be enough to keep up&amp;rdquo; and that &amp;ldquo;multiple detectors can be defined assuming GPU resources are available.&amp;rdquo; If your arithmetic lands close to the ceiling, that is the escape hatch, not a bigger drive.&lt;/p>
&lt;h2 id="the-fourth-budget-is-watts">The fourth budget is watts&lt;/h2>
&lt;p>Cameras draw power, and the megapixel number predicts that no better than it predicts storage.&lt;/p>
&lt;p>Reolink lists the fixed 4K RLC-811A at &amp;ldquo;DC 12.0V⎓1A, &amp;lt;12W&amp;rdquo; and PoE &amp;ldquo;IEEE 802.3af, 48V active.&amp;rdquo; The 4K &lt;a href="https://reolink.com/us/product/rlc-823a/" rel="noopener">RLC-823A&lt;/a> PTZ is listed at &amp;ldquo;DC 12.0V⎓2A, &amp;lt;24W&amp;rdquo; and PoE &amp;ldquo;IEEE 802.3at.&amp;rdquo; Identical resolution, identical 6144 kbps default, double the power class.&lt;/p>
&lt;p>Six fixed cameras plus two PTZs is roughly 120 W of rated device draw before cable loss and headroom. Plenty of eight-port PoE switches do not supply that, because &amp;ldquo;eight PoE ports&amp;rdquo; describes connectors rather than a power budget. Add the rated watts, add the run length, add a margin, and buy on the total; the &lt;a href="https://techfuelhq.com/tools/poe-budget-calculator/">PoE budget calculator&lt;/a> does exactly that. The NVR host draws power around the clock too: the &lt;a href="https://techfuelhq.com/homelab/24-7-homelab-idle-power-costs-2026/">24/7 idle power costs&lt;/a> page prices that line.&lt;/p>
&lt;h2 id="getting-your-real-number-off-the-camera">Getting your real number off the camera&lt;/h2>
&lt;p>Reolink&amp;rsquo;s &lt;a href="https://support.reolink.com/articles/360012182273-How-to-Find-the-Bandwidth-that-Reolink-Cameras-will-Take/" rel="noopener">support article&lt;/a> says to go to &lt;strong>Settings → Stream&lt;/strong> and click &lt;strong>Maximum Bitrate&lt;/strong>. That is the camera&amp;rsquo;s ceiling. Use it as the first planning input, then measure what actually lands on disk over representative day and night activity.&lt;/p>
&lt;p>What the number means depends on the control mode. Axis&amp;rsquo;s &lt;a href="https://whitepapers.axis.com/en-us/bitrate-control-for-ip-video" rel="noopener">bitrate control white paper&lt;/a> explains that variable bitrate lets demand vary with the scene to protect image quality, while a maximum bitrate raises compression when needed, which can cost quality; actual output can sit below the cap or briefly overshoot it.&lt;/p>
&lt;p>Codec changes the bitrate needed for acceptable quality. Catellier and Pinson&amp;rsquo;s &lt;a href="https://its.ntia.gov/publications/details.aspx?pub=2818" rel="noopener">subjective study for NTIA/ITS&lt;/a> investigates H.265/HEVC&amp;rsquo;s coding-efficiency improvement over H.264/AVC. Reolink&amp;rsquo;s current spec pages list both H.264 and H.265 for the RLC-520A and the RLC-811A, so the codec setting, not the model, is the variable to check. Axis&amp;rsquo;s &lt;a href="https://whitepapers.axis.com/en-us/axis-zipstream-technology" rel="noopener">Zipstream&lt;/a> makes the same point from the vendor side: it adapts &amp;ldquo;based on scene motion, scene content, ambient light level, and settings,&amp;rdquo; a list with no resolution in it.&lt;/p>
&lt;h2 id="where-a-bitrate-table-stops-working">Where a bitrate table stops working&lt;/h2>
&lt;p>Equal bitrate is not equal quality. In the same NTIA study, &amp;ldquo;for all 20 scenes coded with H.265/HEVC at 4 Mbps mean opinion scores span 38% of the subjective scale, which indicates the importance of scene selection.&amp;rdquo; Nearly two fifths of the quality range, at one fixed bitrate, purely from what was in front of the lens. A quiet hallway and a wind-blown tree line can look very different at the same average bitrate, so record representative activity, inspect moving objects and night footage, and adjust each scene on its own.&lt;/p>
&lt;h2 id="leave-capacity-for-overhead-and-changes-in-bitrate">Leave capacity for overhead and changes in bitrate&lt;/h2>
&lt;p>Four cameras averaging 4096 kbps during continuous recording for 30 days produce about &lt;strong>5.31 TB&lt;/strong> of footage. At an actual average of 6144 kbps, that becomes 7.96 TB, which leaves no practical reserve on an 8TB drive. Filesystem space and other files also reduce what is left for recordings, and &lt;a href="https://docs.frigate.video/configuration/record/" rel="noopener">Frigate&amp;rsquo;s recording settings&lt;/a> decide which segments are kept, so hold the recording mode and retention fixed while you measure.&lt;/p>
&lt;p>This planning example reserves 20% of nominal drive capacity for overhead and margin. That reserve is an assumption for this comparison, not a Frigate requirement. Divide the footage estimate by 0.8 to get the nominal capacity target:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Continuous recording for 30 days&lt;/th>
&lt;th scope="col" style="text-align: right">Estimated footage&lt;/th>
&lt;th scope="col" style="text-align: right">Capacity target with 20% reserved&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Continuous recording for 30 days">Four cameras at 4096 kbps&lt;/td>
&lt;td style="text-align: right" data-label="Estimated footage">5.31 TB&lt;/td>
&lt;td style="text-align: right" data-label="Capacity target with 20% reserved">6.64 TB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Continuous recording for 30 days">Five cameras at 4096 kbps&lt;/td>
&lt;td style="text-align: right" data-label="Estimated footage">6.64 TB&lt;/td>
&lt;td style="text-align: right" data-label="Capacity target with 20% reserved">8.29 TB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Continuous recording for 30 days">Four cameras at 6144 kbps&lt;/td>
&lt;td style="text-align: right" data-label="Estimated footage">7.96 TB&lt;/td>
&lt;td style="text-align: right" data-label="Capacity target with 20% reserved">9.95 TB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Continuous recording for 30 days">Five cameras at 6144 kbps&lt;/td>
&lt;td style="text-align: right" data-label="Estimated footage">9.95 TB&lt;/td>
&lt;td style="text-align: right" data-label="Capacity target with 20% reserved">12.44 TB&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>An 8TB drive clears the first example. A 10TB drive clears the second and, just, the third. A fifth camera at 6144 kbps needs a larger drive or a change to retention or recording mode. Do not count the full nominal label as free recording space.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Drive&lt;/th>
&lt;th scope="col" style="text-align: right">Newegg price, November 17, 2026&lt;/th>
&lt;th scope="col">4-cam 30-day footage at 4096 kbps&lt;/th>
&lt;th scope="col">Buy&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Drive">Seagate SkyHawk 4TB (ST4000VX016)&lt;/td>
&lt;td style="text-align: right" data-label="Newegg price, November 17, 2026">$179.99&lt;/td>
&lt;td data-label="4-cam 30-day footage at 4096 kbps">No; covers 14 days at 6144 kbps and little else&lt;/td>
&lt;td data-label="Buy">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Seagate&amp;#43;SkyHawk&amp;#43;ST4000VX016&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/frigate-nvr-sizing-bitrate-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fseagate-skyhawk-st4000vx016-4tb-for-video-surveillance-5400-rpm%2Fp%2FN82E16822185066%3Fitem%3DN82E16822185066" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/frigate-nvr-sizing-bitrate-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Drive">Seagate SkyHawk 8TB (ST8000VX010)&lt;/td>
&lt;td style="text-align: right" data-label="Newegg price, November 17, 2026">$412.99&lt;/td>
&lt;td data-label="4-cam 30-day footage at 4096 kbps">Yes, 66% full&lt;/td>
&lt;td data-label="Buy">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Seagate&amp;#43;SkyHawk&amp;#43;ST8000VX010&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/frigate-nvr-sizing-bitrate-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fseagate-skyhawk-st8000vx010-8tb-for-video-surveillance-5400-rpm%2Fp%2FN82E16822185097%3Fitem%3D9SIC8D2M9N6119" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/frigate-nvr-sizing-bitrate-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Drive">&lt;strong>Seagate SkyHawk AI 10TB (ST10000VE001)&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Newegg price, November 17, 2026">&lt;strong>$499.99&lt;/strong>&lt;/td>
&lt;td data-label="4-cam 30-day footage at 4096 kbps">&lt;strong>Yes, 53% full, and covers the 6144 kbps default too&lt;/strong>&lt;/td>
&lt;td data-label="Buy">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Seagate&amp;#43;SkyHawk&amp;#43;AI&amp;#43;10TB&amp;#43;ST10000VE001&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/frigate-nvr-sizing-bitrate-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2F1Z4-002P-023P0%3Fitem%3D9SIC8D2M914760" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/frigate-nvr-sizing-bitrate-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Newegg prices are the lowest in-stock listing for each named model in Newegg&amp;rsquo;s product feed on November 17, 2026; check the seller, condition and warranty on the listing before you pay. Drive prices move weekly. If the 10TB price stings, &lt;a href="https://techfuelhq.com/homelab/refurbished-enterprise-hard-drives-guide-2026/">refurbished enterprise drives&lt;/a> buy more retention per dollar, &lt;a href="https://techfuelhq.com/articles/hdd-price-crisis-2026/">why hard drives got so expensive&lt;/a> explains this year&amp;rsquo;s prices, and &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">best NAS hard drives&lt;/a> compares drive classes.&lt;/p>
&lt;h2 id="the-four-numbers-in-order">The four numbers, in order&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Average recorded bitrate per camera&lt;/strong>. Multiply by 10.8 GB per Mbps per day, then by retention; add overhead and reserve. A configured cap is an assumption until measured. → &lt;a href="https://techfuelhq.com/tools/frigate-nvr-storage-calculator/">storage calculator&lt;/a>&lt;/li>
&lt;li>&lt;strong>Detect substream resolution&lt;/strong>, tested against the objects you need to recognize. Run Frigate&amp;rsquo;s shared-memory calculator on it.&lt;/li>
&lt;li>&lt;strong>Observed detection workload&lt;/strong>, starting from the documented 5 fps. Check the specific accelerator and model during busy scenes; inverse latency is not a universal capacity rule.&lt;/li>
&lt;li>&lt;strong>Rated watts per camera&lt;/strong>, summed, plus cable loss and headroom. → &lt;a href="https://techfuelhq.com/tools/poe-budget-calculator/">PoE budget calculator&lt;/a>&lt;/li>
&lt;/ol>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>Frigate documentation, opened 2026-11-18: &lt;a href="https://docs.frigate.video/configuration/record/" rel="noopener">recording&lt;/a> (streams written without re-encoding; storage usage), &lt;a href="https://docs.frigate.video/frigate/camera_setup/" rel="noopener">camera setup&lt;/a> (detect is the only decoded stream; detect fps), &lt;a href="https://docs.frigate.video/frigate/installation/" rel="noopener">installation&lt;/a> (shm calculator and 720p example), &lt;a href="https://docs.frigate.video/frigate/hardware/" rel="noopener">recommended hardware&lt;/a> (Coral arithmetic and status, MemryX), &lt;a href="https://docs.frigate.video/frigate/planning_setup/" rel="noopener">planning a new installation&lt;/a>, &lt;a href="https://docs.frigate.video/frigate/video_pipeline/" rel="noopener">video pipeline&lt;/a>, &lt;a href="https://docs.frigate.video/configuration/object_detectors/" rel="noopener">object detectors&lt;/a>&lt;/li>
&lt;li>Reolink specification pages, opened 2026-11-18: &lt;a href="https://reolink.com/us/product/rlc-520a/" rel="noopener">RLC-520A&lt;/a>, &lt;a href="https://reolink.com/us/product/rlc-811a/" rel="noopener">RLC-811A&lt;/a>, &lt;a href="https://reolink.com/us/product/rlc-823a/" rel="noopener">RLC-823A&lt;/a>, and the &lt;a href="https://support.reolink.com/articles/360012182273-How-to-Find-the-Bandwidth-that-Reolink-Cameras-will-Take/" rel="noopener">finding your bitrate&lt;/a> support article&lt;/li>
&lt;li>Axis Communications white papers: &lt;a href="https://whitepapers.axis.com/en-us/bitrate-control-for-ip-video" rel="noopener">bitrate control for IP video&lt;/a>, &lt;a href="https://whitepapers.axis.com/en-us/axis-zipstream-technology" rel="noopener">Zipstream technology&lt;/a>; product specifications for the &lt;a href="https://www.axis.com/products/axis-p3265-lve/support" rel="noopener">AXIS P3265-LVE&lt;/a>&lt;/li>
&lt;li>A. A. Catellier and M. H. Pinson, &lt;a href="https://its.ntia.gov/publications/details.aspx?pub=2818" rel="noopener">&lt;em>Characterization of the HEVC Coding Efficiency Advance Using 20 Scenes, ITU-T Rec. P.913 Compliant Subjective Methods, VQM, and PSNR&lt;/em>&lt;/a>, NTIA/ITS, December 2015&lt;/li>
&lt;li>Drive prices: Newegg product feed via Rakuten (MID 44583), cache dated 2026-11-17, lowest in-stock row for each named model&lt;/li>
&lt;/ul></description></item><item><title>Audiobookshelf Docker Setup: Self-Hosted Audiobooks (2026)</title><link>https://techfuelhq.com/tutorials/audiobookshelf-docker-setup-2026/</link><pubDate>Sat, 13 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/audiobookshelf-docker-setup-2026/</guid><atom:updated>2026-11-18T06:20:00Z</atom:updated><description>&lt;p>Audiobookshelf is a single Docker container that turns a folder of audiobook files into a real library server: per-user progress sync, metadata matching, mobile apps, and podcast RSS support. It&amp;rsquo;s the most complete Audible replacement available for self-hosting, and it&amp;rsquo;s one of the simplest installs on the self-hosted stack.&lt;/p>
&lt;h2 id="what-you-get">What you get&lt;/h2>
&lt;ul>
&lt;li>Web interface for browsing and streaming from any browser&lt;/li>
&lt;li>iOS and Android apps (official, free, both still beta) with progress sync&lt;/li>
&lt;li>Per-user accounts (track your books separately from family members)&lt;/li>
&lt;li>Metadata matching from Audible, Google Books, Open Library, iTunes and FantLab&lt;/li>
&lt;li>Podcast RSS support with scheduled downloads&lt;/li>
&lt;li>M4B chapter support, speed controls, sleep timer&lt;/li>
&lt;/ul>
&lt;p>No companion containers and no database service: the SQLite database lives in the &lt;code>/config&lt;/code> mount. One container, four mounts.&lt;/p>
&lt;h2 id="before-you-start">Before you start&lt;/h2>
&lt;ul>
&lt;li>A Linux host with Docker Engine and the Compose plugin (&lt;code>docker compose version&lt;/code> should answer).&lt;/li>
&lt;li>Port 13378 free on that host.&lt;/li>
&lt;li>Your audiobooks laid out as described in the next section. The folder layout decides whether books are recognised correctly.&lt;/li>
&lt;li>Local disk for &lt;code>/config&lt;/code>. The project says the SQLite database there must not be stored on, or accessed over, the network (a NAS share, for example): it may seem to work, then performance suffers and the database eventually corrupts. The media folders can live on a NAS; see the &lt;a href="https://techfuelhq.com/homelab/best-nas-for-plex-jellyfin-2026/">NAS guide&lt;/a> if you are choosing one.&lt;/li>
&lt;/ul>
&lt;h2 id="step-1-lay-out-the-library-folders">Step 1: Lay out the library folders&lt;/h2>
&lt;p>Audiobookshelf treats every folder as one book. A single-file book can sit at the root of the library, but anything else needs its own folder, and the folder structure can supply metadata in the form &lt;code>Author/Series/Book&lt;/code> or &lt;code>Author/Book&lt;/code>:&lt;/p>
&lt;pre tabindex="0">&lt;code>/audiobooks/
Author Name/
Book Title/
Book Title.m4b
Series Name/
Vol 1 - First Book/
First Book.m4b
Vol 2 - Second Book {Narrator Name}/
Second Book.m4b
&lt;/code>&lt;/pre>&lt;p>A series sequence such as &lt;code>Vol 1 - &lt;/code> or &lt;code>1. &lt;/code> goes in the book&amp;rsquo;s folder name, and a narrator in curly braces. Two books dropped loose into the same folder are read as one book, which is the most common setup mistake.&lt;/p>
&lt;p>For MP3 audiobooks that come as numbered chapter files, the folder is still the book:&lt;/p>
&lt;pre tabindex="0">&lt;code>/audiobooks/
Author Name/
Book Title/
01 - Chapter One.mp3
02 - Chapter Two.mp3
03 - Chapter Three.mp3
&lt;/code>&lt;/pre>&lt;p>Audiobookshelf sorts a multi-file book&amp;rsquo;s audio files by disc and track number, so keep those tags right. With M4B, the chapters travel inside the file.&lt;/p>
&lt;p>For podcasts, use a separate directory. Each podcast is one flat folder (no season subfolders), with every audio file an episode:&lt;/p>
&lt;pre tabindex="0">&lt;code>/podcasts/
Podcast Name/
(Audiobookshelf manages files here when it downloads episodes)
&lt;/code>&lt;/pre>&lt;h2 id="step-2-docker-compose">Step 2: Docker Compose&lt;/h2>
&lt;p>Save this as &lt;code>/opt/audiobookshelf/compose.yaml&lt;/code>. It is written against Audiobookshelf &lt;a href="https://github.com/advplyr/audiobookshelf/releases/tag/v2.38.0" rel="noopener">2.38.0&lt;/a>, the stable release published November 17, 2026, which also fixes several access-control bugs between users. The project publishes &lt;code>latest&lt;/code> for the newest stable release, &lt;code>edge&lt;/code> for every commit to master, and a version tag such as &lt;code>2.38.0&lt;/code> for each release; pin the version tag so an upgrade happens when you choose. The &lt;code>v3&lt;/code> tag is a test build of the next major version and does not belong on a library you care about.&lt;/p>
&lt;p>Keep the previous version&amp;rsquo;s image locally until playback and client progress sync have been verified after the upgrade.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">audiobookshelf&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">ghcr.io/advplyr/audiobookshelf:2.38.0&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">audiobookshelf&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;13378:80&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">TZ=America/Chicago&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># Audiobookshelf ignores PUID/PGID. To run as your own user,&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># uncomment this and use the numbers from `id -u` and `id -g`:&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># user: &amp;#34;1000:1000&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/path/to/audiobooks:/audiobooks&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/path/to/podcasts:/podcasts&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/opt/audiobookshelf/config:/config&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/opt/audiobookshelf/metadata:/metadata&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Replace &lt;code>/path/to/audiobooks&lt;/code> and &lt;code>/path/to/podcasts&lt;/code> with your actual library paths. Each mount should be its own directory, not one inside another. &lt;code>/config&lt;/code> holds the SQLite database; &lt;code>/metadata&lt;/code> holds metadata, cover and author images, logs and backups. If you uncomment &lt;code>user:&lt;/code>, that account needs read access to the media and write access to &lt;code>config&lt;/code> and &lt;code>metadata&lt;/code>. Setting &lt;code>TZ&lt;/code> and other values through a &lt;code>.env&lt;/code> file works the way the &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">Compose environment variables guide&lt;/a> explains.&lt;/p>
&lt;p>&lt;strong>Port warning:&lt;/strong> &lt;code>13378:80&lt;/code> publishes Audiobookshelf on every network interface of the host, and the server speaks plain HTTP. That is what phones on your LAN need, but do not forward 13378 on your router. If everything reaches it through a reverse proxy on the same host, publish &lt;code>127.0.0.1:13378:80&lt;/code> instead, which Docker documents as reachable only from the host itself.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir -p /opt/audiobookshelf/&lt;span style="color:#f92672">{&lt;/span>config,metadata&lt;span style="color:#f92672">}&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd /opt/audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose config --quiet
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose ps
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose logs --tail&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">50&lt;/span> audiobookshelf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>docker compose ps&lt;/code> should show the container running, and the log tail should end without errors.&lt;/p>
&lt;h2 id="step-3-first-login">Step 3: First login&lt;/h2>
&lt;p>Open &lt;code>http://your-host-ip:13378&lt;/code>. There is no default username or password: on the first visit you create the root account, and from it you can add admins and users later.&lt;/p>
&lt;h2 id="step-4-initial-library-setup">Step 4: Initial library setup&lt;/h2>
&lt;p>After logging in:&lt;/p>
&lt;ol>
&lt;li>Open &lt;strong>Settings&lt;/strong>, then &lt;strong>Libraries&lt;/strong>, and add a new library.&lt;/li>
&lt;li>Name it &amp;ldquo;Audiobooks&amp;rdquo;, choose the Books media type, and add the folder &lt;code>/audiobooks&lt;/code> (the container path, not the host path).&lt;/li>
&lt;li>Save, then run a &lt;strong>Scan&lt;/strong>. Audiobookshelf walks the directory tree and builds the library.&lt;/li>
&lt;/ol>
&lt;p>For podcasts: create a second library with the Podcasts media type and the folder &lt;code>/podcasts&lt;/code>.&lt;/p>
&lt;p>A scan reads local metadata only: folder names, audio tags, OPF and NFO files. Online metadata comes from matching, the next step. If a scan finds nothing, check the folder layout first, then that the container can see the files:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker compose exec audiobookshelf ls /audiobooks
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-5-metadata-matching">Step 5: Metadata matching&lt;/h2>
&lt;p>After the initial scan, most books will have the title and author from the directory name but no cover art, description, or narrator. Matching against an online provider is deliberately a manual action. Run it:&lt;/p>
&lt;p>&lt;strong>Per-book:&lt;/strong> open a book, choose &lt;strong>Match&lt;/strong>, pick a provider and result, select which fields to take, and apply.&lt;/p>
&lt;p>&lt;strong>Bulk:&lt;/strong> in &lt;strong>Settings → Libraries&lt;/strong>, open the library&amp;rsquo;s dropdown and choose &lt;strong>Match Books&lt;/strong>. You can also select several books in the library view and match them together.&lt;/p>
&lt;p>Quick Match picks the closest result automatically, judged by the provider&amp;rsquo;s result order and how close the provider&amp;rsquo;s duration is to your file&amp;rsquo;s. It is not always right, especially when the provider does not carry the book, so check anything that looks off with a manual Match or another provider. For obscure titles, you&amp;rsquo;ll get no match and need to edit manually.&lt;/p>
&lt;p>&lt;strong>Best metadata source for most books:&lt;/strong> Audible. The Audiobookshelf Audible provider pulls cover art and narrator data that Open Library and Google Books often lack. Set it as the library&amp;rsquo;s default metadata provider in that library&amp;rsquo;s settings; you can still pick another provider for any single search.&lt;/p>
&lt;h2 id="adding-podcast-feeds">Adding podcast feeds&lt;/h2>
&lt;ol>
&lt;li>Open the podcast library and go to the &lt;strong>Add&lt;/strong> tab.&lt;/li>
&lt;li>Search by name, paste the RSS feed URL, or upload an OPML file.&lt;/li>
&lt;li>Pick the podcast, fill in its details and add it.&lt;/li>
&lt;li>In the podcast&amp;rsquo;s settings, use the &lt;strong>Episodes&lt;/strong> tab to download past episodes and the &lt;strong>Schedule&lt;/strong> tab to turn on automatic checks.&lt;/li>
&lt;/ol>
&lt;p>Automatic episode checks are off by default and are set per podcast. By default every episode is kept. If you set &lt;strong>Max episodes to keep&lt;/strong>, the server deletes at most one old episode per check, and it does not look at whether anyone has listened to it. After 24 failed checks in a row, the schedule for that podcast switches itself off. A feed hosted on your own LAN is blocked by the server&amp;rsquo;s SSRF filter until you set &lt;code>DISABLE_SSRF_REQUEST_FILTER=1&lt;/code>.&lt;/p>
&lt;p>For podcast-only installs, the audiobook library is optional: you can run Audiobookshelf as a podcast manager alone.&lt;/p>
&lt;h2 id="step-6-mobile-app-setup">Step 6: Mobile app setup&lt;/h2>
&lt;ol>
&lt;li>Install &amp;ldquo;Audiobookshelf&amp;rdquo; from Google Play (Android, beta) or through the TestFlight link on audiobookshelf.org (iOS, early beta). As of November 18, 2026 the app README says the iOS beta is full at Apple&amp;rsquo;s 10,000-tester limit; until a seat opens, the project suggests the web client saved as a web app, sideloading the official build, or a third-party app.&lt;/li>
&lt;li>Open the app → &amp;ldquo;Connect to your server&amp;rdquo;&lt;/li>
&lt;li>Enter your server URL: &lt;code>http://your-host-ip:13378&lt;/code> (local) or your external domain if using NPM&lt;/li>
&lt;/ol>
&lt;p>Audiobookshelf has no built-in remote access; the project expects you to bring a VPN or a reverse proxy. For access outside the home network without a public domain, Tailscale is the simplest path: install Tailscale on your phone and server, then use the Tailscale IP (&lt;code>100.x.x.x&lt;/code>) as the server address in the Audiobookshelf app. The app connects over the WireGuard mesh without any port forwarding or SSL setup. See the &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale remote access guide&lt;/a>; the options weighed in the &lt;a href="https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/">Jellyfin remote access guide&lt;/a> apply here too.&lt;/p>
&lt;p>For public HTTPS with a proper domain: point Nginx Proxy Manager at &lt;code>audiobookshelf:80&lt;/code> (or host IP:13378), enable SSL, and turn on WebSockets support, which the project lists as required. Then use the public domain in the app.&lt;/p>
&lt;h2 id="sharing-with-family-members">Sharing with family members&lt;/h2>
&lt;p>Create additional user accounts in &lt;strong>Settings → Users&lt;/strong>. Account types are root (the first admin), admin, user, and guest (a user who cannot change their own password).&lt;/p>
&lt;p>Each user gets their own:&lt;/p>
&lt;ul>
&lt;li>Listening progress (per book, per podcast episode)&lt;/li>
&lt;li>Bookmarks&lt;/li>
&lt;/ul>
&lt;p>Users see the same library but their progress is independent. If a family member starts listening to a book, their &amp;ldquo;last played&amp;rdquo; timestamp won&amp;rsquo;t affect your progress. One account per person matters: the project says account sharing is unsupported and can misbehave when two people listen at once.&lt;/p>
&lt;p>&lt;strong>Permissions per user:&lt;/strong> you can restrict users to specific libraries or tags, disable downloads, or give admin access. By default, user and guest accounts can reach all non-explicit content in every library. For family members who only listen, a standard user with no download permission is the right setup.&lt;/p>
&lt;h2 id="listening-stats">Listening stats&lt;/h2>
&lt;p>Audiobookshelf builds its stats from listening sessions. The listening sessions page in the server settings shows every past and open session, filterable by user, and each row opens details that include the device used. The project asks you to keep sessions rather than delete them, since the stats depend on them. The Audiobookshelf API exposes session data if you want it in an external dashboard.&lt;/p>
&lt;h2 id="backing-up-audiobookshelf">Backing up Audiobookshelf&lt;/h2>
&lt;p>Audiobookshelf&amp;rsquo;s data lives in two places:&lt;/p>
&lt;ol>
&lt;li>&lt;code>/opt/audiobookshelf/config/&lt;/code>: the SQLite database (&lt;code>absdatabase.sqlite&lt;/code>)&lt;/li>
&lt;li>&lt;code>/opt/audiobookshelf/metadata/&lt;/code>: metadata, cover and author images, logs, and the built-in backups&lt;/li>
&lt;/ol>
&lt;p>Your actual audiobook files (in &lt;code>/audiobooks/&lt;/code>) are the source of truth and should be backed up independently as part of your media storage backup strategy; &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">restic, Borg or Kopia&lt;/a> all handle that.&lt;/p>
&lt;p>&lt;strong>Built-in backups.&lt;/strong> The Backups page in the server settings creates database backups on demand or on a schedule, keeps as many as you set, and can restore one with its Restore button. They land in &lt;code>/metadata/backups&lt;/code> by default and contain the database and the images in the metadata folder, never your media. Copy them somewhere other than the same disk.&lt;/p>
&lt;p>&lt;strong>Full state archive.&lt;/strong> For a copy that also captures the Compose file and the whole config and metadata folders, run this from &lt;code>/opt/audiobookshelf&lt;/code>. Stop the container so the SQLite database and its journal files are captured together. The archive also stores the Compose file with the version used for that backup:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>set -euo pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>backup_dir&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;/backup/audiobookshelf/&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>install -d -m &lt;span style="color:#ae81ff">0700&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose stop audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap &lt;span style="color:#e6db74">&amp;#39;docker compose start audiobookshelf&amp;#39;&lt;/span> EXIT
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tar -C /opt/audiobookshelf -czf &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/state.tar.gz.tmp&amp;#34;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> config metadata compose.yaml
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tar -tzf &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/state.tar.gz.tmp&amp;#34;&lt;/span> &amp;gt;/dev/null
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/state.tar.gz.tmp&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/state.tar.gz&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose start audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap - EXIT
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>printf &lt;span style="color:#e6db74">&amp;#39;Backup directory: %s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Copy the archive to a separate backup target. Listing it checks readability. To confirm recovery, restore into an isolated instance with copies of the media and check accounts, library entries and saved listening positions before relying on the backup.&lt;/p>
&lt;h2 id="coexistence-with-jellyfin">Coexistence with Jellyfin&lt;/h2>
&lt;p>Audiobookshelf and Jellyfin handle different media types and don&amp;rsquo;t conflict. Jellyfin handles video (movies, TV shows, home video); Audiobookshelf handles audio (audiobooks, podcasts). Both can run on the same host, same Docker Compose file, sharing the same reverse proxy.&lt;/p>
&lt;p>Don&amp;rsquo;t add your audiobook directory to Jellyfin: Jellyfin has weak audiobook support and won&amp;rsquo;t import M4B chapter data correctly. Audiobookshelf is the right tool for audio; Jellyfin is the right tool for video. The &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">Jellyfin setup guide&lt;/a> covers the video side.&lt;/p>
&lt;h2 id="updating-audiobookshelf">Updating Audiobookshelf&lt;/h2>
&lt;p>Read the &lt;a href="https://github.com/advplyr/audiobookshelf/releases" rel="noopener">release notes&lt;/a> for the target version. Run the backup sequence above and record its directory. Edit &lt;code>image:&lt;/code> in &lt;code>compose.yaml&lt;/code> to that exact release:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker compose config --quiet
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose pull audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose ps audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose logs --tail&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">100&lt;/span> audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>curl --fail --silent --show-error http://127.0.0.1:13378/ &amp;gt;/dev/null
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The HTTP check runs from the host and confirms the web server responds. Log in and play a book. Change its position, then confirm that position on a second device. A running container alone does not verify database migrations or progress sync. To get told when the container stops answering, point an &lt;a href="https://techfuelhq.com/tutorials/uptime-kuma-docker-setup-2026/">Uptime Kuma&lt;/a> monitor at it.&lt;/p>
&lt;p>If those checks fail, stop the new container. Preserve its data for diagnosis. Restore the old Compose pin with its matching pre-upgrade state, because an older image may not understand a database migrated by a newer one. Replace the backup path below with the directory printed before the upgrade:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cd /opt/audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose stop audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv config &lt;span style="color:#e6db74">&amp;#34;config.failed-&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv metadata &lt;span style="color:#e6db74">&amp;#34;metadata.failed-&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tar -xzf /backup/audiobookshelf/REPLACE-WITH-BACKUP-TIMESTAMP/state.tar.gz &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -C /opt/audiobookshelf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose config --quiet
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d audiobookshelf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Repeat those checks after rollback. Keep the media backup separate; the state archive does not include audiobook or podcast files.&lt;/p>
&lt;hr>
&lt;p>&lt;em>Audiobookshelf is item #9 in the &lt;a href="https://techfuelhq.com/articles/self-hosted-apps-replace-saas-2026/">12 best self-hosted apps guide&lt;/a>: see that article for how it fits alongside Jellyfin, Nextcloud, and the rest of the stack. For video streaming alongside your audiobook library, the &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">Jellyfin Docker setup guide&lt;/a> covers hardware transcoding and remote access.&lt;/em>&lt;/p></description></item><item><title>Headscale: Self-Hosting the Tailscale Control Server (2026)</title><link>https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/</link><pubDate>Sat, 15 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/</guid><atom:updated>2026-11-18T06:10:00Z</atom:updated><description>&lt;p>Headscale is an open-source server that stands in for Tailscale&amp;rsquo;s coordination server, so your Tailscale clients register with a machine you run instead of with Tailscale. The setup is short: a Linux host clients can reach, HTTPS on port 443, a user, a key, and one flag on each client. The harder question is whether you need it at all, so that comes first.&lt;/p>
&lt;h2 id="first-the-case-against-doing-this">First, the case against doing this&lt;/h2>
&lt;p>&lt;a href="https://tailscale.com/pricing" rel="noopener">Tailscale&amp;rsquo;s pricing page&lt;/a>, checked November 18, 2026, lists Personal at $0 for non-commercial use, with up to 6 users, unlimited user devices, up to 3 ACL groups and up to 50 tagged resources to start. A tagged server is a different resource category from a user device; count the kind you actually deploy. One person with a small lab may already fit, and Headscale swaps a managed service for one you patch, back up and recover yourself.&lt;/p>
&lt;p>I want to be blunt, because the search results for this topic are not: &lt;strong>for the majority of homelabs, Headscale solves a problem you do not have.&lt;/strong> Running it is a hobby in its own right, and that is a completely legitimate reason to run it. It is not the same reason as necessity, and the two get blurred constantly.&lt;/p>
&lt;p>Three situations where it genuinely earns the work:&lt;/p>
&lt;p>&lt;strong>You object to the metadata, not the cost.&lt;/strong> Tailscale&amp;rsquo;s coordination server knows your device names, your public keys, and who connects to what. The traffic is end-to-end encrypted and they cannot read it, but the graph is theirs. If that specific fact is what bothers you, Headscale is a direct answer and no amount of free tier fixes it.&lt;/p>
&lt;p>&lt;strong>Your structure does not fit the Personal plan.&lt;/strong> More than 6 users, or an ACL model that needs more than 3 groups, and you are looking at a paid tier. At that point the comparison is a real one.&lt;/p>
&lt;p>&lt;strong>You want the control plane to survive theirs.&lt;/strong> Existing tailnets keep passing traffic when the coordination server is unreachable, but new nodes and key rotations do not. If your tolerance for that is zero, owning the control plane is the only fix.&lt;/p>
&lt;p>Everything else — &amp;ldquo;self-hosting is better,&amp;rdquo; &amp;ldquo;I want to own my stack&amp;rdquo; — is preference, and preference is fine. Just price it against a free service that already works.&lt;/p>
&lt;h2 id="what-it-supports">What it supports&lt;/h2>
&lt;p>This is the &lt;a href="https://github.com/juanfont/headscale/blob/v0.29.7/docs/about/features.md" rel="noopener">v0.29.7 feature matrix&lt;/a>, checked November 18, 2026. The &lt;a href="https://github.com/juanfont/headscale/releases/tag/v0.29.7" rel="noopener">v0.29.7 release notes&lt;/a> set Tailscale v1.80.0 as the minimum supported client and, because it is a security release, recommend running Tailscale v1.104.4 or newer on your nodes alongside it.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Feature&lt;/th>
&lt;th scope="col">v0.29.7 documented status&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Feature">Registration (web login or pre-auth key), MagicDNS and split DNS&lt;/td>
&lt;td data-label="v0.29.7 documented status">Supported&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature">Taildrop and Taildrive&lt;/td>
&lt;td data-label="v0.29.7 documented status">Supported&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature">Subnet routers and exit nodes&lt;/td>
&lt;td data-label="v0.29.7 documented status">Supported&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature">Embedded DERP server and peer relays&lt;/td>
&lt;td data-label="v0.29.7 documented status">Supported&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature">ACLs, grants and Tailscale SSH&lt;/td>
&lt;td data-label="v0.29.7 documented status">Supported&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature">OIDC registration&lt;/td>
&lt;td data-label="v0.29.7 documented status">Supported; OIDC groups cannot be used in ACLs&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature">Funnel, Serve and network flow logs&lt;/td>
&lt;td data-label="v0.29.7 documented status">Not supported&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Basic protocol compatibility is not feature parity. If one of the unsupported entries is essential to your remote-access plan, settle it before migrating. &lt;a href="https://tailscale.com/opensource" rel="noopener">Tailscale describes Headscale&lt;/a> as developed independently and community-maintained, outside its supported product, so read Headscale&amp;rsquo;s release notes before upgrading clients and keep another way into the host.&lt;/p>
&lt;h2 id="setting-it-up">Setting it up&lt;/h2>
&lt;p>These steps follow Headscale&amp;rsquo;s own &lt;a href="https://github.com/juanfont/headscale/blob/v0.29.7/docs/setup/requirements.md" rel="noopener">requirements&lt;/a>, &lt;a href="https://github.com/juanfont/headscale/blob/v0.29.7/docs/setup/install/official.md" rel="noopener">install&lt;/a> and &lt;a href="https://github.com/juanfont/headscale/blob/v0.29.7/docs/usage/getting-started.md" rel="noopener">getting started&lt;/a> pages for v0.29.7. Replace &lt;code>headscale.example.com&lt;/code> with your hostname throughout.&lt;/p>
&lt;h3 id="1-pick-the-host-and-the-hostname">1. Pick the host and the hostname&lt;/h3>
&lt;p>Headscale asks for a server with a public IP address (dual-stack IPv4 and IPv6 recommended) and strongly recommends HTTPS on port 443, because the Tailscale client assumes it in some situations. It does very little work: it hands out keys and routes, then nodes talk directly.&lt;/p>
&lt;p>An existing home server qualifies if inbound connections can reach it; one behind CGNAT cannot, and the &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">Dynamic DNS guide&lt;/a> shows how to check. Hosting at home ties the coordination server to the homelab&amp;rsquo;s power and uplink; an off-site host separates the two. A subdomain on a domain you already own works for the hostname. If neither fits, compare domain or hosting options before installing.&lt;/p>
&lt;p>Ports Headscale may need open to the internet: TCP 443 always, TCP 80 if you use its built-in Let&amp;rsquo;s Encrypt client with the HTTP-01 challenge, and UDP 3478 if you turn on the embedded DERP server. Keep TCP 9090, the metrics and debug endpoint, private.&lt;/p>
&lt;p>Each forwarded port exposes Headscale to the whole internet, so keep it patched; to undo, delete the port forwards or firewall rules and the service is unreachable again.&lt;/p>
&lt;h3 id="2-install-the-debian-package">2. Install the Debian package&lt;/h3>
&lt;p>The DEB package is the recommended route on Debian 12 or newer and Ubuntu 22.04 or newer: it creates the &lt;code>headscale&lt;/code> user, a default configuration and a systemd service. Download the &lt;code>.deb&lt;/code> for your architecture from the &lt;a href="https://github.com/juanfont/headscale/releases/latest" rel="noopener">releases page&lt;/a>, then:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo apt install ./headscale.deb
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="3-edit-the-configuration">3. Edit the configuration&lt;/h3>
&lt;p>Open &lt;code>/etc/headscale/config.yaml&lt;/code>. The example ships listening on &lt;code>127.0.0.1:8080&lt;/code> with &lt;code>server_url: http://127.0.0.1:8080&lt;/code>; for production, set &lt;code>server_url&lt;/code> to the HTTPS address clients will use, such as &lt;code>https://headscale.example.com:443&lt;/code>, and the &lt;code>listen_addr&lt;/code> your setup needs (the example&amp;rsquo;s production value is &lt;code>0.0.0.0:8080&lt;/code>).&lt;/p>
&lt;p>For TLS, either put a reverse proxy in front, set &lt;code>tls_cert_path&lt;/code> and &lt;code>tls_key_path&lt;/code> to a full-chain certificate, or set &lt;code>tls_letsencrypt_hostname&lt;/code> and let Headscale&amp;rsquo;s &lt;a href="https://github.com/juanfont/headscale/blob/v0.29.7/docs/ref/tls.md" rel="noopener">built-in ACME client&lt;/a> fetch one. Its default HTTP-01 challenge needs port 80 reachable; TLS-ALPN-01 uses port 443 instead.&lt;/p>
&lt;h3 id="4-restart-and-check-it-is-reachable">4. Restart and check it is reachable&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo systemctl restart headscale
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo systemctl status headscale
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then open &lt;code>https://headscale.example.com/health&lt;/code> from outside your network. If that page does not load, clients will not register either.&lt;/p>
&lt;h3 id="5-create-a-user-and-a-pre-auth-key">5. Create a user and a pre-auth key&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo headscale users create alice
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo headscale users list
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo headscale preauthkeys create --user &amp;lt;USER_ID&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Take the user ID from &lt;code>headscale users list&lt;/code>. By default a pre-auth key is valid for one hour and works once.&lt;/p>
&lt;h3 id="6-join-each-client">6. Join each client&lt;/h3>
&lt;p>On a Linux client with Tailscale installed:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tailscale up --login-server https://headscale.example.com --authkey &amp;lt;YOUR_AUTH_KEY&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Without a key, &lt;code>tailscale up --login-server https://headscale.example.com&lt;/code> opens a page with an Auth ID; approve it on the server with &lt;code>headscale auth register --user &amp;lt;USER&amp;gt; --auth-id &amp;lt;AUTH_ID&amp;gt;&lt;/code>. Headscale&amp;rsquo;s documentation has separate pages for Android, Apple and Windows clients.&lt;/p>
&lt;h3 id="7-back-up-the-data-directory">7. Back up the data directory&lt;/h3>
&lt;p>Headscale&amp;rsquo;s documentation assumes SQLite, with the database, private keys and policy in &lt;code>/var/lib/headscale&lt;/code>. Back that directory up; losing it means registering every device again.&lt;/p>
&lt;h2 id="where-this-sits-against-the-alternatives">Where this sits against the alternatives&lt;/h2>
&lt;p>If you have not committed yet, the comparison is worth doing properly. I have written up &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale against plain WireGuard&lt;/a>, which is the real decision for most people, and &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale against Cloudflare Tunnel&lt;/a> for the case where you want to publish rather than connect. &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird against Tailscale&lt;/a> covers the other self-hostable mesh worth a look, and it is the one I would compare Headscale to most carefully, because it was designed to be self-hosted rather than adapted to it. &lt;a href="https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/">ZeroTier against Tailscale&lt;/a> covers the virtual-switch alternative.&lt;/p>
&lt;p>If you just want remote access to your homelab today and are not attached to owning the control plane, &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale on a homelab&lt;/a> takes about ten minutes. If you want no third party in the path at all, &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard on Proxmox&lt;/a> is the floor: more manual, no coordination server to run, no vendor.&lt;/p>
&lt;h2 id="what-i-have-not-tested">What I have not tested&lt;/h2>
&lt;p>I have not run Headscale through a Tailscale client major-version bump, which is the failure mode I would most want data on before recommending it to someone whose remote access depends on it. The project tracks upstream well by reputation. Reputation is not a measurement.&lt;/p>
&lt;p>I have not tested the OIDC integration, so I cannot tell you how painful the ACL group limitation is in practice, only that it is documented.&lt;/p>
&lt;p>I have not run it at a scale where SQLite is the constraint.&lt;/p></description></item><item><title>12 Best Self-Hosted Apps and Services 2026 to Replace SaaS</title><link>https://techfuelhq.com/articles/self-hosted-apps-replace-saas-2026/</link><pubDate>Fri, 01 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/self-hosted-apps-replace-saas-2026/</guid><atom:updated>2026-11-18T06:10:00Z</atom:updated><description>&lt;p>The twelve homelab apps I would run in 2026 are Immich for photos, Nextcloud AIO for files, Vaultwarden for passwords, Paperless-ngx for paper, Jellyfin for media, AdGuard Home for DNS, Tailscale for remote access, Home Assistant OS for the smart home, AudioBookshelf for audiobooks, n8n for automation, BookStack for a wiki and Uptime Kuma for monitoring. Each one replaces a subscription. Ten run as Docker containers, Home Assistant OS wants a VM, Tailscale installs on the host, and all twelve fit on one 32 GB mini PC.&lt;/p>
&lt;p>Every version and tag below was read from the project&amp;rsquo;s own releases page or image registry on November 18, 2026. Projects ship often; check the releases link next to each pin before you copy it.&lt;/p>
&lt;h2 id="the-scannable-table--12-apps-what-they-replace-what-they-need">The scannable table — 12 apps, what they replace, what they need&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">#&lt;/th>
&lt;th scope="col">App&lt;/th>
&lt;th scope="col">Replaces&lt;/th>
&lt;th scope="col">Difficulty (1–5)&lt;/th>
&lt;th scope="col">Plan for&lt;/th>
&lt;th scope="col">Killer feature&lt;/th>
&lt;th scope="col">Verdict&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="#">1&lt;/td>
&lt;td data-label="App">&lt;strong>Immich&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Google Photos / iCloud Photos&lt;/td>
&lt;td data-label="Difficulty (1–5)">3&lt;/td>
&lt;td data-label="Plan for">6 GB RAM, 2 cores, Docker&lt;/td>
&lt;td data-label="Killer feature">ML face + object search that genuinely beats Google&amp;rsquo;s UI&lt;/td>
&lt;td data-label="Verdict">Ship it. Pin the release and read its notes before each upgrade.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">2&lt;/td>
&lt;td data-label="App">&lt;strong>Nextcloud AIO&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Google Drive / Dropbox / Workspace&lt;/td>
&lt;td data-label="Difficulty (1–5)">3&lt;/td>
&lt;td data-label="Plan for">4 GB RAM, 2 cores, 40 GB disk&lt;/td>
&lt;td data-label="Killer feature">One container manages the whole stack including backups&lt;/td>
&lt;td data-label="Verdict">Use AIO. Skip the manual compose.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">3&lt;/td>
&lt;td data-label="App">&lt;strong>Vaultwarden&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Bitwarden cloud / 1Password&lt;/td>
&lt;td data-label="Difficulty (1–5)">1&lt;/td>
&lt;td data-label="Plan for">256 MB RAM&lt;/td>
&lt;td data-label="Killer feature">Bitwarden-compatible, runs on a potato, end-to-end encrypted&lt;/td>
&lt;td data-label="Verdict">Easiest win on the list.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">4&lt;/td>
&lt;td data-label="App">&lt;strong>Paperless-ngx&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Evernote / Dropbox Scan / paper&lt;/td>
&lt;td data-label="Difficulty (1–5)">3&lt;/td>
&lt;td data-label="Plan for">2 GB RAM, OCR is CPU-hungry&lt;/td>
&lt;td data-label="Killer feature">Tika + OCR + tagging makes paper actually searchable&lt;/td>
&lt;td data-label="Verdict">Replace your filing cabinet.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">5&lt;/td>
&lt;td data-label="App">&lt;strong>Jellyfin&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Plex / Netflix / Disney+&lt;/td>
&lt;td data-label="Difficulty (1–5)">2&lt;/td>
&lt;td data-label="Plan for">4 GB RAM, Intel N100 or 11th-gen+ iGPU for transcode&lt;/td>
&lt;td data-label="Killer feature">No subscriptions, no phoning home, hardware transcoding works&lt;/td>
&lt;td data-label="Verdict">Still the Plex-killer. AMD GPUs remain weak for transcode.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">6&lt;/td>
&lt;td data-label="App">&lt;strong>AdGuard Home&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Pi-hole / NextDNS&lt;/td>
&lt;td data-label="Difficulty (1–5)">1&lt;/td>
&lt;td data-label="Plan for">256 MB RAM&lt;/td>
&lt;td data-label="Killer feature">DNS-over-HTTPS upstream + per-client rules in a clean UI&lt;/td>
&lt;td data-label="Verdict">Picked over Pi-hole for the better UI.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">7&lt;/td>
&lt;td data-label="App">&lt;strong>Tailscale&lt;/strong> (or Headscale)&lt;/td>
&lt;td data-label="Replaces">ZeroTier, paid remote-access VPN&lt;/td>
&lt;td data-label="Difficulty (1–5)">1 (Tailscale) / 4 (Headscale)&lt;/td>
&lt;td data-label="Plan for">Negligible&lt;/td>
&lt;td data-label="Killer feature">WireGuard mesh that punches NAT and &amp;ldquo;just works&amp;rdquo;&lt;/td>
&lt;td data-label="Verdict">Tailscale free tier is enough for most. Headscale if you want to host the control plane.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">8&lt;/td>
&lt;td data-label="App">&lt;strong>Home Assistant OS&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Apple Home / Google Home / SmartThings&lt;/td>
&lt;td data-label="Difficulty (1–5)">4&lt;/td>
&lt;td data-label="Plan for">4 GB RAM, 2 vCPUs, 32 GB disk (VM script default; HA&amp;rsquo;s minimum is 2 GB)&lt;/td>
&lt;td data-label="Killer feature">Local control, no cloud dependency, every protocol&lt;/td>
&lt;td data-label="Verdict">Run it as a VM, not a container.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">9&lt;/td>
&lt;td data-label="App">&lt;strong>AudioBookshelf&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Audible / Libby&lt;/td>
&lt;td data-label="Difficulty (1–5)">2&lt;/td>
&lt;td data-label="Plan for">1 GB RAM&lt;/td>
&lt;td data-label="Killer feature">Tracks progress per-user across devices, podcast support included&lt;/td>
&lt;td data-label="Verdict">Drop-in for an Audible library you already own.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">10&lt;/td>
&lt;td data-label="App">&lt;strong>n8n&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Zapier / Make / IFTTT&lt;/td>
&lt;td data-label="Difficulty (1–5)">3&lt;/td>
&lt;td data-label="Plan for">4 GB RAM, 2 vCPUs for the official Compose stack&lt;/td>
&lt;td data-label="Killer feature">500+ integrations, queue mode for real workloads&lt;/td>
&lt;td data-label="Verdict">Beats Zapier for anything serious. Fair-code, not open source; you maintain it.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">11&lt;/td>
&lt;td data-label="App">&lt;strong>BookStack&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">Notion / Confluence (read-mostly)&lt;/td>
&lt;td data-label="Difficulty (1–5)">2&lt;/td>
&lt;td data-label="Plan for">1 GB RAM&lt;/td>
&lt;td data-label="Killer feature">Books → Chapters → Pages structure that doesn&amp;rsquo;t fight you&lt;/td>
&lt;td data-label="Verdict">Picked over Outline for simpler hosting.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="#">12&lt;/td>
&lt;td data-label="App">&lt;strong>Uptime Kuma&lt;/strong>&lt;/td>
&lt;td data-label="Replaces">UptimeRobot / Better Stack&lt;/td>
&lt;td data-label="Difficulty (1–5)">1&lt;/td>
&lt;td data-label="Plan for">256 MB RAM&lt;/td>
&lt;td data-label="Killer feature">Self-hostable status page for friends and family&lt;/td>
&lt;td data-label="Verdict">The first thing every homelab should add after DNS.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="what-got-cut-and-why">What got cut and why&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Plex&lt;/strong> — not a SaaS replacement; it &lt;em>is&lt;/em> the SaaS. Jellyfin replaces Plex.&lt;/li>
&lt;li>&lt;strong>Pi-hole&lt;/strong> — voted out for AdGuard Home. The DNS-over-HTTPS upstream and per-client rules in AdGuard&amp;rsquo;s UI are meaningfully better, and the Docker deploy is identical in difficulty. Pi-hole still works fine if you already run it. One deliberate disagreement inside this site: the &lt;a href="https://techfuelhq.com/articles/self-hosting-essentials/">self-hosting starter order&lt;/a> still opens on Pi-hole, because for someone&amp;rsquo;s first container the smaller footprint and the mountain of beginner documentation matter more than DoH. Both guides are pointing at the same job. This is a preference, not a correctness call, and &lt;a href="https://techfuelhq.com/homelab/pihole-vs-adguard-home-2026/">Pi-hole vs AdGuard Home&lt;/a> lays out the trade-off.&lt;/li>
&lt;li>&lt;strong>Seafile&lt;/strong> — solid block-sync, but Nextcloud AIO has closed the gap and the ecosystem (calendar, contacts, office) is broader.&lt;/li>
&lt;li>&lt;strong>Plausible CE / Umami / Mealie / FreshRSS / Linkding&lt;/strong> — all good, but none beat the 12 above on daily use or an obvious SaaS replacement. If a self-hosted &lt;strong>bookmark manager&lt;/strong> is specifically what you&amp;rsquo;re after, Linkding is fine but the two strongest options get their own head-to-head in &lt;a href="https://techfuelhq.com/homelab/karakeep-vs-linkwarden-2026/">Karakeep vs Linkwarden&lt;/a>.&lt;/li>
&lt;li>&lt;strong>Mail-in-a-Box / Mailcow&lt;/strong> — explicitly cut. Self-hosted outbound email in 2026 still gets your IP scored as suspicious by Microsoft and Google more often than not, and inbound MX is fine until your dynamic IP changes or your ISP blocks port 25. Use a paid relay (Fastmail, Migadu, Proton) and move on.&lt;/li>
&lt;li>&lt;strong>Matrix / Mattermost / Rocket.Chat&lt;/strong> — a self-hosted chat server is its own category, not a general SaaS swap, so it sits outside this list. There is also no drop-in clone of Discord&amp;rsquo;s text-plus-voice bundle in 2026. If replacing a Discord community or a team chat is what you actually want, the &lt;a href="https://techfuelhq.com/articles/self-hosted-discord-alternatives-2026/">self-hosted Discord alternatives comparison&lt;/a> breaks down which tool fits and the voice/video reality. Worth knowing before you pick: Mattermost gates production SSO behind paid plans, and &lt;a href="https://github.com/RocketChat/Rocket.Chat/releases/tag/9.0.0" rel="noopener">Rocket.Chat 9.0.0&lt;/a>, released November 10, 2026, made LDAP, SAML and custom OAuth require a premium plan. The &lt;a href="https://techfuelhq.com/self-hosted/self-hosted-sso-tax-2026/">self-hosted SSO tax tracker&lt;/a> documents both with free-SSO alternatives.&lt;/li>
&lt;/ul>
&lt;p>A difficulty score of 1 is &amp;ldquo;single container, defaults work, ten-minute deploy.&amp;rdquo; A 5 is &amp;ldquo;you&amp;rsquo;ll read documentation for a weekend and read it again at the next major upgrade.&amp;rdquo; Most of the 12 land at 1–3. The apps that survive in homelabs are the ones where the 80% case is boring.&lt;/p>
&lt;h2 id="where-to-start">Where to start&lt;/h2>
&lt;p>Do not stand up Immich and Home Assistant on day one. Deploy the ten-minute wins first, then climb in this order.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Day one: Vaultwarden, AdGuard Home, Uptime Kuma, Tailscale.&lt;/strong> Single containers where the defaults work, under 1 GB of planned RAM combined. Back up the password vault and keep a way to restore DNS and remote access.&lt;/li>
&lt;li>&lt;strong>First weekend: Jellyfin, Immich, AudioBookshelf, BookStack.&lt;/strong> The apps you&amp;rsquo;ll open daily, an afternoon each. Start Immich&amp;rsquo;s first library import when you won&amp;rsquo;t need the box for a while.&lt;/li>
&lt;li>&lt;strong>Once you&amp;rsquo;re hooked: Nextcloud AIO, Paperless-ngx, n8n, Home Assistant.&lt;/strong> Real commitments with real upside. Home Assistant is a hobby more than a deploy; run it as a VM.&lt;/li>
&lt;/ol>
&lt;h2 id="the-top-5--full-setups">The top 5 — full setups&lt;/h2>
&lt;h3 id="1-immich--the-google-photos-replacement-that-finally-works">1. Immich — the Google Photos replacement that finally works&lt;/h3>
&lt;p>The mobile app uploads from iOS and Android in the background, the ML stack identifies faces and objects locally, and the timeline UI beats Google Photos for most operations. The catch is RAM. Immich&amp;rsquo;s &lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">requirements page&lt;/a> sets a 6 GB minimum and recommends 8 GB, asks for at least 2 CPU cores (4 recommended), requires Docker with the Compose plugin, and says Docker inside an LXC container is not recommended, so use a full VM on Proxmox. Moving an existing library over is its own job; the &lt;a href="https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/">Google Photos to Immich migration guide&lt;/a> covers Takeout and &lt;code>immich-go&lt;/code>, and &lt;a href="https://techfuelhq.com/tutorials/self-hosted-photo-library-immich-photoprism-ente-2026/">Immich vs PhotoPrism vs Ente&lt;/a> covers the case for end-to-end encryption instead.&lt;/p>
&lt;p>&lt;a href="https://github.com/immich-app/immich/releases" rel="noopener">v3.4.1&lt;/a> (November 11, 2026) was the newest release on November 18. Use the compose file from the release you install, never one from the main branch; the file itself warns that main may not match the latest release.&lt;/p>
&lt;ol>
&lt;li>In a dedicated directory, save the &lt;a href="https://raw.githubusercontent.com/immich-app/immich/v3.4.1/docker/docker-compose.yml" rel="noopener">v3.4.1 docker-compose.yml&lt;/a> and the &lt;a href="https://raw.githubusercontent.com/immich-app/immich/v3.4.1/docker/example.env" rel="noopener">v3.4.1 example.env&lt;/a>, renamed to &lt;code>.env&lt;/code>.&lt;/li>
&lt;li>In &lt;code>.env&lt;/code>, set &lt;code>UPLOAD_LOCATION&lt;/code> to your media directory (it mounts at &lt;code>/data&lt;/code> inside the server) and &lt;code>DB_DATA_LOCATION&lt;/code> to local storage; the file says network shares are not supported for the database.&lt;/li>
&lt;li>Replace &lt;code>DB_PASSWORD=postgres&lt;/code> with a random password using only &lt;code>A-Za-z0-9&lt;/code>, as the file instructs.&lt;/li>
&lt;li>The example sets &lt;code>IMMICH_VERSION=v3&lt;/code>, which follows the v3 line. Set &lt;code>IMMICH_VERSION=v3.4.1&lt;/code> to stay on the release you tested, and change it deliberately when you upgrade.&lt;/li>
&lt;li>For Intel Quick Sync transcoding, uncomment the &lt;code>extends&lt;/code> block under &lt;code>immich-server&lt;/code> (commented out in v3.4.1), set its service to &lt;code>quicksync&lt;/code>, and save &lt;a href="https://raw.githubusercontent.com/immich-app/immich/v3.4.1/docker/hwaccel.transcoding.yml" rel="noopener">v3.4.1 hwaccel.transcoding.yml&lt;/a> next to the compose file. Then configure transcoding in Immich using its &lt;a href="https://docs.immich.app/features/hardware-transcoding" rel="noopener">transcoding guide&lt;/a>.&lt;/li>
&lt;/ol>
&lt;p>From that directory, run &lt;code>docker compose config&lt;/code> to check interpolation, then &lt;code>docker compose up -d&lt;/code>. Before importing your library, upload a disposable photo, recreate the containers, and confirm it remains available.&lt;/p>
&lt;p>&lt;strong>Port warning:&lt;/strong> the compose file publishes &lt;code>2283:2283&lt;/code>, which Docker exposes on every host interface. If a reverse proxy on the same host fronts Immich, change it to &lt;code>127.0.0.1:2283:2283&lt;/code> (see &lt;a href="#check-what-docker-publishes-before-you-move-a-service-home">the port note below&lt;/a>).&lt;/p>
&lt;p>Critical detail: &lt;strong>Immich is not a backup&lt;/strong>. The database can corrupt. Use &lt;a href="https://docs.immich.app/administration/backup-and-restore/" rel="noopener">Immich&amp;rsquo;s official backup guide&lt;/a> and keep originals on a separate disk from the Immich Postgres.&lt;/p>
&lt;h3 id="2-nextcloud-aio--file-sync-calendar-contacts-managed-by-one-container">2. Nextcloud AIO — file sync, calendar, contacts, managed by one container&lt;/h3>
&lt;p>The official &lt;a href="https://github.com/nextcloud/all-in-one" rel="noopener">Nextcloud All-in-One&lt;/a> project ships everything — Apache, PHP, the database, Redis, the office stack, Talk, the backup container — managed by a single mastercontainer that you talk to over a web UI on port 8080. It is the right answer for new self-hosters and for experienced ones who got tired of debugging PHP-FPM at 1 a.m. The stable release on November 18, 2026 was &lt;a href="https://github.com/nextcloud/all-in-one/releases" rel="noopener">v15.0.2&lt;/a> (November 3); v15.1.0 is a beta.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># The README&amp;#39;s command for Linux with no web server or reverse proxy already in place&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo docker run &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --init &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --sig-proxy&lt;span style="color:#f92672">=&lt;/span>false &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --name nextcloud-aio-mastercontainer &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --restart always &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --publish 80:80 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --publish 8080:8080 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --publish 8443:8443 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --volume /var/run/docker.sock:/var/run/docker.sock:ro &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> ghcr.io/nextcloud-releases/all-in-one:latest
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Port warning:&lt;/strong> this publishes 80, 8080 and 8443 on every host interface. The AIO README says 80 and 8443 are not required when AIO runs behind a reverse proxy; follow its &lt;a href="https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md" rel="noopener">reverse proxy documentation&lt;/a> if you have one.&lt;/p>
&lt;p>&lt;strong>Docker socket warning:&lt;/strong> the mastercontainer gets the Docker socket (read-only) so it can create and manage the other containers, which hands it control of Docker on that host. If you don&amp;rsquo;t want any container to hold the socket, the README points to its &lt;a href="https://github.com/nextcloud/all-in-one/tree/main/manual-install" rel="noopener">manual install&lt;/a>, which runs without it.&lt;/p>
&lt;p>The &lt;code>latest&lt;/code> tag here is the AIO mastercontainer, which the project explicitly maintains as the supported entry point — the actual Nextcloud server image &lt;em>underneath&lt;/em> gets pinned by AIO to a tested release. That&amp;rsquo;s the one place I make an exception to the &amp;ldquo;no &lt;code>:latest&lt;/code>&amp;rdquo; rule. If you want full version control, watch the &lt;a href="https://github.com/nextcloud/all-in-one/releases" rel="noopener">Nextcloud AIO releases page&lt;/a> and use a digest pin instead.&lt;/p>
&lt;p>In AIO v15.0.2&amp;rsquo;s &lt;a href="https://github.com/nextcloud/all-in-one/blob/v15.0.2/php/src/Data/ConfigurationManager.php" rel="noopener">configuration code&lt;/a>, a new instance installs the Calendar and Contacts apps and switches on Talk, Imaginary and Whiteboard, and the default office suite is Euro-Office; Collabora is still a choice. The AIO interface states the floor: with any optional container enabled, at least 2 GB of RAM, a dual-core CPU and 40 GB of system storage; with everything enabled, at least 5 GB of RAM and a quad-core CPU.&lt;/p>
&lt;p>For the complete setup — NPM reverse proxy config, Office activation, CalDAV/CardDAV client setup, and AIO backup — see the &lt;a href="https://techfuelhq.com/tutorials/nextcloud-aio-docker-setup-2026/">Nextcloud AIO Docker setup guide&lt;/a>.&lt;/p>
&lt;h3 id="3-vaultwarden--bitwarden-on-a-potato">3. Vaultwarden — Bitwarden, on a potato&lt;/h3>
&lt;p>Vaultwarden is a Rust reimplementation of the Bitwarden server API by &lt;a href="https://github.com/dani-garcia/vaultwarden" rel="noopener">dani-garcia&lt;/a>. The newest release on November 18, 2026 was &lt;strong>1.37.5&lt;/strong> (November 1), per the &lt;a href="https://github.com/dani-garcia/vaultwarden/releases" rel="noopener">Vaultwarden releases&lt;/a>. It fixes two security advisories (website icons and emergency access), and the maintainers say it is required for web vault 2026.7.1+ to turn two-step login methods on or off. 1.37.4 (October 5) fixed seven advisories, one of them rated High. Take the newest 1.37.x and nothing older. 1.37.5 also stops at startup on invalid configuration values, so read its upgrade notes if you carry an old environment file. It is fully compatible with the official Bitwarden apps, browser extensions and desktop clients, which is the whole point — your phone doesn&amp;rsquo;t know it&amp;rsquo;s not talking to Bitwarden&amp;rsquo;s cloud.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># docker-compose.yml — Vaultwarden, version-pinned&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">vaultwarden&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">vaultwarden/server:1.37.5-alpine&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">vaultwarden&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">DOMAIN&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;https://vault.example.lan&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">SIGNUPS_ALLOWED&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;false&amp;#34;&lt;/span> &lt;span style="color:#75715e"># flip to true for first user, then back&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># The admin page stays off until ADMIN_TOKEN is set. To turn it on, run&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># docker run --rm -it vaultwarden/server:1.37.5-alpine /vaultwarden hash&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># then uncomment the next line, paste the PHC string it prints, and&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># write every $ as $$ so Compose does not treat it as a variable.&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e"># ADMIN_TOKEN: &amp;#34;$$argon2id$$v=19$$m=65540,t=3,p=4$$...&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./vw-data:/data&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">127.0.0.1&lt;/span>:&lt;span style="color:#ae81ff">8222&lt;/span>:&lt;span style="color:#ae81ff">80&lt;/span> &lt;span style="color:#75715e"># reachable only from this host, for a reverse proxy here&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The port line binds to &lt;code>127.0.0.1&lt;/code> so only a reverse proxy on the same host can reach the vault; a plain &lt;code>8222:80&lt;/code> would publish it on every interface. WebSocket notifications run on the main port since 1.29.0, so the old &lt;code>WEBSOCKET_ENABLED&lt;/code> variable is &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-WebSocket-notifications" rel="noopener">ignored&lt;/a> and not in the file above. Two things people miss. Vaultwarden &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-HTTPS" rel="noopener">needs HTTPS&lt;/a>, because browsers only expose the web vault&amp;rsquo;s crypto APIs over HTTPS; put it behind Caddy or Traefik with Let&amp;rsquo;s Encrypt, or use &lt;a href="https://tailscale.com/docs/features/tailscale-funnel" rel="noopener">Tailscale Funnel&lt;/a> for a zero-config TLS path. And &lt;strong>back up &lt;code>./vw-data&lt;/code> somewhere off the host&lt;/strong> — a vault you can&amp;rsquo;t restore is a vault you don&amp;rsquo;t have. The &lt;a href="https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/">Vaultwarden on Proxmox setup guide&lt;/a> covers Caddy reverse proxy, the Tailscale-only setup path, and an automated SQLite backup script with online backup API support.&lt;/p>
&lt;h3 id="4-jellyfin--plex-without-the-company">4. Jellyfin — Plex without the company&lt;/h3>
&lt;p>Jellyfin is the mature fork of Emby. It does what Plex does — library scanning, transcoding, apps for phones and TVs — without phoning home, without watching your viewing history, and without a &amp;ldquo;Pass&amp;rdquo; subscription gating hardware acceleration. The feature-by-feature case is in &lt;a href="https://techfuelhq.com/articles/jellyfin-vs-plex-2026/">Jellyfin vs Plex&lt;/a>, and the &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">Jellyfin Docker setup guide&lt;/a> has the full walkthrough.&lt;/p>
&lt;p>&lt;a href="https://github.com/jellyfin/jellyfin/releases" rel="noopener">Jellyfin 12.4&lt;/a> shipped October 26, 2026. LinuxServer&amp;rsquo;s image has no bare &lt;code>12.4&lt;/code> tag, so the file pins the full build tag, &lt;code>12.4ubu2604-ls60&lt;/code>, which LinuxServer pushed on November 17.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># docker-compose.yml — Jellyfin with Intel Quick Sync transcoding&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">jellyfin&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">lscr.io/linuxserver/jellyfin:12.4ubu2604-ls60&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">jellyfin&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">PUID=1000&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">PGID=1000&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">TZ=America/Chicago&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">JELLYFIN_PublishedServerUrl=http://192.168.1.50:8096&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">devices&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/dev/dri:/dev/dri &lt;/span> &lt;span style="color:#75715e"># Intel iGPU passthrough for QSV&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./config:/config&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/srv/media:/data/media:ro&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">8096&lt;/span>:&lt;span style="color:#ae81ff">8096&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Port warning:&lt;/strong> &lt;code>8096:8096&lt;/code> publishes Jellyfin on every host interface, which your TVs and phones need on the LAN. If the host also has a public or VPN-facing address, bind it to the LAN address instead (&lt;code>192.168.1.50:8096:8096&lt;/code>, Docker&amp;rsquo;s documented host-IP form), and reach it from outside through Tailscale rather than a router port forward.&lt;/p>
&lt;p>Intel Quick Sync is what makes Jellyfin viable on a &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">budget mini PC&lt;/a>. Jellyfin&amp;rsquo;s &lt;a href="https://jellyfin.org/docs/general/administration/hardware-selection/" rel="noopener">hardware selection guide&lt;/a> names the Core i5-11400, Pentium Gold G7400 and N100 as integrated-graphics picks with 8 GB of system RAM. It has removed 7th to 10th-gen Intel from that list because Intel deprecated their media toolkit, while saying chips you already own are still capable; for a purchase, buy 11th-gen or newer.&lt;/p>
&lt;p>AMD GPUs remain the weakest transcode option in 2026. Jellyfin&amp;rsquo;s own &lt;a href="https://jellyfin.org/docs/general/administration/hardware-selection/" rel="noopener">hardware selection guide&lt;/a> calls AMD &amp;ldquo;the least preferred choice&amp;rdquo; for its sub-par H.264 encoders before RDNA 4 (RX 9000). It says the poor encoder quality and driver support apply &amp;ldquo;even on Linux&amp;rdquo;. If your homelab is AMD-only, plan for direct-play clients (NVIDIA Shield, Apple TV, a recent smart TV). The Jellyfin team also keeps a clear &lt;a href="https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/" rel="noopener">hardware acceleration matrix&lt;/a>; read it before you buy a box.&lt;/p>
&lt;h3 id="5-home-assistant-os--local-first-smart-home">5. Home Assistant OS — local-first smart home&lt;/h3>
&lt;p>Home Assistant replaces Apple Home, Google Home, and SmartThings at once. It is not easy; deep automation takes real time.&lt;/p>
&lt;p>The recommended path in 2026 is still &lt;strong>Home Assistant OS&lt;/strong> running as a VM rather than the Docker container. The &lt;a href="https://www.home-assistant.io/installation/linux" rel="noopener">Container install&lt;/a> &amp;ldquo;does not have access to apps&amp;rdquo;, which is what Home Assistant has called add-ons since the &lt;a href="https://www.home-assistant.io/blog/2026/02/04/release-20262/" rel="noopener">2026.2 release&lt;/a>, and those apps (Mosquitto, Zigbee2MQTT, ESPHome, the official Z-Wave stack) are most of what makes HA worth running. Supervised installs &lt;a href="https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/" rel="noopener">lost support&lt;/a> with 2025.12.&lt;/p>
&lt;p>For a Proxmox host, the community-maintained &lt;a href="https://community-scripts.org/scripts/haos-vm" rel="noopener">Home Assistant OS VM script&lt;/a> creates the VM with 2 vCPUs, 4 GB of RAM and a 32 GB disk by default, per the &lt;a href="https://github.com/community-scripts/ProxmoxVE/blob/main/vm/haos-vm.sh" rel="noopener">script&amp;rsquo;s source&lt;/a>. Home Assistant&amp;rsquo;s own &lt;a href="https://www.home-assistant.io/installation/alternative" rel="noopener">minimum&lt;/a> is 2 GB of RAM and 2 vCPUs; the table plans for the script&amp;rsquo;s 4 GB. Pass through a USB Zigbee/Z-Wave coordinator if you have one. The &lt;a href="https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/">Home Assistant on Proxmox tutorial&lt;/a> walks the whole install.&lt;/p>
&lt;p>The &lt;a href="https://www.home-assistant.io/blog/2026/03/04/release-20263/" rel="noopener">Home Assistant 2026.3 release notes&lt;/a> moved container images to zstd compression, supported on Docker 23.0.0 and containerd 1.5.0 or later. A Docker host older than that will fail to pull the image, while any modern Docker is fine. Read release notes before every monthly upgrade. HA breaks integrations a few times a year. Upgrades are not background tasks.&lt;/p>
&lt;h2 id="the-other-7--short-notes">The other 7 — short notes&lt;/h2>
&lt;h3 id="adguard-home-replaces-pi-hole-nextdns-your-routers-bad-ad-blocker">AdGuard Home (replaces Pi-hole, NextDNS, your router&amp;rsquo;s bad ad blocker)&lt;/h3>
&lt;p>Pin &lt;code>adguard/adguardhome:v0.107.80&lt;/code>, the &lt;a href="https://github.com/AdguardTeam/AdGuardHome/releases" rel="noopener">newest stable release&lt;/a> (November 3, 2026) on November 18; the Docker tag keeps the &lt;code>v&lt;/code>, and there is no floating &lt;code>v0.107&lt;/code> tag. The v1.0.0 builds on the same page are betas. Point your router&amp;rsquo;s DHCP DNS at the AdGuard container IP and every device on your network — phones, smart TVs, the IoT garbage — gets DNS-level filtering with zero per-device setup. The DoH/DoT upstream config is in the UI; switch it to Quad9 or Cloudflare 1.1.1.1 and you&amp;rsquo;ve also leaked less DNS to your ISP than you did last week.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/tutorials/adguard-home-local-dns-proxmox-2026/">AdGuard Home + Local DNS on Proxmox tutorial&lt;/a> covers the LXC setup from scratch: port 53 in an unprivileged container, the OISD plus Steven Black blocklists, local A records for &lt;code>pve.lan&lt;/code> / &lt;code>nas.lan&lt;/code>, and an optional Unbound recursive resolver that cuts upstream providers out entirely.&lt;/p>
&lt;h3 id="tailscale-replaces-zerotier-and-a-paid-remote-access-vpn">Tailscale (replaces ZeroTier and a paid remote-access VPN)&lt;/h3>
&lt;p>Yes, Tailscale is technically a SaaS for the coordinator. The free Personal plan on the &lt;a href="https://tailscale.com/pricing" rel="noopener">pricing page&lt;/a> (November 18, 2026) covers up to 6 users, unlimited user devices and up to 50 tagged resources to start, and exit nodes count as tagged resources. That is enough for almost every homelab. Direct connections are preferred. When a direct path fails, DERP servers or peer relays can carry the traffic; all three paths remain end-to-end encrypted with WireGuard. See &lt;a href="https://tailscale.com/docs/reference/connection-types" rel="noopener">Tailscale connection types&lt;/a>.&lt;/p>
&lt;p>If you are choosing between Tailscale and ZeroTier, see &lt;a href="https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/">ZeroTier vs Tailscale&lt;/a>. If you genuinely refuse the coordinator, &lt;a href="https://github.com/juanfont/headscale" rel="noopener">Headscale&lt;/a> is the open-source alternative — but plan for a difficulty score of 4 rather than 1. And if the real question is how to reach these services from outside your LAN at all, &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale vs Cloudflare Tunnel&lt;/a> covers the private-network-versus-public-tunnel split and the current free-tier limits.&lt;/p>
&lt;h3 id="audiobookshelf-replaces-audible">AudioBookshelf (replaces Audible)&lt;/h3>
&lt;p>If you already own audiobooks (legitimately, ideally), AudioBookshelf gives you per-user progress sync, mobile apps, and podcast support in a single container with no companion services. The official apps are free and both still labelled beta: Android is on Google Play, but iOS is an early &lt;a href="https://github.com/advplyr/audiobookshelf-app" rel="noopener">TestFlight beta&lt;/a> that the README marked full on November 18, 2026, citing Apple&amp;rsquo;s 10,000-tester limit, so an iPhone household may be waiting for a seat.&lt;/p>
&lt;p>Podcast RSS auto-download is built in. Pin &lt;code>ghcr.io/advplyr/audiobookshelf:2.38.0&lt;/code> (November 17, 2026, per the &lt;a href="https://github.com/advplyr/audiobookshelf/releases" rel="noopener">releases&lt;/a>) rather than &lt;code>:latest&lt;/code>, per the no-&lt;code>:latest&lt;/code> rule above. Full setup with library directory structure, mobile app config, metadata matching, and Tailscale remote access is in the &lt;a href="https://techfuelhq.com/tutorials/audiobookshelf-docker-setup-2026/">AudioBookshelf Docker guide&lt;/a>.&lt;/p>
&lt;h3 id="n8n-replaces-zapier-make-ifttt">n8n (replaces Zapier, Make, IFTTT)&lt;/h3>
&lt;p>Over 500 native integrations by &lt;a href="https://n8n.io/" rel="noopener">n8n&amp;rsquo;s own count&lt;/a>, a queue mode for production workloads that the free Community edition includes, and the ability to drop into JavaScript when the visual builder won&amp;rsquo;t do what you need. It is not open source. n8n ships under its &lt;a href="https://github.com/n8n-io/n8n/blob/master/LICENSE.md" rel="noopener">Sustainable Use License&lt;/a>, which allows use &amp;ldquo;only for your own internal business purposes or for non-commercial or personal use&amp;rdquo;. SSO, environments or log streaming need one of the &lt;a href="https://docs.n8n.io/deploy/host-n8n/community-edition-features" rel="noopener">paid plans&lt;/a>.&lt;/p>
&lt;p>Pin a release tag of &lt;code>n8nio/n8n&lt;/code>. On November 18, 2026 the &lt;code>stable&lt;/code> tag on &lt;a href="https://hub.docker.com/r/n8nio/n8n/tags" rel="noopener">Docker Hub&lt;/a> pointed at the same image as &lt;code>2.48.4&lt;/code> (November 13); the 3.x releases on the &lt;a href="https://github.com/n8n-io/n8n/releases" rel="noopener">releases page&lt;/a> are marked pre-release. The 2.0 release (December 8, 2025) removed the Start node, dropped MySQL and MariaDB as databases and &lt;a href="https://docs.n8n.io/changelog/v20-breaking-changes" rel="noopener">renamed the release channels&lt;/a> from &lt;code>latest&lt;/code>/&lt;code>next&lt;/code> to &lt;code>stable&lt;/code>/&lt;code>beta&lt;/code>, which is the kind of change a floating tag delivers without warning.&lt;/p>
&lt;h3 id="bookstack-replaces-notion-as-a-wiki--docs-site">BookStack (replaces Notion as a wiki / docs site)&lt;/h3>
&lt;p>For pure note-taking, Obsidian beats every self-hosted option. For a team or family &lt;strong>wiki&lt;/strong> — recipes, runbooks, &amp;ldquo;how the network is set up&amp;rdquo; — BookStack is the right answer. Outline is also good but the hosting story is harder. The stack is two containers, BookStack plus &lt;a href="https://www.bookstackapp.com/docs/admin/installation/" rel="noopener">MySQL 8.0+ or MariaDB 10.6+&lt;/a>.&lt;/p>
&lt;p>Pin &lt;code>lscr.io/linuxserver/bookstack:26.09.3&lt;/code> rather than &lt;code>:latest&lt;/code>, per the no-&lt;code>:latest&lt;/code> rule above. &lt;a href="https://github.com/BookStackApp/BookStack/releases" rel="noopener">v26.09.3&lt;/a> (November 11, 2026) and v26.09.2 before it were both security releases. Do not stop at an older tag. Configure LDAP if you&amp;rsquo;re already running Authentik or Keycloak for unified auth.&lt;/p>
&lt;h3 id="uptime-kuma-replaces-uptimerobot-better-stack">Uptime Kuma (replaces UptimeRobot, Better Stack)&lt;/h3>
&lt;p>Once you have 12 services running, you need to know which one died at 2 a.m. before your family tells you the internet is &amp;ldquo;broken.&amp;rdquo; Use &lt;code>louislam/uptime-kuma:2&lt;/code>, which pointed at the same image as &lt;a href="https://github.com/louislam/uptime-kuma/releases" rel="noopener">2.5.12&lt;/a> (November 17, 2026) on November 18. Not &lt;code>:latest&lt;/code>: the project&amp;rsquo;s &lt;a href="https://hub.docker.com/r/louislam/uptime-kuma" rel="noopener">Docker Hub page&lt;/a> calls that tag deprecated and bad practice and recommends &lt;code>:2&lt;/code>. A 3.0.0 beta appeared the same day; stay on &lt;code>:2&lt;/code> until 3.0 is stable. The &lt;a href="https://techfuelhq.com/tutorials/uptime-kuma-docker-setup-2026/">Uptime Kuma Docker guide&lt;/a> covers where to run it so it survives the outage it is meant to report, and &lt;a href="https://techfuelhq.com/articles/self-hosting-essentials/">the self-hosting essentials guide&lt;/a> puts it in the first-week stack.&lt;/p>
&lt;h3 id="paperless-ngx-replaces-evernote-scan-dropbox-scan-paper">Paperless-ngx (replaces Evernote scan, Dropbox Scan, paper)&lt;/h3>
&lt;p>Drop a PDF in the consume folder, OCR runs, the document is tagged, you can full-text-search five years of mail in seconds. Pin &lt;code>ghcr.io/paperless-ngx/paperless-ngx:3.5.0&lt;/code>, the &lt;a href="https://github.com/paperless-ngx/paperless-ngx/releases" rel="noopener">newest release&lt;/a> on November 18, 2026 (released November 17). The project publishes no bare &lt;code>:3&lt;/code> tag; use a full release tag or a floating minor such as &lt;code>:3.5&lt;/code>.&lt;/p>
&lt;p>Run PostgreSQL next to it. The docs recommend it for multi-user or higher-throughput setups over the default SQLite, and v3 &lt;a href="https://docs.paperless-ngx.com/migration-v3/" rel="noopener">requires&lt;/a> &lt;code>PAPERLESS_DBENGINE&lt;/code> to be set for PostgreSQL or MariaDB, because v2 inferred the engine from &lt;code>PAPERLESS_DBHOST&lt;/code> and v3 no longer does. Word or Excel documents and email files need Tika and Gotenberg containers alongside; the &lt;a href="https://docs.paperless-ngx.com/configuration/" rel="noopener">configuration docs&lt;/a> require both servers for them. The full compose stack with correspondent auto-tagging, subdirectory tag mapping, and NPM HTTPS is in the &lt;a href="https://techfuelhq.com/tutorials/paperless-ngx-docker-setup-2026/">Paperless-ngx setup guide&lt;/a>.&lt;/p>
&lt;h2 id="best-self-hosted-services-beyond-the-twelve">Best self-hosted services beyond the twelve&lt;/h2>
&lt;p>The list above covers the apps with the clearest SaaS swap. Automation comes up often enough to need its own answer, and the port-publishing check at the end of this section applies to every compose file on the page. For a self-hosted AI stack, see the &lt;a href="https://techfuelhq.com/articles/self-hosted-ai-stack-2026/">self-hosted AI stack guide&lt;/a>.&lt;/p>
&lt;h3 id="best-self-hosted-automation-n8n-or-home-assistant">Best self-hosted automation: n8n or Home Assistant&lt;/h3>
&lt;p>Two entries on the list automate things, and they cover different ground. n8n moves data between web services and APIs, the way Zapier does. Home Assistant automates devices in your home. &lt;a href="https://www.home-assistant.io/docs/automation/basics/" rel="noopener">Home Assistant&amp;rsquo;s automation guide&lt;/a> splits every automation into a trigger, an optional condition and an action, and builds them in the visual editor under Settings, then Automations &amp;amp; scenes. Choose n8n when the trigger is a web event or a schedule across services. Choose Home Assistant when the trigger is a sensor, a person arriving or a device changing state.&lt;/p>
&lt;p>If you pick n8n, &lt;a href="https://docs.n8n.io/deploy/host-n8n/" rel="noopener">its self-hosting overview&lt;/a> says that without a license key it runs as the free Community edition, and it names Docker Compose as the best fit for production deployments with databases and additional services. n8n&amp;rsquo;s &lt;a href="https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose/" rel="noopener">Docker Compose guide&lt;/a> serves the editor on port 5678 and covers three limits that matter:&lt;/p>
&lt;ul>
&lt;li>The compose file defines no database service, so n8n uses its built-in SQLite database, stored with its encryption key in the &lt;code>n8n-data&lt;/code> volume.&lt;/li>
&lt;li>For a production instance, n8n says to swap in PostgreSQL.&lt;/li>
&lt;li>The guide asks for at least 4 GB of RAM and 2 vCPUs, because its stack includes a Docker-in-Docker sandbox for n8n Assistant. The table above plans for that.&lt;/li>
&lt;/ul>
&lt;h3 id="check-what-docker-publishes-before-you-move-a-service-home">Check what Docker publishes before you move a service home&lt;/h3>
&lt;p>The compose files on this page publish ports such as 2283 (Immich) and 8096 (Jellyfin) without a host address. Docker&amp;rsquo;s &lt;a href="https://docs.docker.com/engine/network/port-publishing/" rel="noopener">port-publishing page&lt;/a> calls publishing insecure by default, because the port becomes available to the outside world as well as the Docker host. Adding &lt;code>127.0.0.1&lt;/code> to the publish flag, as in &lt;code>-p 127.0.0.1:8080:80&lt;/code>, limits the port to the host itself, and a host IP such as &lt;code>192.168.1.100:8080:80&lt;/code> limits it to that address. Docker&amp;rsquo;s &lt;a href="https://docs.docker.com/engine/network/packet-filtering-firewalls/" rel="noopener">firewall page&lt;/a> adds that published container traffic is diverted before it reaches ufw&amp;rsquo;s rules, so a ufw rule does not protect it. If a service should only be reachable through a reverse proxy or Tailscale, bind it to localhost.&lt;/p>
&lt;h2 id="what-hardware-runs-all-12">What hardware runs all 12&lt;/h2>
&lt;p>The table&amp;rsquo;s RAM figures add up to 26.75 GB with all twelve running at once: about 27 GB, which leaves roughly 5 GB of a 32 GB box. Treat 32 GB as the floor. CPU is less of a problem than people think. Immich&amp;rsquo;s machine learning is the spike, and the rest idle hard.&lt;/p>
&lt;p>&lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">Best Mini PCs for a Homelab in 2026&lt;/a> picks the Minisforum MS-01 for a host you plan to grow and a used OptiPlex 7060 Micro or ThinkCentre M720q to start cheap, with 32 GB as the practical minimum. The used 8th-gen boxes run the stack, but if Jellyfin will transcode, buy an N100 or an 11th-gen-or-newer chip, for the Quick Sync reason above. Boot from NVMe and keep media on a separate disk. The &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox vs TrueNAS vs Unraid comparison&lt;/a> covers the OS choice, and the &lt;a href="https://techfuelhq.com/articles/proxmox-mini-pc-setup/">Proxmox mini PC setup walkthrough&lt;/a> takes a new box from USB stick to first VM.&lt;/p>
&lt;p>For one box that holds the whole list, the MS-01 ships ready with 32 GB: on November 17, 2026, Newegg listed the MINISFORUM MS-01 with a Core i5-12600H, 32GB of RAM and a 1TB SSD at $999.00.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=MINISFORUM&amp;#43;MS-01&amp;#43;i5-12600H&amp;#43;32GB&amp;#43;1TB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/self-hosted-apps-replace-saas-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fminisforum-barebone-systems-mini-pc-intel-core-i5-12600h%2Fp%2F2SW-002G-000S5%3Fitem%3D9SIBJ6VKG46759" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/self-hosted-apps-replace-saas-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>An old gaming PC in a closet skips the purchase; the &lt;a href="https://techfuelhq.com/articles/repurpose-gaming-pc-proxmox-server-2026/">repurpose-as-server guide&lt;/a> works out whether its idle draw is worth it, and the &lt;a href="https://techfuelhq.com/tools/pc-builder/">PC Builder&lt;/a> checks socket/RAM/PSU/GPU-clearance compatibility if you build a tower instead. If the stack outgrows a single 2.5GbE link, the &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE homelab networking guide&lt;/a> covers the cheap switch options.&lt;/p>
&lt;h2 id="does-it-save-money">Does it save money?&lt;/h2>
&lt;p>Two of the subscriptions this stack replaces, read from the vendors&amp;rsquo; pricing pages on November 18, 2026: &lt;a href="https://1password.com/pricing/personal" rel="noopener">1Password Families&lt;/a> has a regular price of $5.99 a month billed yearly (new customers were offered $4.49 for the first year), and &lt;a href="https://zapier.com/pricing" rel="noopener">Zapier Professional&lt;/a> starts from $19.99 a month. Together that is $25.98 a month, or $311.76 a year, before Google One or Plex Pass; check those on their own plan pages, because their prices did not load as text on November 18.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/tools/selfhost-breakeven/">Self-Hosting Break-Even Calculator&lt;/a> takes your own subscriptions, hardware price and electricity rate and returns the month the box pays for itself, and the &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">Power &amp;amp; Cost Calculator&lt;/a> turns the host&amp;rsquo;s idle watts into a yearly bill at your rate.&lt;/p>
&lt;h3 id="migration-data-budget">Can my internet plan handle the first photo migration?&lt;/h3>
&lt;p>Before you download a photo library to the new server, check when your home internet allowance resets. &lt;a href="https://support.google.com/accounts/answer/3024190" rel="noopener">Google Takeout&lt;/a> lets you download a Photos archive without deleting the Google copy. Count the download across your home internet connection once. Copying that archive from a laptop to Immich entirely over your local network does not send it through the ISP a second time. Uploading an off-site backup is a separate transfer if your provider counts uploads. Split the work into batches if needed; keep a verified copy before removing anything from the old service.&lt;/p>
&lt;p>Here is a sample decision using a 900 GB allowance from April 15 through May 14. By the end of April 29, the household meter shows 420 GB, including a 120 GB one-time transfer that already finished. That leaves 300 GB of ordinary use over 15 days, or 20 GB/day. If the next 15 days look similar, reserve another 300 GB for normal use. You also need a 60 GB off-site upload before reset. &lt;strong>That puts you at 780 GB before the optional 180 GB photo download.&lt;/strong> Downloading it now projects 960 GB, or 60 GB over. Waiting until May 15 leaves 120 GB of room this period and moves the download into the next one.&lt;/p>
&lt;p>If your plan charged per started 50 GB block, 60 GB of excess would use two blocks. Whether that costs money depends on the rate, any courtesy allowance and any fee ceiling on your account. The &lt;a href="https://techfuelhq.com/tools/data-usage-calculator/#billing-cycle">billing-cycle worksheet&lt;/a> compares both dates and lets you enter an unlimited add-on price if it covers this period.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;p>Each version and tag below was checked against the project&amp;rsquo;s releases or image registry on November 18, 2026, each requirement against its docs and each price against the vendor&amp;rsquo;s page.&lt;/p>
&lt;ul>
&lt;li>Releases: &lt;a href="https://github.com/immich-app/immich/releases" rel="noopener">Immich&lt;/a>, &lt;a href="https://github.com/nextcloud/all-in-one/releases" rel="noopener">Nextcloud AIO&lt;/a>, &lt;a href="https://github.com/dani-garcia/vaultwarden/releases" rel="noopener">Vaultwarden&lt;/a>, &lt;a href="https://github.com/paperless-ngx/paperless-ngx/releases" rel="noopener">Paperless-ngx&lt;/a>, &lt;a href="https://github.com/jellyfin/jellyfin/releases" rel="noopener">Jellyfin&lt;/a>, &lt;a href="https://github.com/AdguardTeam/AdGuardHome/releases" rel="noopener">AdGuard Home&lt;/a>, &lt;a href="https://github.com/advplyr/audiobookshelf/releases" rel="noopener">AudioBookshelf&lt;/a>, &lt;a href="https://github.com/n8n-io/n8n/releases" rel="noopener">n8n&lt;/a>, &lt;a href="https://github.com/BookStackApp/BookStack/releases" rel="noopener">BookStack&lt;/a>, &lt;a href="https://github.com/louislam/uptime-kuma/releases" rel="noopener">Uptime Kuma&lt;/a>, &lt;a href="https://github.com/RocketChat/Rocket.Chat/releases" rel="noopener">Rocket.Chat&lt;/a>&lt;/li>
&lt;li>Requirements and setup: &lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">Immich requirements&lt;/a>, &lt;a href="https://github.com/nextcloud/all-in-one" rel="noopener">Nextcloud All-in-One&lt;/a>, &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki" rel="noopener">Vaultwarden wiki&lt;/a>, &lt;a href="https://jellyfin.org/docs/general/administration/hardware-selection/" rel="noopener">Jellyfin hardware selection&lt;/a>, &lt;a href="https://www.home-assistant.io/installation/" rel="noopener">Home Assistant installation&lt;/a>, &lt;a href="https://docs.paperless-ngx.com/configuration/" rel="noopener">Paperless-ngx configuration&lt;/a>, &lt;a href="https://www.bookstackapp.com/docs/admin/installation/" rel="noopener">BookStack installation&lt;/a>, &lt;a href="https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose/" rel="noopener">n8n Docker Compose install&lt;/a>, &lt;a href="https://docs.docker.com/engine/network/port-publishing/" rel="noopener">Docker port publishing&lt;/a>&lt;/li>
&lt;li>Plans and prices: &lt;a href="https://tailscale.com/pricing" rel="noopener">Tailscale&lt;/a>, &lt;a href="https://1password.com/pricing/personal" rel="noopener">1Password&lt;/a>, &lt;a href="https://zapier.com/pricing" rel="noopener">Zapier&lt;/a>, &lt;a href="https://one.google.com/about/plans" rel="noopener">Google One plans&lt;/a>, &lt;a href="https://www.plex.tv/plans/" rel="noopener">Plex&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>Email corrections to &lt;a href="mailto:contact@techfuelhq.com">contact@techfuelhq.com&lt;/a>.&lt;/p></description></item><item><title>Synology or Build? The Five-Year NAS Cost</title><link>https://techfuelhq.com/homelab/synology-vs-diy-nas-five-year-cost-2026/</link><pubDate>Mon, 07 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/synology-vs-diy-nas-five-year-cost-2026/</guid><atom:updated>2026-11-18T06:05:00Z</atom:updated><description>&lt;p>A four-bay Synology and a four-bay box you assemble yourself both sit in a cupboard drawing power every hour for five years. Everyone assumes the DIY one is cheaper to run and that the electricity is where the appliance premium comes back. Neither half of that is true.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/homelab/nas-os-month-eight-2026/">NAS operating system comparison&lt;/a> ends by saying all four appliances are wrong if what you want is a machine you administer yourself. This page is that purchase, costed: &lt;strong>what does five years of each actually take out of your account, drives excluded?&lt;/strong>&lt;/p>
&lt;h2 id="the-five-year-number">The five-year number&lt;/h2>
&lt;p>Drives are excluded from every row because they are the same purchase either way — four 8TB NAS drives cost what they cost whichever box they go in. What is left is the enclosure, the memory, a boot device where one is needed, the operating system, and sixty months of electricity.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Five years, drives excluded&lt;/th>
&lt;th scope="col" style="text-align: right">Hardware&lt;/th>
&lt;th scope="col" style="text-align: right">Electricity&lt;/th>
&lt;th scope="col" style="text-align: right">&lt;strong>Total&lt;/strong>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Five years, drives excluded">&lt;strong>Synology DS925+&lt;/strong>, DSM&lt;/td>
&lt;td style="text-align: right" data-label="Hardware">$889.99&lt;/td>
&lt;td style="text-align: right" data-label="Electricity">$226&lt;/td>
&lt;td style="text-align: right" data-label="Total">&lt;strong>$1,116&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Five years, drives excluded">&lt;strong>AOOSTAR WTR Pro 5825U&lt;/strong>, TrueNAS&lt;/td>
&lt;td style="text-align: right" data-label="Hardware">$598.98&lt;/td>
&lt;td style="text-align: right" data-label="Electricity">$169–$193&lt;/td>
&lt;td style="text-align: right" data-label="Total">&lt;strong>$768–$792&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Five years, drives excluded">Same build, Unraid Lifetime&lt;/td>
&lt;td style="text-align: right" data-label="Hardware">$847.98&lt;/td>
&lt;td style="text-align: right" data-label="Electricity">$169–$193&lt;/td>
&lt;td style="text-align: right" data-label="Total">$1,017–$1,041&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Five years, drives excluded">Same build, Unraid Starter&lt;/td>
&lt;td style="text-align: right" data-label="Hardware">$647.98&lt;/td>
&lt;td style="text-align: right" data-label="Electricity">$169–$193&lt;/td>
&lt;td style="text-align: right" data-label="Total">$817–$841&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>&lt;strong>The DIY build is $323 to $347 cheaper across five years, and electricity accounts for $32 to $56 of that.&lt;/strong> Roughly a tenth. The rest is the box price and the fact that DSM is included while an Unraid licence is not.&lt;/p>
&lt;p>Buy the most expensive Unraid tier and the DIY route still finishes $74 to $98 ahead. That is the whole electricity argument, resolved: it is a rounding error against a $291 difference in sticker price.&lt;/p>
&lt;h2 id="what-the-boxes-actually-draw">What the boxes actually draw&lt;/h2>
&lt;p>These are NAS Compares&amp;rsquo; measurements, taken with the drives installed and the array built:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Machine&lt;/th>
&lt;th scope="col" style="text-align: right">Measured idle&lt;/th>
&lt;th scope="col" style="text-align: right">Measured load&lt;/th>
&lt;th scope="col" style="text-align: right">Five years at idle&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Machine">Synology DS925+&lt;/td>
&lt;td style="text-align: right" data-label="Measured idle">~28W&lt;/td>
&lt;td style="text-align: right" data-label="Measured load">62–64W&lt;/td>
&lt;td style="text-align: right" data-label="Five years at idle">$226&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Machine">AOOSTAR WTR Pro (Ryzen 7 5825U)&lt;/td>
&lt;td style="text-align: right" data-label="Measured idle">21–24W&lt;/td>
&lt;td style="text-align: right" data-label="Measured load">64–66W&lt;/td>
&lt;td style="text-align: right" data-label="Five years at idle">$169–$193&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Machine">Topton MW-N100-NAS ITX board&lt;/td>
&lt;td style="text-align: right" data-label="Measured idle">28.2W&lt;/td>
&lt;td style="text-align: right" data-label="Measured load">55W peak&lt;/td>
&lt;td style="text-align: right" data-label="Five years at idle">$227&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Machine">Topton MW-N305-NAS ITX board&lt;/td>
&lt;td style="text-align: right" data-label="Measured idle">27–28W&lt;/td>
&lt;td style="text-align: right" data-label="Measured load">64–66W&lt;/td>
&lt;td style="text-align: right" data-label="Five years at idle">$218–$226&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Rob Andrews at NAS Compares recorded the DS925+ at &amp;ldquo;approximately 28 watts&amp;rdquo; in a fully idle state, base apps installed and the system not being accessed, rising to 62–64W with all four bays filled, SSDs in, the CPU under strain and both 2.5GbE connections active (&lt;a href="https://nascompares.com/2025/05/02/synology-ds925-nas-review/" rel="noopener">review, 2 May 2025&lt;/a>). The &lt;a href="https://nascompares.com/review/aoostar-wtr-pro-nas-review/" rel="noopener">WTR Pro review of 11 September 2024&lt;/a> gives &amp;ldquo;an average of 21-24W when the drives and system were in Idle&amp;rdquo;, and 64–66W with the drives being read and the CPU at 40–50%. The array in that review was four Seagate IronWolf 4TB drives in a one-disk-redundancy ZFS pool under Unraid, stated in the throughput section rather than beside the idle figure.&lt;/p>
&lt;p>Note what the load column does. Under actual work the appliance and the DIY box land within two watts of each other. The idle spread is the entire difference, and the idle spread is worth $6 to $11 a year.&lt;/p>
&lt;h2 id="building-your-own-does-not-lower-the-idle-draw">Building your own does not lower the idle draw&lt;/h2>
&lt;p>This is the part that gets assumed and is wrong often enough to cost people money.&lt;/p>
&lt;p>The same reviewer, same method, measured the &lt;a href="https://nascompares.com/review/topton-n100-10gbe-nas-motherboard-review-mw-n100-nas/" rel="noopener">Topton MW-N100-NAS&lt;/a> — the six-SATA, 10GbE ITX board a parts-built four-bay usually starts from — at &amp;ldquo;around 28.2W with drives connected.&amp;rdquo; That is the Synology&amp;rsquo;s figure to a tenth of a watt, from a board whose CPU carries a 6W TDP. The &lt;a href="https://nascompares.com/review/n305-6-bay-10gbe-nas-motherboard-review-mw-n305-nas/" rel="noopener">N305 version of the same board&lt;/a> recorded &amp;ldquo;idle power consumption of just 27-28 watts with six connected drives in hibernation&amp;rdquo; — with the drives parked, which should have been the best case.&lt;/p>
&lt;p>A 6W processor does not produce a 6W machine. The SATA controller, three network interfaces and the board&amp;rsquo;s own power delivery set the floor, and on these boards the floor is high. &lt;strong>If low idle is the goal, the board is the wrong place to look for it.&lt;/strong> The laptop-class SoC in the AOOSTAR box is what buys the 21W, not the fact that you assembled it.&lt;/p>
&lt;p>Our &lt;a href="https://techfuelhq.com/homelab/24-7-homelab-idle-power-costs-2026/">idle power reference for homelab hardware&lt;/a> has the wider device-by-device table if you are budgeting a whole rack rather than one NAS.&lt;/p>
&lt;h2 id="the-setting-that-beats-both-boxes">The setting that beats both boxes&lt;/h2>
&lt;p>Synology publishes its own numbers, and they disagree with the measured one in a way worth understanding rather than averaging.&lt;/p>
&lt;p>The &lt;a href="https://www.synology.com/en-us/products/DS925&amp;#43;" rel="noopener">DS925+ product specification&lt;/a>, last updated 6 August 2026, lists &lt;strong>37.91 watts (Access)&lt;/strong> and &lt;strong>12.33 watts (HDD Hibernation)&lt;/strong>. NAS Compares measured 28W. None of these three contradicts the others, because they describe three different machines-in-a-moment: drives spinning and being read, drives spun up but nothing being served, drives parked.&lt;/p>
&lt;p>Priced over five years at $0.184/kWh:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">DS925+ state&lt;/th>
&lt;th scope="col" style="text-align: right">Watts&lt;/th>
&lt;th scope="col" style="text-align: right">Five years&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="DS925&amp;#43; state">Access (Synology, published)&lt;/td>
&lt;td style="text-align: right" data-label="Watts">37.91&lt;/td>
&lt;td style="text-align: right" data-label="Five years">$306&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="DS925&amp;#43; state">Fully idle (NAS Compares, measured)&lt;/td>
&lt;td style="text-align: right" data-label="Watts">~28&lt;/td>
&lt;td style="text-align: right" data-label="Five years">$226&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="DS925&amp;#43; state">HDD hibernation (Synology, published)&lt;/td>
&lt;td style="text-align: right" data-label="Watts">12.33&lt;/td>
&lt;td style="text-align: right" data-label="Five years">$99&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>&lt;strong>That $206 swing on one machine is between three and a half and six times the $32-to-$56 gap between the two machines.&lt;/strong> Whether your drives get to park matters more than which enclosure you bought, and it is the only power lever on this page big enough to notice.&lt;/p>
&lt;p>It is also the lever most people never pull. Anything that touches the array on a timer — a surveillance recorder, a container writing logs, a backup client polling every few minutes, a media server refreshing metadata — wakes the drives and keeps them awake. Hibernation is a real setting and mostly a theoretical saving. Assume the 28W figure, run the numbers in the &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">power cost calculator&lt;/a> against your own utility rate, and treat anything better as a bonus.&lt;/p>
&lt;h2 id="what-the-291-buys-and-what-it-does-not">What the $291 buys, and what it does not&lt;/h2>
&lt;p>The gap in the hardware column is &lt;span class="claim" data-claim-key="ds925plus.usd" data-claim-value="889.99" data-claim-scope="Newegg, 4-bay diskless, US" data-claim-date="2026-08-17">$889.99&lt;/span>
against &lt;span class="claim" data-claim-key="wtrpro5825u.usd" data-claim-value="379.00" data-claim-scope="AOOSTAR direct, US warehouse" data-claim-date="2026-09-07">$379.00&lt;/span>
for the AOOSTAR barebone, plus &lt;span class="claim" data-claim-key="ddr4.16gb.sodimm.usd" data-claim-value="129.99" data-claim-scope="Newegg, 16GB DDR4-3200 SODIMM" data-claim-date="2026-08-17">$129.99&lt;/span>
for a 16GB DDR4-3200 SO-DIMM and &lt;span class="claim" data-claim-key="boot.nvme.512gb.usd" data-claim-value="89.99" data-claim-scope="Newegg, 512GB NVMe" data-claim-date="2026-08-17">$89.99&lt;/span>
for a boot NVMe the Synology does not need, since DSM installs onto the array.&lt;/p>
&lt;p>For that $291 you get DSM, a three-year warranty you can extend to five by buying an extension, and a support line. You do not get more hardware. The DS925+ ships 4GB of DDR4 ECC against the DIY box&amp;rsquo;s 16GB, an embedded Ryzen V1500B against a Ryzen 7 5825U, and two 2.5GbE ports against two 2.5GbE ports.&lt;/p>
&lt;p>Three constraints ride along with the appliance, all of them from Synology&amp;rsquo;s own documents:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>M.2 is still closed.&lt;/strong> The &lt;a href="https://www.synology.com/en-us/company/news/article/dsm73" rel="noopener">DSM 7.3 announcement&lt;/a> of 8 October 2025 reopened third-party drives for storage pools on 25 model year units, and its footnote reads: &amp;ldquo;Creation of M.2 based storage pool and cache still requires drives on the HCL.&amp;rdquo; The specification sheet says the same. A Synology SNV3410-400G listed at &lt;span class="claim" data-claim-key="snv3410.400g.usd" data-claim-value="474.99" data-claim-scope="Newegg, listed price, US" data-claim-date="2026-09-07">$474.99&lt;/span>
on Newegg on 7 September 2026; a 512GB ADATA Legend 710 you cannot use for that pool listed at $89.99 in the August feed.&lt;/li>
&lt;li>&lt;strong>Memory expansion is conditioned.&lt;/strong> The DS925+ specification states Synology &amp;ldquo;will not provide complete product warranty or technical support if non-Synology memory modules are used for memory expansion.&amp;rdquo; Going past 4GB means buying their module or accepting that.&lt;/li>
&lt;li>&lt;strong>No hardware transcoding, at all.&lt;/strong> The specification sheet lists no video transcoding section for the DS925+, and none for the cheaper DS425+ either. The drive policy got walked back in a point release. This one did not, and it is the change on the 2025 Plus line that deserved the attention the drive policy got. If transcoding is why you are shopping, the &lt;a href="https://techfuelhq.com/homelab/best-nas-for-plex-jellyfin-2026/">NAS transcoding guide&lt;/a> sorts the field by that spec alone.&lt;/li>
&lt;/ul>
&lt;p>Synology-branded drives cost real money over the equivalent Exos for no benefit I can identify. That was the drives. The M.2 price above is the same policy, still in force.&lt;/p>
&lt;h2 id="build-it-and-run-truenas">Build it and run TrueNAS&lt;/h2>
&lt;p>&lt;strong>Buy the AOOSTAR WTR Pro 5825U barebone, a 16GB DDR4-3200 SO-DIMM and a cheap boot NVMe, and put &lt;a href="https://techfuelhq.com/storage/unraid-vs-truenas-vs-omv-vs-proxmox-2026/">TrueNAS&lt;/a> on it.&lt;/strong> That is $598.98 in hardware, nothing for the operating system, and $169 to $193 of electricity over five years. It gives you four times the memory, a genuinely faster processor, ZFS checksumming instead of Btrfs on a locked appliance, any NVMe you like in the M.2 slots, and a machine you can repurpose when your storage needs change.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=AOOSTAR&amp;#43;WTR&amp;#43;PRO&amp;#43;5825U&amp;#43;4&amp;#43;bay&amp;#43;NAS&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/synology-vs-diy-nas-five-year-cost-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-09-07&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2F3C6-038N-021X9" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/synology-vs-diy-nas-five-year-cost-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-09-07&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Pay for Unraid instead of TrueNAS if your drives are mismatched sizes and you want to add one at a time — &lt;span class="claim" data-claim-key="unraid.starter.usd" data-claim-value="49" data-claim-scope="unraid.net, one-time licence" data-claim-date="2026-09-07">$49&lt;/span>
Starter caps at six storage devices with one year of updates, &lt;span class="claim" data-claim-key="unraid.lifetime.usd" data-claim-value="249" data-claim-scope="unraid.net, one-time licence" data-claim-date="2026-09-07">$249&lt;/span>
Lifetime is unlimited devices and updates forever. Even the expensive tier keeps the DIY route ahead on five-year cost. It just stops being the obvious call.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/homelab/best-budget-nas-builds-2025/">budget NAS build guide&lt;/a> has the full parts list, the recertified-drive route, and what the memory shortage did to every line of it.&lt;/p>
&lt;h2 id="buy-the-ds925-if-dsm-is-the-product">Buy the DS925+ if DSM is the product&lt;/h2>
&lt;p>Synology still makes the best NAS operating system. Not the hardware. Not the drive list. The software, which is what you are still using at month eight.&lt;/p>
&lt;p>&lt;strong>Buy the DS925+ if you want an appliance that works the day it arrives, an app catalogue that does not run out, and a phone number when it breaks.&lt;/strong> You are paying $291 up front and $6 to $11 a year more in electricity for exactly that, and it is a defensible purchase — it is just not a cheaper one, and no power calculation is going to make it one.&lt;/p>
&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Synology&amp;#43;DiskStation&amp;#43;DS925&amp;#43;4&amp;#43;bay&amp;#43;diskless&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/synology-vs-diy-nas-five-year-cost-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-09-07&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16822108847" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/synology-vs-diy-nas-five-year-cost-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-09-07&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>The cheaper door into DSM is the DS425+ at &lt;span class="claim" data-claim-key="ds425plus.usd" data-claim-value="599.99" data-claim-scope="Newegg, 4-bay diskless, US" data-claim-date="2026-08-17">$599.99&lt;/span>
— within a dollar of the DIY build&amp;rsquo;s hardware total, and &lt;a href="https://www.synology.com/en-us/products/DS425&amp;#43;" rel="noopener">Synology&amp;rsquo;s sheet for it&lt;/a> lists a Celeron J4125, 2GB of non-ECC memory and no transcoding section. It closes the price gap by giving up the hardware.&lt;/p>
&lt;p>Prices move, the memory market in 2026 moves weekly, and two of these listings carry marketplace sellers. Read the seller name before the price.&lt;/p>
&lt;h2 id="wrong-for">Wrong for&lt;/h2>
&lt;p>&lt;strong>The DIY build is wrong&lt;/strong> if you want an app catalogue rather than a compose file, if nobody in the house can restore a pool at 11pm, or if you were counting on a support contract.&lt;/p>
&lt;p>&lt;strong>The DS925+ is wrong&lt;/strong> if you need hardware transcoding, if you want a third-party NVMe cache, or if you are buying it because someone told you the appliance pays for itself in electricity. It does not. At the measured wattages it costs $6 to $11 a year more to run than the box it is already more expensive than.&lt;/p>
&lt;p>&lt;strong>Both are wrong&lt;/strong> if you are choosing on power alone. Across every machine on this page the five-year electricity spread is $169 to $227 — under sixty dollars end to end. Choose on the software, the drive policy and the sticker, then set your utility rate in the &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">power calculator&lt;/a> and stop thinking about it.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://nascompares.com/2025/05/02/synology-ds925-nas-review/" rel="noopener">NAS Compares — Synology DS925+ NAS Review&lt;/a>, 2 May 2025 — measured idle and load draw, noise, thermals&lt;/li>
&lt;li>&lt;a href="https://nascompares.com/review/aoostar-wtr-pro-nas-review/" rel="noopener">NAS Compares — Aoostar WTR Pro NAS Review&lt;/a>, 11 Sep 2024 — measured idle and load draw with four IronWolf 4TB drives&lt;/li>
&lt;li>&lt;a href="https://nascompares.com/review/topton-n100-10gbe-nas-motherboard-review-mw-n100-nas/" rel="noopener">NAS Compares — Topton MW-N100-NAS motherboard review&lt;/a> (14 Nov 2024, updated 4 Dec 2024) and &lt;a href="https://nascompares.com/review/n305-6-bay-10gbe-nas-motherboard-review-mw-n305-nas/" rel="noopener">MW-N305-NAS review&lt;/a>, 4 Dec 2024 — measured ITX board idle draw&lt;/li>
&lt;li>&lt;a href="https://www.synology.com/en-us/products/DS925&amp;#43;" rel="noopener">Synology DS925+ specifications&lt;/a> and the &lt;a href="https://global.synologydownload.com/download/Document/Hardware/ProductSpec/DiskStation/25-year/DS925&amp;#43;/enu/Product_Spec_DS925&amp;#43;_enu.pdf" rel="noopener">product specification PDF&lt;/a>, last updated 6 Aug 2026 — published wattages, memory and M.2 conditions, warranty&lt;/li>
&lt;li>&lt;a href="https://www.synology.com/en-us/products/DS425&amp;#43;" rel="noopener">Synology DS425+ specifications&lt;/a> — Celeron J4125, 2GB non-ECC, no transcoding section&lt;/li>
&lt;li>&lt;a href="https://www.synology.com/en-us/company/news/article/dsm73" rel="noopener">Synology DSM 7.3 announcement&lt;/a>, 8 Oct 2025 — third-party drive reversal and the surviving M.2 HCL footnote&lt;/li>
&lt;li>&lt;a href="https://aoostar.com/products/aoostar-wtr-pro-4-bay-90t-storage-amd-ryzen-7-5825u-nas-mini-pc-support-2-5-3-5-hdd-%E5%A4%8D%E5%88%B6" rel="noopener">AOOSTAR WTR PRO 5825U product page&lt;/a> — barebone price, DDR4-3200 memory support, package contents&lt;/li>
&lt;li>&lt;a href="https://unraid.net/pricing" rel="noopener">Unraid pricing&lt;/a> — the one-time licence tiers, device caps and update terms&lt;/li>
&lt;li>&lt;a href="https://www.eia.gov/electricity/monthly/epm_table_grapher.php?t=epmt_5_3" rel="noopener">EIA Electric Power Monthly, Table 5.3&lt;/a> — 18.44 cents/kWh, May 2026 US residential average&lt;/li>
&lt;/ul>
&lt;p>Email corrections to &lt;a href="mailto:contact@techfuelhq.com">contact@techfuelhq.com&lt;/a>.&lt;/p></description></item><item><title>GPU Overheating: Is Your Graphics Card Too Hot? (2026)</title><link>https://techfuelhq.com/articles/gpu-overheating-2026/</link><pubDate>Fri, 10 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/gpu-overheating-2026/</guid><atom:updated>2026-11-18T06:05:00Z</atom:updated><description>&lt;p>A GPU is overheating when its core temperature reaches the card&amp;rsquo;s published maximum and the clocks fall to hold it there. Below that limit, with the fans responding and the clocks holding, it isn&amp;rsquo;t overheating, whatever the hotspot line in your overlay says.&lt;/p>
&lt;p>NVIDIA publishes that maximum for its desktop cards: 85 to 90 °C across the RTX 50 series (85 °C on the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5070-family/" rel="noopener">RTX 5070&lt;/a>, 88 °C on the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5080/" rel="noopener">RTX 5080&lt;/a>, 90 °C on the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5090/" rel="noopener">RTX 5090&lt;/a>) and 90 °C on every desktop RTX 40 card. NVIDIA says those figures describe its Founders Edition or reference design and that add-in-card specifications may vary. AMD&amp;rsquo;s &lt;a href="https://www.amd.com/en/products/graphics/desktops/radeon/9000-series/amd-radeon-rx-9070xt.html" rel="noopener">RX 9070 XT page&lt;/a> lists no maximum temperature. The &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">safe GPU temperature guide&lt;/a> has the limit for every card; this page is the order to check things in when you&amp;rsquo;re near it.&lt;/p>
&lt;h2 id="step-1-read-the-core-temperature-against-your-cards-limit">Step 1: Read the core temperature against your card&amp;rsquo;s limit&lt;/h2>
&lt;p>Use your normal game at stock settings. Open &lt;a href="https://www.hwinfo.com/" rel="noopener">HWiNFO&lt;/a> or the board maker&amp;rsquo;s monitoring tool and note the exact card model and the name of the sensor. On supported Radeon cards, &lt;a href="https://www.amd.com/en/resources/support-articles/faqs/DH3-038.html" rel="noopener">AMD Software&amp;rsquo;s Performance Metrics&lt;/a> separates GPU current and junction temperatures and can log clock speed and fan RPM alongside them.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you see&lt;/th>
&lt;th scope="col">What to compare&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you see">GPU temperature&lt;/td>
&lt;td data-label="What to compare">The card&amp;rsquo;s own maximum. On an RTX 5080 that is 88 °C; the &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">full table&lt;/a> covers the others. Don&amp;rsquo;t apply it to a hotspot or to another card.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">GPU hotspot or junction&lt;/td>
&lt;td data-label="What to compare">The simultaneous GPU temperature. NVIDIA publishes no hotspot maximum, so a hotspot number has no official limit to hit.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Memory or memory junction&lt;/td>
&lt;td data-label="What to compare">Keep it separate from the GPU hotspot; compare only with guidance for that exact memory and board.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Falling clock speed&lt;/td>
&lt;td data-label="What to compare">The reported reason, in Step 2. A lower clock on its own doesn&amp;rsquo;t tell you whether heat or power caused it.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>On an NVIDIA card, &lt;code>nvidia-smi --query-gpu=name,temperature.gpu,temperature.gpu.tlimit --format=csv&lt;/code> prints the core temperature and the T.Limit margin, the degrees left before the maximum operating temperature. &lt;a href="https://docs.nvidia.com/deploy/nvidia-smi/index.html" rel="noopener">NVIDIA&amp;rsquo;s nvidia-smi documentation&lt;/a> says a T.Limit of 0 °C or lower means the GPU may optimize its clock for thermal conditions, and that not every product reports it.&lt;/p>
&lt;p>This step rules out the most common false alarm: a high number read off the wrong sensor. If the core stays well inside its limit, skip to &lt;a href="#when-its-not-really-the-temperature">When it&amp;rsquo;s not really the temperature&lt;/a>. If the temperature climbs to the limit or the system becomes unstable, end the load. There is no need to run a stress test to force a shutdown.&lt;/p>
&lt;h2 id="step-2-check-whether-the-clocks-actually-fall">Step 2: Check whether the clocks actually fall&lt;/h2>
&lt;p>A card at its maximum is supposed to protect itself, so the question is whether heat is costing you clock speed. &lt;a href="https://docs.nvidia.com/deploy/nvidia-smi/index.html" rel="noopener">nvidia-smi&lt;/a> separates the reasons: SW Thermal Slowdown means a software algorithm is reducing clocks below the requested clocks because the GPU is hotter than its Max Operating Temp, and SW Power Cap means clocks are being reduced because the GPU is consuming too much power. NVIDIA&amp;rsquo;s &lt;a href="https://docs.nvidia.com/deploy/nvml-api/latest/api/group__nvmlClocksEventReasons.html" rel="noopener">NVML reference&lt;/a> describes HW Thermal Slowdown as cutting core clocks by a factor of 2 or more.&lt;/p>
&lt;p>This step rules out a power limit dressed up as a heat problem. A power cap is not a cooling fault and no amount of airflow fixes it. The &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling guide&lt;/a> walks through reading these flags on both NVIDIA and AMD cards.&lt;/p>
&lt;h2 id="step-3-compare-the-same-card-under-the-same-load">Step 3: Compare the same card under the same load&lt;/h2>
&lt;p>Have an older log? Repeat the game scene at stock settings and record the room temperature and fan speed, because a case that took in cool air in January may behave differently in a warm room even when the card and its cooler haven&amp;rsquo;t changed. Write down the game, the time under load and the tool version. No older log? Start one now. If the same scene repeatedly brings on a thermal limit or lost performance, send both runs to support.&lt;/p>
&lt;p>If you track the hotspot too, take it from the same session as the core and don&amp;rsquo;t subtract separately recorded peaks that may have happened minutes apart. On RTX 50 cards, CPUID&amp;rsquo;s &lt;a href="https://www.cpuid.com/softwares/hwmonitor.html" rel="noopener">HWMonitor history&lt;/a> lists the hotspot reading as fixed in version 1.65.1 on July 16, 2026. What a wide core-to-hotspot gap can and can&amp;rsquo;t tell you is in the &lt;a href="https://techfuelhq.com/articles/gpu-hotspot-temperature-2026/">GPU hotspot temperature guide&lt;/a>; a gap on its own doesn&amp;rsquo;t identify dust, the mount or the paste.&lt;/p>
&lt;p>This step rules out the room, the scene and the tool as the thing that changed.&lt;/p>
&lt;h2 id="step-4-clean-the-dust-and-fix-case-airflow">Step 4: Clean the dust and fix case airflow&lt;/h2>
&lt;p>Keep the cooler on the board. Start with the case and see what changes in the same scene.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;p>If the intake filters or accessible fins are visibly blocked, clean them according to the board and case makers&amp;rsquo; instructions. Power down, open the case, and blow the fins and fans out with a can of compressed air (&lt;a href="https://www.amazon.com/s?k=compressed&amp;#43;air&amp;#43;duster&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" data-affiliate-page="/articles/gpu-overheating-2026/" data-affiliate-slot="inline" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false">Amazon&lt;/a>, &lt;a href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3Dcompressed%2Bair%2Bduster" rel="nofollow sponsored noopener" data-affiliate-page="/articles/gpu-overheating-2026/" data-affiliate-slot="inline" data-affiliate-retailer="Newegg" data-affiliate-position="primary" data-google-vignette="false">Newegg&lt;/a>), holding the fan blades still so they don&amp;rsquo;t spin. Don&amp;rsquo;t forget the case intake filters, which choke airflow to the whole system.
The full order of operations, including which parts to clean first and what never to spray at a board, is in my &lt;a href="https://techfuelhq.com/tutorials/how-to-clean-pc-2026/">step-by-step PC cleaning procedure&lt;/a>.&lt;/p>
&lt;p>A cool GPU needs cool air reaching it. Make sure intake and exhaust fans are working and unobstructed, the PC isn&amp;rsquo;t buried in an enclosed desk cabinet, and cables aren&amp;rsquo;t blocking the front intake. If the case is short of fans, add intake or exhaust fans (&lt;a href="https://www.amazon.com/s?k=120mm&amp;#43;case&amp;#43;fan&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" data-affiliate-page="/articles/gpu-overheating-2026/" data-affiliate-slot="inline" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false">Amazon&lt;/a>, &lt;a href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3D120mm%2Bcase%2Bfan" rel="nofollow sponsored noopener" data-affiliate-page="/articles/gpu-overheating-2026/" data-affiliate-slot="inline" data-affiliate-retailer="Newegg" data-affiliate-position="primary" data-google-vignette="false">Newegg&lt;/a>) in sizes the case manual lists, then repeat the same scene.&lt;/p>
&lt;p>This step rules out the cheapest cause, a card that is simply breathing hot or blocked air.&lt;/p>
&lt;h2 id="step-5-check-the-gpu-fans-at-stock-settings">Step 5: Check the GPU fans at stock settings&lt;/h2>
&lt;p>During ordinary play, compare the fan RPM or fan command with whether the fans turn. A stopped fan at idle can be normal; a fan that no longer spins when commanded under load is a useful service symptom, and &lt;a href="https://techfuelhq.com/articles/gpu-fans-not-spinning-2026/">GPU Fans Not Spinning&lt;/a> covers that fault. &lt;a href="https://techfuelhq.com/articles/gpu-fans-stuck-at-100-percent/">Fans stuck at 100%&lt;/a> are a separate fault to investigate. A frame-rate cap may reduce the workload, but the lower reading afterwards isn&amp;rsquo;t proof the cooler was faulty.&lt;/p>
&lt;p>If the card was overclocked or undervolted, return it to its standard profile for this check. For a service request, keep the run at the manufacturer&amp;rsquo;s settings so the technician can see what happened before any tuning changed the conditions.&lt;/p>
&lt;p>This step rules out a fan or fan-control fault before anyone opens the cooler.&lt;/p>
&lt;h2 id="step-6-get-model-specific-service-advice-before-opening-the-cooler">Step 6: Get model-specific service advice before opening the cooler&lt;/h2>
&lt;p>Stop here if the core still reaches its maximum with clean filters, working case fans and GPU fans that spin on command. Send the board maker the exact model, the matched run and any thermal-limit or fan-failure evidence before removing the cooler. Read the warranty for your product and region; for instance, &lt;a href="https://www.asus.com/us/support/faq/1045224/" rel="noopener">ASUS&amp;rsquo;s U.S. graphics-card criteria&lt;/a> set out what it treats as customer-induced damage.&lt;/p>
&lt;p>If the maker confirms that an out-of-warranty card needs a user-serviceable repair, get the specified materials and procedure first. A temperature gap cannot tell you what thickness of pad to buy or whether you need new thermal paste at all. When the maker&amp;rsquo;s procedure leaves the choice to you, the &lt;a href="https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/">PTM7950 vs thermal paste comparison&lt;/a> covers the two materials.&lt;/p>
&lt;h2 id="run-cooler-once-the-card-is-healthy">Run cooler once the card is healthy&lt;/h2>
&lt;p>An undervolt asks the card to hold its clock at a lower voltage, which cuts power and heat. It doesn&amp;rsquo;t fix a fan, dust or contact fault, so do it after the steps above. The &lt;a href="https://techfuelhq.com/articles/how-to-undervolt-gpu-2026/">GPU undervolting guide&lt;/a> has the steps for NVIDIA and AMD cards.&lt;/p>
&lt;h2 id="when-its-not-really-the-temperature">When it&amp;rsquo;s not really the temperature&lt;/h2>
&lt;p>A crash can have several causes. If the sensors do not show a thermal limit, a driver fault or unstable overclock remains possible. If games crash to desktop or you get black screens without high temps, see &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">Fix GPU Driver Crashes&lt;/a>. If you&amp;rsquo;re seeing weird colors, flickering, or graphical glitches, hot VRAM can cause it, but so can a dying card, and those need a different diagnosis: &lt;a href="https://techfuelhq.com/articles/gpu-artifacts-2026/">GPU Artifacts vs Dying VRAM&lt;/a>. If the whole machine reboots under load, record what you can about the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU temperature&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">power-loss symptoms&lt;/a>. A normal GPU reading doesn&amp;rsquo;t diagnose either one.&lt;/p>
&lt;p>If the card runs its normal workload within its documented limits, there is no need to chase a lower number with the fans at maximum speed.&lt;/p>
&lt;p>&lt;em>Found an error? Email &lt;a href="mailto:contact@techfuelhq.com">contact@techfuelhq.com&lt;/a> with the article URL.&lt;/em>&lt;/p></description></item><item><title>Beszel vs Netdata vs Glances: Homelab Monitoring</title><link>https://techfuelhq.com/homelab/beszel-vs-netdata-vs-glances-2026/</link><pubDate>Wed, 17 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/beszel-vs-netdata-vs-glances-2026/</guid><atom:updated>2026-11-18T06:00:00Z</atom:updated><description>&lt;p>For a homelab with more than one machine I would run Beszel (v0.20.0, September 19). It is one hub and an agent per host, with one dashboard of all of them and alerts, and it costs nothing. Netdata (v2.11.1, September 16) is the one I would put on the box I am debugging, because it collects most metrics every second, keeps them for up to 14 days and runs anomaly detection on the agent, at a cost its resource-utilization page puts at 100-200 MB of RAM on an empty system; its Cloud dashboards provide access to 5 nodes without a paid plan. Glances (v4.5.9, November 7, the last 4.x release) is a live look at one machine. Uptime Kuma (2.5.12, November 17) answers a different question, whether a service is reachable, and since v0.20.0 in September 2026 Beszel&amp;rsquo;s agents cover part of that job too. Current releases on November 18, 2026: Beszel v0.21.2 (November 12) and Netdata v2.12.3 (November 4).&lt;/p>
&lt;h2 id="at-a-glance">At a glance&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Beszel&lt;/th>
&lt;th scope="col">Netdata&lt;/th>
&lt;th scope="col">Glances&lt;/th>
&lt;th scope="col">Uptime Kuma&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Job&lt;/td>
&lt;td data-label="Beszel">Resource dashboard, plus probes&lt;/td>
&lt;td data-label="Netdata">Deep real-time metrics&lt;/td>
&lt;td data-label="Glances">Single-box glance&lt;/td>
&lt;td data-label="Uptime Kuma">Uptime checks and status pages&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">License&lt;/td>
&lt;td data-label="Beszel">MIT&lt;/td>
&lt;td data-label="Netdata">GPL-3.0+ agent, free closed-source UI&lt;/td>
&lt;td data-label="Glances">LGPL-3.0&lt;/td>
&lt;td data-label="Uptime Kuma">MIT&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Architecture&lt;/td>
&lt;td data-label="Beszel">Hub + agents&lt;/td>
&lt;td data-label="Netdata">Agent per node, optional Parent&lt;/td>
&lt;td data-label="Glances">One process per host&lt;/td>
&lt;td data-label="Uptime Kuma">Single app&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Multi-server dashboard&lt;/td>
&lt;td data-label="Beszel">Yes&lt;/td>
&lt;td data-label="Netdata">5 nodes without a paid plan (Cloud and local dashboards)&lt;/td>
&lt;td data-label="Glances">Central browser&lt;/td>
&lt;td data-label="Uptime Kuma">Yes (checks)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Historical data&lt;/td>
&lt;td data-label="Beszel">Yes, up to 30 days&lt;/td>
&lt;td data-label="Netdata">Yes, tiered&lt;/td>
&lt;td data-label="Glances">About an hour, in memory&lt;/td>
&lt;td data-label="Uptime Kuma">Yes (checks)&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="feature-and-footprint-matrix">Feature and footprint matrix&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Beszel&lt;/th>
&lt;th scope="col">Netdata&lt;/th>
&lt;th scope="col">Glances&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Latest release (read Nov 18, 2026)&lt;/td>
&lt;td data-label="Beszel">v0.21.2, Nov 12, 2026&lt;/td>
&lt;td data-label="Netdata">v2.12.3, Nov 4, 2026&lt;/td>
&lt;td data-label="Glances">v4.5.9, Nov 7, 2026 (last 4.x; 5.0 in beta)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Licence&lt;/td>
&lt;td data-label="Beszel">MIT&lt;/td>
&lt;td data-label="Netdata">Agent GPL-3.0+; dashboard UI closed-source and free to use (NCUL1)&lt;/td>
&lt;td data-label="Glances">LGPL-3.0&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Runs on each host&lt;/td>
&lt;td data-label="Beszel">The Beszel agent, a binary or a container, reporting to one hub built on PocketBase&lt;/td>
&lt;td data-label="Netdata">The Netdata Agent, which can stream to a Netdata Parent&lt;/td>
&lt;td data-label="Glances">Glances, one Python process; cross-platform&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Several hosts, free&lt;/td>
&lt;td data-label="Beszel">The hub gives a dashboard of the connected systems&lt;/td>
&lt;td data-label="Netdata">Dashboard access for 5 nodes, on Netdata Cloud and on an Agent&amp;rsquo;s local dashboard, anonymous or Community; unlimited on paid plans (Homelab $90/yr)&lt;/td>
&lt;td data-label="Glances">&lt;code>glances --browser&lt;/code> lists Glances servers; WebUI since 4.3&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">History with nothing added&lt;/td>
&lt;td data-label="Beszel">1-minute points for an hour; averages kept up to 30 days&lt;/td>
&lt;td data-label="Netdata">per-second up to 14 days, per-minute up to 3 months, per-hour up to 2 years, 1 GiB per tier, about 4 GiB of disk&lt;/td>
&lt;td data-label="Glances">1,200 values per stat in memory, about an hour; longer only through an export&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Alerts&lt;/td>
&lt;td data-label="Beszel">Most metrics, many notification services; container health and failed systemd services since v0.19.0&lt;/td>
&lt;td data-label="Netdata">Hundreds of built-in alerts&lt;/td>
&lt;td data-label="Glances">Colour thresholds; a shell command on warning or critical&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Service checks&lt;/td>
&lt;td data-label="Beszel">ICMP, TCP, HTTP and DNS probes from each agent since v0.20.0; alert on an hour&amp;rsquo;s packet loss, 5% by default; TLS certificate expiry checks since v0.21.0&lt;/td>
&lt;td data-label="Netdata">httpcheck, ping and portcheck collectors&lt;/td>
&lt;td data-label="Glances">Ports plugin: ICMP, TCP, URL&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Containers and disks&lt;/td>
&lt;td data-label="Beszel">Docker and Podman containers; S.M.A.R.T.; ZFS pools since v0.19.0&lt;/td>
&lt;td data-label="Netdata">Containers and VMs; S.M.A.R.T. through the smartctl collector&lt;/td>
&lt;td data-label="Glances">Docker, Podman and LXD; VMs through Multipass and Virsh; SMART plugin, off by default&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Windows&lt;/td>
&lt;td data-label="Beszel">Agent through WinGet or Scoop&lt;/td>
&lt;td data-label="Netdata">Windows Agent; its local dashboard works on every plan, free Community included&lt;/td>
&lt;td data-label="Glances">Runs on Windows; install psutil first&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Published footprint&lt;/td>
&lt;td data-label="Beszel">None published&lt;/td>
&lt;td data-label="Netdata">About 200 MB RAM and under 5% of one core with default settings; 250-350 MB and up to 5%-20% of a core in typical production; about 30 MiB as a lightweight Child on an edge device (resource-utilization page and README)&lt;/td>
&lt;td data-label="Glances">None published&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Read September 26, 2026 from each project&amp;rsquo;s releases and docs, and from Beszel&amp;rsquo;s source for its retention periods; the release, service-check and Netdata rows were re-read November 18, 2026. Beszel shipped three releases between August 17 and September 19, and three more by November 12. Glances shipped the day I read it. The first row ages fastest.&lt;/p>
&lt;h2 id="beszel-the-simple-multi-server-dashboard">Beszel: the simple multi-server dashboard&lt;/h2>
&lt;p>&lt;a href="https://github.com/henrygd/beszel" rel="noopener">Beszel&lt;/a> (MIT, by henrygd) is a hub built on PocketBase and an agent on each host, and the agent reports CPU, memory, disk usage and I/O, network, load, temperature, fan speed, GPU, battery, containers, drive SMART health and ZFS pools. The hub keeps the history, sends the alerts, and handles users, OAuth / OIDC logins and backups to disk or S3-compatible storage.&lt;/p>
&lt;p>Two Beszel releases in September 2026 changed what it does. v0.19.0 (September 3) made agents verify the hub&amp;rsquo;s HTTPS certificate, so an agent pointed at a hub with a self-signed certificate now needs &lt;code>CA_CERT_FILE&lt;/code> or it will not connect, and the same release added alerts for container health, failed systemd services, and CPU I/O wait and steal. v0.20.0 (September 19) lets each agent probe targets over ICMP, TCP, HTTP or DNS every 1 to 3,600 seconds and chart response time and packet loss.&lt;/p>
&lt;p>The v0.21 releases (October 2 to November 12) build on that. v0.21.0 added TLS certificate-expiry checks to HTTPS monitors, a list of pending package updates on the system page, Wi-Fi signal strength and systemd service logs; v0.21.1 added an expiry alert for those certificates and opt-in cgroup CPU and memory accounting; v0.21.2 limits sign-in attempts to 10 per minute per address. v0.21.1 and v0.21.2 also fix several permission checks, among them agents being able to overwrite another system&amp;rsquo;s records, so keep the hub current.&lt;/p>
&lt;p>The agent installs on Linux and FreeBSD from a script, on macOS through Homebrew, and on Windows through WinGet or Scoop. Beszel&amp;rsquo;s version numbers are still below 1.0, and v0.19.0 broke self-signed setups. Read the notes before an upgrade. On Proxmox, put the agent on the host or in a VM. Beszel issue #176, open since September 2024 and still open on November 18, 2026, reports agents inside LXC containers showing the host&amp;rsquo;s RAM; v0.21.2 fixed a separate LXC memory bug, in which usage wrongly subtracted the host&amp;rsquo;s ZFS ARC. The &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM guide&lt;/a> covers the rest of that trade-off.&lt;/p>
&lt;p>&lt;strong>Pick Beszel if&lt;/strong> you want one dashboard and alerts across several machines and do not want to run Prometheus and Grafana.&lt;/p>
&lt;h2 id="netdata-depth-and-real-time-diagnostics">Netdata: depth and real-time diagnostics&lt;/h2>
&lt;p>&lt;a href="https://github.com/netdata/netdata" rel="noopener">Netdata&lt;/a> collects most metrics every second with little configuration, runs unsupervised anomaly detection on the agent, and stores its own tiered history, which by default keeps per-second data for up to 14 days, per-minute for up to 3 months and per-hour for up to 2 years, each tier capped at 1 GiB, about 4 GiB of disk in all. Netdata v2.11.0 (August 12) added OpenTelemetry (OTLP) log ingestion next to the systemd journal, and a Network Monitor dashboard for SNMP devices and flows as a technical preview. v2.12.0 (September 30) added OpenTelemetry traces as an Early Access feature and a Redfish collector that reads fans, temperatures, power supplies and drives from a server&amp;rsquo;s BMC; v2.12.3 (November 4) was the current release on November 18, 2026. The agent is GPL-3.0+. The dashboard UI is closed-source and free to use.&lt;/p>
&lt;p>One limit matters once a homelab has more than a few boxes. Netdata gives anonymous and Community users dashboard access to 5 nodes, &amp;ldquo;on Netdata Cloud dashboards and on the local dashboard of Agents and Parents.&amp;rdquo; It calls this &amp;ldquo;a plan entitlement, not a streaming or connection limit&amp;rdquo;: any number of nodes can stream to a Parent and keep collecting and storing data, while a node outside your five preferred nodes shows as Locked until you select it or upgrade. The Homelab plan lifts the limit for $90 a year (personal, non-commercial use), and Business starts at $7 per node per month billed annually, or $8.75 billed monthly (Netdata&amp;rsquo;s pricing page, November 18, 2026). On Windows, Netdata&amp;rsquo;s installer notes say the local dashboard works as it does on Linux, on every plan including the free Community tier.&lt;/p>
&lt;p>Netdata publishes its footprint, which neither of the others does, and as of November 18, 2026 its resource-utilization page and README agree: under 5% of one CPU core and about 200 MB of RAM on a typical server with default settings (per-second collection of about 3,000 metrics, machine learning on every metric, three storage tiers and all stock alerts), 250-350 MB of RAM and up to 5%-20% of a core in typical production, and about 30 MiB on an edge device configured as a lightweight Child. The same page names the levers: more metrics raise CPU, RAM and disk use, a higher sample frequency costs CPU and disk, more tiers mean more memory, and machine-learning training is CPU-intensive.&lt;/p>
&lt;p>&lt;strong>Pick Netdata if&lt;/strong> you want per-second metrics and anomaly detection on the machine you are troubleshooting, and dashboard access to 5 nodes without a paid plan is enough.&lt;/p>
&lt;h2 id="glances-the-quick-single-box-look">Glances: the quick single-box look&lt;/h2>
&lt;p>&lt;a href="https://github.com/nicolargo/glances" rel="noopener">Glances&lt;/a> (LGPL-3.0, by nicolargo; not to be confused with Glance, the dashboard in the &lt;a href="https://techfuelhq.com/tutorials/glance-dashboard-setup-2026/">Glance setup guide&lt;/a>) is a cross-platform top/htop alternative written in Python that runs as a terminal UI, a web UI (&lt;code>glances -w&lt;/code>) or a REST API. It shows the host (CPU, memory, disk, network, sensors) and its processes, containers from Docker, Podman or LXD, and VMs from Multipass or Virsh. History lives only in memory. Glances keeps 1,200 values per stat, which its config docs put at about an hour. For more, export to InfluxDB, Prometheus, TimescaleDB or another of its targets and chart it elsewhere.&lt;/p>
&lt;p>Thresholds colour the display; warning and critical thresholds can also run a shell command, which is how Glances raises an alert. For several machines, &lt;code>glances --browser&lt;/code> lists the Glances servers named in its configuration file or found on the network over zeroconf, in the terminal or, since 4.3, in the web UI. Glances v4.5.7 (September 26) carried four security patches, including an unauthenticated credential disclosure through the ports plugin. v4.5.9 (November 7) replaced the python-jose library, which had a CVE, with PyJWT, and is the last 4.x release; Glances 5.0.0 is in beta.&lt;/p>
&lt;p>&lt;strong>Port warning:&lt;/strong> Glances&amp;rsquo; quickstart gives 0.0.0.0, every network interface, as the default bind address in server mode, and &lt;code>glances -w&lt;/code> serves the web UI to other machines on port 61208. Set a login with &lt;code>--password&lt;/code> (the user name is &lt;code>glances&lt;/code> unless you change it with &lt;code>--username&lt;/code>), as the quickstart documents, before you run it anywhere but a trusted LAN.&lt;/p>
&lt;p>&lt;strong>Pick Glances if&lt;/strong> you want a rich live view of one box over SSH or in a browser, or a metrics source to feed another stack.&lt;/p>
&lt;h2 id="uptime-kuma-a-different-job">Uptime Kuma: a different job&lt;/h2>
&lt;p>&lt;a href="https://github.com/louislam/uptime-kuma" rel="noopener">Uptime Kuma&lt;/a> (MIT, by Louis Lam, who also wrote &lt;a href="https://github.com/louislam/dockge" rel="noopener">Dockge&lt;/a>) checks whether services answer over HTTP(S) or a TCP port, with keyword and JSON-query checks on the response, ping, DNS records and Docker containers. It sends alerts through 90+ notification services and serves status pages mapped to your own domain. Uptime Kuma&amp;rsquo;s 2.x line has been stable since 2.0.0 (October 20, 2025); 2.5.12 (November 17, 2026) was the current release on November 18, with a 3.0.0 beta published the same day. My &lt;a href="https://techfuelhq.com/tutorials/uptime-kuma-docker-setup-2026/">Uptime Kuma setup guide&lt;/a> covers where to run it, which is somewhere outside the network it watches.&lt;/p>
&lt;p>Beszel v0.20.0 moved into part of this job. Its HTTP probe times a GET request, a status of 400 or above counts as loss, and the alert fires when a monitor&amp;rsquo;s packet loss over the past hour passes the threshold, 5% by default. It charts latency and loss per host. I would still keep Uptime Kuma for anything someone outside the house relies on, and let Beszel&amp;rsquo;s probes watch the gateway and DNS.&lt;/p>
&lt;div class="visual-block">
&lt;div style="background:#0d1220;padding:24px 20px 22px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',sans-serif;color:#e8eaf2;">
&lt;div style="font-size:18px;font-weight:700;letter-spacing:-0.3px;">Which question are you actually asking?&lt;/div>
&lt;div style="font-size:0.875rem;color:#93a0bd;margin-top:5px;line-height:1.55;max-width:620px;">The confusion clears the moment you name the question. These tools split into two jobs first, and only then by how deep you want to look.&lt;/div>
&lt;div style="margin-top:18px;background:#141b2c;border:1px solid rgba(255,255,255,0.09);border-radius:8px;padding:11px 14px;text-align:center;font-size:13px;font-weight:700;color:#eef1f8;">What do you need to know about your homelab?&lt;/div>
&lt;div style="display:flex;gap:12px;flex-wrap:wrap;margin-top:12px;">
&lt;div style="flex:1 1 210px;min-width:0;background:#0b1626;border:1px solid #4a9eff33;border-top:3px solid #4a9eff;border-radius:8px;padding:13px 14px;">
&lt;div style="font-size:0.875rem;font-weight:700;color:#bcdcff;">&amp;ldquo;Is a service reachable?&amp;rdquo;&lt;/div>
&lt;div style="font-size:0.8125rem;color:#89a7cf;line-height:1.45;margin-top:4px;">Up, down, or slow &amp;mdash; HTTP, TCP port, ping, DNS.&lt;/div>
&lt;div style="margin-top:11px;background:#0e1f36;border:1px solid #4a9eff55;border-radius:7px;padding:9px 11px;">
&lt;div style="font-size:13px;font-weight:800;color:#dcebff;">Uptime Kuma&lt;/div>
&lt;div style="font-size:0.8125rem;color:#9db6dd;line-height:1.4;margin-top:3px;">Checks &amp;plus; status pages &amp;plus; 90&amp;plus; notification services. Beszel's probes cover latency and loss from each host.&lt;/div>
&lt;/div>
&lt;/div>
&lt;div style="flex:2 1 320px;min-width:0;background:#0c1f16;border:1px solid #35d07f33;border-top:3px solid #35d07f;border-radius:8px;padding:13px 14px;">
&lt;div style="font-size:0.875rem;font-weight:700;color:#c8f5dd;">&amp;ldquo;How are my resources?&amp;rdquo;&lt;/div>
&lt;div style="font-size:0.8125rem;color:#8fcaa8;line-height:1.45;margin-top:4px;">Why is a box struggling &amp;mdash; CPU, RAM, disk, temperature. Now pick by depth:&lt;/div>
&lt;div style="display:flex;flex-direction:column;gap:8px;margin-top:11px;">
&lt;div style="background:#111d16;border:1px solid #e6ff8f44;border-left:1px solid #e6ff8f;border-radius:7px;padding:9px 11px;">&lt;div style="display:flex;justify-content:space-between;align-items:baseline;gap:8px;">&lt;span style="font-size:0.875rem;font-weight:800;color:#e6ff8f;">Beszel&lt;/span>&lt;span style="font-size:0.8125rem;color:#a9c25a;font-weight:700;">start here&lt;/span>&lt;/div>&lt;div style="font-size:0.8125rem;color:#9fb27a;line-height:1.4;margin-top:2px;">One dashboard across all your hosts, with alerts and 30 days of history.&lt;/div>&lt;/div>
&lt;div style="background:#0b1626;border:1px solid #4a9eff44;border-left:1px solid #4a9eff;border-radius:7px;padding:9px 11px;">&lt;span style="font-size:0.875rem;font-weight:800;color:#bcdcff;">Glances&lt;/span>&lt;div style="font-size:0.8125rem;color:#89a7cf;line-height:1.4;margin-top:2px;">A quick, rich look at ONE box right now &amp;mdash; terminal, web, or API.&lt;/div>&lt;/div>
&lt;div style="background:#241706;border:1px solid #f0a74244;border-left:1px solid #f0a742;border-radius:7px;padding:9px 11px;">&lt;span style="font-size:0.875rem;font-weight:800;color:#ffd9a8;">Netdata&lt;/span>&lt;div style="font-size:0.8125rem;color:#c79a63;line-height:1.4;margin-top:2px;">Per-second metrics and on-agent anomaly detection when you need to dig in. Dashboard access for 5 nodes without a paid plan.&lt;/div>&lt;/div>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;h2 id="which-should-you-run">Which should you run?&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>One dashboard and alerts across several hosts →&lt;/strong> Beszel.&lt;/li>
&lt;li>&lt;strong>Per-second depth and anomaly detection on one box →&lt;/strong> Netdata, with dashboard access for 5 nodes without a paid plan.&lt;/li>
&lt;li>&lt;strong>A live look at one machine, or a metrics source for another stack →&lt;/strong> Glances.&lt;/li>
&lt;li>&lt;strong>Uptime notifications and a public status page →&lt;/strong> Uptime Kuma, next to whichever of the above you run.&lt;/li>
&lt;/ul>
&lt;p>The stack I would run is a Beszel agent on every host and Uptime Kuma on a machine outside the network. Netdata goes on a box only while I am chasing a problem there. Glances is for a look over SSH. Put the web UIs behind a &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">reverse proxy&lt;/a>.&lt;/p>
&lt;p>Budget memory for the whole stack in the &lt;a href="https://techfuelhq.com/tools/docker-ram-planner/">Docker RAM planner&lt;/a>. The Beszel hub runs happily as one Compose stack, and &lt;a href="https://techfuelhq.com/tutorials/dockge-docker-compose-manager-2026/">Dockge&lt;/a> keeps a handful of those manageable.&lt;/p>
&lt;h2 id="a-note-on-footprint-numbers">A note on footprint numbers&lt;/h2>
&lt;p>Only Netdata publishes a number. Beszel&amp;rsquo;s README says &amp;ldquo;Smaller and less resource-intensive than leading solutions&amp;rdquo; and gives none. Glances gives none either. The figures I found on other comparison pages lack a reproducible measurement method, which makes them hard to plan a Raspberry Pi around.&lt;/p>
&lt;p>Measuring your own takes twenty minutes. Start the agent, leave it alone for ten minutes, then take ten one-minute samples (&lt;code>pidstat&lt;/code> is in the sysstat package):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pidstat -r -u -p &lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>pgrep -d, -f beszel-agent&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#ae81ff">60&lt;/span> &lt;span style="color:#ae81ff">10&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Use &lt;code>netdata&lt;/code> or &lt;code>glances&lt;/code> in place of &lt;code>beszel-agent&lt;/code>. For Netdata the pattern also catches plugin processes with &lt;code>netdata&lt;/code> in their command line, which you want counted. The &lt;code>Average:&lt;/code> lines give RSS in kB and %CPU per process in separate tables. Sum RSS and %CPU separately across processes. For containers, run &lt;code>docker stats --no-stream&lt;/code> a few times a minute apart instead. A summed RSS counts shared libraries more than once, and docker stats reports the container&amp;rsquo;s cgroup memory rather than RSS, so compare native runs with native runs and containers with containers. Write down the version and which collectors were enabled, including GPU and SMART. In Beszel issue #1203 an agent on a Proxmox host used far more CPU after an upgrade because &lt;code>intel_gpu_top&lt;/code> restarted in a loop.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>Beszel: &lt;a href="https://github.com/henrygd/beszel/releases" rel="noopener">releases&lt;/a> · &lt;a href="https://github.com/henrygd/beszel" rel="noopener">repository and README&lt;/a> · &lt;a href="https://beszel.dev/guide/agent-installation" rel="noopener">agent installation&lt;/a> · &lt;a href="https://beszel.dev/guide/network-monitors" rel="noopener">network monitoring&lt;/a> · &lt;a href="https://github.com/henrygd/beszel/blob/main/internal/records/records_deletion.go" rel="noopener">record retention in the source&lt;/a> · issues &lt;a href="https://github.com/henrygd/beszel/issues/176" rel="noopener">#176&lt;/a> and &lt;a href="https://github.com/henrygd/beszel/issues/1203" rel="noopener">#1203&lt;/a>&lt;/li>
&lt;li>Netdata: &lt;a href="https://github.com/netdata/netdata/releases" rel="noopener">releases&lt;/a> · &lt;a href="https://learn.netdata.cloud/docs/netdata-agent/resource-utilization" rel="noopener">resource utilization&lt;/a> · &lt;a href="https://github.com/netdata/netdata/blob/master/packaging/windows/WINDOWS_INSTALLER.md" rel="noopener">Windows installer notes&lt;/a> · &lt;a href="https://github.com/netdata/netdata/blob/master/docs/netdata-agent/sizing-netdata-agents/disk-requirements-and-retention.md" rel="noopener">disk requirements and retention&lt;/a> · &lt;a href="https://github.com/netdata/netdata/blob/master/docs/netdata-oss-limitations.md" rel="noopener">access control and feature availability&lt;/a> · &lt;a href="https://www.netdata.cloud/pricing/" rel="noopener">pricing&lt;/a> · &lt;a href="https://github.com/netdata/netdata" rel="noopener">repository and licence table&lt;/a>&lt;/li>
&lt;li>Glances: &lt;a href="https://github.com/nicolargo/glances/releases" rel="noopener">releases&lt;/a> · &lt;a href="https://glances.readthedocs.io/en/latest/config.html" rel="noopener">configuration&lt;/a> · &lt;a href="https://glances.readthedocs.io/en/latest/aoa/containers.html" rel="noopener">containers&lt;/a> · &lt;a href="https://glances.readthedocs.io/en/latest/quickstart.html" rel="noopener">quickstart and central browser&lt;/a> · &lt;a href="https://github.com/nicolargo/glances" rel="noopener">repository&lt;/a>&lt;/li>
&lt;li>Uptime Kuma: &lt;a href="https://github.com/louislam/uptime-kuma/releases" rel="noopener">releases&lt;/a> · &lt;a href="https://github.com/louislam/uptime-kuma" rel="noopener">repository and README&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Adding a User to the Docker Group Is Not a Convenience Setting (2026)</title><link>https://techfuelhq.com/tutorials/add-user-to-docker-group-2026/</link><pubDate>Sat, 15 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/add-user-to-docker-group-2026/</guid><atom:updated>2026-11-18T05:58:00Z</atom:updated><description>&lt;p>Here is the command you came for:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo groupadd docker &lt;span style="color:#75715e"># only if the group does not exist yet&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo usermod -aG docker $USER
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># then log out and log back in&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>And here is the sentence that belongs next to it, which Docker puts in a Warning box on its own &lt;a href="https://docs.docker.com/engine/install/linux-postinstall/" rel="noopener">post-installation page&lt;/a> and almost nobody repeats:&lt;/p>
&lt;blockquote>
&lt;p>The docker group grants root-level privileges to the user.&lt;/p>&lt;/blockquote>
&lt;p>Not &amp;ldquo;elevated access to Docker&amp;rdquo;. Root on the host.&lt;/p>
&lt;p>This page is written against Docker Engine 29.10.0, the current release on November 18, 2026, and Docker&amp;rsquo;s post-installation page as it read that day.&lt;/p>
&lt;h2 id="check-that-it-worked">Check that it worked&lt;/h2>
&lt;p>After you have logged back in:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>id -nG &lt;span style="color:#75715e"># docker should appear in the list&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker run hello-world &lt;span style="color:#75715e"># no sudo&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Docker&amp;rsquo;s docs use &lt;code>docker run hello-world&lt;/code> as the check: it downloads a test image, runs it, prints a message and exits. If &lt;code>id -nG&lt;/code> does not list &lt;code>docker&lt;/code>, the shell you are in predates the change; see &lt;a href="#why-the-change-does-not-take-effect-immediately">why the change does not take effect immediately&lt;/a>.&lt;/p>
&lt;p>To undo it later:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo gpasswd --delete &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$USER&lt;span style="color:#e6db74">&amp;#34;&lt;/span> docker
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># sign out of the desktop or SSH session completely, then sign back in&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>id -nG &lt;span style="color:#75715e"># docker should be gone&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Docker&amp;rsquo;s docs are specific that a new terminal is not enough here: existing processes keep the membership until they exit.&lt;/p>
&lt;h2 id="why-it-is-root-concretely">Why it is root, concretely&lt;/h2>
&lt;p>The reason &lt;code>sudo&lt;/code> is needed in the first place is architectural. Docker&amp;rsquo;s docs put it plainly: the daemon binds a Unix socket rather than a TCP port, that socket is owned by root, and the daemon itself always runs as root. Joining the &lt;code>docker&lt;/code> group does not reduce what the daemon can do. It gives you write access to the socket that commands it.&lt;/p>
&lt;p>The socket is the entire access-control model. Moby&amp;rsquo;s own &lt;a href="https://github.com/moby/moby/blob/master/contrib/init/systemd/docker.socket" rel="noopener">systemd socket unit&lt;/a> ships it as &lt;code>SocketUser=root&lt;/code>, &lt;code>SocketGroup=docker&lt;/code>, &lt;code>SocketMode=0660&lt;/code>. There is no per-user authorization layer behind it. Anything that can write to that socket can ask the root daemon for anything.&lt;/p>
&lt;p>So the escalation is not clever:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker run --mount type&lt;span style="color:#f92672">=&lt;/span>bind,src&lt;span style="color:#f92672">=&lt;/span>/,dst&lt;span style="color:#f92672">=&lt;/span>/host -it alpine sh
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You are now root inside a container with the host&amp;rsquo;s entire filesystem at &lt;code>/host&lt;/code>. Docker&amp;rsquo;s &lt;a href="https://docs.docker.com/engine/security/" rel="noopener">security page&lt;/a> states it directly: the container can alter your host filesystem without any restriction. Edit &lt;code>/host/etc/shadow&lt;/code>, drop a key in &lt;code>/host/root/.ssh/authorized_keys&lt;/code>, whatever you like.&lt;/p>
&lt;p>Notice what is absent. No &lt;code>--privileged&lt;/code>. No sudo prompt. No password. No entry in the sudo log.&lt;/p>
&lt;p>That last one is the part I find most under-discussed. &lt;code>sudo&lt;/code> leaves a trail. Group membership does not.&lt;/p>
&lt;h2 id="so-why-does-every-tutorial-recommend-it">So why does every tutorial recommend it&lt;/h2>
&lt;p>Because Docker&amp;rsquo;s own docs frame it as convenience first. The section opens by offering two ways to run docker commands without sudo, and adding your user to the group is the first one listed. The Warning box sits &lt;em>underneath&lt;/em> that.&lt;/p>
&lt;p>Read in order, the page teaches convenience and then qualifies it. Skimmed (which is how anyone with a broken build reads a post-install page), you get the command and miss the box. Docker clearly knows this happens, because they had to add a second and more explicit warning on the Windows side, where &lt;a href="https://docs.docker.com/desktop/setup/install/windows-install/" rel="noopener">&lt;code>docker-users&lt;/code> membership&lt;/a> is described as equivalent to granting administrative privileges on the host. OWASP made not exposing the daemon socket &lt;a href="https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html" rel="noopener">rule number one&lt;/a> of its Docker cheat sheet.&lt;/p>
&lt;p>The warning exists. It is just positioned to lose.&lt;/p>
&lt;h2 id="why-the-change-does-not-take-effect-immediately">Why the change does not take effect immediately&lt;/h2>
&lt;p>You run &lt;code>usermod&lt;/code>, you run &lt;code>docker ps&lt;/code>, and you still get permission denied. Nothing is broken.&lt;/p>
&lt;p>Supplementary group IDs are a credential attached to a process when it is created. Your shell was created before you joined the group, so it does not carry the membership, and re-reading &lt;code>/etc/group&lt;/code> is not something a running process does. The shell will never pick it up. Neither will your desktop session, or the terminal you opened an hour ago.&lt;/p>
&lt;p>Docker&amp;rsquo;s instruction is to log out and log back in so that group membership is re-evaluated, and they note a Linux VM may need a full restart.&lt;/p>
&lt;p>To test without logging out:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>newgrp docker
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker run hello-world
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>newgrp&lt;/code> starts a subshell that carries the group. It is a session-level patch. Close that shell and you are back where you started, so do not mistake it for the change having applied globally.&lt;/p>
&lt;h2 id="the-configjson-warning-nobody-explains">The config.json warning nobody explains&lt;/h2>
&lt;p>If you used &lt;code>sudo docker&lt;/code> before joining the group, you will eventually see this:&lt;/p>
&lt;pre tabindex="0">&lt;code>WARNING: Error loading config file: /home/user/.docker/config.json - stat
/home/user/.docker/config.json: permission denied
&lt;/code>&lt;/pre>&lt;p>Root created that directory in your home. Docker documents two fixes: remove &lt;code>~/.docker&lt;/code> (it is recreated automatically, but any custom settings are lost), or change its ownership and permissions:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo chown &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$USER&lt;span style="color:#e6db74">&amp;#34;&lt;/span>:&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$USER&lt;span style="color:#e6db74">&amp;#34;&lt;/span> /home/&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$USER&lt;span style="color:#e6db74">&amp;#34;&lt;/span>/.docker -R
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo chmod g+rwx &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HOME&lt;span style="color:#e6db74">/.docker&amp;#34;&lt;/span> -R
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Cosmetic, not dangerous. It will nag until you clear it.&lt;/p>
&lt;h2 id="what-to-do-instead">What to do instead&lt;/h2>
&lt;p>I am not going to tell you never to join the docker group. Plenty of people should. The point is to do it knowing what it is.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Option&lt;/th>
&lt;th scope="col">What can reach the root daemon&lt;/th>
&lt;th scope="col">Prompt before access&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Option">&lt;code>sudo docker&lt;/code>&lt;/td>
&lt;td data-label="What can reach the root daemon">Each command you authenticate&lt;/td>
&lt;td data-label="Prompt before access">sudo password, logged by sudo&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">&lt;code>docker&lt;/code> group&lt;/td>
&lt;td data-label="What can reach the root daemon">Every process in your login session&lt;/td>
&lt;td data-label="Prompt before access">None&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">On-demand group (&lt;code>newgrp&lt;/code> + group password)&lt;/td>
&lt;td data-label="What can reach the root daemon">Only the Docker-enabled shell and what it starts&lt;/td>
&lt;td data-label="Prompt before access">Group password per shell&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">Rootless mode&lt;/td>
&lt;td data-label="What can reach the root daemon">No root daemon: your user runs its own&lt;/td>
&lt;td data-label="Prompt before access">None&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>&lt;strong>Rootless mode&lt;/strong> is the real fix, because it removes the root daemon rather than gating access to one. It has genuine limitations and I have not run it long enough under a homelab workload to tell you which of those bite in practice.&lt;/p>
&lt;p>Docker&amp;rsquo;s &lt;a href="https://docs.docker.com/engine/security/rootless/" rel="noopener">rootless setup&lt;/a> needs &lt;code>newuidmap&lt;/code> and &lt;code>newgidmap&lt;/code> (the &lt;code>uidmap&lt;/code> package on most distributions) and at least 65,536 subordinate IDs for your user in &lt;code>/etc/subuid&lt;/code> and &lt;code>/etc/subgid&lt;/code>. With Docker 20.10 or later installed from DEB or RPM packages, you run the setup script as your normal user, not root:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Docker suggests disabling the system-wide daemon first:&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo systemctl disable --now docker.service docker.socket
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo rm /var/run/docker.sock
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># then, as your normal user:&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>dockerd-rootless-setuptool.sh install
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker info &lt;span style="color:#75715e"># Context: rootless, and Security Options lists rootless&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If you keep the system-wide daemon running, Docker&amp;rsquo;s page says the install needs &lt;code>--force&lt;/code>, and until you disable it you are still running rootful Docker alongside. If the script is missing, install the &lt;code>docker-ce-rootless-extras&lt;/code> package. The script creates a &lt;code>rootless&lt;/code> CLI context and tells you which environment variables to set.&lt;/p>
&lt;p>&lt;strong>On-demand group access&lt;/strong> is the middle path Docker&amp;rsquo;s post-install page now documents for a single-user workstation: keep your user out of the group, set a group password with &lt;code>sudo gpasswd docker&lt;/code>, and start a Docker-enabled shell with &lt;code>newgrp docker&lt;/code> when you need one. Docker&amp;rsquo;s own warning applies: it reduces ambient access to the socket, but it does not reduce the root-level privileges once you are in, and it is not a boundary against malicious code already running as your user.&lt;/p>
&lt;p>&lt;strong>&lt;code>sudo docker&lt;/code>&lt;/strong> keeps every invocation authenticated and logged. It is mildly annoying and it is the correct default on a machine that is not yours alone.&lt;/p>
&lt;p>&lt;strong>Join the group deliberately&lt;/strong> on a box where root-equivalent access is already a thing you accept. On a dedicated homelab Docker host that you administer alone and could rebuild in an afternoon, the trade is reasonable and I would make it.&lt;/p>
&lt;p>What I would not do is join the group on a shared machine, a work laptop, or anything with credentials on it you would not want a container to read, and then tell myself it was a permissions tweak.&lt;/p>
&lt;p>The same reasoning governs anything you point at that socket. A &lt;a href="https://techfuelhq.com/tutorials/dockge-docker-compose-manager-2026/">Dockge&lt;/a> or Portainer container with the socket mounted is not a dashboard; it is that same root-equivalent access with a web login in front of it.&lt;/p>
&lt;h2 id="the-docker-desktop-exception">The Docker Desktop exception&lt;/h2>
&lt;p>This is the one place the warning genuinely does not carry over. On Docker Desktop the daemon and your containers run inside a Linux VM, and Docker documents that &lt;a href="https://docs.docker.com/desktop/setup/install/windows-permission-requirements/" rel="noopener">VM as the security boundary&lt;/a>. Container root is not host root in the way it is on a native Linux install.&lt;/p>
&lt;p>Do not port the Linux Engine threat model onto Desktop unexamined. Do not port Desktop&amp;rsquo;s comfort back onto a Linux server either: on Windows, &lt;code>docker-users&lt;/code> carries its own warning, in Docker&amp;rsquo;s words equivalent to granting administrative privileges on the host. Docker&amp;rsquo;s install page adds that Linux containers on the WSL 2 backend do not need that group at all.&lt;/p>
&lt;h2 id="what-i-have-not-tested">What I have not tested&lt;/h2>
&lt;p>I have not run rootless mode as a daily driver, so I cannot tell you where its limitations actually hurt versus where they are theoretical.&lt;/p>
&lt;p>I have not audited whether any mainstream distro ships auditd rules that would record socket writes by group members. My claim above is that &lt;code>sudo&lt;/code> logs and group membership does not, which follows from how each works, but I have not sat down and confirmed what a default install captures.&lt;/p>
&lt;h2 id="what-getting-this-wrong-costs">What getting this wrong costs&lt;/h2>
&lt;p>On your own homelab box, usually nothing. That is exactly why the habit spreads.&lt;/p>
&lt;p>The bill arrives somewhere else. It arrives when the same muscle memory runs &lt;code>usermod -aG docker&lt;/code> on a shared build server, and the service account that now has passwordless unlogged root is the one whose CI token leaks six months later. Nobody has to attack Docker. The group was the grant.&lt;/p>
&lt;p>Run the command if it suits your machine. Just do not believe it only saves you four keystrokes.&lt;/p>
&lt;p>Once docker runs without sudo, the next things most people need are &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">how Compose actually loads &lt;code>.env&lt;/code> and &lt;code>env_file:&lt;/code>&lt;/a>, &lt;a href="https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/">which prune commands are safe when the disk fills&lt;/a>, and &lt;a href="https://techfuelhq.com/tutorials/docker-exit-code-137-oomkilled-2026/">what exit code 137 means&lt;/a> when a container dies.&lt;/p></description></item><item><title>NetBird vs Tailscale (2026): The Self-Hosted Mesh VPN Question</title><link>https://techfuelhq.com/networking/netbird-vs-tailscale-2026/</link><pubDate>Sun, 05 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/netbird-vs-tailscale-2026/</guid><atom:updated>2026-11-18T05:55:00Z</atom:updated><description>&lt;p>Tailscale and NetBird both give you a WireGuard mesh with key distribution, NAT traversal and access policy handled for you. The real split is who runs the control plane. Tailscale runs it for you as a managed service. NetBird ships its own coordination server as open source and supports you running it. If you are still deciding between a managed mesh and raw WireGuard, start with &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale vs WireGuard&lt;/a> instead.&lt;/p>
&lt;h2 id="the-20-second-answer">The 20-second answer&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Personal remote access, no server to run:&lt;/strong> Tailscale, when the free Personal plan covers your users, ACL groups and tagged servers. &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Setting it up on a homelab&lt;/a> is the next step.&lt;/li>
&lt;li>&lt;strong>You want the control server on your own hardware:&lt;/strong> self-hosted NetBird, through the vendor&amp;rsquo;s own documented stack.&lt;/li>
&lt;li>&lt;strong>A team:&lt;/strong> compare the dated plan table below and the total running cost. NetBird Cloud is a managed option too.&lt;/li>
&lt;/ul>
&lt;p>Price the maintenance before you self-host anything.&lt;/p>
&lt;h2 id="same-engine-different-brain">Same engine, different brain&lt;/h2>
&lt;p>Both products share the same &lt;strong>data plane&lt;/strong>: WireGuard, the small, fast, modern tunnel that has been the standard for point-to-point encrypted links since it landed in the mainline Linux kernel. Both also add the same category of things WireGuard deliberately leaves out - automatic key distribution, NAT traversal, stable addressing, and access policy. That shared &amp;ldquo;coordination layer&amp;rdquo; is why people compare them at all.&lt;/p>
&lt;p>Where they split is the &lt;strong>control plane&lt;/strong> - the coordination server that brokers keys, tracks which device is where, and distributes your policy:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Tailscale&lt;/strong> runs that control plane as a &lt;strong>proprietary, fully managed service.&lt;/strong> You never operate a server. The &lt;a href="https://github.com/tailscale/tailscale/blob/main/LICENSE" rel="noopener">core client repository&lt;/a> uses BSD-3-Clause. &lt;a href="https://tailscale.com/opensource" rel="noopener">Tailscale&amp;rsquo;s open source page&lt;/a> lists the DERP relay code as open source and says its hosted coordination server remains proprietary. If you want the brain on your own hardware, the community answer is &lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a>, an independent reimplementation of Tailscale&amp;rsquo;s control server.&lt;/li>
&lt;li>&lt;strong>NetBird&lt;/strong> ships its &lt;strong>own coordination server as open source&lt;/strong>, as a supported part of the product. You can use NetBird Cloud or follow its &lt;a href="https://docs.netbird.io/selfhosted/selfhosted-quickstart" rel="noopener">self-hosting guide&lt;/a>. Its &lt;a href="https://github.com/netbirdio/netbird/blob/main/LICENSE" rel="noopener">repository license&lt;/a> is BSD-3-Clause except for &lt;code>management/&lt;/code>, &lt;code>signal/&lt;/code>, &lt;code>relay/&lt;/code> and &lt;code>combined/&lt;/code>, which use AGPLv3.&lt;/li>
&lt;/ul>
&lt;p>So &amp;ldquo;NetBird vs Tailscale&amp;rdquo; really means: &lt;strong>do you want a managed brain you never touch, or the option to own the brain yourself without leaving the supported path?&lt;/strong>&lt;/p>
&lt;h2 id="the-one-question-that-decides-it-do-you-want-to-run-the-control-plane">The one question that decides it: do you want to run the control plane?&lt;/h2>
&lt;p>This is the axis everything else hangs on.&lt;/p>
&lt;p>If the answer is &lt;strong>&amp;ldquo;no, I never want to run or secure another server,&amp;rdquo;&lt;/strong> Tailscale is built for you. You install clients, log in with an identity you already have, and Tailscale operates the coordination service. For a huge share of homelabbers - one person, a NAS, a couple of Pis, a laptop and a phone - that is exactly the right trade, as long as the Personal plan covers the users, groups and tagged servers you need.&lt;/p>
&lt;p>If the answer is &lt;strong>&amp;ldquo;yes, I want the coordination server on my own hardware,&amp;rdquo;&lt;/strong> NetBird is the stronger pick. You &lt;em>can&lt;/em> get there with Tailscale by running Headscale, and many people happily do. But Headscale is a community project chasing a proprietary target, with its own feature list and minimum client version. NetBird self-hosting is the vendor&amp;rsquo;s own stack. If owning the control plane is a hard requirement rather than a nice-to-have, that distinction matters.&lt;/p>
&lt;h2 id="what-self-hosting-netbird-asks-of-you">What self-hosting NetBird asks of you&lt;/h2>
&lt;p>&lt;a href="https://docs.netbird.io/about-netbird/how-netbird-works" rel="noopener">NetBird&amp;rsquo;s architecture guide&lt;/a> describes three logical roles. Management holds network state and distributes policy; signal helps peers negotiate; relay forwards encrypted traffic when a direct path fails.&lt;/p>
&lt;p>The &lt;a href="https://docs.netbird.io/selfhosted/selfhosted-quickstart" rel="noopener">quickstart&lt;/a>, checked November 18, 2026, deploys them as one Docker Compose stack with built-in Traefik for TLS and built-in local users, so an external identity provider is optional. It asks for a Linux VM with at least 1 CPU and 2 GB of memory, a public domain name pointing at it, and public access on TCP 443 and UDP 3478. A home connection behind CGNAT cannot offer that inbound access; the &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">Dynamic DNS guide&lt;/a> starts with that check.&lt;/p>
&lt;p>Opening those two ports puts a public service on the internet, so keep the server patched; closing the two forwards on your router or cloud firewall takes it off again.&lt;/p>
&lt;p>You own updates, backups, certificate renewal and relay capacity. &lt;a href="https://docs.netbird.io/about-netbird/self-hosted-vs-cloud" rel="noopener">NetBird&amp;rsquo;s cloud/self-host comparison&lt;/a> names the features that need an Enterprise Commercial License when self-hosted: SCIM provisioning, traffic-event logging, event streaming to SIEM tools, EDR integrations and peer approval. A homelab rarely needs any of them.&lt;/p>
&lt;p>Tailscale runs its own coordination service, so you maintain clients and policy rather than that infrastructure. Headscale moves the control-server work back to you.&lt;/p>
&lt;h2 id="what-you-get-on-each">What you get on each&lt;/h2>
&lt;p>Checked against each project&amp;rsquo;s documentation on November 18, 2026.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">NetBird&lt;/th>
&lt;th scope="col">Tailscale&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Clients&lt;/td>
&lt;td data-label="NetBird">Linux, macOS, Windows, Android, iOS, plus NAS, router and Docker installs&lt;/td>
&lt;td data-label="Tailscale">Linux, macOS, Windows, Android, iOS&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Exit node (all internet traffic through one peer)&lt;/td>
&lt;td data-label="NetBird">Yes, NetBird 0.27.0 or later&lt;/td>
&lt;td data-label="Tailscale">Yes&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Reach a whole LAN through one peer&lt;/td>
&lt;td data-label="NetBird">Network routes (on the free plan)&lt;/td>
&lt;td data-label="Tailscale">Subnet routers&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Private DNS names&lt;/td>
&lt;td data-label="NetBird">Private DNS (on the free plan)&lt;/td>
&lt;td data-label="Tailscale">MagicDNS, on by default for tailnets created since October 20, 2022&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">SSH over the mesh&lt;/td>
&lt;td data-label="NetBird">NetBird SSH (on the free plan)&lt;/td>
&lt;td data-label="Tailscale">Tailscale SSH&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Publish a service publicly&lt;/td>
&lt;td data-label="NetBird">Reverse Proxy, in beta&lt;/td>
&lt;td data-label="Tailscale">Funnel, in beta, on all plans&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Self-hosted control server&lt;/td>
&lt;td data-label="NetBird">Vendor&amp;rsquo;s quickstart: 1 CPU, 2 GB, public TCP 443 and UDP 3478, a domain&lt;/td>
&lt;td data-label="Tailscale">Not offered; Headscale is the community option&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="policy-and-day-to-day-ui-vs-acl-file">Policy and day-to-day: UI vs ACL file&lt;/h2>
&lt;p>For daily driving, the biggest felt difference is how you express access rules.&lt;/p>
&lt;p>&lt;strong>NetBird&lt;/strong> leans on a &lt;strong>web UI with groups and policies&lt;/strong> - you build access rules with dropdowns and toggles, and assign peers to groups that automate routing and permissions. For people who do not want to think in config syntax, this is friendlier, and it scales cleanly as the number of peers grows.&lt;/p>
&lt;p>Tailscale&amp;rsquo;s &lt;a href="https://tailscale.com/docs/reference/syntax/policy-file" rel="noopener">policy reference&lt;/a> defines a HuJSON file with ACLs and grants, and documents a visual policy editor too, so not every change means editing text.&lt;/p>
&lt;p>Neither is objectively better - it is a genuine UI-vs-config-file preference. If you like GitOps-style policy-as-code, Tailscale fits your hands. If you want to hand a teammate a console and dropdowns, NetBird does.&lt;/p>
&lt;h2 id="performance-compare-the-path">Performance: compare the path&lt;/h2>
&lt;p>There is no same-host, same-path benchmark on this page. Both carry traffic over WireGuard, so expect similar direct-path performance; the CPU, operating system, client build, MTU and the network in between still set the numbers you get.&lt;/p>
&lt;p>The difference that matters is the fallback. &lt;a href="https://tailscale.com/docs/reference/connection-types" rel="noopener">Tailscale documents&lt;/a> direct UDP paths alongside DERP and peer relays. &lt;a href="https://docs.netbird.io/about-netbird/understanding-nat-and-connectivity" rel="noopener">NetBird&amp;rsquo;s NAT guide&lt;/a> describes ICE negotiation and its own encrypted-traffic relay over QUIC or WebSocket, with TURN kept for legacy compatibility.&lt;/p>
&lt;p>To compare them yourself, record client versions and connection type, then time a transfer and check latency between the same two hosts. Repeat from the restrictive network you actually use while away. A fast direct path at home says little about a relayed mobile or office path, and the relay&amp;rsquo;s location and capacity can matter more than the product name.&lt;/p>
&lt;h2 id="cost-especially-at-scale">Cost, especially at scale&lt;/h2>
&lt;p>The &lt;a href="https://netbird.io/pricing" rel="noopener">NetBird pricing page&lt;/a> and &lt;a href="https://tailscale.com/pricing" rel="noopener">Tailscale pricing page&lt;/a> were checked November 18, 2026. NetBird&amp;rsquo;s page displayed EUR and Tailscale&amp;rsquo;s USD, so the table keeps each currency.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Hosted plan&lt;/th>
&lt;th scope="col">Listed amount&lt;/th>
&lt;th scope="col">Relevant scope&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Hosted plan">NetBird Free&lt;/td>
&lt;td data-label="Listed amount">€0&lt;/td>
&lt;td data-label="Relevant scope">Up to 5 users, 100 machines&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Hosted plan">NetBird Team&lt;/td>
&lt;td data-label="Listed amount">€6 per user/month&lt;/td>
&lt;td data-label="Relevant scope">100 machines plus 10 per user; enterprise IdP SSO/MFA and SCIM listed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Hosted plan">NetBird Business&lt;/td>
&lt;td data-label="Listed amount">€12 per user/month&lt;/td>
&lt;td data-label="Relevant scope">Adds device posture checks and traffic-event logging&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Hosted plan">Tailscale Personal&lt;/td>
&lt;td data-label="Listed amount">$0&lt;/td>
&lt;td data-label="Relevant scope">Non-commercial; 6 users, unlimited user devices, 3 ACL groups, 50 tagged resources to start&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Hosted plan">Tailscale Standard&lt;/td>
&lt;td data-label="Listed amount">$8 per user/month&lt;/td>
&lt;td data-label="Relevant scope">SCIM and up to 10 ACL groups listed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Hosted plan">Tailscale Premium&lt;/td>
&lt;td data-label="Listed amount">$18 per user/month&lt;/td>
&lt;td data-label="Relevant scope">Up to 300 ACL groups, network flow logs and log streaming listed&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Count user devices, tagged resources and machine allowances separately, because each plan caps them differently. A lower per-seat headline cannot settle total cost across two currencies and different entitlements. For self-hosting, add the server, your time and any commercial feature licence.&lt;/p>
&lt;h2 id="the-extras-that-can-tip-a-close-call">The extras that can tip a close call&lt;/h2>
&lt;p>&lt;strong>Post-quantum keys.&lt;/strong> NetBird added opt-in Rosenpass support in client v0.25.4, but its &lt;a href="https://docs.netbird.io/client/post-quantum-cryptography" rel="noopener">documentation&lt;/a> now marks it deprecated: from v0.82.0 the client prints a warning, the feature may be removed in a future release, and NetBird advises against new deployments depending on it. Do not choose NetBird for Rosenpass.&lt;/p>
&lt;p>&lt;strong>Publishing a service.&lt;/strong> &lt;a href="https://docs.netbird.io/manage/reverse-proxy" rel="noopener">NetBird Reverse Proxy&lt;/a> is in beta. It gives a service a public domain with an automatic TLS certificate, self-hosted deployments must use Traefik as their external reverse proxy, and it does not support Rosenpass. &lt;a href="https://tailscale.com/docs/features/tailscale-funnel" rel="noopener">Tailscale Funnel&lt;/a> is also in beta and available on all plans. If publishing rather than connecting is the main job, read &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale vs Cloudflare Tunnel&lt;/a> first.&lt;/p>
&lt;h2 id="side-by-side">Side-by-side&lt;/h2>
&lt;p>Documentation and prices checked November 18, 2026; use the linked guides for the release you deploy.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">NetBird&lt;/th>
&lt;th scope="col">Tailscale&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Data plane&lt;/td>
&lt;td data-label="NetBird">WireGuard&lt;/td>
&lt;td data-label="Tailscale">WireGuard&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Control plane&lt;/td>
&lt;td data-label="NetBird">Vendor publishes self-hosted server; cloud available&lt;/td>
&lt;td data-label="Tailscale">Proprietary managed service; independent Headscale alternative&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">License scope&lt;/td>
&lt;td data-label="NetBird">BSD-3-Clause; specified server directories AGPLv3&lt;/td>
&lt;td data-label="Tailscale">Core repository BSD-3-Clause; hosted control server proprietary&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Self-hosting cost&lt;/td>
&lt;td data-label="NetBird">Server and maintenance; some enterprise features need a commercial licence&lt;/td>
&lt;td data-label="Tailscale">Headscale server and maintenance&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Hosted free plan&lt;/td>
&lt;td data-label="NetBird">5 users, 100 machines&lt;/td>
&lt;td data-label="Tailscale">Personal: 6 users; group and tagged-resource caps above&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Policy workflow&lt;/td>
&lt;td data-label="NetBird">Dashboard groups and policies&lt;/td>
&lt;td data-label="Tailscale">HuJSON ACLs/grants with a visual editor&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Public service exposure&lt;/td>
&lt;td data-label="NetBird">Reverse Proxy beta&lt;/td>
&lt;td data-label="Tailscale">Funnel beta&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Direct-path speed&lt;/td>
&lt;td data-label="NetBird">No paired benchmark here&lt;/td>
&lt;td data-label="Tailscale">No paired benchmark here&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Deciding factor&lt;/td>
&lt;td data-label="NetBird">Owning the vendor&amp;rsquo;s documented control stack&lt;/td>
&lt;td data-label="Tailscale">Having the vendor operate the control service&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="so-which-should-you-run">So which should you run?&lt;/h2>
&lt;p>Pick Tailscale for a personal homelab when its managed service and free plan fit the access rules you need. Pick self-hosted NetBird when control-plane ownership is a requirement you are prepared to maintain. Look at NetBird Cloud if its dashboard suits you and you want managed infrastructure.&lt;/p>
&lt;p>Consider &lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a> when you want to keep Tailscale clients with a community control server; check its feature list and minimum client version before migrating.&lt;/p>
&lt;p>Whichever you pick, test the direct and relay paths from your real remote network before making it your only way back into the lab.&lt;/p></description></item><item><title>How to Test a UPS: Charge Is Not Health</title><link>https://techfuelhq.com/homelab/ups-testing-reality-2026/</link><pubDate>Mon, 07 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/ups-testing-reality-2026/</guid><atom:updated>2026-11-18T05:50:00Z</atom:updated><description>&lt;p>The number on the front of a UPS is a charge reading. It is not a health reading.&lt;/p>
&lt;p>&lt;strong>A unit showing full can drop the load the moment it transfers.&lt;/strong> The display will have been telling you everything was fine right up until the instant it stopped being fine, and it was not lying — it was answering a different question than the one you thought you were asking.&lt;/p>
&lt;p>That gap between charged and working is the whole subject here. &lt;a href="https://techfuelhq.com/tools/ups-runtime-calculator/">Sizing the unit&lt;/a> is settled territory: VA against watts, runtime against your shutdown window, with the &lt;a href="https://techfuelhq.com/homelab/24-7-homelab-idle-power-costs-2026/">idle power reference&lt;/a> for what typical homelab gear draws. This is about what comes after you have bought the right size — proving it does the job, on a schedule, before the power goes out and proves it for you.&lt;/p>
&lt;p>For the actual purchase decision, our &lt;a href="https://techfuelhq.com/reviews/cyberpower-cp1500pfclcd-review-2026/">CyberPower CP1500PFCLCD review&lt;/a> explains its generation and battery differences. The &lt;a href="https://techfuelhq.com/reviews/apc-back-ups-pro-br1500ms2-review-2026/">APC Back-UPS Pro BR1500MS2 review&lt;/a> covers the corresponding load, installation and shutdown-software questions.&lt;/p>
&lt;h2 id="the-quick-version-five-checks-at-home">The quick version: five checks at home&lt;/h2>
&lt;p>These run in order from harmless to disruptive. Steps 1, 3 and 4 change nothing. Step 2 puts the load on battery for a few seconds. Step 5 shuts down the machines the UPS protects, so do it only in a maintenance window with current backups. The rest of the page explains each step and the record that goes with it.&lt;/p>
&lt;h3 id="1-check-the-batterys-age">1. Check the battery&amp;rsquo;s age&lt;/h3>
&lt;p>Schneider puts most APC batteries at three to five years and says every 8°C (15°F) of extra operating temperature halves that life (&lt;a href="https://www.se.com/us/en/faqs/FA158934/" rel="noopener">Schneider Electric FA158934&lt;/a>). If NUT is already running, &lt;code>upsc upsname@localhost&lt;/code> shows &lt;code>battery.date&lt;/code>, the battery installation or last change date, on UPSes that report it (&lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_variables.html" rel="noopener">NUT variable reference&lt;/a>). A battery past that window is the first suspect, whatever the panel says.&lt;/p>
&lt;h3 id="2-run-the-built-in-self-test">2. Run the built-in self-test&lt;/h3>
&lt;p>Start it at a time when a brief interruption would be acceptable. On most Back-UPS units, Schneider says to press and hold the power button while the unit is on and plugged in, and let go at the second beep or when the online LED starts blinking; it varies by model, so check the manual (&lt;a href="https://www.se.com/us/en/faqs/FAQ000267818/" rel="noopener">Schneider Electric FAQ000267818&lt;/a>). The same note advises a load of 10% to 30% of the unit&amp;rsquo;s capacity for the test and warns that a Back-UPS can drop the load if it overloads on battery. With NUT, &lt;code>upscmd -l upsname&lt;/code> lists the instant commands your UPS supports; a battery test appears there as &lt;code>test.battery.start.quick&lt;/code> or a similar &lt;code>test.battery.start&lt;/code> command when the hardware has one (&lt;a href="https://networkupstools.org/docs/man/upscmd.html" rel="noopener">upscmd manual&lt;/a>, &lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_instant_commands_4.html" rel="noopener">instant commands&lt;/a>).&lt;/p>
&lt;h3 id="3-read-the-result">3. Read the result&lt;/h3>
&lt;p>A Back-UPS that finds runtime close to or below its standard two-minute limit raises a replace-battery alarm; on Back-UPS Pro models Schneider describes it as rapid chirping with a replace-battery indicator (&lt;a href="https://www.se.com/us/en/faqs/FAQ000267818/" rel="noopener">FAQ000267818&lt;/a>). In NUT, &lt;code>ups.test.result&lt;/code> holds the result of the last self-test when the driver exposes it (&lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_variables.html" rel="noopener">NUT variable reference&lt;/a>).&lt;/p>
&lt;h3 id="4-preview-the-shutdown-without-powering-anything-off">4. Preview the shutdown without powering anything off&lt;/h3>
&lt;p>On the machine running NUT, &lt;code>upsdrvctl -t shutdown&lt;/code> displays the shutdown sequence without calling the drivers. NUT&amp;rsquo;s &lt;a href="https://networkupstools.org/docs/user-manual.chunked/ar01s06.html" rel="noopener">shutdown testing instructions&lt;/a> start there.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>upsdrvctl -t shutdown
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="5-time-a-real-shutdown-in-a-maintenance-window">5. Time a real shutdown in a maintenance window&lt;/h3>
&lt;p>Open the &lt;a href="https://techfuelhq.com/downloads/ups-shutdown-verification-record.csv" download type="text/csv">shutdown verification record&lt;/a>, start a stopwatch and run NUT&amp;rsquo;s forced-shutdown test. NUT says it executes the full shutdown sequence: the computer is powered off, may stay off for a few seconds to a few minutes depending on the driver and UPS, and then powers on again. A successful sequence is one where the operating system halts before the battery runs out and the system restarts when power returns.&lt;/p>
&lt;p>Warning: the next command shuts down this machine and can switch off the UPS output and everything attached to it, even with mains present.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>upsmon -c fsd
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This tests the shutdown chain while mains is present. Whether the battery carries the load through that chain is the on-battery run in the full procedure below; follow your UPS maker&amp;rsquo;s approved procedure for that, and stop at your time limit.&lt;/p>
&lt;h2 id="the-built-in-self-test-is-not-a-runtime-test">The built-in self-test is not a runtime test&lt;/h2>
&lt;p>Most units test themselves. The test covers less than the name suggests.&lt;/p>
&lt;p>Schneider&amp;rsquo;s documentation for the Smart-UPS line says the unit self-tests when you switch it on and every two weeks after that, and that during the test it runs on battery for approximately ten seconds (&lt;a href="https://www.se.com/us/en/faqs/FA405317/" rel="noopener">Schneider Electric FA405317&lt;/a>). The Back-UPS line runs the same ten seconds on a different clock — Schneider describes the automatic test as happening every seven days after the unit is powered on — and its replace-battery alarm is framed against a standard two-minute runtime limit (&lt;a href="https://www.se.com/us/en/faqs/FAQ000267818/" rel="noopener">Schneider Electric FAQ000267818&lt;/a>).&lt;/p>
&lt;p>The self-test puts the connected load on battery and checks the battery and internal subsystems. Keep it enabled. A pass is useful evidence about that short test; it does not show how long your workload takes to stop or whether power will last through that sequence. Schneider also warns that a Back-UPS can drop the load during a self-test if it overloads on battery. Schedule even this short check when an interruption is acceptable.&lt;/p>
&lt;p>&lt;strong>Charge is a percentage. Capacity is minutes. The panel shows you the first one and you need the second one.&lt;/strong>&lt;/p>
&lt;h2 id="keep-a-timed-shutdown-record">Keep a timed shutdown record&lt;/h2>
&lt;p>&lt;a href="https://techfuelhq.com/downloads/ups-shutdown-verification-record.csv" download type="text/csv">Download the UPS shutdown verification record (CSV)&lt;/a>. Open it in a spreadsheet, fill the &lt;code>value&lt;/code> column and save a separate copy for each run. The other columns give units and recording instructions. The blank sheet contains no measured results.&lt;/p>
&lt;p>I would test one chain at a time: UPS, the machine running NUT, the network path needed by any other clients, then the guests and hosts that must stop. If the switch loses power before another host receives its shutdown signal, a working USB cable on the first machine does not finish the job.&lt;/p>
&lt;h3 id="set-the-boundary-before-testing">Set the boundary before testing&lt;/h3>
&lt;p>Use a maintenance window when the connected equipment can lose power, confirm backups, and let the UPS charge as its manual requires. Record the model, battery installation date if known, connected equipment and normal workload. Check for an existing fault or overload before starting. Resolve those first.&lt;/p>
&lt;p>For a battery-supported run, follow the exact model&amp;rsquo;s approved test procedure and retain protective earthing. Do not improvise mains wiring or assume that pulling an input plug is appropriate for every UPS. Set a conservative time limit and a recovery plan before switching to battery. Stop on an overload, unexpected power loss, communication failure or the time limit. Restore normal input by the approved procedure; do not keep draining the battery to obtain a bigger number.&lt;/p>
&lt;p>If you do not yet have a working automatic shutdown configuration, stop at preparation. This record verifies an existing setup; it is not a NUT installation recipe. NUT&amp;rsquo;s &lt;a href="https://networkupstools.org/docs/user-manual.chunked/ar01s06.html" rel="noopener">shutdown testing instructions&lt;/a> separate previewing the shutdown sequence from executing it. A forced-shutdown test is a real shutdown, even with mains present. It can switch off the UPS output and all attached equipment.&lt;/p>
&lt;h3 id="read-the-status-without-changing-it">Read the status without changing it&lt;/h3>
&lt;p>On an already configured NUT system, replace &lt;code>upsname&lt;/code> with its configured UPS name. This read-only command displays the values the driver exposes:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>upsc upsname@localhost
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;a href="https://networkupstools.org/docs/man/upsc.html" rel="noopener">upsc manual&lt;/a> documents that address format. Use the NUT server&amp;rsquo;s hostname instead of &lt;code>localhost&lt;/code> when reading a remote server. Save the output with the record. A missing field is &lt;code>unknown&lt;/code>, never zero.&lt;/p>
&lt;p>NUT defines &lt;code>ups.load&lt;/code> as percent, &lt;code>ups.realpower&lt;/code> as watts and &lt;code>battery.runtime&lt;/code> as seconds in its &lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_variables.html" rel="noopener">variable reference&lt;/a>. Keep those units separate. Record where a watt reading came from; a UPS-reported watt value is not a wall-meter measurement. Label displayed runtime as an estimate.&lt;/p>
&lt;h3 id="record-the-sequence">Record the sequence&lt;/h3>
&lt;p>For an on-battery run, start one stopwatch when the UPS reports the switch to battery. Use it for every elapsed time, and save timestamped logs as supporting evidence. For a software-only rehearsal, start at the shutdown request instead and mark battery-only fields &lt;code>not tested&lt;/code>.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Record field&lt;/th>
&lt;th scope="col">What to enter&lt;/th>
&lt;th scope="col">What it tells you&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Record field">&lt;code>transfer_survived&lt;/code>&lt;/td>
&lt;td data-label="What to enter">Yes, no or not tested&lt;/td>
&lt;td data-label="What it tells you">Whether the protected equipment stayed on through transfer&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Record field">&lt;code>shutdown_trigger_s&lt;/code>&lt;/td>
&lt;td data-label="What to enter">Elapsed seconds, plus the event or rule in &lt;code>shutdown_trigger&lt;/code>&lt;/td>
&lt;td data-label="What it tells you">When shutdown was requested; do not infer it from a later loss of network access&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Record field">&lt;code>last_guest_stopped_s&lt;/code>&lt;/td>
&lt;td data-label="What to enter">Elapsed seconds and a reference to guest/task logs&lt;/td>
&lt;td data-label="What it tells you">Whether the last guest completed a clean stop before the host went off&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Record field">&lt;code>host_off_s&lt;/code>&lt;/td>
&lt;td data-label="What to enter">Elapsed seconds and how power-off was confirmed&lt;/td>
&lt;td data-label="What it tells you">When the protected host finished; an unreachable web UI alone does not establish this&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Record field">&lt;code>input_restored_s&lt;/code>&lt;/td>
&lt;td data-label="What to enter">Elapsed seconds&lt;/td>
&lt;td data-label="What it tells you">Whether mains returned before or after shutdown completed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Record field">&lt;code>ups_output_lost_s&lt;/code>&lt;/td>
&lt;td data-label="What to enter">Elapsed seconds only if it happened&lt;/td>
&lt;td data-label="What it tells you">An unexpected loss before clean shutdown is a failed run, not a target to aim for&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Record field">&lt;code>reported_runtime_at_trigger_s&lt;/code>&lt;/td>
&lt;td data-label="What to enter">The runtime estimate displayed at the trigger, or unknown&lt;/td>
&lt;td data-label="What it tells you">Context for the next check; it is not a measured reserve&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The sheet also records NUT/OS versions, battery charge, load, the test procedure, planned deadline, faults and restart checks. Keep a separate list of every protected host if the UPS feeds several. One successful host does not pass the others.&lt;/p>
&lt;p>NUT&amp;rsquo;s &lt;a href="https://networkupstools.org/docs/man/upsmon.html" rel="noopener">upsmon manual&lt;/a> distinguishes on-battery, low-battery and forced-shutdown events. Note which one your configuration uses. Once forced shutdown has started, returning mains is not a reliable cancellation method: NUT&amp;rsquo;s FSD state remains set until its data-server daemon restarts. Follow your prepared recovery procedure.&lt;/p>
&lt;h3 id="calculate-two-times-then-mark-the-result">Calculate two times, then mark the result&lt;/h3>
&lt;p>&lt;strong>Shutdown duration = &lt;code>host_off_s − shutdown_trigger_s&lt;/code>.&lt;/strong> This is the time your existing shutdown chain took after the request. Preserve the guest logs, because a host that powered off by forcibly terminating a guest has not passed the clean-shutdown check.&lt;/p>
&lt;p>&lt;strong>Planned margin = &lt;code>planned_deadline_s − host_off_s&lt;/code>.&lt;/strong> This measures completion against the deadline you chose. It does not measure how much battery was left. The &lt;a href="https://techfuelhq.com/tools/ups-runtime-calculator/">UPS runtime calculator&lt;/a> can help choose a starting expectation, but its curve cannot certify an aged battery in your rack.&lt;/p>
&lt;p>Mark an on-battery run &lt;code>pass&lt;/code> only if transfer survived, every protected guest and host stopped cleanly before the chosen deadline, and UPS output lasted through that completion without mains assistance. If you restored mains early, lost the record or could not confirm a guest&amp;rsquo;s stop, mark it &lt;code>incomplete&lt;/code>. Any dropped load, forced guest stop or missed deadline is &lt;code>fail&lt;/code>. A software-only rehearsal can pass its shutdown checks while battery support remains untested.&lt;/p>
&lt;p>Save the actual logs next to the sheet.&lt;/p>
&lt;p>After restoring normal power, record whether the UPS and its protected equipment returned as intended. Check that services are available and the battery is recharging. NUT&amp;rsquo;s testing instructions include restart behavior for a reason. On the next run, compare the same equipment, workload and trigger; a shorter test with fewer guests is not evidence of an improved battery.&lt;/p>
&lt;h2 id="pure-sine-or-dont-put-a-server-psu-behind-it">Pure sine, or don&amp;rsquo;t put a server PSU behind it&lt;/h2>
&lt;p>This one has a mechanism, and the mechanism is published by the people selling the cheaper option.&lt;/p>
&lt;p>CyberPower&amp;rsquo;s explanation of its own PFC Sinewave line is that a simulated sine wave produces a zero-output state during the phase change — a gap in the waveform — and that this gap can interrupt equipment running an active-PFC power supply when the unit switches from mains to battery (&lt;a href="https://www.cyberpowersystems.com/news/pfc-sinewave-series-ups-systems-the-most-affordable-feature-rich-pure-sine-wave-ups/" rel="noopener">CyberPower, PFC Sinewave Series&lt;/a>).&lt;/p>
&lt;p>Read where that failure lands. Not during a brownout, not on a slow degrade — at transfer. The single event the UPS exists to handle is the event a simulated-sine unit is worst at, and active PFC is standard in modern PC and server supplies; CyberPower&amp;rsquo;s own page dates that transition to the last fifteen years.&lt;/p>
&lt;p>&lt;strong>Simulated sine into an active-PFC supply is asking for trouble on transfer. Pure sine for anything with a server PSU behind it.&lt;/strong>&lt;/p>
&lt;p>Two sine wave units have full reviews on this site. Ratings are from each maker&amp;rsquo;s datasheet (&lt;a href="https://dl4jz3rbrsfum.cloudfront.net/documents/CyberPower_DS_CP1500PFCLCD.pdf" rel="noopener">CyberPower&lt;/a>, &lt;a href="https://cdn.gescan.com/PIM_Docs/Docs/STEP_ASSETS_PDF/298390643.pdf" rel="noopener">APC&lt;/a>); the Newegg prices are from its catalogue on November 17, 2026, and both were marketplace listings, so read the seller name before the price.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">UPS&lt;/th>
&lt;th scope="col">Maker&amp;rsquo;s rating&lt;/th>
&lt;th scope="col">Newegg, November 17, 2026&lt;/th>
&lt;th scope="col">Buy&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="UPS">&lt;a href="https://techfuelhq.com/reviews/cyberpower-cp1500pfclcd-review-2026/">CyberPower CP1500PFCLCD&lt;/a>&lt;/td>
&lt;td data-label="Maker&amp;rsquo;s rating">1500VA / 1000W, sine wave on battery&lt;/td>
&lt;td data-label="Newegg, November 17, 2026">$239.95&lt;/td>
&lt;td data-label="Buy">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=CyberPower&amp;#43;CP1500PFCLCD&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/ups-testing-reality-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fcyberpower-cp1500pfclcd-nema-5-15r%2Fp%2FN82E16842102134" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/ups-testing-reality-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="UPS">&lt;a href="https://techfuelhq.com/reviews/apc-back-ups-pro-br1500ms2-review-2026/">APC Back-UPS Pro BR1500MS2&lt;/a>&lt;/td>
&lt;td data-label="Maker&amp;rsquo;s rating">1500VA / 900W, sine wave&lt;/td>
&lt;td data-label="Newegg, November 17, 2026">$318.70&lt;/td>
&lt;td data-label="Buy">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=APC&amp;#43;BR1500MS2&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/ups-testing-reality-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fapc-br1500ms2%2Fp%2FN82E16842301736" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/ups-testing-reality-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="usb-and-nut-not-a-network-management-card">USB and NUT, not a network management card&lt;/h2>
&lt;p>Network management cards cost absurd money next to the UPS they plug into. A &lt;a href="https://www.se.com/uk/en/product/AP9641/network-management-card-3-nmc3-with-environmental-monitoring-secure-remote-ups-monitoring-and-management/" rel="noopener">UPS network management card&lt;/a> is a separate accessory bought on top of the unit, and for a single-site homelab it buys network-side monitoring you can get from a cable.&lt;/p>
&lt;p>USB plus &lt;a href="https://networkupstools.org/" rel="noopener">NUT&lt;/a> does the job and is what I&amp;rsquo;d run. Three pieces:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>usbhid-ups&lt;/code>&lt;/strong> should detect anything implementing the HID Power Device Class, with the amount of data varying by manufacturer and model. NUT lists the newer Eaton USB models, all MGE and Dell USB models, all AMETEK Powervar UPM models, and some models from APC, Belkin, CyberPower, EcoFlow, Powercom, PowerWalker, TrippLite and Vertiv (&lt;a href="https://networkupstools.org/docs/man/usbhid-ups.html" rel="noopener">usbhid-ups man page&lt;/a>). Check your exact model against the compatibility list before you count on it.&lt;/li>
&lt;li>&lt;strong>&lt;code>upsmon&lt;/code>&lt;/strong> watches for the critical condition — on battery, low charge — sets the forced-shutdown flag, and lets every machine it is monitoring run its own shutdown command with a delay you set (&lt;a href="https://networkupstools.org/docs/user-manual.chunked/Configuration_notes.html" rel="noopener">NUT configuration notes&lt;/a>).&lt;/li>
&lt;li>&lt;strong>&lt;code>upscmd&lt;/code>&lt;/strong> lists and runs the instant commands supported by your UPS, including the alarm control below when available.&lt;/li>
&lt;/ul>
&lt;p>That is the entire feature set most homelabs wanted from the card.&lt;/p>
&lt;p>&lt;strong>If it can&amp;rsquo;t trigger a clean shutdown of what&amp;rsquo;s plugged into it, most of the value is gone.&lt;/strong> A UPS that only buys you a few minutes of uptime during which nobody is home to act is a very expensive way to delay the same unclean power-off. Configure the shutdown chain when the unit arrives, then use the timed record above to check that each machine completes it.&lt;/p>
&lt;h2 id="the-alarm-will-go-off-at-3am">The alarm will go off at 3am&lt;/h2>
&lt;p>It will. The alarm is standard equipment, and the first time it fires is the worst possible moment to be learning where the mute button is.&lt;/p>
&lt;p>Decide now what you want it to do, and set it now. NUT exposes &lt;code>beeper.disable&lt;/code>, &lt;code>beeper.mute&lt;/code>, &lt;code>beeper.enable&lt;/code> and &lt;code>beeper.toggle&lt;/code> as instant commands (&lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_instant_commands_4.html" rel="noopener">same reference&lt;/a>), so this is one &lt;code>upscmd&lt;/code> call, done while you are awake and thinking clearly about whether you actually want an audible alarm in that room.&lt;/p>
&lt;h2 id="batteries-are-a-consumable">Batteries are a consumable&lt;/h2>
&lt;p>Plan for the replacement rather than being surprised by it. Sealed lead-acid cells are on a several-year cycle, and third-party replacements are standard practice — not a corner cut.&lt;/p>
&lt;p>Schneider puts most APC batteries at three to five years and notes that every 8°C (15°F) of extra operating temperature halves that life (&lt;a href="https://www.se.com/us/en/faqs/FA158934/" rel="noopener">Schneider Electric FA158934&lt;/a>). That second figure is the one people miss. A UPS in a warm closet is not on the same schedule as the same UPS in a basement, and if you have put yours in the warm closet, the replacement year on your calendar is optimistic.&lt;/p>
&lt;p>Which puts you back at the test. The only way to know where your battery is on that curve is to have measured it recently under load.&lt;/p>
&lt;h2 id="what-id-do-pure-sine-usb-nut-and-a-recorded-test">What I&amp;rsquo;d do: pure sine, USB, NUT, and a recorded test&lt;/h2>
&lt;p>&lt;strong>Buy a pure sine wave unit sized to your load, connect it over USB, run NUT, and schedule a shutdown verification.&lt;/strong> For my single-rack plan, I would start there before buying a management card. Check that the exact UPS supports the functions your setup needs.&lt;/p>
&lt;p>Keep the &lt;a href="https://techfuelhq.com/downloads/ups-shutdown-verification-record.csv" download type="text/csv">verification record&lt;/a> beside your backup checks. Repeat after a battery replacement, a material load change or a shutdown configuration change, as well as the schedule recommended by the UPS maker. If the protected load cannot complete its clean shutdown within the available window, correct the battery, load or shutdown timing before relying on the setup unattended.&lt;/p>
&lt;p>&lt;strong>This is wrong for a few situations.&lt;/strong> Simulated sine into active PFC — do not, at any price. A consumer unit under a full rack, where the load is past what the unit is rated to hold and the runtime is theatre. And anyone who will not set up automatic shutdown, because at that point the money bought a surge protector with a battery in it, which is where this started.&lt;/p>
&lt;p>Keep backups on separate equipment. A successful shutdown test does not replace them.&lt;/p>
&lt;h2 id="sources-for-the-timed-record">Sources for the timed record&lt;/h2>
&lt;p>Read October 4, 2026 and re-read November 18, 2026:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://www.se.com/us/en/faqs/FA405317/" rel="noopener">Schneider: Smart-UPS self-test&lt;/a> and &lt;a href="https://www.se.com/us/en/faqs/FAQ000267818/" rel="noopener">Back-UPS self-test&lt;/a>: duration, use of the connected load, the overload caveat, the manual self-test and the replace-battery alarm.&lt;/li>
&lt;li>&lt;a href="https://www.se.com/us/en/faqs/FA158934/" rel="noopener">Schneider: APC battery life&lt;/a>: three to five years and the temperature rule.&lt;/li>
&lt;li>&lt;a href="https://networkupstools.org/docs/user-manual.chunked/ar01s06.html" rel="noopener">NUT configuration notes, Testing shutdowns&lt;/a>: preview versus executed shutdown and checking recovery.&lt;/li>
&lt;li>&lt;a href="https://networkupstools.org/docs/man/upscmd.html" rel="noopener">NUT upscmd manual&lt;/a> and &lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_instant_commands_4.html" rel="noopener">instant commands&lt;/a>: listing and running battery tests.&lt;/li>
&lt;li>&lt;a href="https://dl4jz3rbrsfum.cloudfront.net/documents/CyberPower_DS_CP1500PFCLCD.pdf" rel="noopener">CyberPower CP1500PFCLCD datasheet&lt;/a> and &lt;a href="https://cdn.gescan.com/PIM_Docs/Docs/STEP_ASSETS_PDF/298390643.pdf" rel="noopener">APC BR1500MS2 datasheet&lt;/a>: capacity and waveform.&lt;/li>
&lt;li>&lt;a href="https://networkupstools.org/docs/man/upsmon.html" rel="noopener">NUT upsmon manual&lt;/a>: on-battery, low-battery and forced-shutdown states; FSD persistence; software-triggered shutdown tests.&lt;/li>
&lt;li>&lt;a href="https://networkupstools.org/docs/man/upsc.html" rel="noopener">NUT upsc manual&lt;/a> and &lt;a href="https://networkupstools.org/docs/developer-guide.chunked/_variables.html" rel="noopener">variable reference&lt;/a>: read-only status retrieval and field units.&lt;/li>
&lt;/ul></description></item><item><title>Caddy vs Nginx Proxy Manager vs Traefik in 2026</title><link>https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/</link><pubDate>Wed, 17 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/</guid><atom:updated>2026-11-18T05:45:00Z</atom:updated><description>&lt;p>A reverse proxy is the front door to a homelab. It puts clean hostnames and automatic HTTPS in front of all your services, so &lt;code>jellyfin.example.com&lt;/code> opens over HTTPS instead of everyone memorizing &lt;code>192.168.1.14:8096&lt;/code>. That publicly trusted certificate needs a domain you control: Caddy&amp;rsquo;s docs say names under &lt;code>.local&lt;/code>, &lt;code>.internal&lt;/code> and &lt;code>.home.arpa&lt;/code> can&amp;rsquo;t get one, and get certificates from Caddy&amp;rsquo;s own local CA instead, which every device then has to trust.&lt;/p>
&lt;p>Three names dominate the choice in 2026: &lt;strong>Caddy&lt;/strong>, &lt;strong>Nginx Proxy Manager (NPM)&lt;/strong>, and &lt;strong>Traefik&lt;/strong>. They&amp;rsquo;re all free, all open source, and all solve the same problem, but they have genuinely different personalities, and picking well is mostly about matching one to how &lt;em>you&lt;/em> like to work. Versions, licences and features below come from each project&amp;rsquo;s own repos and docs, read November 18, 2026.&lt;/p>
&lt;h2 id="the-choice-in-one-screen">The choice in one screen&lt;/h2>
&lt;p>Skip to the section that fits you, or read the whole thing. Here is the shape of the decision before the details.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Caddy&lt;/th>
&lt;th scope="col">Nginx Proxy Manager&lt;/th>
&lt;th scope="col">Traefik&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">License&lt;/td>
&lt;td data-label="Caddy">&lt;strong>Apache 2.0&lt;/strong>&lt;/td>
&lt;td data-label="Nginx Proxy Manager">&lt;strong>MIT&lt;/strong>&lt;/td>
&lt;td data-label="Traefik">&lt;strong>MIT&lt;/strong> (open-core add-ons)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Interface&lt;/td>
&lt;td data-label="Caddy">Caddyfile (config-as-code)&lt;/td>
&lt;td data-label="Nginx Proxy Manager">&lt;strong>Web GUI&lt;/strong>&lt;/td>
&lt;td data-label="Traefik">Config + Docker labels&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Auto HTTPS&lt;/td>
&lt;td data-label="Caddy">Most automatic (LE + ZeroSSL)&lt;/td>
&lt;td data-label="Nginx Proxy Manager">Per-host, via UI&lt;/td>
&lt;td data-label="Traefik">Cert resolvers (config)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Docker auto-discovery&lt;/td>
&lt;td data-label="Caddy">Plugin only&lt;/td>
&lt;td data-label="Nginx Proxy Manager">&lt;strong>No&lt;/strong>&lt;/td>
&lt;td data-label="Traefik">&lt;strong>Yes (native)&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Learning curve&lt;/td>
&lt;td data-label="Caddy">Moderate&lt;/td>
&lt;td data-label="Nginx Proxy Manager">&lt;strong>Lowest&lt;/strong>&lt;/td>
&lt;td data-label="Traefik">&lt;strong>Steepest&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Written in&lt;/td>
&lt;td data-label="Caddy">Go (single binary)&lt;/td>
&lt;td data-label="Nginx Proxy Manager">nginx + OpenResty + Node UI + DB&lt;/td>
&lt;td data-label="Traefik">Go (single binary)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">GitHub stars (approx, 2026-11-18)&lt;/td>
&lt;td data-label="Caddy">~79k&lt;/td>
&lt;td data-label="Nginx Proxy Manager">~35k&lt;/td>
&lt;td data-label="Traefik">~66k&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Latest stable (2026-11-18)&lt;/td>
&lt;td data-label="Caddy">2.11.9 (Nov 5)&lt;/td>
&lt;td data-label="Nginx Proxy Manager">2.17.0 (Nov 12)&lt;/td>
&lt;td data-label="Traefik">3.7.19 (Nov 13)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Best for&lt;/td>
&lt;td data-label="Caddy">Config-as-code, easiest TLS&lt;/td>
&lt;td data-label="Nginx Proxy Manager">Beginners, GUI lovers&lt;/td>
&lt;td data-label="Traefik">Docker/K8s dynamic labs&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>&lt;em>Star counts and latest-release tags were read from each project&amp;rsquo;s GitHub API on November 18, 2026 and drift over time; check each repo for today&amp;rsquo;s numbers.&lt;/em>&lt;/p>
&lt;p>The single most useful way to feel the difference is to watch each one do the exact same job. Here is what it takes to put HTTPS in front of one service in all three:&lt;/p>
&lt;div class="visual-block">
&lt;div style="background:#0d1117;padding:24px 20px 22px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',sans-serif;color:#e8eaf2;">
&lt;div style="font-size:18px;font-weight:700;letter-spacing:-0.3px;">The same service, three ways&lt;/div>
&lt;div style="font-size:0.875rem;color:#93a0bd;margin-top:5px;line-height:1.55;max-width:600px;">One job &amp;mdash; reverse-proxy &lt;span style="color:#c3cbe0;font-family:ui-monospace,Menlo,Consolas,monospace;">app.example.com&lt;/span> to a container at &lt;span style="color:#c3cbe0;font-family:ui-monospace,Menlo,Consolas,monospace;">192.168.1.10:8080&lt;/span> with automatic HTTPS. Three completely different surfaces. This contrast, not benchmarks, is the actual choice.&lt;/div>
&lt;div style="display:flex;gap:14px;flex-wrap:wrap;margin-top:20px;">
&lt;div style="flex:1 1 210px;min-width:0;background:#11161f;border:1px solid rgba(255,255,255,0.08);border-top:3px solid #4a9eff;border-radius:8px;padding:14px 13px 13px;">
&lt;div style="font-size:13.5px;font-weight:700;color:#eef1f8;">Nginx Proxy Manager&lt;/div>
&lt;div style="font-size:0.8125rem;color:#4a9eff;font-weight:600;margin:2px 0 11px;">point &amp;amp; click&lt;/div>
&lt;div style="font-size:0.875rem;color:#c3cbe0;line-height:1.5;">
&lt;div style="display:flex;justify-content:space-between;gap:8px;padding:5px 0;border-bottom:1px solid rgba(255,255,255,0.06);">&lt;span style="color:#8b97b8;">Domain&lt;/span>&lt;span style="font-family:ui-monospace,Menlo,Consolas,monospace;">app.example.com&lt;/span>&lt;/div>
&lt;div style="display:flex;justify-content:space-between;gap:8px;padding:5px 0;border-bottom:1px solid rgba(255,255,255,0.06);">&lt;span style="color:#8b97b8;">Forward host&lt;/span>&lt;span style="font-family:ui-monospace,Menlo,Consolas,monospace;">192.168.1.10&lt;/span>&lt;/div>
&lt;div style="display:flex;justify-content:space-between;gap:8px;padding:5px 0;border-bottom:1px solid rgba(255,255,255,0.06);">&lt;span style="color:#8b97b8;">Forward port&lt;/span>&lt;span style="font-family:ui-monospace,Menlo,Consolas,monospace;">8080&lt;/span>&lt;/div>
&lt;div style="display:flex;align-items:center;gap:7px;padding:7px 0 4px;">&lt;span style="width:13px;height:13px;border-radius:3px;background:#4a9eff;color:#04122a;font-size:0.8125rem;font-weight:900;display:inline-flex;align-items:center;justify-content:center;">&amp;check;&lt;/span>&lt;span>SSL tab &amp;rarr; Request new certificate&lt;/span>&lt;/div>
&lt;/div>
&lt;div style="margin-top:11px;padding-top:9px;border-top:1px dashed rgba(255,255,255,0.12);font-size:0.8125rem;color:#7fb0ee;font-weight:600;">~6 clicks &amp;middot; no file &amp;middot; no restart&lt;/div>
&lt;/div>
&lt;div style="flex:1 1 210px;min-width:0;background:#11161f;border:1px solid rgba(255,255,255,0.08);border-top:3px solid #5dca7a;border-radius:8px;padding:14px 13px 13px;">
&lt;div style="font-size:13.5px;font-weight:700;color:#eef1f8;">Caddy&lt;/div>
&lt;div style="font-size:0.8125rem;color:#5dca7a;font-weight:600;margin:2px 0 11px;">config as code&lt;/div>
&lt;div style="font-family:ui-monospace,Menlo,Consolas,monospace;font-size:0.875rem;line-height:1.6;color:#dfe6f2;background:#0a0d12;border-radius:6px;padding:10px 11px;white-space:pre-wrap;word-break:break-word;">&lt;span style="color:#5dca7a;">app.example.com&lt;/span> {
reverse_proxy &lt;span style="color:#e8c07a;">192.168.1.10:8080&lt;/span>
}&lt;/div>
&lt;div style="margin-top:11px;padding-top:9px;border-top:1px dashed rgba(255,255,255,0.12);font-size:0.8125rem;color:#a6d94a;font-weight:600;">3 lines &amp;middot; 1 file &amp;middot; HTTPS is automatic&lt;/div>
&lt;/div>
&lt;div style="flex:1 1 210px;min-width:0;background:#11161f;border:1px solid rgba(255,255,255,0.08);border-top:3px solid #f0a020;border-radius:8px;padding:14px 13px 13px;">
&lt;div style="font-size:13.5px;font-weight:700;color:#eef1f8;">Traefik&lt;/div>
&lt;div style="font-size:0.8125rem;color:#f0a020;font-weight:600;margin:2px 0 11px;">label discovery&lt;/div>
&lt;div style="font-family:ui-monospace,Menlo,Consolas,monospace;font-size:0.875rem;line-height:1.55;color:#dfe6f2;background:#0a0d12;border-radius:6px;padding:10px 11px;white-space:pre-wrap;word-break:break-word;">labels:
- &lt;span style="color:#e8c07a;">traefik.enable=true&lt;/span>
- &lt;span style="color:#e8c07a;">traefik.http.routers.app.rule=&lt;/span>
&lt;span style="color:#e8c07a;">Host(&amp;#96;app.example.com&amp;#96;)&lt;/span>
- &lt;span style="color:#e8c07a;">...tls.certresolver=le&lt;/span>&lt;/div>
&lt;div style="margin-top:9px;font-size:0.8125rem;color:#93a0bd;line-height:1.5;">plus a one-time static config (entrypoints, cert resolver) that every service then reuses.&lt;/div>
&lt;div style="margin-top:9px;padding-top:9px;border-top:1px dashed rgba(255,255,255,0.12);font-size:0.8125rem;color:#f3b855;font-weight:600;">3+ labels per service &amp;middot; auto-routes on deploy&lt;/div>
&lt;/div>
&lt;/div>
&lt;div style="margin-top:16px;padding-top:12px;border-top:1px solid rgba(255,255,255,0.07);font-size:0.875rem;color:#93a0bd;line-height:1.6;">All three arrive at the identical HTTPS front door. NPM asks you to fill a form, Caddy asks you to write two lines, Traefik asks you to label a container. Pick the surface that matches how you already like to work &amp;mdash; that, far more than speed, is what makes a proxy feel right six months later.&lt;/div>
&lt;div style="text-align:right;margin-top:8px;font-size:0.8125rem;color:#93a0bd;">techfuelhq.com &amp;middot; minimal working config per tool, from each project's docs&lt;/div>
&lt;/div>
&lt;/div>
&lt;h2 id="caddy-the-simplest-automatic-https">Caddy: the simplest automatic HTTPS&lt;/h2>
&lt;p>&lt;a href="https://github.com/caddyserver/caddy" rel="noopener">Caddy&lt;/a> is a Go-based web server and reverse proxy under &lt;strong>Apache 2.0&lt;/strong>, fully open source with no paid tier, shipped as a &lt;strong>single static binary&lt;/strong> (about 79k GitHub stars and version 2.11.9 on November 18, 2026). Its headline feature is &lt;strong>automatic HTTPS&lt;/strong>: the moment Caddy knows a hostname, it obtains and renews certificates in the background, using &lt;strong>Let&amp;rsquo;s Encrypt and ZeroSSL with automatic failover&lt;/strong>, redirects HTTP to HTTPS, and issues certificates from an internal CA for local names and IP addresses. Those internal certificates only work on devices that trust Caddy&amp;rsquo;s root; Caddy&amp;rsquo;s docs say any client that doesn&amp;rsquo;t &amp;ldquo;will show security errors.&amp;rdquo; A working HTTPS reverse proxy is about three lines of &lt;strong>Caddyfile&lt;/strong>, which is exactly why so many people who &amp;ldquo;just wanted it to work&amp;rdquo; ended up here.&lt;/p>
&lt;p>The trade-offs: there&amp;rsquo;s &lt;strong>no built-in GUI&lt;/strong> (config is a text file), and Caddy core doesn&amp;rsquo;t natively auto-discover Docker containers. The third-party &lt;a href="https://github.com/lucaslorentz/caddy-docker-proxy" rel="noopener">&lt;code>caddy-docker-proxy&lt;/code>&lt;/a> plugin adds that if you want it. &lt;strong>Socket warning:&lt;/strong> its README runs the container with &lt;code>/var/run/docker.sock&lt;/code> mounted, and whatever holds that socket can control the Docker host. The README&amp;rsquo;s controller/server split is the safer layout it documents: only the controller instance needs the socket, and the server instances that serve your traffic do not.&lt;/p>
&lt;p>One bit of history worth knowing: Caddy briefly sold commercial licenses in 2017-2019, but &lt;strong>permanently moved everything to open source under Apache 2.0 in October 2019&lt;/strong>, so today it&amp;rsquo;s unambiguously free. It&amp;rsquo;s the most-starred of the three and actively maintained.&lt;/p>
&lt;p>&lt;strong>Pick Caddy if&lt;/strong> you like config-as-code, want the least-fuss automatic HTTPS on the market, and don&amp;rsquo;t need a GUI.&lt;/p>
&lt;h2 id="nginx-proxy-manager-the-beginners-favorite">Nginx Proxy Manager: the beginner&amp;rsquo;s favorite&lt;/h2>
&lt;p>&lt;a href="https://github.com/NginxProxyManager/nginx-proxy-manager" rel="noopener">NPM&lt;/a> is a &lt;strong>web GUI wrapped around nginx + OpenResty + Certbot&lt;/strong>, distributed as a Docker image, under the &lt;strong>MIT&lt;/strong> license (verified against its raw LICENSE file; despite some secondhand claims that it&amp;rsquo;s GPL, it is not). You add proxy hosts in a browser, click to request a Let&amp;rsquo;s Encrypt cert, and it generates the nginx config for you. It has the &lt;strong>lowest learning curve of the three&lt;/strong>, which is why it&amp;rsquo;s the standard &amp;ldquo;start here&amp;rdquo; recommendation. It had about 35k GitHub stars on November 18, 2026, and v2.17.0 (November 12) was the current release.&lt;/p>
&lt;p>Two caveats. First, its state lives in a &lt;strong>database and generated config&lt;/strong> rather than portable code, so it isn&amp;rsquo;t naturally version-controlled; keep your own backups. Second, because NPM &lt;strong>bundles its own stack&lt;/strong> (nginx/OpenResty, Certbot, a Node.js UI, and a database), that bundle can lag upstream security fixes, and there have been notable CVEs. The most-cited is &lt;strong>CVE-2025-50579&lt;/strong> (CVSS 5.3), a CORS-misconfiguration flaw reported against v2.12.3 that lets a malicious website steal an admin&amp;rsquo;s JWT token and take over the panel; its &lt;a href="https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4509" rel="noopener">GitHub issue&lt;/a> was still open on November 18, 2026. The fix is discipline: keep it updated and &lt;strong>never expose the admin UI publicly&lt;/strong>.&lt;/p>
&lt;p>Recent releases help. v2.13.6 (January 2026) added TOTP two-factor authentication, v2.16.0 (September 2026) added a logs viewer and per-path access lists, and most releases add Certbot DNS plugins. Read the notes before you pull a new image: v2.16.0 and v2.17.0 both warn that their Certbot update may stop DNS plugins working as expected, and v2.17.0 lists breaking changes for the EdgeDNS, Beget and Infomaniak plugins.&lt;/p>
&lt;p>&lt;strong>Pick NPM if&lt;/strong> you want a point-and-click workflow for a handful of services and would rather not touch config files.&lt;/p>
&lt;h2 id="traefik-dynamic-discovery-for-docker-labs">Traefik: dynamic discovery for Docker labs&lt;/h2>
&lt;p>&lt;a href="https://github.com/traefik/traefik" rel="noopener">Traefik&lt;/a> (MIT, about 66k stars, version 3.7.19 on November 13, 2026, with 3.8 in release candidates) is a modern, &lt;strong>dynamic&lt;/strong> reverse proxy built for containers, shipped as a &lt;strong>single Go binary&lt;/strong>. Its defining trait: it &lt;strong>auto-discovers services and builds routes at runtime&lt;/strong> by reading provider APIs. Add a few &lt;strong>Docker labels&lt;/strong> to a container and Traefik creates the route instantly, no restart, and it does the same for Kubernetes (including the Gateway API), Consul, Nomad, and more. This is the capability NPM lacks entirely and Caddy needs a plugin for.&lt;/p>
&lt;p>&lt;strong>Socket warning:&lt;/strong> Traefik&amp;rsquo;s Docker provider works by reading the Docker socket, and its docs say plainly that &amp;ldquo;accessing the Docker API without any restriction is a security concern: If Traefik is attacked, then the attacker might get access to the underlying host.&amp;rdquo; The safer setups they list include a filtering socket proxy (they name Tecnativa&amp;rsquo;s Docker Socket Proxy), TLS client certificates on a TCP endpoint, or exposing the socket only on a private Docker network. Set &lt;code>exposedByDefault&lt;/code> to &lt;code>false&lt;/code> as well: it defaults to &lt;code>true&lt;/code>, and with &lt;code>false&lt;/code> Traefik ignores any container without a &lt;code>traefik.enable=true&lt;/code> label.&lt;/p>
&lt;p>The cost is complexity. Traefik divides configuration into &lt;strong>static&lt;/strong> (startup: entrypoints, providers, certificate resolvers) and &lt;strong>dynamic&lt;/strong> (hot-reloaded routers, services, middlewares), and you need to understand that model plus label discipline. The more you settle in the static config, the fewer labels each container carries. Either way it&amp;rsquo;s the &lt;strong>steepest learning curve&lt;/strong> here.&lt;/p>
&lt;p>On licensing, Traefik runs &lt;strong>open-core&lt;/strong>: the proxy itself is free, while Traefik Labs sells Hub and Enterprise tiers. Traefik&amp;rsquo;s v3.7 docs list the native Coraza web application firewall middleware as &amp;ldquo;available exclusively in Traefik Hub&amp;rdquo;; the open-source proxy can load the WASM-based Coraza plugin instead. Traefik v3 (GA 2024) also brought HTTP/3, WebAssembly middleware plugins, OpenTelemetry, and an experimental &lt;strong>fastProxy&lt;/strong> option its docs describe as a high-performance reverse proxy for routing; it does not work with HTTP/2, so HTTP/2 requests to a backend fall back to the regular proxy.&lt;/p>
&lt;p>&lt;strong>Pick Traefik if&lt;/strong> your lab is Docker- or Kubernetes-heavy, you want services to register themselves as you deploy them, and you&amp;rsquo;re comfortable with the configuration model.&lt;/p>
&lt;h2 id="which-should-you-run">Which should you run?&lt;/h2>
&lt;p>People rarely pick the &lt;em>wrong&lt;/em> proxy; they pick one whose &lt;strong>operating style doesn&amp;rsquo;t match their skill level or their stack&lt;/strong>. So match it to yourself:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Beginner, few services, wants a GUI →&lt;/strong> &lt;strong>Nginx Proxy Manager.&lt;/strong> Start here.&lt;/li>
&lt;li>&lt;strong>Wants config-as-code and the easiest automatic HTTPS, no GUI →&lt;/strong> &lt;strong>Caddy.&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Docker/Kubernetes-heavy, wants dynamic auto-registration →&lt;/strong> &lt;strong>Traefik.&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>A common growth path is to learn on NPM, then migrate to Caddy (for config-as-code) or Traefik (for Docker discovery) as the lab matures, and that migration is easy because you can always read the generated config and copy it out. If you&amp;rsquo;re also choosing how to &lt;em>manage&lt;/em> those containers, see &lt;a href="https://techfuelhq.com/homelab/komodo-vs-portainer-vs-dockge-2026/">Komodo vs Portainer vs Dockge&lt;/a>.&lt;/p>
&lt;p>A proxy only matters once something sits behind it. The setups that need one on this site: &lt;a href="https://techfuelhq.com/tutorials/nextcloud-aio-docker-setup-2026/">Nextcloud AIO with a reverse proxy&lt;/a>, &lt;a href="https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/">Vaultwarden on Proxmox&lt;/a> (it wants HTTPS), and the reverse-proxy route in &lt;a href="https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/">Jellyfin remote access&lt;/a>. Before Let&amp;rsquo;s Encrypt can issue anything, your domain has to resolve, which &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS&lt;/a> handles on a home connection, and the HTTP challenge needs port 80 reachable from the internet, the TLS-ALPN challenge port 443 (&lt;a href="https://techfuelhq.com/networking/port-forwarding-2026/">port forwarding&lt;/a>); a DNS challenge needs no open ports. If you would rather not open ports at all, compare &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale and Cloudflare Tunnel&lt;/a> first.&lt;/p>
&lt;h2 id="on-performance-the-question-everyone-asks-and-no-one-needs">On performance: the question everyone asks and no one needs&lt;/h2>
&lt;p>&amp;ldquo;Which is fastest?&amp;rdquo; is the first thing people ask and the last thing that should decide it. None of the three projects publishes a like-for-like benchmark against the others, and the community benchmarks that circulate use different hardware, configurations and versions, so any ranking is one test&amp;rsquo;s result rather than a settled order.&lt;/p>
&lt;p>For a homelab the answer barely matters. The traffic a house generates is tiny next to what any of these proxies is built to handle, and when a self-hosted service feels slow, look at the disk, the network or the service behind the proxy first. Choose on configuration style, not throughput.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>Caddy repository &amp;amp; license (Apache 2.0): &lt;a href="https://github.com/caddyserver/caddy" rel="noopener">Caddy repository&lt;/a> · Automatic HTTPS docs (public vs local hostnames, internal CA, issuer fallback): &lt;a href="https://caddyserver.com/docs/automatic-https" rel="noopener">Caddy Automatic HTTPS documentation&lt;/a>&lt;/li>
&lt;li>Caddy open-source move (issue #2786, Oct 2019): &lt;a href="https://github.com/caddyserver/caddy/issues/2786" rel="noopener">Caddy issue 2786&lt;/a> · caddy-docker-proxy (socket mount, controller/server split): &lt;a href="https://github.com/lucaslorentz/caddy-docker-proxy" rel="noopener">caddy-docker-proxy repository&lt;/a>&lt;/li>
&lt;li>Nginx Proxy Manager repository, license (MIT) and releases: &lt;a href="https://github.com/NginxProxyManager/nginx-proxy-manager" rel="noopener">Nginx Proxy Manager repository&lt;/a> · &lt;a href="https://github.com/NginxProxyManager/nginx-proxy-manager/releases" rel="noopener">Nginx Proxy Manager releases&lt;/a>&lt;/li>
&lt;li>Traefik repository (MIT) &amp;amp; configuration overview: &lt;a href="https://github.com/traefik/traefik" rel="noopener">Traefik repository&lt;/a> · &lt;a href="https://doc.traefik.io/traefik/getting-started/configuration-overview/" rel="noopener">Traefik configuration overview&lt;/a> · &lt;a href="https://doc.traefik.io/traefik/v3.7/reference/install-configuration/providers/docker/" rel="noopener">Docker provider and Docker API access&lt;/a> · &lt;a href="https://doc.traefik.io/traefik/v3.7/reference/routing-configuration/http/middlewares/waf/" rel="noopener">Coraza WAF middleware (Traefik Hub)&lt;/a> · &lt;a href="https://doc.traefik.io/traefik/v3.7/reference/install-configuration/experimental/fastproxy/" rel="noopener">fastProxy (experimental)&lt;/a>&lt;/li>
&lt;li>NPM CORS CVE-2025-50579 (CVSS 5.3, NVD): &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-50579" rel="noopener">NVD CVE-2025-50579 record&lt;/a> · issue thread: &lt;a href="https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4509" rel="noopener">Nginx Proxy Manager issue 4509&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>ZFS vs Btrfs (2026): Which Should Your NAS Run?</title><link>https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/</guid><atom:updated>2026-11-18T05:40:00Z</atom:updated><description>&lt;p>Two filesystems get recommended for the same job, and they are not the same tool. ZFS is a storage stack that happens to ship a filesystem inside it. Btrfs is a filesystem that learned to manage more than one device. On a NAS, a Proxmox datastore, or a backup target, the decision collapses to one question: do you need parity RAID you can trust with data you cannot rebuild?&lt;/p>
&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · ZFS vs Btrfs&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Parity array of three or more drives:&lt;/strong> ZFS RAIDZ. Checksummed, no RAID-5 write hole.&lt;/li>
&lt;li>&lt;strong>Two-drive mirror or single disk:&lt;/strong> Btrfs. Cheap snapshots, subvolumes, and no ARC budget.&lt;/li>
&lt;li>&lt;strong>Proxmox VM datastore:&lt;/strong> mirrors on either filesystem rather than RAIDZ, because IOPS matter more than bandwidth.&lt;/li>
&lt;li>&lt;strong>Small ARM board or 4 GB NAS:&lt;/strong> Btrfs. Proxmox's ZFS rule of thumb is 2 GiB plus 1 GiB per TiB.&lt;/li>
&lt;li>&lt;strong>Never:&lt;/strong> Btrfs's own RAID5 or RAID6 profile for data you care about.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;h2 id="what-both-filesystems-actually-guarantee">What both filesystems actually guarantee&lt;/h2>
&lt;p>Both are copy-on-write. New data lands in free space, the checksum is written, and only then does the tree pointer move to the new block. An interrupted write leaves the old tree intact.&lt;/p>
&lt;p>Both checksum. ZFS states plainly that all metadata and data is checksummed, and that it automatically repairs bad data from a good copy when corruption is detected (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">OpenZFS zpoolconcepts&lt;/a>). Btrfs checksums data and metadata by default and verifies those checksums after reading, using crc32c unless you switch to xxhash, sha256, or blake2 (&lt;a href="https://btrfs.readthedocs.io/en/latest/Checksumming.html" rel="noopener">Btrfs Checksumming&lt;/a>).&lt;/p>
&lt;p>Both snapshot, both scrub, and both have a send stream. The divergence is not in the feature list. It is in how much verification each one performs without being asked, and in which RAID profiles are actually finished.&lt;/p>
&lt;h2 id="where-zfs-wins-raidz-the-write-hole-and-repair-on-read">Where ZFS wins: RAIDZ, the write hole, and repair on read&lt;/h2>
&lt;p>The single most important line in the OpenZFS manual is that raidz does not suffer from the RAID-5/6 write hole, the window after a power loss where data and parity can be left inconsistent (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). That is the property that makes parity RAID defensible on a home array at all.&lt;/p>
&lt;p>Capacity follows the usual arithmetic. A mirror of N disks each holding X bytes stores X bytes and survives N-1 failures. A raidz vdev holds roughly (N minus parity) times X, raidz1 has one parity disk, raidz2 has two, raidz3 has three, and the manual recommends keeping a raidz vdev between three and nine disks (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). A four-drive raidz1 gives you three drives of usable space. The same four drives as two mirrors give you two, but Proxmox&amp;rsquo;s ZFS wiki says that layout writes like two single disks and reads like four, while a raidz vdev behaves approximately like a single disk for IOPS (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>).&lt;/p>
&lt;p>Expansion used to be the fatal flaw. It is not anymore, as of OpenZFS 2.3.0. &lt;code>zpool attach&lt;/code> can add a device to an existing raidz vdev while maintaining redundancy, and the documentation is explicit that expansion does not change the number of failures a vdev tolerates, so a RAID-Z2 stays a RAID-Z2 afterwards (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-attach.8.html" rel="noopener">zpool-attach&lt;/a>). Two footnotes matter: each expansion uses the 3.5 MiB boot area ZFS reserves near the start of every disk as scratch space, which caps a raidz vdev at 56 disks with ashift=16, and blocks written before the expansion keep their old data-to-parity ratio until they are rewritten (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-attach.8.html" rel="noopener">zpool-attach&lt;/a>). Proxmox documents raidz expansion as available from Proxmox VE 9 on ZFS 2.3.3 (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>).&lt;/p>
&lt;p>Self-healing is the second win, and it is subtler than the marketing suggests. ZFS repairs bad data from a good copy as corruption is detected, not only during a scrub (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). The &lt;code>zpool scrub&lt;/code> command exists to force a full sweep of every block (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-scrub.8.html" rel="noopener">zpool-scrub&lt;/a>), but a verified read of a damaged block already triggers repair. That difference shows up years later, when a drive starts returning bad sectors silently.&lt;/p>
&lt;h2 id="where-btrfs-wins-flexible-devices-cheap-snapshots-small-hardware">Where Btrfs wins: flexible devices, cheap snapshots, small hardware&lt;/h2>
&lt;p>Btrfs treats a pool as a set of devices you can add, remove, or replace on demand, and it lets you change the RAID profile of existing data with &lt;code>btrfs balance&lt;/code> rather than rebuilding the filesystem (&lt;a href="https://btrfs.readthedocs.io/en/latest/Volume-management.html" rel="noopener">Volume-management&lt;/a>). If you started with two drives as RAID1 and later want RAID0 for scratch space, you convert in place. ZFS has no equivalent; you plan the vdev layout up front.&lt;/p>
&lt;p>Subvolumes are the other practical advantage. One pool can hold many independently snapshot-able subvolumes, and Proxmox&amp;rsquo;s BTRFS storage type places disk images in subvolumes so it can take snapshots (&lt;a href="https://pve.proxmox.com/wiki/Storage:_BTRFS" rel="noopener">Proxmox BTRFS storage&lt;/a>). Btrfs send and receive carry those subvolumes to another host as full or incremental streams, with each command protected by CRC32C (&lt;a href="https://btrfs.readthedocs.io/en/latest/Send-receive.html" rel="noopener">Send-receive&lt;/a>). ZFS does the same thing with &lt;code>zfs send&lt;/code> (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zfs-send.8.html" rel="noopener">zfs-send&lt;/a>). Either stream is replication; for file-level backups with their own retention, see &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">restic vs Borg vs Kopia&lt;/a>.&lt;/p>
&lt;p>Memory is where Btrfs quietly wins the small-hardware argument. ZFS runs an Adaptive Replacement Cache in RAM, and Proxmox recommends budgeting at least 2 GiB of base memory plus 1 GiB per TiB of stored data, with the ARC enforcing a hard 64 MiB minimum (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>). On a 4 GB ARM NAS or a mini PC you also use as a media server, that budget can be most of the machine once the pool passes a couple of TiB. Btrfs has no ARC and uses the kernel page cache, so there is no cache budget to plan for.&lt;/p>
&lt;h2 id="the-decision-table">The decision table&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Requirement&lt;/th>
&lt;th scope="col">ZFS&lt;/th>
&lt;th scope="col">Btrfs&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Requirement">Parity RAID in production&lt;/td>
&lt;td data-label="ZFS">RAIDZ1/2/3&lt;/td>
&lt;td data-label="Btrfs">Native RAID5/6 unstable, evaluation only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">RAID-5/6 write hole&lt;/td>
&lt;td data-label="ZFS">Not present in raidz&lt;/td>
&lt;td data-label="Btrfs">Documented, journal not implemented&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Two-drive mirror with snapshots&lt;/td>
&lt;td data-label="ZFS">Works, needs ARC budget&lt;/td>
&lt;td data-label="Btrfs">Works, minimal overhead&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Single disk with rollback&lt;/td>
&lt;td data-label="ZFS">Possible, heavier&lt;/td>
&lt;td data-label="Btrfs">Native subvolume snapshots&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">VM datastore IOPS&lt;/td>
&lt;td data-label="ZFS">Mirrors only, raidz is one disk of IOPS&lt;/td>
&lt;td data-label="Btrfs">Mirrors only, same logic&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Add a disk to existing parity set&lt;/td>
&lt;td data-label="ZFS">&lt;code>zpool attach&lt;/code>, OpenZFS 2.3+&lt;/td>
&lt;td data-label="Btrfs">Not applicable, no stable native parity profile&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Change RAID profile in place&lt;/td>
&lt;td data-label="ZFS">No, plan the layout first&lt;/td>
&lt;td data-label="Btrfs">&lt;code>btrfs balance&lt;/code> convert&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Metadata checksums&lt;/td>
&lt;td data-label="ZFS">Always&lt;/td>
&lt;td data-label="Btrfs">Default, crc32c unless changed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Repair on a normal read&lt;/td>
&lt;td data-label="ZFS">Yes, from a good copy&lt;/td>
&lt;td data-label="Btrfs">Verifies, but needs a scrub to find all copies&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Send/receive to remote&lt;/td>
&lt;td data-label="ZFS">&lt;code>zfs send&lt;/code>/&lt;code>zfs receive&lt;/code>&lt;/td>
&lt;td data-label="Btrfs">&lt;code>btrfs send&lt;/code>/&lt;code>btrfs receive&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Memory guidance&lt;/td>
&lt;td data-label="ZFS">2 GiB base + 1 GiB/TiB (Proxmox rule of thumb)&lt;/td>
&lt;td data-label="Btrfs">No dedicated cache&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Per-vdev disk guidance&lt;/td>
&lt;td data-label="ZFS">3-9 disks for raidz&lt;/td>
&lt;td data-label="Btrfs">Profile-dependent&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="recovery-and-the-operational-caveats-that-bite">Recovery and the operational caveats that bite&lt;/h2>
&lt;p>The Btrfs RAID56 warning is not a legacy footnote. The project&amp;rsquo;s own manual says RAID5 and RAID6 should not be used in production, only for evaluation or testing, that power-failure safety for metadata with RAID56 is not complete, and that you should not use raid5 or raid6 for metadata at all, using raid1 or raid1c3 instead (&lt;a href="https://btrfs.readthedocs.io/en/latest/btrfs-man5.html" rel="noopener">btrfs(5)&lt;/a>). The status page still lists RAID56 as unstable (&lt;a href="https://btrfs.readthedocs.io/en/latest/Status.html" rel="noopener">Btrfs Status&lt;/a>). If you build a Btrfs array yourself, that rules out its raid5 and raid6 profiles for anything you care about.&lt;/p>
&lt;p>That warning is about Btrfs&amp;rsquo;s own parity profiles, and it is not a verdict on every four-bay Btrfs NAS. Synology&amp;rsquo;s DSM is the common case: you choose a RAID type for the storage pool, then create a volume on top of that pool and pick Btrfs or ext4 for it (&lt;a href="https://global.synologydownload.com/download/Document/Software/UserGuide/Os/DSM/7.2/enu/Syno_UsersGuide_NAServer_7_2_enu.pdf" rel="noopener">DSM 7.2 user guide&lt;/a>). The RAID belongs to the pool underneath, and Synology says its Btrfs recovers broken data using the supported RAID volumes, including RAID 5, RAID 6 and SHR (&lt;a href="https://www.synology.com/en-us/dsm/Btrfs" rel="noopener">Synology Btrfs&lt;/a>). If you are weighing a Synology against a box you run yourself, the &lt;a href="https://techfuelhq.com/homelab/synology-vs-diy-nas-five-year-cost-2026/">five-year cost comparison&lt;/a> puts DSM next to a TrueNAS build, and the &lt;a href="https://techfuelhq.com/homelab/nas-os-month-eight-2026/">NAS software comparison&lt;/a> covers DSM against UGOS Pro, TOS and QTS.&lt;/p>
&lt;p>Btrfs auto-repair is real but conditional. It salvages data from another valid copy when the profile has redundancy, and the documentation notes that other damaged copies are not detected unless a scrub runs (&lt;a href="https://btrfs.readthedocs.io/en/latest/Auto-repair.html" rel="noopener">Auto-repair&lt;/a>). So your scrub schedule is not optional housekeeping on Btrfs; it is the only mechanism that finds the second bad copy.&lt;/p>
&lt;p>Device replacement has a sharp edge on Btrfs: replace and delete insist on being able to read or reconstruct all data, and the operation aborts if a read fails with an input/output error (&lt;a href="https://btrfs.readthedocs.io/en/latest/Status.html" rel="noopener">Status&lt;/a>). A source disk that is dying slowly can stall the rebuild you started because it was dying. Replace at the first sign of failure rather than waiting for the disk to drop out, and never treat a rebuild as a backup.&lt;/p>
&lt;p>On the ZFS side, the caveats are about planning rather than corruption. A raidz vdev behaves approximately like a single disk for IOPS while providing a lot of bandwidth, and Proxmox is direct that IOPS is the more important metric for running virtual machines (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>). This is why a six-drive RAIDZ2 pool (the &lt;a href="https://techfuelhq.com/homelab/six-bay-nas-drives-rebuild-2026/">six-bay rebuild guide&lt;/a> covers its rebuild times) gives you roughly one disk of IOPS for VMs, while a three-mirror pool on the same disks writes like three disks and reads like six. If your workload is databases, virtual machines, or anything with small random reads, mirrors beat parity on both filesystems.&lt;/p>
&lt;p>The OpenZFS FAQ strongly recommends ECC memory where the strongest integrity guarantees are required, and the reason is narrow: without ECC, a random bit flip can go undetected and OpenZFS, like any other filesystem, will write the damaged data to disk. The same FAQ says home users have to weigh that against the cost (&lt;a href="https://openzfs.github.io/openzfs-docs/Project%20and%20Community/FAQ.html" rel="noopener">OpenZFS FAQ&lt;/a>). I cover which failure modes ECC actually prevents in &lt;a href="https://techfuelhq.com/homelab/ecc-home-server-verify-2026/">what breaks without ECC on a home server&lt;/a>, and it is a more honest treatment than the usual blanket warning.&lt;/p>
&lt;h2 id="which-one-should-you-pick">Which one should you pick&lt;/h2>
&lt;p>If you are building a parity array, run ZFS. Three to nine drives in raidz1 or raidz2, checksums on everything, no write hole, and a scrub that actually finds silent corruption. Use the &lt;a href="https://techfuelhq.com/tools/nas-storage-calculator/">NAS storage calculator&lt;/a> to size usable capacity before you buy, because raidz overhead is not intuitive.&lt;/p>
&lt;p>If you are building a two-drive mirror, a single-disk boot volume, or anything on a small ARM board, run Btrfs. You give up nothing that matters at that scale, and you keep your RAM. Turning an old PC into a NAS sits between the two; the &lt;a href="https://techfuelhq.com/homelab/nas-from-old-pc-2026/">old-PC NAS guide&lt;/a> weighs OpenMediaVault against TrueNAS and Unraid for that hardware.&lt;/p>
&lt;p>If you are virtualizing, the filesystem is the second decision. The first is mirrors versus parity, and it decides everything downstream. The &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox capacity planner&lt;/a> will tell you how much usable space a given layout leaves you, but the IOPS answer is already settled by the word RAIDZ.&lt;/p>
&lt;p>For the wider stack decision, including whether ZFS should live on the hypervisor at all, read &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Unraid vs TrueNAS vs Proxmox for homelab storage&lt;/a> and the &lt;a href="https://techfuelhq.com/storage/unraid-vs-truenas-vs-omv-vs-proxmox-2026/">four-way NAS OS comparison&lt;/a>. If you have already committed to a ZFS pool, the &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">pool setup and ARC tuning walkthrough&lt;/a> covers the commands, and drive selection is covered in &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">best NAS hard drives&lt;/a>.&lt;/p></description></item><item><title>GPU Hotspot Temperature: Limits, Delta and Fault Signs (2026)</title><link>https://techfuelhq.com/articles/gpu-hotspot-temperature-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/gpu-hotspot-temperature-2026/</guid><atom:updated>2026-11-18T05:40:00Z</atom:updated><description>&lt;p>A reader sends me an overlay screenshot about once a week. The GPU temperature line says something calm, the hotspot line says something alarming, and the question is always the same: is the card dying? Almost every time, the honest answer is that one number cannot tell you, because the useful measurement is the gap between the two.&lt;/p>
&lt;p>I am not going to hand you a magic delta threshold. Neither NVIDIA nor AMD publishes one, and any site that gives you a single number is guessing on your behalf. What the vendors do document is how to read the sensors and how to tell whether the card is actually being slowed down by heat. That is enough to make a real decision.&lt;/p>
&lt;h2 id="what-the-hotspot-reading-actually-is">What the hotspot reading actually is&lt;/h2>
&lt;p>The hotspot, which AMD&amp;rsquo;s software calls the junction temperature, is the hottest point on the graphics die. The ordinary GPU temperature line is a different, lower sensor, usually described as edge or core temperature. Our own &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">GPU hotspot delta census&lt;/a> defines it plainly: the hotspot is the highest reading among the temperature sensors on the die, and the delta is hotspot minus core from the same session.&lt;/p>
&lt;p>That definition matters because it tells you what the delta is measuring. It is not a verdict. It is a description of how evenly heat is crossing from silicon into the cold plate. A wide spread means one region of the die is much hotter than the part the edge sensor sees.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s own command-line tool may or may not give you this reading. The &lt;a href="https://docs.nvidia.com/deploy/nvidia-smi/index.html" rel="noopener">nvidia-smi documentation&lt;/a> never uses the word hotspot, but it lists a GPU Current Max Temp field described as the current temperature from the hottest part of the GPU, and says it is not supported on all devices. It also lists GPU Current Temp as the average GPU temperature and a T.Limit sensor that reports the margin to the maximum operating temperature. Third-party tools such as HWMonitor and LACT report the hotspot on RTX 50 cards too, which is exactly why tool version matters so much here.&lt;/p>
&lt;h2 id="what-nvidia-and-amd-actually-publish">What NVIDIA and AMD actually publish&lt;/h2>
&lt;p>The only temperature limit NVIDIA prints for its desktop cards is the Maximum GPU Temperature on each specification page, and it belongs to the core reading, not the hotspot: 88 °C on the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5080/" rel="noopener">RTX 5080&lt;/a>, 85 °C on the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5070-family/" rel="noopener">RTX 5070&lt;/a>, 90 °C on the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5090/" rel="noopener">RTX 5090&lt;/a> and 90 °C across the RTX 40 cards. Those pages list no hotspot or junction figure, and nvidia-smi&amp;rsquo;s GPU Current Max Temp field comes with no maximum of its own. The &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">safe GPU temperature guide&lt;/a> has the limit for every desktop RTX 50 and RTX 40 card.&lt;/p>
&lt;p>AMD&amp;rsquo;s &lt;a href="https://www.amd.com/en/products/graphics/desktops/radeon/9000-series/amd-radeon-rx-9070xt.html" rel="noopener">RX 9070 XT specification page&lt;/a> lists board power and clocks and no maximum temperature at all. The one junction figure AMD has published is from 2019: in a &lt;a href="https://web.archive.org/web/20250127201455/https://community.amd.com/t5/gaming/amd-radeon-community-update-more-control-over-gpu-power-and/ba-p/418629" rel="noopener">Radeon community update&lt;/a> it said RX 5700-series cards keep raising clocks until a sensor reaches a 110 °C junction temperature, and that up to 110 °C junction during typical gaming was expected and within spec. That statement covers the RX 5700 series. Don&amp;rsquo;t carry it to an RDNA 4 card.&lt;/p>
&lt;p>So a hotspot number has nothing official to be measured against. The core limit tells you whether the card is near its ceiling; the hotspot tells you how evenly the die is being cooled.&lt;/p>
&lt;h2 id="edge-hotspot-and-memory-are-three-different-jobs">Edge, hotspot, and memory are three different jobs&lt;/h2>
&lt;p>People collapse these into one &amp;ldquo;GPU temp&amp;rdquo; and then argue about it. Keep them apart:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Reading&lt;/th>
&lt;th scope="col">What it describes&lt;/th>
&lt;th scope="col">What it is good for&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Reading">GPU temperature (edge)&lt;/td>
&lt;td data-label="What it describes">A core sensor, typically the cooler-running of the die readings&lt;/td>
&lt;td data-label="What it is good for">Tracking overall cooler performance and fan response&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reading">Hotspot / junction&lt;/td>
&lt;td data-label="What it describes">The hottest die sensor&lt;/td>
&lt;td data-label="What it is good for">Judging how evenly the die is being cooled&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reading">Memory junction&lt;/td>
&lt;td data-label="What it describes">GDDR package sensors&lt;/td>
&lt;td data-label="What it is good for">Judging memory cooling, separate from die contact&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The delta is computed from the first two, and only if both come from the same sustained run. Our census validator rejects a hotspot below core, a hotspot outside its documented 20–125 °C range, a core outside 20–100 °C, and any load shorter than ten minutes. Those rules exist because a ten-second screenshot of a menu is not a thermal measurement. The 20–125 °C and 20–100 °C limits are the census schema&amp;rsquo;s input checks, set in its &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">field definitions&lt;/a>; they are not temperature limits from NVIDIA or AMD.&lt;/p>
&lt;p>This is the single most common mistake I see in forum threads: someone records a core maximum from one run and a hotspot maximum from another, subtracts them, and posts the result. Two session maxima are not a delta. They may have happened minutes apart under different loads.&lt;/p>
&lt;h2 id="the-bands-and-what-i-check-in-each">The bands, and what I check in each&lt;/h2>
&lt;p>Our census publishes exact-model distributions in five fixed bands rather than inventing a universal limit: 0–9 °C, 10–19 °C, 20–29 °C, 30–39 °C, and 40 °C or higher. The edges are part of the dataset version, so a row collected this year stays comparable to one collected next year.&lt;/p>
&lt;p>Here is how I use each band. This is a diagnostic posture, not a measurement I am claiming to have taken:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Delta band&lt;/th>
&lt;th scope="col">How I read it&lt;/th>
&lt;th scope="col">First thing I check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Delta band">0–9 °C&lt;/td>
&lt;td data-label="How I read it">Unusually tight. Possible, but confirm the tool is not repeating one sensor.&lt;/td>
&lt;td data-label="First thing I check">Tool name and version; whether the hotspot field is supported on this card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">10–19 °C&lt;/td>
&lt;td data-label="How I read it">The ordinary working range for a card with good contact&lt;/td>
&lt;td data-label="First thing I check">Nothing, if clocks and throttle flags are healthy&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">20–29 °C&lt;/td>
&lt;td data-label="How I read it">Worth watching. Often load, airflow, or fan-curve dependent&lt;/td>
&lt;td data-label="First thing I check">Sustained-load duration, case airflow, fan curve&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">30–39 °C&lt;/td>
&lt;td data-label="How I read it">A contact or mounting conversation is reasonable&lt;/td>
&lt;td data-label="First thing I check">Mounting pressure, paste or pad state, cooler seating&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">40 °C or higher&lt;/td>
&lt;td data-label="How I read it">The pattern I treat as a fault until proven otherwise&lt;/td>
&lt;td data-label="First thing I check">Full remount, or warranty service if the card is covered&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>None of those bands comes from a maker. The census edges describe where submitted readings fall, and the middle column is a reading posture, not a limit NVIDIA or AMD sets.&lt;/p>
&lt;p>Two cautions before you act on that table. A zero-degree delta is valid in our schema, but a tool that is reading the wrong sensor can also produce one, so verify support before you celebrate. And a delta in the 20s on a hot day in a cramped case is not the same finding as the same delta in a ventilated tower at stock settings.&lt;/p>
&lt;h2 id="confirm-the-tool-before-you-believe-the-number">Confirm the tool before you believe the number&lt;/h2>
&lt;p>This is the step almost everyone skips, and it is where half the &amp;ldquo;my hotspot is broken&amp;rdquo; reports come from.&lt;/p>
&lt;p>On the NVIDIA side, CPUID&amp;rsquo;s &lt;a href="https://www.cpuid.com/softwares/hwmonitor.html" rel="noopener">HWMonitor changelog&lt;/a> records hotspot temperature on RTX 50 GPUs as fixed in version 1.65.1, and version 1.66 as improving the hotspot report on AMD Radeon RX 9000 cards. On Linux, &lt;a href="https://github.com/ilya-zlobintsev/LACT/releases/tag/v0.10.0" rel="noopener">LACT v0.10.0&lt;/a> says the hotspot sensor on Blackwell &amp;ldquo;now works with a Blackwell-specific path, instead of reporting bogus values,&amp;rdquo; and the project&amp;rsquo;s &lt;a href="https://github.com/ilya-zlobintsev/LACT/pull/1122" rel="noopener">pull request 1122&lt;/a> is where that path was added.&lt;/p>
&lt;p>&amp;ldquo;Instead of reporting bogus values&amp;rdquo; is the sentence to remember. A wrong sensor path does not usually throw an error. It hands you a plausible number that describes something else, and you build a whole theory on top of it.&lt;/p>
&lt;p>On AMD cards the driver exposes both readings directly. &lt;a href="https://www.amd.com/en/resources/support-articles/faqs/DH3-038.html" rel="noopener">AMD&amp;rsquo;s performance metrics article DH3-038&lt;/a> lists both GPU Current Temperature and GPU Junction Temperature among the metrics you can log, with a sampling interval adjustable from 0.25 to 5 seconds. &lt;a href="https://www.amd.com/en/resources/support-articles/faqs/DH3-020.html" rel="noopener">DH3-020&lt;/a> notes that GPU Hotspot Temperature is only available on Radeon VII, Radeon RX 5000 Series and newer products. If you are on an older card, the field may simply not exist on your hardware.&lt;/p>
&lt;p>So the first check is free and takes ten seconds: write down the tool name and exact version next to every reading you plan to compare. That record survives a reboot, and it is the one piece of evidence you will still have when the numbers stop making sense.&lt;/p>
&lt;h2 id="is-the-card-actually-being-slowed-down">Is the card actually being slowed down?&lt;/h2>
&lt;p>A wide delta is not proof of throttling. It is proof of an uneven thermal profile. Whether that costs you performance is a separate question, and both vendors expose a flag for it.&lt;/p>
&lt;p>On NVIDIA hardware, the &lt;a href="https://docs.nvidia.com/deploy/nvml-api/latest/api/group__nvmlClocksEventReasons.html" rel="noopener">NVML clocks event reasons&lt;/a> separate software and hardware thermal slowdown from power capping and other reasons for reduced clocks. In practice that means you can see whether the card is being held back by heat or by its wattage limit, which are completely different problems with completely different fixes.&lt;/p>
&lt;p>The T.Limit reading in &lt;a href="https://docs.nvidia.com/deploy/nvidia-smi/index.html" rel="noopener">nvidia-smi&lt;/a> is the quick version. It reports margin, not temperature, and the documentation says a T.Limit value of 0 °C or lower indicates the GPU may optimize its clock based on thermal conditions. A healthy margin that stays positive under load is a good sign. For a one-line core reading in Windows, the &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/#gpu-temperature-task-manager-and-nvidia-smi">Task Manager and nvidia-smi checks&lt;/a> cover it.&lt;/p>
&lt;p>Run the query while the load is running, not after:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>nvidia-smi -q -d TEMPERATURE,POWER,CLOCK,PERFORMANCE
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Save that output to a file. A log on disk survives a reboot; a live overlay reading does not, and the moment you restart to reseat a cable you lose the evidence you were about to reason from.&lt;/p>
&lt;p>On AMD, the junction reading and the clock behavior in the same overlay give you the same comparison, with the 0.25-second sampling floor from DH3-038 fine enough to catch a spike.&lt;/p>
&lt;h2 id="ordered-checks-cheapest-first">Ordered checks, cheapest first&lt;/h2>
&lt;p>Work down this list and stop as soon as the pattern resolves. Each step is cheaper and less invasive than the one below it.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Take one honest reading.&lt;/strong> Same session, same load, at least ten minutes, both numbers recorded together. If you cannot satisfy that, you do not have data yet.&lt;/li>
&lt;li>&lt;strong>Verify the tool version.&lt;/strong> Check the changelog for your card family. On RTX 50, HWMonitor below 1.65.1 or LACT below 0.10.0 is not a reading you should build a decision on.&lt;/li>
&lt;li>&lt;strong>Check the throttle flag.&lt;/strong> Positive T.Limit margin and no thermal slowdown event means the delta is not costing you clocks, whatever it looks like.&lt;/li>
&lt;li>&lt;strong>Look at fan behavior.&lt;/strong> A curve that never ramps, or a zero-RPM mode that never exits under load, produces a wide delta for reasons that have nothing to do with paste; the &lt;a href="https://techfuelhq.com/articles/gpu-fans-not-spinning-2026/">GPU fans not spinning guide&lt;/a> covers that case. The &lt;a href="https://techfuelhq.com/articles/gpu-fans-stuck-at-100-percent/">GPU fans stuck at full speed guide&lt;/a> covers the opposite failure, where the controller reacts to a sensor you cannot see.&lt;/li>
&lt;li>&lt;strong>Test case airflow without changing hardware.&lt;/strong> Remove the side panel while the load runs and watch whether both readings fall together. If they do, the problem is the enclosure and the fan curves, not the card.&lt;/li>
&lt;li>&lt;strong>Only then consider the mount.&lt;/strong> If the delta stays wide with airflow and fans sorted, the remaining suspects are mounting pressure and the thermal interface. Even screw torque in an X pattern, verified contact, and a fresh interface are the correct sequence. Thermal Grizzly&amp;rsquo;s &lt;a href="https://www.thermal-grizzly.com/en/kryonaut/s-tg-k-100-r" rel="noopener">Kryonaut page&lt;/a> says temperature changes can gradually displace paste from the contact area, which it calls pump-out, and Honeywell&amp;rsquo;s &lt;a href="https://prod-edam.solstice.com/content/dam/honeywell-edam/pmt/oneam/en-us/electronic-materials/thermal-interface-materials/documents/100600-esm-tds-ptm7950-pcm-ltr-en.pdf" rel="noopener">PTM7950 data sheet&lt;/a> claims no pump-out for its phase-change pad. The &lt;a href="https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/">PTM7950 vs thermal paste comparison&lt;/a> covers which to use.&lt;/li>
&lt;li>&lt;strong>Undervolt last.&lt;/strong> Once the mechanical side is right, a flatter voltage-frequency curve reduces total heat. It does not repair contact, and applying it first just moves both numbers down and hides the fault.&lt;/li>
&lt;/ol>
&lt;p>If you want the full flag-by-flag walkthrough for both processors and graphics cards, the &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling fix guide&lt;/a> goes deeper on the telemetry side, and the &lt;a href="https://techfuelhq.com/articles/gpu-overheating-2026/">GPU overheating guide&lt;/a> covers the physical checks. For a model-by-model ceiling reference, the &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">safe GPU temperature guide&lt;/a> is the companion piece.&lt;/p>
&lt;h2 id="when-to-stop">When to stop&lt;/h2>
&lt;p>Stop diagnosing and start deciding when one of these is true.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The card is under warranty and the delta pattern points at contact.&lt;/strong> A support ticket is cheaper than a voided warranty. Policies vary by brand and region, so read the terms for your exact model before the screwdriver comes out.&lt;/li>
&lt;li>&lt;strong>The delta stays wide after a correct remount.&lt;/strong> One careful remount with verified contact and an even torque pattern is a reasonable attempt. A second and third are not diagnosis, they are hope. If the spread persists, the card needs service or replacement.&lt;/li>
&lt;li>&lt;strong>The hotspot reads below the edge temperature.&lt;/strong> That is not a hot card, that is a sensor or tool problem. Recheck the version before you touch hardware.&lt;/li>
&lt;li>&lt;strong>The throttle flag never fires and clocks hold.&lt;/strong> Then you have a cosmetic number, not a fault. Close the overlay and go use the machine.&lt;/li>
&lt;/ul>
&lt;p>If none of the checks resolve it, the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> lets you record each test result and the readings beside it so a technician gets a record instead of a story. And if you have a reading worth contributing, the &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">census intake&lt;/a> is open. That dataset is how the bands above get better over time.&lt;/p></description></item><item><title>Cat6 vs Cat6A: Decide It by Run Length, Not Speed (2026)</title><link>https://techfuelhq.com/networking/cat6-vs-cat6a-2026/</link><pubDate>Sat, 12 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/cat6-vs-cat6a-2026/</guid><atom:updated>2026-11-18T05:40:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Cat6 vs Cat6A&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Pull Cat6A&lt;/strong> for anything inside a wall, anything that might carry 10GBASE-T past about 37 meters, and anything zip-tied into a bundle. The cable is the cheap part of that job.&lt;/li>
&lt;li>&lt;strong>Pull Cat6&lt;/strong> for short, open runs at 1 to 5 gigabit. Both categories carry those speeds to 100 meters, and the money goes further in the switch.&lt;/li>
&lt;li>&lt;strong>The price gap&lt;/strong> on Newegg on November 17, 2026 was $119 per 1,000 feet between one maker's solid-copper Cat6 and Cat6A riser reels ($170.00 against $289.00), plus Cat6A-rated jacks if you want it to certify.&lt;/li>
&lt;li>&lt;strong>Buy solid copper.&lt;/strong> Copper-clad aluminum (CCA) bulk cable is not TIA-compliant and is a poor match for PoE.&lt;/li>
&lt;li>&lt;strong>Wrong for:&lt;/strong> anyone told "Cat6 does 10 gig to 55 meters" as a promise. Fluke's own read of that guidance is that "no one really knows."&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Every page on this question hands you the same two numbers, 250 MHz against 500 MHz and 55 meters against 100. Neither decides anything. Length does. The decision is about where the cable goes, how long it is, and whether it will ever carry 10GBASE-T. I run this site&amp;rsquo;s &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE&lt;/a> page, so this one stays on the cable itself. I have not certified a run for this page; every reach figure below is quoted from its owner, and the price is what Monoprice showed me on 2026-09-12.&lt;/p>
&lt;h2 id="the-deciders-that-matter-ranked">The deciders that matter, ranked&lt;/h2>
&lt;h3 id="1-will-the-run-ever-carry-10gbase-t-and-how-long-is-it">1. Will the run ever carry 10GBASE-T, and how long is it&lt;/h3>
&lt;p>This is the whole decision for most people, and the number everyone repeats is softer than it sounds. Fluke Networks&amp;rsquo; knowledge base quotes the guidance directly: &amp;ldquo;TSB-155 states: &amp;lsquo;10GBASE-T should operate over channel lengths of up to 37 meters of Category 6 cabling, and should operate over channel lengths between 37 and 55 meters of Category 6 cabling depending on the alien crosstalk environment. Channel lengths over 55 meters may require mitigation.&amp;rsquo;&amp;rdquo;&lt;/p>
&lt;p>Then Fluke adds its own read: &amp;ldquo;What this means is that no one really knows. There are so many variables in the cabling system. We have observed links as long as 60 m that meet the PS AXtalk requirements and links of 30 m which do not.&amp;rdquo;&lt;/p>
&lt;p>That is the test-gear vendor hedging the standard. So the working Cat6 number for 10 gigabit is 37 meters, with no guarantee out to 55 and a test past that. Cat6A does not hedge. It carries 10GBASE-T to 100 meters by specification; Fluke&amp;rsquo;s article opens with that, saying that to support it &amp;ldquo;up to 100 m (328 ft), you should be looking to the Category 6A specification.&amp;rdquo;&lt;/p>
&lt;p>What happens past the limit is where the vendors disagree, and I quote both. trueCABLE: &amp;ldquo;Cat6 only supports 10 Gbps to 165 feet (55 meters) under ideal conditions—less in heavy cross talk environments. Past 165 feet, Cat6 supports a maximum of 5 Gbps application speed.&amp;rdquo;&lt;/p>
&lt;p>Cable Matters, in its July 14, 2026 comparison, says Cat6 can run &amp;ldquo;up to 10 Gbps at lengths up to 55 meters. Over that length, and up to 100 meters its data rate drops to just 1Gbps.&amp;rdquo; One says 5 gigabit past 55 meters. One says 1. The link negotiates whatever the pair of ports can hold, so the answer on your run is whatever your run tests at.&lt;/p>
&lt;h3 id="2-is-it-bundled">2. Is it bundled&lt;/h3>
&lt;p>Alien crosstalk is what Cat6A&amp;rsquo;s construction is built against, and it is a bundle problem. The 8-point reply in a January 2024 r/HomeNetworking thread put it in one sentence: &amp;ldquo;Cat 6A is expressly designed for large, tight, long bundles of Ethernet like you see in a larger office building, where &amp;rsquo;long&amp;rsquo; is &amp;gt; 25 meters, and large is a bundle of 7 or more active cables and tight is zip tied together every 50 cm.&amp;rdquo; Those distances and counts are one commenter&amp;rsquo;s rule of thumb rather than a specification.&lt;/p>
&lt;p>trueCABLE describes the construction that addresses it: Cat6A &amp;ldquo;is made to tighter tolerances than Cat6 Ethernet cable. This means the copper conductors are twisted tighter and additional built-in ANEXT protection due to the higher operation frequency.&amp;rdquo; A single Cat6 run through a joist bay has no neighbors to hear. Twelve runs tie-wrapped up a riser do. That is the whole difference.&lt;/p>
&lt;h3 id="3-what-speed-you-will-hold-it-to">3. What speed you will hold it to&lt;/h3>
&lt;p>If the answer is 1, 2.5 or 5 gigabit, the categories are equal. trueCABLE lists it first among the similarities: both &amp;ldquo;Support 10 Mbps through 5 Gbps application speeds to 328 feet (100 meters).&amp;rdquo;&lt;/p>
&lt;p>A 51-point reply in the February 2024 r/HomeNetworking thread, as read on 2026-09-12, makes the point people miss: &amp;ldquo;Nothing about the cable says what frequencies they actually use. The switch port and the NIC negotiate and use the best and highest link rate that is available to them.&amp;rdquo; A 2.5GbE port on a sound Cat6 run inside 100 meters links at 2.5GbE. Full stop. Buying Cat6A for a 2.5GbE house is buying headroom, which is a fine reason if you say it out loud. The &lt;a href="https://techfuelhq.com/tools/transfer-time-calculator/">transfer-time calculator&lt;/a> shows what each link speed would save on the copies you actually make.&lt;/p>
&lt;h3 id="4-whether-you-can-ever-get-back-in">4. Whether you can ever get back in&lt;/h3>
&lt;p>This is the decider the spec sheets skip. I weight it most. The cable is the cheapest part of any in-wall pull; the drywall, the fish tape and the afternoon are the cost, and you pay them again if the run turns out short of what you need. The wall is the expensive part. A patch cable across a desk is Cat6. Every time. A run stapled inside a finished wall is a Cat6A decision, because the extra cost of a Cat6A box is nothing against opening the wall twice.&lt;/p>
&lt;h3 id="5-poe-and-heat">5. PoE and heat&lt;/h3>
&lt;p>trueCABLE&amp;rsquo;s article notes that Cat6A &amp;ldquo;typically makes use of thicker conductor wires (copper + plastic insulation on the individual conductor).&amp;rdquo; I have no heat measurement of my own, and the two spools I priced are both 23 AWG, so I do not weight PoE heat in this decision. For a camera or an access point on a short run it does not move the decision. Short runs shrug it off. The long, bundled runs where it might matter are the ones Cat6A already wins on crosstalk. The &lt;a href="https://techfuelhq.com/tools/poe-budget-calculator/">PoE budget calculator&lt;/a> totals what the switch has to supply.&lt;/p>
&lt;h3 id="6-termination-hardware">6. Termination hardware&lt;/h3>
&lt;p>The plug is the same. What changes is the rating of the jack behind it. trueCABLE: &amp;ldquo;Cat6A requires Cat6A rated patch panels and Cat6A rated keystone wall jacks.&amp;rdquo; Budget for those if the point of pulling Cat6A is to certify the channel. A Cat6A cable on Cat6 keystones is a Cat6 channel, whatever the jacket says.&lt;/p>
&lt;h2 id="side-by-side">Side by side&lt;/h2>
&lt;p>Every cell is quoted from the source named in the row; the price row is a Newegg catalogue reading dated in the row.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Cat6&lt;/th>
&lt;th scope="col">Cat6A&lt;/th>
&lt;th scope="col">Source&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">10GBASE-T reach&lt;/td>
&lt;td data-label="Cat6">37 m per TSB-155; 37 to 55 m &amp;ldquo;depending on the alien crosstalk environment&amp;rdquo;; over 55 m &amp;ldquo;may require mitigation&amp;rdquo;&lt;/td>
&lt;td data-label="Cat6A">100 m (328 ft)&lt;/td>
&lt;td data-label="Source">Fluke Networks knowledge base&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Past the 10-gigabit limit&lt;/td>
&lt;td data-label="Cat6">5 Gbps maximum (trueCABLE) or 1 Gbps (Cable Matters)&lt;/td>
&lt;td data-label="Cat6A">Not applicable to 100 m&lt;/td>
&lt;td data-label="Source">trueCABLE; Cable Matters, July 14, 2026&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">1, 2.5 and 5 GbE reach&lt;/td>
&lt;td data-label="Cat6">100 m&lt;/td>
&lt;td data-label="Cat6A">100 m&lt;/td>
&lt;td data-label="Source">trueCABLE, &amp;ldquo;10 Mbps through 5 Gbps application speeds to 328 feet&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Construction&lt;/td>
&lt;td data-label="Cat6">Four twisted pairs, eight conductors&lt;/td>
&lt;td data-label="Cat6A">Same, twisted tighter, with &amp;ldquo;additional built-in ANEXT protection&amp;rdquo;&lt;/td>
&lt;td data-label="Source">trueCABLE&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Handling&lt;/td>
&lt;td data-label="Cat6">Lighter, easier to pull&lt;/td>
&lt;td data-label="Cat6A">Thicker, and in Cable Matters&amp;rsquo; words (about Cat6A and Cat7 together) &amp;ldquo;heavier, and harder to install&amp;rdquo;&lt;/td>
&lt;td data-label="Source">Cable Matters, July 14, 2026&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Maximum operating frequency&lt;/td>
&lt;td data-label="Cat6">250 MHz (a higher MHz figure printed on a spool is the vendor&amp;rsquo;s sweep, above the category limit)&lt;/td>
&lt;td data-label="Cat6A">500 MHz&lt;/td>
&lt;td data-label="Source">trueCABLE (&amp;ldquo;Cat6 maximum operating frequency is 250 MHz&amp;rdquo;); Fluke Networks, which says a 10GBASE-T link must be tested for channel parameters &amp;ldquo;to 500 MHz&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Termination&lt;/td>
&lt;td data-label="Cat6">RJ45 on T568A or B&lt;/td>
&lt;td data-label="Cat6A">Same plug; Cat6A-rated keystones and patch panels to certify&lt;/td>
&lt;td data-label="Source">trueCABLE&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">1,000 ft solid bare-copper U/UTP CMR reel, same maker, Newegg, November 17, 2026&lt;/td>
&lt;td data-label="Cat6">$170.00 (Elite Cat6 Riser, 23 AWG, marketplace seller)&lt;/td>
&lt;td data-label="Cat6A">$289.00 (Elite Cat6a Riser, 23 AWG, marketplace seller)&lt;/td>
&lt;td data-label="Source">Newegg catalogue&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="where-cat5e-cat6e-cat7-and-cat8-fit">Where Cat5e, Cat6e, Cat7 and Cat8 fit&lt;/h2>
&lt;p>Plain Cat5 is now a defunct category; Fluke&amp;rsquo;s history table lists it at 100 Mb/s. Cat5e is the older gigabit baseline: 100 MHz and 1 Gb/s, with 2.5 or 5 Gb/s possible in some installations. Fluke&amp;rsquo;s application table uses 100-meter channels unless it marks a shorter exception. Cat6 raises the rating to 250 MHz and adds the short-run 10GBASE-T option discussed above; the 37-to-55-meter caveat is specifically about 10GBASE-T over Cat6.&lt;/p>
&lt;p>Cat6e is not a recognized step between Cat6 and Cat6A.&lt;/p>
&lt;p>&lt;a href="https://www.flukenetworks.com/knowledge-base/applicationstandards-articles-copper/category-6e-its-not-category-6a" rel="noopener">Fluke says&lt;/a> cable sold as Category 6e may exceed Cat6 requirements, but it does not meet Cat6A&amp;rsquo;s alien-crosstalk requirements. Treat its supported speed as whatever recognized category the complete installed channel certifies to, rather than a separate Cat6e speed.&lt;/p>
&lt;p>Cat7 is an ISO/IEC category that Fluke lists at 10 Gb/s, but it was never officially recognized by the TIA.&lt;/p>
&lt;p>Cat8 is a different tool: Fluke describes it as 25 or 40 Gb/s cabling for 30-meter data-center switch-to-server links. Neither changes the ordinary home choice between Cat6 and Cat6A. For a new 100-meter-capable 10GBASE-T channel, Cat6A is the direct standard.&lt;/p>
&lt;h2 id="a-cat6a-buying-shortlist">A Cat6A buying shortlist&lt;/h2>
&lt;p>Check the conductor before anything else. &lt;a href="https://www.truecable.com/blogs/cable-academy/copper-clad-aluminum-vs-solid-copper-ethernet-cables" rel="noopener">trueCABLE&amp;rsquo;s article on copper-clad aluminum&lt;/a> says the TIA standard &amp;ldquo;specifically forbids the use of anything other than copper&amp;rdquo; in these cables, that aluminum&amp;rsquo;s higher resistance makes CCA a poor match for proper PoE, and that CCA must be labeled as CCA on the box and the jacket. If a bulk box is suspiciously cheap or light and the listing never says solid or bare copper, skip it.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;p>For an indoor wall or riser run, a concrete starting point is trueCABLE part &lt;code>6ACMRBLU_1Krl&lt;/code>: 1,000 feet of 23AWG solid bare-copper U/UTP cable with a CMR jacket. &lt;a href="https://www.truecable.com/collections/cat6a-cable/products/cat6a-cable-riser?variant=13372471083075" rel="noopener">The manufacturer documents&lt;/a> 10GbE to 100 meters, PoE through 802.3bt, cETLus certification and ANSI/TIA-568.2-E compliance. It is not plenum-rated or outdoor cable, so choose the correct jacket for the route. Newegg&amp;rsquo;s only listing for this reel on November 17, 2026 was a marketplace seller at $597.40, so compare that against trueCABLE&amp;rsquo;s own store before you buy.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=trueCABLE&amp;#43;Cat6A&amp;#43;Riser&amp;#43;CMR&amp;#43;1000ft&amp;#43;23AWG&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/cat6-vs-cat6a-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DtrueCABLE%2BCat6A%2BRiser%2B1000ft" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/cat6-vs-cat6a-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>For a finished patch lead, use a factory-terminated Cat6A cable with the shielding type that matches the channel. Cable Matters model &lt;code>160012&lt;/code> is a &lt;a href="https://www.cablematters.com/pc-247-160-cable-matters-5-pack-snagless-cat-6a-cat6a-sstpsftp-shielded-ethernet-cable-availble-1ft-200ft-in-length.aspx" rel="noopener">26AWG bare-copper S/FTP patch cable&lt;/a>, offered in lengths from 1 to 200 feet. A shielded patch lead is useful only when the jacks, patch panel and grounding plan also support shielding. Do not use a stranded patch cable as permanent in-wall bulk cable.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Cable&amp;#43;Matters&amp;#43;160012&amp;#43;Cat6A&amp;#43;snagless&amp;#43;shielded&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/cat6-vs-cat6a-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DCable%2BMatters%2BCat6A%2BSnagless%2BShielded" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/cat6-vs-cat6a-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>“Best Cat6A cable” therefore has two answers: solid CMR or CMP bulk cable for the permanent run, and a factory patch lead for the rack-to-device link. Keep the whole channel Cat6A-rated if certification is the goal; &lt;a href="https://www.flukenetworks.com/blog/cabling-chronicles/channel-permanent-link-patch-cords-mptl-e2e-oh-my" rel="noopener">Fluke notes that patch cords can be the weak link&lt;/a>. For the switch and router at either end, the &lt;a href="https://techfuelhq.com/articles/best-homelab-networking-gear-under-200/">homelab networking gear under $200&lt;/a> and &lt;a href="https://techfuelhq.com/networking/best-wifi-7-router-2026/">Wi-Fi 7 router&lt;/a> guides cover the boxes these runs feed.&lt;/p>
&lt;h2 id="what-i-run-and-why">What I run and why&lt;/h2>
&lt;p>The one cable I can speak for is the one behind my own desk. On 2026-09-12 Windows reports the Intel I225-V controller in this PC linked at 1 Gbps by auto-negotiation. Intel&amp;rsquo;s specification page lists the I225-V&amp;rsquo;s data rate per port as 2.5GbE, so something other than the controller is holding it at 1 gigabit, either the switch port or the run itself, and I have not opened the wall to read the jacket. That is the point. At 1 gigabit the category is irrelevant. I would learn nothing by pulling it.&lt;/p>
&lt;p>If I were pulling new copper through this house, I would pull Cat6A for every in-wall run and keep Cat6 for the patch cables on the desk and in the rack. Not because I plan 10GBASE-T over copper; the &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE page&lt;/a> makes my case for SFP+ with DAC and fiber where the runs are short, and that case has not changed.&lt;/p>
&lt;p>It is because a wall run is a one-time cost and the extra cost per box is the smallest number in the job. For a house that will live at &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">2.5GbE&lt;/a>, Cat6 is the correct answer and Cat6A is insurance you can afford. Buy the insurance for the runs you cannot reach again. Skip it for the rest.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://www.flukenetworks.com/knowledge-base/applicationstandards-articles-copper/10gbase-t-field-testing-requirements" rel="noopener">Fluke Networks Knowledge Base, 10GBASE-T field testing requirements (TSB-155 quotation and the 37, 55 and 100 meter language)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.truecable.com/blogs/cable-academy/cat6-vs-cat6a" rel="noopener">trueCABLE Cable Academy, Don Schultz, The Difference Between Cat6 vs Cat6A Ethernet Cable (June 9, 2023)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.truecable.com/blogs/cable-academy/copper-clad-aluminum-vs-solid-copper-ethernet-cables" rel="noopener">trueCABLE Cable Academy, CCA vs Solid Copper Ethernet Cables&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.cablematters.com/Blog/Networking/cat6-vs-cat6a-vs-cat7" rel="noopener">Cable Matters, Cat 6 vs. Cat 6a. vs. Cat 7: Which One Should You Choose? (July 14, 2026)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.monoprice.com/product?p_id=8103" rel="noopener">Monoprice, Cat6 1000ft Blue CMR UL Bulk Cable, Solid, UTP, 23AWG, 550MHz (product 8103, $229.99 on 2026-09-12)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.monoprice.com/product?p_id=18600" rel="noopener">Monoprice, 1000ft Cat6A Ethernet Cable, UTP, 23AWG, 10G, CMR-Rated (product 18600, $309.99 on 2026-09-12)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.intel.com/content/www/us/en/products/sku/184676/intel-ethernet-controller-i225v/specifications.html" rel="noopener">Intel, Ethernet Controller I225-V specifications&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.flukenetworks.com/blog/cabling-chronicles/ethernet-cable-history" rel="noopener">Fluke Networks, Ethernet Cable Categories Explained: A Brief History (February 24, 2022)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.flukenetworks.com/expertise/role/network-engineers" rel="noopener">Fluke Networks, Network Engineer Tools and Troubleshooting Guide (category application table)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.flukenetworks.com/knowledge-base/applicationstandards-articles-copper/category-6e-its-not-category-6a" rel="noopener">Fluke Networks, Category 6e - It&amp;rsquo;s not Category 6A (January 28, 2014)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.reddit.com/r/HomeNetworking/comments/1aqnyjp/all_cat6_and_cat6a_differences_beyond_the_cat6/" rel="noopener">Reddit r/HomeNetworking, ALL Cat6 and Cat6a differences beyond the &amp;ldquo;Cat6 can run 10 gig on a shorter distance&amp;rdquo; (February 14, 2024)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.reddit.com/r/HomeNetworking/comments/18zzvix/is_it_worth_to_use_a_cat6a_cable_over_a_cat6/" rel="noopener">Reddit r/HomeNetworking, Is it worth to use a CAT6A cable over a CAT6 nowadays? (January 6, 2024)&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Forgejo vs Gitea 2026: Which Self-Hosted Git to Pick</title><link>https://techfuelhq.com/homelab/forgejo-vs-gitea-2026/</link><pubDate>Sat, 04 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/forgejo-vs-gitea-2026/</guid><atom:updated>2026-11-18T05:30:00Z</atom:updated><description>&lt;p>If you&amp;rsquo;re standing up a self-hosted Git server in 2026, the two names you&amp;rsquo;ll weigh are &lt;strong>Forgejo&lt;/strong> and &lt;strong>Gitea&lt;/strong>, and they&amp;rsquo;re no longer the same thing wearing different logos. Forgejo began as a friendly fork of Gitea, became a &lt;strong>hard fork in early 2024&lt;/strong>, and has been diverging ever since.&lt;/p>
&lt;p>So the real question isn&amp;rsquo;t &amp;ldquo;which logo do I like,&amp;rdquo; it&amp;rsquo;s &amp;ldquo;which project do I want to run for the next five years.&amp;rdquo; Here&amp;rsquo;s how they compare on the things that decide it: governance, licensing, federation and migration. Each claim is tied to the project that makes it. Several Gitea-side points come from Forgejo&amp;rsquo;s own comparison page; where they do, the text says so.&lt;/p>
&lt;h2 id="the-two-at-a-glance">The two at a glance&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Forgejo&lt;/th>
&lt;th scope="col">Gitea&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Governance&lt;/td>
&lt;td data-label="Forgejo">&lt;strong>Codeberg e.V.&lt;/strong> (non-profit, community-led)&lt;/td>
&lt;td data-label="Gitea">For-profit company (&lt;strong>Gitea Ltd&lt;/strong>), Open Core&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">License&lt;/td>
&lt;td data-label="Forgejo">&lt;strong>GPLv3+&lt;/strong> (since v9.0; MIT before)&lt;/td>
&lt;td data-label="Gitea">&lt;strong>MIT&lt;/strong> + commercial edition&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Fork status&lt;/td>
&lt;td data-label="Forgejo">Hard fork since &lt;strong>early 2024&lt;/strong>&lt;/td>
&lt;td data-label="Gitea">Original project&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Latest stable (read November 18, 2026)&lt;/td>
&lt;td data-label="Forgejo">&lt;strong>v17.0.1&lt;/strong> (October 26); LTS line v15.0.x&lt;/td>
&lt;td data-label="Gitea">&lt;strong>28.4.0&lt;/strong> (November 15)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Federation (ActivityPub)&lt;/td>
&lt;td data-label="Forgejo">&lt;strong>In active development&lt;/strong>, monthly progress reports&lt;/td>
&lt;td data-label="Gitea">None known to Forgejo (its page, updated December 13, 2024)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">CI/CD&lt;/td>
&lt;td data-label="Forgejo">Forgejo Actions (familiar to GitHub users, not designed to be compatible)&lt;/td>
&lt;td data-label="Gitea">Gitea Actions (&amp;ldquo;mostly compatible&amp;rdquo; with GitHub Actions)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Upgrade / accessibility tests&lt;/td>
&lt;td data-label="Forgejo">&lt;strong>Yes&lt;/strong> (e2e, upgrade and browser tests with accessibility checks)&lt;/td>
&lt;td data-label="Gitea">One example browser test (Forgejo&amp;rsquo;s page, as of June 21, 2025)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Migration&lt;/td>
&lt;td data-label="Forgejo">Drop-in from &lt;strong>Gitea ≤ v1.22 → Forgejo v10 → current v17&lt;/strong> (no drop-in path from Gitea v1.23 or 28.x)&lt;/td>
&lt;td data-label="Gitea">—&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Best for&lt;/td>
&lt;td data-label="Forgejo">Community governance, federation, homelab&lt;/td>
&lt;td data-label="Gitea">MIT license, Gitea Enterprise features&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Both are lightweight, single-binary Git forges that run happily on a mini PC or a small VM, both do issues/PRs/wiki/releases/CI, and both are far lighter than GitLab. The differences below are about &lt;em>who controls the project and where it&amp;rsquo;s going&lt;/em>, not about whether it can host your repos. Either one can.&lt;/p>
&lt;h2 id="why-forgejo-exists-the-governance-split">Why Forgejo exists: the governance split&lt;/h2>
&lt;p>This is the part that started everything. In &lt;strong>October 2022&lt;/strong>, the Gitea project&amp;rsquo;s domains and trademark were transferred to a for-profit company (Gitea Ltd), &amp;ldquo;without knowledge or approval of the community&amp;rdquo; by Forgejo&amp;rsquo;s account.&lt;/p>
&lt;p>Forgejo&amp;rsquo;s comparison page dates the project&amp;rsquo;s creation to that same month; a team of former Gitea maintainers and people from the wider Free Software community announced it publicly on &lt;strong>December 15, 2022&lt;/strong>, with &lt;strong>Codeberg e.V.&lt;/strong>, a registered German non-profit, as its custodian. Forgejo says it is &amp;ldquo;developed in the interest of the general public&amp;rdquo;; its criticism of Gitea is that ownership by a for-profit company &amp;ldquo;leads to decisions being made to maximize profit rather than favor the interest of the general public.&amp;rdquo;&lt;/p>
&lt;p>In 2026, Forgejo governance is a formal, documented structure: community elections, a transparent roadmap, public decision-making. Gitea, by contrast, runs an &lt;strong>Open Core&lt;/strong> model: the core is MIT-licensed, but the company also develops software that is not published under a Free Software licence and (per Forgejo&amp;rsquo;s comparison) requires &lt;strong>copyright assignment even for MIT-licensed contributions&lt;/strong>.&lt;/p>
&lt;p>Neither model is inherently wrong. A company-backed project can ship features and support that a volunteer non-profit can&amp;rsquo;t always match, but the two pull in different directions, which is exactly why the fork became a &lt;em>hard&lt;/em> fork.&lt;/p>
&lt;h2 id="licensing-mit-vs-gplv3-and-why-it-probably-doesnt-affect-you">Licensing: MIT vs GPLv3+ (and why it probably doesn&amp;rsquo;t affect you)&lt;/h2>
&lt;p>Gitea is &lt;strong>MIT-licensed&lt;/strong>: maximally permissive, so anyone (including a company) can take the code, modify it and ship it in a closed product. Forgejo was MIT too, up to and including its v8 series. &lt;strong>Starting with its v9.0 release (2024), Forgejo relicensed to GPLv3-or-later&lt;/strong>, a copyleft license.&lt;/p>
&lt;p>The stated reason: to keep Forgejo&amp;rsquo;s code from being pulled back into a commercially controlled Gitea. So the license divergence is really the governance dispute expressed in legal terms.&lt;/p>
&lt;p>For a &lt;strong>homelab user, this is invisible.&lt;/strong> GPLv3 only creates obligations when you &lt;em>distribute a modified version&lt;/em> of the software. Running Forgejo for yourself, your family or your team triggers none of them.&lt;/p>
&lt;p>The license matters if you&amp;rsquo;re a business planning to build and sell a closed product on top of the code (MIT lets you; GPLv3 doesn&amp;rsquo;t), or if you have a philosophical preference for copyleft over permissive. Otherwise, both are genuinely Free/Open-Source and you can ignore this section.&lt;/p>
&lt;h2 id="where-they-actually-differ-now">Where they actually differ now&lt;/h2>
&lt;p>Since the hard fork, the codebases have drifted. The concrete differences in 2026:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Forge federation (Forgejo&amp;rsquo;s flagship bet).&lt;/strong> Forgejo is working on &lt;strong>ActivityPub-based forge federation&lt;/strong>, the ability for issues, pull requests and stars to work across independent instances, the way Mastodon federates social posts, and publishes monthly progress reports. Forgejo&amp;rsquo;s comparison page said on December 13, 2024 that, to its knowledge, there was no federation work in Gitea. If a &amp;ldquo;self-hosted but not isolated&amp;rdquo; future appeals to you, this is Forgejo&amp;rsquo;s single biggest differentiator.&lt;/li>
&lt;li>&lt;strong>CI/CD.&lt;/strong> Both ship an Actions system modelled on GitHub&amp;rsquo;s. Forgejo&amp;rsquo;s documentation says Forgejo Actions is &amp;ldquo;designed to be familiar to users of GitHub Actions, but it is not designed to be compatible,&amp;rdquo; and that workflows should work with some minimal changes; one listed difference is that most Forgejo runners default to a Debian bookworm image with only Node.js, where GitHub uses a larger Ubuntu image. Gitea&amp;rsquo;s documentation calls Gitea Actions &amp;ldquo;similar and mostly compatible&amp;rdquo; with GitHub Actions. Either way, test an existing workflow before you count on it. Forgejo is tested and released with Forgejo Actions; Gitea is developed on GitHub and tested and released with GitHub Actions.&lt;/li>
&lt;li>&lt;strong>Testing and accessibility.&lt;/strong> Per Forgejo&amp;rsquo;s own comparison, Forgejo relies on end-to-end and upgrade tests, plus browser tests that include &lt;strong>accessibility checks&lt;/strong>; the same page says Gitea has no end-to-end or upgrade tests and, as of June 21, 2025, only an example browser test. For an app you&amp;rsquo;ll upgrade for years, upgrade-test coverage is a quiet but real reliability signal.&lt;/li>
&lt;li>&lt;strong>Development stack.&lt;/strong> Forgejo is developed on Forgejo itself, with localization on Weblate; Gitea is developed on GitHub with localization on Crowdin. A values signal more than a feature, but it&amp;rsquo;s real.&lt;/li>
&lt;/ul>
&lt;p>What has &lt;em>not&lt;/em> meaningfully diverged: the core self-hosting experience. Repo hosting, the web UI, issues, PRs, wiki, packages and releases are still very similar, because they share the same origin. This is why the choice is about trajectory, not day-one features.&lt;/p>
&lt;h2 id="running-forgejo-in-a-homelab">Running Forgejo in a homelab&lt;/h2>
&lt;p>Forgejo&amp;rsquo;s Docker guide gives a Compose file that starts with SQLite (it defaults to SQLite when no database is configured). This is that example with one change, the web port bound to localhost for a reverse proxy on the same host:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">networks&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">forgejo&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">external&lt;/span>: &lt;span style="color:#66d9ef">false&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">server&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">codeberg.org/forgejo/forgejo:17&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">forgejo&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">USER_UID=1000&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">USER_GID=1000&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">always&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">networks&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">forgejo&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./forgejo:/data&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/etc/localtime:/etc/localtime:ro&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;127.0.0.1:3000:3000&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;222:22&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Port warning:&lt;/strong> Forgejo&amp;rsquo;s own example publishes &lt;code>3000:3000&lt;/code> on every network interface. Bind the web port to &lt;code>127.0.0.1&lt;/code> as above and put a reverse proxy in front, the setup Forgejo&amp;rsquo;s reverse-proxy guide shows with &lt;code>reverse_proxy 127.0.0.1:3000&lt;/code> in Caddy; keep port 222 (Git over SSH) to your LAN and out of your router&amp;rsquo;s port forwards.&lt;/p>
&lt;p>The &lt;code>17&lt;/code> tag follows the latest 17.x release. Forgejo&amp;rsquo;s guide says moving from one major version to the next (for instance from 12 to 13) &amp;ldquo;requires a manual operation and human verification,&amp;rdquo; so read the release notes before you change the tag. The &lt;code>./forgejo&lt;/code> folder must be owned by the UID/GID you set, or the container may not start. Choosing the proxy is its own decision: &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">Caddy vs Nginx Proxy Manager vs Traefik&lt;/a>. Keep secrets out of the Compose file with an &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">.env file&lt;/a>, back up &lt;code>./forgejo&lt;/code>, which the example mounts as the container&amp;rsquo;s &lt;code>/data&lt;/code>, with one of the tools in &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">restic vs Borg vs Kopia&lt;/a>, and if you manage several stacks, &lt;a href="https://techfuelhq.com/homelab/komodo-vs-portainer-vs-dockge-2026/">Komodo vs Portainer vs Dockge&lt;/a> covers the managers.&lt;/p>
&lt;h2 id="compatibility-and-migration-the-practical-part">Compatibility and migration: the practical part&lt;/h2>
&lt;p>Here&amp;rsquo;s the reassuring news for anyone on an older Gitea: Forgejo publishes an official path for taking over a Gitea instance. From its upgrade guide:&lt;/p>
&lt;blockquote>
&lt;p>Upgrades to Forgejo are transparently supported up to Gitea v1.22 included, in two steps: (1) upgrade from any Gitea version up to and including &lt;strong>v1.22.x&lt;/strong> to &lt;strong>Forgejo v10.0.x&lt;/strong>, then (2) upgrade from Forgejo v10.0.x to &lt;strong>any Forgejo version greater than v10&lt;/strong>.&lt;/p>&lt;/blockquote>
&lt;p>In practice that means: back up your Gitea database and data directory, run Forgejo v10.0.x pointed at the same data, then upgrade Forgejo the rest of the way to the current release, with no re-cloning repositories and no re-creating users. Forgejo v10 is only the doorway, not the destination; the current stable line is &lt;strong>v17.0.x&lt;/strong>, and v15.0.x is the long-term-support line. Forgejo&amp;rsquo;s release life cycle gives a stable release three months of full support plus two weeks after the next one ships, and the LTS release published in the first quarter of each year a year and three months of critical bugfix and security support.&lt;/p>
&lt;p>&lt;strong>The ceiling is the catch, and it has gotten sharper.&lt;/strong> Forgejo&amp;rsquo;s supported path still caps at &lt;strong>Gitea v1.22&lt;/strong>, while Gitea kept shipping: 1.23 through 1.27, then &lt;strong>28.0.0 on September 30, 2026&lt;/strong>, when Gitea dropped &amp;ldquo;the historical 1. prefix from its version numbers,&amp;rdquo; and 28.4.0 on November 15. If your Gitea is newer than v1.22, you are &lt;em>past&lt;/em> the transparent path, and you cannot get back to it by upgrading Gitea further.&lt;/p>
&lt;p>Nor can you simply drop back down. Gitea&amp;rsquo;s own upgrade guide warns that once a newer release has migrated your database, it &amp;ldquo;can not be used for an old Gitea, use a backup to downgrade.&amp;rdquo; Downgrading across a minor version means &lt;strong>restoring a pre-upgrade backup&lt;/strong>, not just running the older binary. If you did not keep a backup from before you left v1.22, that door is shut.&lt;/p>
&lt;p>Your options in that case are to stay on Gitea, or to move repositories, issues and users across with Forgejo&amp;rsquo;s API-based repository migration instead of a drop-in data-directory swap: a real migration with real gaps, not a binary swap. Check your Gitea version &lt;em>before&lt;/em> you plan the move, not after.&lt;/p>
&lt;p>The caveat: this is &lt;strong>effectively a one-way door&lt;/strong>. Because Forgejo has diverged (and relicensed) since the hard fork, there&amp;rsquo;s no supported route to migrate a modern Forgejo instance &lt;em>back&lt;/em> to Gitea. That&amp;rsquo;s not a reason to avoid the move; it&amp;rsquo;s a reason to make the decision deliberately and keep a backup of your pre-migration state. On Gitea 1.22 or older in a Docker Compose stack, the swap is mostly a change of image and a data backup.&lt;/p>
&lt;h2 id="which-should-you-run">Which should you run?&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>New homelab or small-team forge, no existing instance →&lt;/strong> &lt;strong>Forgejo.&lt;/strong> You get the same lightweight experience plus non-profit governance, copyleft licensing, upgrade/accessibility testing and the federation work. It&amp;rsquo;s the lower-risk long-term bet for a project you don&amp;rsquo;t want a company to be able to close.&lt;/li>
&lt;li>&lt;strong>You specifically need Gitea&amp;rsquo;s commercial &amp;ldquo;Enterprise&amp;rdquo; features, or you&amp;rsquo;re building a product on top and want the permissive MIT license →&lt;/strong> &lt;strong>Gitea.&lt;/strong>&lt;/li>
&lt;li>&lt;strong>You already run a stable Gitea and nothing hurts →&lt;/strong> there&amp;rsquo;s no urgency. Gitea is still open and maintained. If you are on 1.23 or later, a move means an API migration, so wait until a Forgejo feature (federation, an Actions improvement) actually pulls you.&lt;/li>
&lt;/ul>
&lt;p>Self-hosted Git is one of the highest-value things you can pull off SaaS. It&amp;rsquo;s a core piece of the &lt;a href="https://techfuelhq.com/articles/self-hosted-apps-replace-saas-2026/">self-hosted stack that replaces rented tools&lt;/a>, and it runs fine in a container next to everything else. Whichever you pick, you&amp;rsquo;re keeping your code on infrastructure you control. Deciding whether to run it in a &lt;a href="https://techfuelhq.com/articles/proxmox-vs-docker-2026/">container or a VM&lt;/a>, or in an &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC or a VM on Proxmox&lt;/a>, is the next call.&lt;/p>
&lt;h2 id="the-verdict">The verdict&lt;/h2>
&lt;p>The tiebreakers are about &lt;em>governance and direction&lt;/em>: Forgejo is the pick if you want a community-controlled, non-profit-governed project with copyleft protection and a federated future, and it&amp;rsquo;s my default recommendation for anyone starting fresh. Gitea remains the right call if you need its commercial features or the permissive MIT license, or if you&amp;rsquo;re simply happy where you are.&lt;/p>
&lt;p>One thing I won&amp;rsquo;t fake: &lt;strong>resource footprint.&lt;/strong> Because Forgejo and Gitea share a common Go codebase, their memory and CPU use are effectively identical — both idle in the low hundreds of megabytes and scale with your repo count and CI usage, not with the logo. Anyone quoting a dramatic footprint gap between the two is guessing; run whichever you choose and watch it on your own box.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>Forgejo, comparison with Gitea (creation, governance, copyright assignment, federation, testing, development infrastructure): &lt;a href="https://forgejo.org/compare-to-gitea/" rel="noopener">Forgejo comparison with Gitea&lt;/a>&lt;/li>
&lt;li>Forgejo, upgrade guide (&amp;ldquo;Upgrades to Forgejo are transparently supported up to Gitea v1.22 included, in two steps&amp;rdquo;; release life cycle): &lt;a href="https://forgejo.org/docs/latest/admin/upgrade/" rel="noopener">Forgejo upgrade guide&lt;/a>&lt;/li>
&lt;li>Forgejo, Gitea migration guide in the v10.0 docs (the version-pinned page for the first step): &lt;a href="https://forgejo.org/docs/v10.0/admin/gitea-migration/" rel="noopener">Forgejo v10 Gitea migration guide&lt;/a>&lt;/li>
&lt;li>Forgejo, installation with Docker (image tags, Compose example, SQLite default, major-version upgrades): &lt;a href="https://forgejo.org/docs/latest/admin/installation/docker/" rel="noopener">Forgejo Docker installation&lt;/a> · reverse proxy: &lt;a href="https://forgejo.org/docs/latest/admin/setup/reverse-proxy/" rel="noopener">Forgejo reverse proxy guide&lt;/a>&lt;/li>
&lt;li>Forgejo Actions and GitHub Actions (&amp;ldquo;not designed to be compatible&amp;rdquo;; known differences): &lt;a href="https://forgejo.org/docs/latest/user/actions/github-actions/" rel="noopener">Forgejo Actions compared with GitHub Actions&lt;/a> · Gitea Actions (&amp;ldquo;similar and mostly compatible&amp;rdquo;): &lt;a href="https://docs.gitea.com/usage/actions/overview" rel="noopener">Gitea Actions overview&lt;/a>&lt;/li>
&lt;li>Gitea, upgrade guide (&amp;ldquo;Database already got upgraded and can not be used for an old Gitea, use a backup to downgrade&amp;rdquo;): &lt;a href="https://docs.gitea.com/installation/upgrade-from-gitea" rel="noopener">Gitea upgrade guide&lt;/a>&lt;/li>
&lt;li>Releases read November 18, 2026: &lt;a href="https://codeberg.org/forgejo/forgejo/releases" rel="noopener">Forgejo releases&lt;/a> (v17.0.1, October 26, 2026) · &lt;a href="https://github.com/go-gitea/gitea/releases" rel="noopener">Gitea releases&lt;/a> (28.4.0, November 15, 2026) · version change: &lt;a href="https://blog.gitea.com/release-of-28.0.0/" rel="noopener">Gitea 28.0.0 is released&lt;/a>&lt;/li>
&lt;li>Forgejo relicenses to GPLv3+ (v9.0; rationale): &lt;a href="https://lwn.net/Articles/986998/" rel="noopener">LWN.net&lt;/a> · &lt;a href="https://forgejo.org/2024-02-forking-forward/" rel="noopener">Forgejo Forking Forward rationale&lt;/a>&lt;/li>
&lt;li>Forgejo becomes a hard fork of Gitea (governance record): &lt;a href="https://codeberg.org/forgejo/governance/issues/58" rel="noopener">Forgejo governance issue 58&lt;/a> · public announcement: &lt;a href="https://forgejo.org/2022-12-15-hello-forgejo/" rel="noopener">Hello Forgejo, December 15, 2022&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>CyberPower CP1500PFCLCD Review: Runtime, Batteries and Revisions</title><link>https://techfuelhq.com/reviews/cyberpower-cp1500pfclcd-review-2026/</link><pubDate>Sun, 04 Oct 2026 23:42:28 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/reviews/cyberpower-cp1500pfclcd-review-2026/</guid><atom:updated>2026-11-18T05:28:32Z</atom:updated><description>&lt;p>&lt;strong>The CP1500PFCLCD is a good buy for a desktop or small homelab that needs enough battery time to shut down cleanly: Newegg sold it for $239.95 on November 17, 2026, and CyberPower publishes 23 minutes at 300W.&lt;/strong> I would choose it around the equipment it must protect, then check the revision before comparing offers. CyberPower has used this name across different hardware: the documented 1000W version has twelve outlets, while older examples carried a 900W rating and ten outlets. &lt;a href="https://www.cyberpowersystems.com/product/ups/pfc-sinewave/cp1500pfclcd/" rel="noopener">Current product page&lt;/a>, &lt;a href="https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html" rel="noopener">historical NUT reports&lt;/a>, &lt;a href="https://www.tomshardware.com/reviews/apc-smt1500-cyberpower-cp1500pfclcd-tripp-lite-smart1500slt,2785-5.html" rel="noopener">2010 inspection&lt;/a>.&lt;/p>
&lt;p>I owned a CP1500PFCLCD for between one and two years. That ownership is the first-person evidence used here.&lt;/p>
&lt;p>I have no recorded revision, runtime measurements, or acoustic measurements to attach to that ownership. The assessment below combines manufacturer documentation with explicitly scoped software reports.&lt;/p>
&lt;h2 id="which-cp1500pfclcd-this-review-covers">Which CP1500PFCLCD this review covers&lt;/h2>
&lt;p>The specification reference is the US 120V, 1500VA/1000W version. These are manufacturer specifications from CyberPower&amp;rsquo;s &lt;a href="https://www.cyberpowersystems.com/product/ups/pfc-sinewave/cp1500pfclcd/" rel="noopener">product page&lt;/a> and &lt;a href="https://dl4jz3rbrsfum.cloudfront.net/documents/CyberPower_DS_CP1500PFCLCD.pdf" rel="noopener">datasheet&lt;/a>.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Detail&lt;/th>
&lt;th scope="col">Documented configuration&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Detail">Output limits&lt;/td>
&lt;td data-label="Documented configuration">1500VA and 1000W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Design&lt;/td>
&lt;td data-label="Documented configuration">Line-interactive; sine-wave output on utility and on battery; active PFC compatible&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Outlets&lt;/td>
&lt;td data-label="Documented configuration">Six battery-backed, six surge-only; NEMA 5-15R, two widely spaced&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Input&lt;/td>
&lt;td data-label="Documented configuration">120V; NEMA 5-15P right-angle plug, 5 ft cord&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Published runtime&lt;/td>
&lt;td data-label="Documented configuration">10 minutes at half load; 2.5 minutes at full load&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Typical recharge&lt;/td>
&lt;td data-label="Documented configuration">8 hours&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Data connection&lt;/td>
&lt;td data-label="Documented configuration">USB HID; dry-contact serial port; optional RMCARD205 network card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">USB charging&lt;/td>
&lt;td data-label="Documented configuration">One Type-A, one Type-C; 3.1A shared&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Battery&lt;/td>
&lt;td data-label="Documented configuration">Two 12V/9Ah sealed lead-acid; one replacement cartridge, matched by serial prefix&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Detail">Physical size&lt;/td>
&lt;td data-label="Documented configuration">3.9 inches wide, 11 high, 14 deep; 24.9 lb&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>That outlet split matters. Twelve sockets do not provide twelve battery-backed connections.&lt;/p>
&lt;p>Before buying, make a short list of what must survive an outage, including the computer, necessary display, NAS, router, and any switch required for shutdown messages, then check that their actual plugs fit the battery side without blocking one another.&lt;/p>
&lt;p>Older reviews need equally careful reading. Tom&amp;rsquo;s Hardware&amp;rsquo;s November 2010 inspection describes five battery-backed outlets and an earlier “Adaptive Sinewave” implementation. It is useful evidence of the product&amp;rsquo;s history, but its waveform description and physical layout should not be transferred to the twelve-outlet version. &lt;a href="https://www.tomshardware.com/reviews/apc-smt1500-cyberpower-cp1500pfclcd-tripp-lite-smart1500slt,2785-5.html" rel="noopener">Original inspection&lt;/a>.&lt;/p>
&lt;h2 id="the-runtime-number-that-changes-the-buying-decision">The runtime number that changes the buying decision&lt;/h2>
&lt;p>CyberPower&amp;rsquo;s runtime chart for the CP1500PFCLCD with no extra battery modules gives these points. CyberPower bases them on new, fully charged batteries at normal operating conditions and calls the curve approximate. &lt;a href="https://www.cyberpowersystems.com/product/ups/pfc-sinewave/cp1500pfclcd/" rel="noopener">CyberPower runtime chart&lt;/a>.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col" style="text-align: right">Load&lt;/th>
&lt;th scope="col" style="text-align: right">Runtime&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">50W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">100 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">100W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">66 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">200W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">30.8 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">300W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">23 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">400W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">14 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">500W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">10 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">600W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">8 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">700W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">6 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">800W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">4 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">900W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">3 min&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: right" data-label="Load">1000W&lt;/td>
&lt;td style="text-align: right" data-label="Runtime">2.5 min&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The useful comparison is your required shutdown time against runtime at your actual load. A 1000W output ceiling says how much load the unit is rated to support; it does not promise a long session at that load. CyberPower&amp;rsquo;s published 10-minute half-load figure corresponds to 500W, while its full-load figure is only 2.5 minutes. Those are manufacturer ratings, not our measurements.&lt;/p>
&lt;p>For a worked sizing example, suppose your protected equipment draws 350W while doing the job you need to finish. Dividing 350 by the documented 1000W ceiling gives 35% loading. CyberPower&amp;rsquo;s chart puts 350W between its 300W point (23 minutes) and its 400W point (14 minutes); any single figure in between is an estimate, not a CyberPower number. Add the display and network equipment to the input if they will remain connected. I would start with our &lt;a href="https://techfuelhq.com/tools/ups-runtime-calculator/">UPS runtime calculator&lt;/a>, treat its result as a planning estimate, and then verify the complete shutdown sequence during a planned maintenance window.&lt;/p>
&lt;p>Define success beforehand. A NAS that finishes shutting down with reserve remaining meets a different requirement from a desktop expected to keep rendering through an outage.&lt;/p>
&lt;p>If your requirement is sustained high-power work, seek a model with documented runtime at that load and the battery capacity to meet it. Buying this tower simply because “1500” sounds large is the wrong shortcut.&lt;/p>
&lt;h2 id="usb-shutdown-is-part-of-the-purchase">USB shutdown is part of the purchase&lt;/h2>
&lt;p>The supplied USB A-to-B communication cable connects the UPS to a computer. The front charging ports have a different job. CyberPower&amp;rsquo;s manual separates them, and it describes PowerPanel software as the route to automatic computer shutdown. Make the data connection during installation. &lt;a href="https://m.media-amazon.com/images/I/A1LdQgA9q1L.pdf" rel="noopener">Manufacturer manual, pages 4–6 of the PDF&lt;/a>.&lt;/p>
&lt;p>The current product page names PowerPanel Business as the management software and lists downloads of version 4.12.4 for Windows, macOS, Linux (32-bit and 64-bit) and a virtual-machine package. That Linux client is a real difference from APC&amp;rsquo;s Back-UPS line, which Schneider does not support on Linux. &lt;a href="https://www.cyberpowersystems.com/product/ups/pfc-sinewave/cp1500pfclcd/" rel="noopener">CyberPower downloads&lt;/a>, &lt;a href="https://techfuelhq.com/reviews/apc-back-ups-pro-br1500ms2-review-2026/#windows-support-is-clearer-than-linux-support">APC BR1500MS2 review&lt;/a>.&lt;/p>
&lt;p>For Linux or a NAS, NUT has CP1500PFCLCD reports using &lt;code>usbhid-ups&lt;/code>. Look closely at their scope: the displayed examples use NUT 2.7.x and report a 900W nominal limit. One submission reports that changing a low-battery setting appeared to succeed without changing the returned value. Another flags unreliable voltage telemetry. These are specific historical reports, not a failure rate for current units. &lt;a href="https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html" rel="noopener">NUT device reports&lt;/a>.&lt;/p>
&lt;p>My takeaway is to verify behavior beyond detection. NUT&amp;rsquo;s &lt;code>upsmon&lt;/code> is the component responsible for invoking system shutdown; reading a charge percentage does not establish that this part is configured. For a group of machines, document which host reads the USB device and how the others receive its status. Keep that communication path powered until every dependent system has finished. &lt;a href="https://networkupstools.org/docs/man/upsmon.html" rel="noopener">NUT shutdown-controller documentation&lt;/a>.&lt;/p>
&lt;p>Our &lt;a href="https://techfuelhq.com/homelab/ups-testing-reality-2026/">UPS testing guide&lt;/a> explains the distinction between charge indication and useful protection. Use the manufacturer&amp;rsquo;s procedures for your hardware when planning the test. If the UPS will protect a NAS you are still building, the &lt;a href="https://techfuelhq.com/homelab/nas-from-old-pc-2026/">old-PC NAS guide&lt;/a> covers the rest of that machine.&lt;/p>
&lt;h2 id="battery-replacement-starts-with-the-serial-number">Battery replacement starts with the serial number&lt;/h2>
&lt;p>CyberPower lists &lt;strong>RB1290X2 for serial numbers beginning CXX&lt;/strong>, and &lt;strong>RB1280X2B for CR9, CXF, or CQC&lt;/strong>. The serial number sits on a small white label on the bottom or back panel, under a barcode. Photograph the label before ordering. A seller listing that says only “fits CP1500PFCLCD” needs more checking. &lt;a href="https://www.cyberpowersystems.com/product/ups/pfc-sinewave/cp1500pfclcd/" rel="noopener">CyberPower product page&lt;/a>.&lt;/p>
&lt;p>Both genuine CyberPower cartridges were in stock at Newegg on November 17, 2026, from marketplace sellers: RB1290X2 from $95.94 and RB1280X2B from $95.83.&lt;/p>
&lt;p>RB1290X2, for serial numbers beginning CXX:&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=CyberPower&amp;#43;RB1290X2&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/reviews/cyberpower-cp1500pfclcd-review-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fcyberpower-rb1290x2%2Fp%2F1T0-000A-00077%3Fitem%3D9SIAFJ8KFD5231" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/reviews/cyberpower-cp1500pfclcd-review-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>RB1280X2B, for serial numbers beginning CR9, CXF or CQC:&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=CyberPower&amp;#43;RB1280X2B&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/reviews/cyberpower-cp1500pfclcd-review-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fcyberpower-rb1280x2b-battery%2Fp%2F04E-00BT-00091%3Fitem%3D9SIAFJ8A0B6434" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/reviews/cyberpower-cp1500pfclcd-review-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Budget a maintenance window. CyberPower lists the battery as not hot-swappable, and the reviewed manual tells owners to turn off and unplug connected equipment, then turn off and unplug the UPS before replacement. Follow its battery instructions; this review does not recommend a live swap. &lt;a href="https://m.media-amazon.com/images/I/A1LdQgA9q1L.pdf" rel="noopener">Manufacturer procedure&lt;/a>.&lt;/p>
&lt;p>Keep the purchase receipt too. CyberPower&amp;rsquo;s product page describes a three-year warranty that includes the batteries, and its limited warranty describes original-purchaser restrictions subject to applicable law and claim conditions. Its connected-equipment promise is conditional and excludes lost data. I would never count that marketing allowance as a replacement for backups. &lt;a href="https://m.media-amazon.com/images/I/61oECrDL60L.pdf" rel="noopener">Warranty document&lt;/a>.&lt;/p>
&lt;h2 id="when-i-would-choose-something-else">When I would choose something else&lt;/h2>
&lt;p>The &lt;a href="https://techfuelhq.com/reviews/apc-back-ups-pro-br1500ms2-review-2026/">APC BR1500MS2&lt;/a> is the comparison to make if APC&amp;rsquo;s software and replacement-battery route suit your setup. Newegg had it at $301.99 on November 17, 2026, $62.04 more than the CyberPower, with a lower 900W rating and APC runtime points that stop at 335W. Compare the same protected load and your required runtime; a higher watt rating alone cannot settle that choice.&lt;/p>
&lt;p>I would pass on a CP1500PFCLCD offer whose revision or battery condition cannot be established. For a clearly identified unit protecting a load with a verified shutdown plan, the combination of replaceable batteries and documented communication support gives it a sensible role. The final buying check is straightforward: exact hardware, suitable load, correct cartridge, and a shutdown that has been exercised.&lt;/p>
&lt;p>&lt;strong>Where to buy the CyberPower CP1500PFCLCD:&lt;/strong> &lt;a href="https://www.amazon.com/s?k=CyberPower+CP1500PFCLCD&amp;tag=techfuelhq-20" rel="nofollow sponsored">Search Amazon&lt;/a> &amp;middot; &lt;a href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;mid=44583&amp;murl=https%3A%2F%2Fwww.newegg.com%2Fcyberpower-cp1500pfclcd-nema-5-15r%2Fp%2FN82E16842102134%3Fitem%3DN82E16842102134" rel="nofollow sponsored">Check Newegg&lt;/a>. Affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/p></description></item></channel></rss>