OpenClaw Hardware Requirements: Real Minimum Specs (2026)

OpenClaw's official minimum hardware requirements are 1 GB RAM, 1 CPU core, 500 MB of free disk, and a 64-bit OS, with Node 22.19 or newer; the official FAQ adds that the Gateway "is lightweight (a small VPS or Raspberry Pi-class box is fine; 4 GB RAM is plenty)." For a comfortable always-on setup we recommend 2 vCPU, 4 GB RAM, and 40 GB of SSD storage for one agent, and 4 vCPU with 8 GB RAM if you run multiple agents or heavy browser automation. No GPU is required.

Minimum and recommended OpenClaw specs

OpenClaw is a Node.js gateway and agent runtime, not a local-LLM workstation app, so its hardware needs are closer to a small web service than a gaming PC. The minimum column below is quoted from the official Raspberry Pi install guide (the only official page with hard numbers); the recommended columns are our inference from the official FAQ plus real GitHub issue reports, and we label them as such.

One correction worth stating plainly: some third-party hardware guides claim OpenClaw needs 16 GB of RAM as a minimum. The official documentation contradicts that. Unless you are also running local models on the same box, 16 GB is comfortable overkill, not a requirement.

What the official OpenClaw docs actually say

The official OpenClaw documentation defines requirements in terms of runtime and OS rather than a big spec matrix. Three pages matter:

• The install guide: Node 24 recommended (the installer script handles it), on macOS, Linux, or Windows. Windows users can use the native Windows Hub app, the PowerShell CLI installer, or a WSL2 Gateway.
• The Node page: "OpenClaw requires Node 22.19 or newer," with Node 24 as "the default and recommended runtime."
• The official FAQ: the Gateway "runs on macOS/Linux (Windows via WSL2) and is lightweight (a small VPS or Raspberry Pi-class box is fine; 4 GB RAM is plenty)."

The Raspberry Pi guide is where the hard floor comes from: "Minimum: 1 GB RAM, 1 core, 500 MB free disk, 64-bit OS" and "Recommended: 2 GB+ RAM, 16 GB+ SD card (or USB SSD), Ethernet." It also carries two warnings that matter for cheap-hardware plans: use a 64-bit OS (32-bit is explicitly ruled out), and "Do not run local LLMs on a Pi" because even small models are too slow there to be useful. OpenClaw itself calls cloud model APIs, which is exactly why the hardware bar stays low.

Real-world memory usage from the community

Real deployments show the Gateway using more memory over long sessions than the minimum specs suggest, which is why we recommend 4 GB as the practical floor for always-on use. Three verifiable GitHub reports as of July 2026:

• Issue #13758: a Gateway on a 4 GB AWS t3.medium reached 1.9 GB RSS and 69% CPU after 13 hours of uncompacted sessions.
• Issue #24689: a pathological case where Gateway memory peaked around 6 GB on an 8 GB VPS in under half an hour, with orphaned child processes after shutdown.
• Issue #41778: openclaw message send hitting JavaScript heap out-of-memory errors on 4 GB servers in specific versions.

The honest takeaway: 1 to 2 GB boxes work for light or experimental use, a normal single-agent Gateway idles far below 4 GB, and long-running or multi-agent setups benefit from 8 GB plus periodic restarts and session compaction. None of this requires exotic hardware; it requires headroom.

Decision table: match hardware to your use case

The right OpenClaw hardware depends on whether the agent runs occasionally on your desk or 24/7 in the cloud. Every row below traces to an official docs page or an official pricing page linked in this post.

VPS recommendations: Hostinger vs Hetzner vs DigitalOcean

A 4 GB VPS is the sweet spot for a 24/7 OpenClaw agent, and in July 2026 that costs between roughly $6 and $12 a month depending on provider and billing games. Prices below come from each provider's official pricing page, linked in the table.

Our take: Hostinger wins on setup speed (its OpenClaw VPS template deploys the Gateway in minutes; see our step-by-step Hostinger setup guide and plan comparison), Hetzner wins on raw price per GB if you are comfortable with DIY Linux administration, and DigitalOcean only makes sense if you already have credits or infrastructure there. Watch two pricing traps: Hostinger's headline prices are promotional first-term rates with higher renewals, and Hetzner lists prices excluding VAT. For the wider landscape, see OpenClaw deployment options compared.

Limitations and Tradeoffs

OpenClaw does not publish a single consolidated hardware matrix; the minimum figures here come from the Raspberry Pi guide and the FAQ, and the recommended tiers are our judgment call layered on official docs plus GitHub issue reports, not vendor benchmarks. Memory behavior also varies by version, session length, and installed skills, so treat 4 GB as a floor, not a guarantee. And if your plan includes running local LLMs on the same machine, none of these numbers apply; model hosting is a GPU-and-VRAM problem that dwarfs OpenClaw's own footprint.

Related Guides

• OpenClaw Install Guide
• Best OpenClaw VPS in 2026
• Best Hostinger VPS Plan for OpenClaw
• OpenClaw Deployment Options Compared

Sources

• OpenClaw Raspberry Pi install guide (official minimums)
• OpenClaw official FAQ
• OpenClaw install guide
• GitHub issue #13758 (Gateway memory over long sessions)
• Hostinger VPS pricing (summer sale live now, up to 70% off through this link)
• Hetzner price adjustment (June 15, 2026)
• DigitalOcean droplet pricing