AdGuard Home
Network-wide DNS filtering for ads and trackers.
Needs to be the DNS server for your network, which is a local-network job. Running it on a rented machine means exposing or tunnelling DNS.
Planning figures used by the calculators: RAM 0.25 GB (our estimate), CPU 0.25 cores (our estimate), storage 1 GB (our estimate). These cover the application itself. Your own photos, films, documents and recordings are entered separately as data storage.
The table lists every figure we hold, what kind of claim it is, and the fragment of the archived document it came from.
Source: AdGuard Home getting started guide, retrieved 2026-09-08, archived as document 20 on the sources page.
Add AdGuard Home to a stack or read how we label a number.
| property | value | basis | evidence | document |
|---|---|---|---|---|
| cpu plan cores | 0.25 cores | our estimate | Our reasoning: No published figure. DNS queries are tiny and cached; a quarter of a core is our planning share. | No document, our reasoning only |
| network need | Needs ports 53/UDP, 80/TCP and 3000/TCP | vendor documented | Quoted from the archived document: To install and use AdGuard Home, the following ports and protocols must be available: 3000/TCP for the initial installation; 80/TCP for the web interface; 53/UDP for the DNS server. | Document 20, retrieved 2026-09-08 |
| ram plan gb | 0.25 GB | our estimate | Our reasoning: No published figure. A single Go binary with in-memory caches; we plan 256 MB for a household. | No document, our reasoning only |
| storage plan gb | 1 GB | our estimate | Our reasoning: No published figure. Binary, filter lists and query log, which has a configurable retention. | No document, our reasoning only |