zacStep-by-step guide to running OpenClaw on a Raspberry Pi. Covers hardware requirements, Node.js installation on ARM, headless configuration, systemd...
Originally published on Remote OpenClaw.
Your Raspberry Pi is sitting on a shelf collecting dust. Meanwhile, you are paying cloud providers to host services that could run on a $50 computer the size of a credit card.
OpenClaw — the open-source AI agent framework with over 321,000 GitHub stars — runs natively on ARM processors. That means your Raspberry Pi can become a dedicated, always-on AI agent that handles your messaging, automates your tasks, and runs 24/7 for pennies a day in electricity.
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
Join the Community
Join 1k+ OpenClaw operators sharing deployment guides, security configs, and workflow automations.
Component
Minimum
Recommended
Board
Raspberry Pi 4 (4GB)
Raspberry Pi 5 (8GB)
Storage
32GB microSD (Class 10)
256GB+ NVMe SSD via USB
Power
Official 5V/3A USB-C
Official 5V/5A USB-C (Pi 5)
Cooling
Passive heatsink
Active fan or aluminum case
Network
Wi-Fi
Ethernet (more stable)
The Raspberry Pi 3 and earlier are not recommended — they lack 64-bit support and sufficient RAM.
OpenClaw needs a 64-bit operating system. Use the Raspberry Pi Imager to flash Raspberry Pi OS (64-bit) Lite. Pre-configure hostname, SSH, Wi-Fi, and credentials before flashing. After booting, SSH in and update everything:
sudo apt update && sudo apt upgrade -y
# Option A: NodeSource (recommended)
curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
sudo apt install -y nodejs
# Verify
node --version
You need v22.16.0 or higher. Version 24 is recommended.
curl -fsSL https://openclaw.ai/install.sh | bash
openclaw onboard --install-daemon
The installer detects your ARM architecture automatically. The --install-daemon flag sets up the Gateway as a background process.
Access the dashboard from another device on your network at http://openclaw-pi.local:18789 or via IP address. Set a static IP for reliable access:
sudo nmcli con mod "Wired connection 1" ipv4.addresses 192.168.1.50/24
sudo nmcli con mod "Wired connection 1" ipv4.method manual
sudo nmcli con up "Wired connection 1"
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
Create /etc/systemd/system/openclaw-gateway.service with Type=simple, Restart=always, and RestartSec=10. Enable and start:
sudo systemctl daemon-reload
sudo systemctl enable openclaw-gateway
sudo systemctl start openclaw-gateway
# View logs
journalctl -u openclaw-gateway -f
Metric
SD Card (Class 10)
USB 3.0 SSD
Sequential Read
~45 MB/s
~350 MB/s
Sequential Write
~20 MB/s
~300 MB/s
Lifespan
1-3 years (heavy use)
5-10 years
Increase swap to 2GB to prevent out-of-memory crashes during complex skill executions.
Set gpu_mem=16 in /boot/firmware/config.txt since you are running headless.
Add Environment=NODE_OPTIONS=--max-old-space-size=2048 to your systemd service and ensure swap is configured.
Always shut down gracefully with sudo shutdown -h now. Better yet, switch to an SSD.
Check CPU temperature with vcgencmd measure_temp — thermal throttling kills performance. Improve cooling if above 80 degrees Celsius.
The Raspberry Pi 5 with 8GB RAM is the best choice. The Pi 4 with 4GB works for lighter workloads. Avoid the Pi 3 and earlier.
No. The Pi Zero only has 512MB of RAM, which is far below the minimum needed.
The Pi does not do the heavy AI processing — that happens on the model provider's servers via API calls. The Pi just runs the Gateway, routes messages, executes skills, and manages state. Even a Pi 4 has plenty of power for that.
Yes, but only on a Pi with 8GB RAM. Two agents is realistic. Three or more will likely cause memory issues.
If using an SD card, sudden power loss can corrupt the filesystem. Use an SSD and consider a UPS HAT for clean shutdowns. OpenClaw itself handles unexpected shutdowns gracefully.
*Last updated: March 2026. Published by the Remote OpenClaw team at remoteopenclaw.com.*