HARDWARE PLANNING

What hardware does n8n need?

There is no useful single hardware number for n8n because the workload lives inside your workflows. Moving a few JSON records once an hour is tiny; handling files, browser jobs, code and many simultaneous executions is not.

CPU

Most light workflows spend much of their time waiting for APIs and network responses, so raw CPU speed is rarely the first bottleneck. CPU demand rises when workflows transform large datasets, run code or perform compute-heavy processing locally.

RAM

Memory demand depends on execution concurrency and how much data each workflow keeps in memory. A small personal instance can run on modest hardware, while high-volume or parallel workloads need more headroom. Monitor actual usage before scaling by guesswork.

Storage

Use persistent storage for configuration and the database. Execution history can grow, especially if you retain successful workflow data for long periods. Set retention deliberately rather than allowing logs and execution records to grow forever.

Database

Small self-hosted deployments can use the default database approach supported by n8n, while larger or production-oriented setups commonly use PostgreSQL. Scaling across multiple workers introduces additional infrastructure and operational complexity.

Mini PC, VPS or NAS?

A small x86 mini PC or VPS is a straightforward home for personal automation. A NAS can also work if its container environment is well supported. Choose the platform you can update and back up confidently rather than the one with the most impressive specifications.

For a first project, follow the small automation server guide.