Mac Mini home server for OpenClaw

A Mac Mini (or any always-on Mac) is a common way to host OpenClaw: low idle power, quiet, and separate from the laptop you carry. You get local disk for skills and memory, easy file drops, and optional iMessage on the same box. This guide covers hardware choices, keeping the Gateway alive, security, and when a VPS is still the better fit.

Config keys and menu bar behavior change between releases—confirm details in official docs and macOS platform guide.

• Always on — Telegram/WhatsApp/cron keep working when your MacBook is closed.
• Isolation — Agent workspace and keys stay off your daily driver (security basics).
• Local workflows — Airdrop files, local paths, browser tools on the same LAN (deployment overview).
• Power — Apple Silicon idles at a few watts; many users report roughly $2–8/month in electricity vs $5–20+/month for a small VPS (plus API costs either way—see cost guide).

Choose a VPS instead if you need public uptime without home IP quirks, you cannot leave hardware running, or your ISP blocks inbound ports. Remote access over Tailscale often bridges “home Gateway, phone elsewhere.”

Use a wired Ethernet connection if possible—Wi‑Fi sleep and roaming cause more “bot went quiet” reports than CPU limits.

1. Dedicate the machine (or a separate macOS user) for the agent—avoid mixing personal iCloud Keychain with test skills.
2. Follow installation and macOS setup (Node, openclaw onboard, provider auth).
3. Connect your first channel—Telegram quickstart is fastest; WhatsApp quickstart uses QR login.
4. Run openclaw security audit --deep before opening DMs widely.

macOS sleep pauses Node and drops some channel sessions. For a home server:

• System Settings → Energy — Disable sleep on power adapter; enable “Wake for network access” if available.
• Menu bar app — The macOS OpenClaw app can manage Gateway lifecycle; see macOS guide.
• LaunchAgent / daemon — Run Gateway under launchd or your process manager so it restarts on crash (patterns in official gateway docs).
• Headless hint — Plug in HDMI dummy or use amphetamine-style “prevent sleep” only on the dedicated host—not on your laptop.

After reboots (macOS updates), verify channels with openclaw doctor and check logs (observability).

Do not port-forward the Gateway to the public internet without token auth and TLS. Prefer:

• Tailscale or VPN — Remote access guide
• SSH tunnel — For occasional Control UI use from a laptop
• Bind Gateway to localhost — Default-safe; only the tunnel/VPN exposes it

• DM pairing on every channel (pairing guide).
• Separate Apple ID / user account optional but helpful for blast radius.
• Automatic macOS updates—schedule them; expect one manual openclaw doctor after major upgrades.
• Time Machine or backup of ~/.openclaw/—treat backups as sensitive (tokens inside).
• Review skills before install (ClawHub safe install).