n8n
Workflow automation that connects APIs and moves data between services.
Memory is set by how much data a single execution holds, not by the number of workflows.
Planning figures used by the calculators: RAM 1 GB (our estimate), CPU 1 cores (our estimate), storage 5 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: n8n memory sizing documentation, retrieved 2026-09-08, archived as document 36 on the sources page.
Add n8n to a stack or read how we label a number.
| property | value | basis | evidence | document |
|---|---|---|---|---|
| cpu plan cores | 1 cores | our estimate | Our reasoning: No published figure. One core suits scheduled household automations without queue mode. | No document, our reasoning only |
| memory behaviour | Memory scales with the data in one execution | vendor documented | Quoted from the archived document: n8n doesn't restrict the amount of data each node can fetch and process. While this gives you freedom, it can lead to errors when workflow executions require more memory than available. | Document 36, retrieved 2026-09-08 |
| ram plan gb | 1 GB | our estimate | Our reasoning: No published figure. 1 GB covers small workflows; the documentation is explicit that a single large execution can exhaust whatever you give it. | No document, our reasoning only |
| storage plan gb | 5 GB | our estimate | Our reasoning: No published figure. Application plus execution history, which you can prune. | No document, our reasoning only |