Deployment
Docker & GPU
Docker support: Yes
GPU: Not required
Check the source notes below before assuming a GPU, transcoding workload or machine-learning feature is included in the baseline deployment.
Monitoring / Analytics / Infra
Network-wide ad blocking via a DNS sinkhole
Requirements
Badges are attached to each value. An estimate is never presented as an official project requirement.
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 512MB Official | 1GB Estimated |
| CPU | 1 Estimated | 1 Estimated |
| Disk | 2GB Official | Not stated Not stated |
Disk figures describe the application footprint recorded in the dataset. Personal media, documents, backups and other user data can require substantially more storage.
RunOnVPS sizing suggestion
1 GB RAM tier
This is our sizing suggestion, derived from Pi-hole’s recommended RAM of 1GB. It is not an official requirement and it does not guarantee that every workload, plug-in set or media library will fit comfortably.
Affiliate link placeholder — no provider selectedThis placeholder intentionally has no URL or affiliate ID in the Day 2 build.
Deployment
Docker support: Yes
GPU: Not required
Check the source notes below before assuming a GPU, transcoding workload or machine-learning feature is included in the baseline deployment.
Commercial alternative
NextDNS
Pi-hole is catalogued here as a self-hosted alternative to NextDNS. Feature parity varies, so compare your required workflow before migrating.
Source check
Stars checked 2026-10-24; license is EUPL-1.2 per the repo LICENSE file (GitHub repo page shows License: Other / NOASSERTION). Official Prerequisites page: 'Min. 2GB free space, 4GB recommended' and '512MB RAM' — min_ram/min_disk are official; 官方未标明 CPU(文档仅称 does not require much processing power),CPU 与 rec 配置为估算. Docker supported via the official Pi-hole Docker repo (README Method 3).
Data source: https://docs.pi-hole.net/main/prerequisites/
Project repository: https://github.com/pi-hole/pi-hole
Keep comparing