Measured on a real homelab
On our homelab it uses about 117 MB of RAM on a normal hour, 223 MB in busy hours, and peaked at 334 MB over the last 30 days (managing 2 servers and ~35 apps and services).
Minimum: 2 cores, 2 GB RAM, 10 GB free disk. It can technically start with 1 core and 512 MB, which is not recommended.
Sources
Official minimum: 2 cores, 2 GB RAM and 10 GB of free disk (it can technically start with 1 core and 512 MB, which the docs advise against). That is for Coolify itself: every app you deploy adds its own RAM on top.
Our rule of thumb: plan for the highest process memory recorded plus 25% headroom: 448 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.