About This Guide: This tutorial shows you how to install OpenClaw on a Synology or QNAP NAS device using Docker, so your personal AI agent runs 24/7 without needing a PC or Mac to stay on. Covers DSM 7.x, QTS 5.x, Docker Compose setup, networking, and optimization. Estimated setup time: 30–45 minutes.
OpenClaw has rapidly become the go-to personal AI agent platform in 2026 — an open-source tool that runs entirely on hardware you own, giving you a 24/7 autonomous assistant that integrates with WhatsApp, Telegram, Discord, iMessage, and Slack. Most users start by running OpenClaw on their laptop or desktop, but that means the moment you close the lid, your AI goes offline.
The smarter solution: run OpenClaw on a Network Attached Storage (NAS) device. Synology and QNAP NAS boxes are purpose-built to run 24/7, consuming only 10–30W of power compared to a Mac mini's 30–60W or a PC's 80–200W. They already support Docker natively, meaning you can containerize your OpenClaw instance and have your personal AI assistant online around the clock — responding to messages, executing scheduled tasks, and managing automations — even while you sleep.
In this guide, we'll walk through the complete setup on both Synology DSM 7.x and QNAP QTS 5.x, covering Docker installation, container configuration, port forwarding, persistent storage, and the critical networking optimizations that keep your agent fast and responsive globally.
Why a NAS Is Perfect for OpenClaw
NAS devices are designed to run continuously. Your OpenClaw agent stays responsive at 3 AM, on weekends, and while you travel.
A NAS running OpenClaw uses about 15–25W — roughly the same as a light bulb. Run it all year for under $20 in electricity.
Both Synology (Container Manager) and QNAP (Container Station) run Docker natively — perfect for OpenClaw's Node.js environment.
Important: NAS Network Requirements
OpenClaw on a NAS makes constant outbound HTTPS calls to AI APIs (Anthropic Claude, OpenAI) and messaging platforms. From a home ISP, these requests can be throttled, geo-blocked, or rate-limited — especially if your ISP detects unusual traffic patterns to foreign API endpoints.
Running VPN07 on your router (or within the NAS Docker stack) routes all OpenClaw traffic through VPN07's 1000Mbps global network, bypassing throttling and ensuring consistent low-latency API responses 24/7.
Prerequisites & Compatible NAS Models
Synology Compatible Models
- Recommended: DS923+, DS723+, DS423+, DS224+
- Also works: Any x86-64 Synology running DSM 7.0+
- RAM: 4GB minimum, 8GB recommended
- Not supported: ARM-only models (DS120j, DS220j)
QNAP Compatible Models
- Recommended: TS-464, TS-264, TS-462, TS-262
- Also works: Any QTS 5.0+ Intel/AMD model with 4GB+ RAM
- Container Station: Version 3.0+ required
- Not supported: 32-bit ARM processors
Before You Start — Checklist
Part 1: Synology NAS Setup (DSM 7.x)
Synology's Container Manager (formerly Docker app) provides the easiest NAS Docker experience. Starting from DSM 7.2, it supports Docker Compose projects directly from the GUI.
1 Install Container Manager
- Open Package Center on your Synology DSM
- Search for "Container Manager" and install it
- Wait for installation to complete, then open Container Manager
- Accept the Docker Hub Terms of Service if prompted
2 Create Storage Folder via File Station
Create a dedicated folder for OpenClaw data. In File Station, create:
/volume1/docker/openclaw/ ← main folder
/volume1/docker/openclaw/data/ ← agent memory & config
/volume1/docker/openclaw/logs/ ← log files
Replace volume1 with your actual volume name if different.
3 Create docker-compose.yml via SSH
Enable SSH in DSM Control Panel → Terminal & SNMP, then connect and create the compose file:
ssh admin@YOUR-NAS-IP -p 22
cd /volume1/docker/openclaw
cat > docker-compose.yml << 'EOF'
version: "3.8"
services:
openclaw:
image: node:22-alpine
container_name: openclaw-agent
restart: unless-stopped
working_dir: /app
volumes:
- ./data:/app/data
- ./logs:/app/logs
environment:
- NODE_ENV=production
- OPENCLAW_STATE_DIR=/app/data
command: >
sh -c "npm install -g openclaw &&
openclaw gateway --port 18789"
ports:
- "18789:18789"
networks:
- openclaw-net
networks:
openclaw-net:
driver: bridge
EOF
4 Launch via Container Manager GUI
- Open Container Manager → click Project tab
- Click Create → name it
openclaw - Select Use an existing docker-compose.yml path
- Browse to
/volume1/docker/openclaw - Click Next → Done to start the project
- Visit
http://NAS-IP:18789to access the OpenClaw dashboard
Part 2: QNAP NAS Setup (QTS 5.x)
QNAP uses Container Station 3 for Docker management. The process is similar to Synology but with QNAP-specific UI steps.
1 Install Container Station 3
Open App Center in QTS, search for "Container Station", and install version 3.x. If you have an older version, update it first. Container Station 3 brings significant performance improvements and full Docker Compose support.
2 SSH Setup and Docker Compose
Enable SSH in QTS Control Panel → Network & File Services → Telnet/SSH. Then:
ssh admin@YOUR-QNAP-IP
mkdir -p /share/Container/openclaw/data
mkdir -p /share/Container/openclaw/logs
cd /share/Container/openclaw
# Create compose file (same as Synology example above)
# Then start it:
docker-compose up -d
# Check status
docker-compose ps
docker-compose logs -f openclaw
3 Configure via Container Station GUI
Open Container Station → Applications tab → Create. Paste or import your docker-compose.yml. QNAP's GUI shows resource usage per container, letting you monitor OpenClaw's CPU and RAM consumption in real time.
Run OpenClaw Onboarding on Your NAS
Once the container is running, you need to run the OpenClaw onboarding wizard to configure your AI provider, messaging channel, and agent persona. Connect via SSH into the running container:
# Enter the running container
docker exec -it openclaw-agent sh
# Install openclaw globally (if not already done by compose command)
npm install -g openclaw
# Run the onboarding wizard
openclaw onboard --install-daemon
# The wizard will ask:
# 1. Your AI provider (Claude, GPT-4, Gemini)
# 2. Your API key
# 3. Your messaging platform (Telegram recommended for NAS)
# 4. Bot token for Telegram
# 5. Memory and persona preferences
# After setup, start the gateway:
openclaw gateway --port 18789
Pro Tip: Telegram is Best for NAS
For NAS deployments, Telegram Bot is the most reliable messaging backend. WhatsApp requires phone pairing (needs a browser session), while Telegram bots work purely via API tokens — perfect for headless servers. Set up a Telegram bot via @BotFather and paste the token during onboarding.
Remote Access & Port Forwarding
For your OpenClaw agent to receive webhooks from Telegram, Discord, and other platforms, the NAS must be reachable from the internet. There are two approaches:
Method A: Reverse Tunnel (Recommended)
Use a reverse tunnel service like Cloudflare Tunnel (free) or ngrok to expose port 18789 without opening firewall ports:
cloudflared tunnel --url http://localhost:18789
Method B: Router Port Forwarding
Forward port 18789 from your router to the NAS IP. Also set a static local IP for your NAS to prevent reassignment after reboots:
Router → Port Forwarding → Add rule: External 18789 → Internal NAS-IP:18789
Performance Optimization for NAS Deployments
Memory Limits
Set container memory limits in your docker-compose.yml to prevent OpenClaw from consuming all NAS RAM (which would starve other services like Plex, Nextcloud):
services:
openclaw:
mem_limit: 1g
memswap_limit: 1g
Auto-Restart & Health Checks
Add a health check so Docker restarts OpenClaw if the gateway becomes unresponsive:
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:18789/health"]
interval: 30s
timeout: 10s
retries: 3
start_period: 40s
Network: Use VPN07 for Global API Access
Home ISPs often throttle or geo-block API traffic to Anthropic, OpenAI, and messaging platforms. Add VPN07 as an environment variable or configure it at the router level to route all NAS traffic through VPN07's 1000Mbps global network — ensuring your agent gets sub-200ms response times from AI APIs globally.
Troubleshooting Common NAS Issues
Container exits immediately after start
Cause: npm install fails due to network issues or the node image has no internet access.
Fix: Check container logs: docker logs openclaw-agent. Ensure NAS has DNS configured and internet access. Try docker pull node:22-alpine first.
Port 18789 not accessible from outside network
Cause: Router firewall or NAS firewall blocking the port.
Fix: Check Synology's Control Panel → Security → Firewall rules. Also check your router's port forwarding settings. Use Cloudflare Tunnel as a reliable alternative that requires no open ports.
High CPU usage or thermal throttling
Cause: OpenClaw processing large AI responses or many concurrent tasks. Fix: Set CPU limits in docker-compose (cpus: '0.5'), reduce agent heartbeat frequency, and ensure NAS ventilation is adequate. Consider scheduling heavy tasks during off-peak hours with OpenClaw's cron skill.
NAS vs. Other Hosting Options: Honest Comparison
| Option | 24/7 Uptime | Power Cost/yr | Hardware Cost | Difficulty |
|---|---|---|---|---|
| NAS (Synology/QNAP) | Yes | ~$15 | Already owned | Medium |
| Mac mini M4 | Yes | ~$35 | $599+ | Easy |
| VPS (cloud) | Yes | $60–240/yr | Ongoing | Medium |
| Laptop/Desktop | No | $50–200/yr | Already owned | Easy |
💡 Our Verdict
If you already own a compatible NAS, it's the most cost-effective way to run OpenClaw 24/7. You're reusing existing hardware that's already powered on for file storage, backup, and media serving. The only real downside is slightly more complex initial setup compared to a Mac mini.
Keep Your NAS OpenClaw Always-On with VPN07
The only VPN built for 24/7 AI agent workloads
A NAS-hosted OpenClaw agent is only as good as its network connection. VPN07 delivers 1000Mbps dedicated bandwidth across servers in 70+ countries, ensuring your agent reaches Anthropic, OpenAI, Telegram, and Discord APIs with zero throttling — 24 hours a day, 7 days a week. With 10 years of proven reliability and a 30-day money-back guarantee, VPN07 is the infrastructure choice for serious AI automation enthusiasts. At just $1.5/month, it's a no-brainer upgrade for any NAS OpenClaw setup.