Measured on a real homelab
On our homelab it uses about 63 MB of RAM on a normal hour, 95 MB in busy hours, and peaked at 122 MB over the last 30 days (private instance, low traffic).
The project publishes no hardware requirements.
Sources
SearXNG publishes no official hardware requirements. In the resource calculator we use 256 MB minimum and 512 MB recommended, derived from this measurement of a low-traffic private instance (process memory peaked at 122 MB including Valkey; 161 MB counting disk cache). A public instance with real traffic needs more.
Our rule of thumb: plan for the highest process memory recorded plus 25% headroom: 192 MB. Our workload is small — scale it with the factors above before buying hardware.
Combine it with other apps in the resource calculator →
Build it: Rent a VPS · Buy a mini-PC
Memory per container from Netdata on the same server, summed across the whole stack (app, database and cache) hour by hour. The main figures are the processes' own memory (anonymous memory: heap, stacks). The docker stats figure is higher because it also counts active disk cache — which Linux gives back when it needs it — and shared memory such as PostgreSQL's shared buffers. Hours where the main container had no data are left out, not counted as zero. Re-measured with a script, not by hand.