Your Old MacBook Is a $2,000 VPS You Already Own
Why I run OpenClaw on a 2015 MacBook instead of renting someone else's computer
The VPS companies want you to believe your drawer full of old hardware is worthless.
I run OpenClaw - a full AI gateway with computer control - on an old 2015 MacBook Pro.
It cost me zero dollars.
It handles my API keys.
It never leaves my physical control.
And it’s faster to set up than waiting for a DigitalOcean droplet to provision.
The $15/month lie
Every OpenClaw tutorial starts the same way: “Spin up a VPS.”
Rent a box in someone else’s data center.
Give them your credit card.
Trust their security.
Pay monthly forever.
All of these tutorials leave out a key fact.
OpenClaw only needs 4 GB of RAM and a CPU from the last decade.
That’s it.
Your 2014 MacBook Air qualifies.
So does the Mac Mini gathering dust behind your monitor.
BitLaunch calls the Mac Mini M4 “the go-to device for Claw”—a $600 investment for “powerful performance and a small footprint.”
True.
But you know what else has a small footprint?
The laptop you stopped using when you upgraded three years ago.
Why I don’t trust hosted solutions with API keys
I’ve watched too many startups pivot.
The cute little AI tool you installed becomes an “enterprise platform.”
Your API keys - sitting in their database - are now an asset in their eventual acquisition.
OpenClaw runs on your machine.
Your Claude key, your OpenAI credentials, your Anthropic tokens - they live in a config file you control.
No third-party dashboard.
No “we encrypt everything, trust us” blog posts.
Physical possession.
When someone pitches me a hosted AI gateway, I ask one question: “If your company disappears tomorrow, do I still have access to my integrations?”
The answer is always no.
The actual hardware requirements
Node.js 22 or higher.
That’s the only hard requirement.
I tested this on three machines: a 2015 MacBook Pro (8 GB RAM), a 2017 MacBook Air (4 GB RAM), and a 2020 Mac Mini (16 GB RAM).
All three ran OpenClaw without breaking a sweat.
The Air was slower to start tasks, but once running, the performance difference was invisible.
Samuel Gregory proved you don’t even need dedicated hardware.
He runs OpenClaw in a virtual macOS instance on his main Mac using Loom.
The tradeoff: some CPU overhead and hard drive space.
The benefit: zero additional devices.
I went the opposite direction.
I wanted physical separation—my work machine stays clean.
My old MacBook sits on a shelf, headless, doing one job.
The 20-minute deployment
Open Terminal on your mac, its under Apps > Utilities
Install Homebrew if it’s not already there by copying and pasting this into your terminal:
/bin/bash -c “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)”Copy and paste this command:
npm install -g openclaw@latestThen copy and paste this one:
openclaw onboard --install-daemonThat’s the whole process.
OpenClaw will walk you through the entire install in the terminal.
The official docs overcomplicate it.
You don’t need Docker unless you’re running Windows.
You don’t need a fancy IDE.
You don’t need to understand the entire codebase.
You need a terminal and 20 minutes.
I keep a GitHub private repo with my exact config (minus the actual API keys).
When I need to redeploy or move machines, I clone it, drop in the keys from my password manager, and run the start command.
Total time: 90 seconds.
Tailscale for remote access
Your old MacBook is now running OpenClaw.
Great.
Now you’re on a coffee shop Wi-Fi and need to access it.
Install Tailscale on both machines - your OpenClaw box and your work laptop.
It creates a private network between your devices.
No port forwarding.
No exposing anything to the public internet.
No VPN configuration files.
I access my OpenClaw instance from three devices.
My main MacBook, my Mac Studio, and my iPhone.
Tailscale handles the routing.
The connection is peer-to-peer when possible, relay server when not.
Either way, it’s encrypted end-to-end.
The network looks like this: 100.x.x.x addresses visible only to your devices.
You SSH into your old MacBook at its Tailscale IP.
You’re in.
Run commands.
Check logs.
Restart services.
The backup strategy nobody talks about
GitHub isn’t just for code.
I use it to version control my entire OpenClaw setup.
Private repo.
Three folders:
config (sanitized—no actual keys)
scripts (startup and maintenance)
docs (my notes on quirks and fixes).
Every time I change something, I commit it.
Every night, a cron job on the MacBook commits the logs (last 100 lines only, rotated).
If the MacBook dies - hard drive failure, coffee spill, theft - I lose nothing.
I grab another old laptop, install Node, clone the repo, add keys, start the service.
Downtime: 30 minutes including the OS updates.
This is the part hosted services charge you for - ”automated backups included!”
They’re selling you git commits.
The security model
Physical access matters.
My OpenClaw machine sits in my home office.
To compromise it, you need to be in my house.
That’s a much higher bar than “guess my VPS password” or “find an exploit in someone’s web dashboard.”
Tailscale adds a second layer: access requires a device I’ve explicitly authorized.
Steal my laptop?
Still can’t get to OpenClaw without my Tailscale credentials.
And those require 2FA.
The third layer is the GitHub backup.
Even if someone gets physical access to the MacBook, they get a machine with no saved credentials—everything pulls from environment variables I set manually on boot.
The repo they might find?
Sanitized configs.
Useless without the keys.
Compare that to a VPS where your credentials live in a web portal protected by a password and maybe SMS 2FA.
The attack surface is huge.
What this actually costs
Old MacBook from your drawer: $0.
If you don’t have one, eBay has 2015 MacBook Pros for $200-300.
One-time cost.
Electricity for a laptop idling 24/7: roughly $2-3/month.
A Mac Mini M4 would be more efficient, but we’re talking about a dollar difference.
Tailscale: free for personal use (up to 100 devices).
GitHub private repo: free for individuals.
Total monthly cost: $3.
Total setup time: one evening.
Total vendor dependencies: zero.
When you actually need a VPS
If you’re running a public service, get a VPS.
If you need 99.99% uptime with automatic failover, get a VPS.
If your internet goes down and that’s a business-ending problem, get a VPS.
But for personal AI workflows?
For experiments and side projects?
For anything where “it’s down for two hours while I’m traveling” is acceptable?
An old MacBook in your home office is better than a rented box in AWS.
You own the hardware.
You control the keys.
You pay once instead of monthly.
You can unplug it and look at it when something goes wrong.
The real reason tutorials push VPS
Affiliate links.
Every “spin up a DigitalOcean droplet” tutorial includes a referral code.
You click it, you sign up, the author gets paid.
There’s nothing wrong with affiliate marketing, but it explains why every guide assumes you need cloud hosting.
Nobody makes money when you dig an old laptop out of a drawer.
I’m not saying VPS hosting is evil.
I’m saying it’s optional for most OpenClaw deployments.
The barrier between you and a working setup is not infrastructure.
It’s permission to use what you already have.
Start tonight
Find an old Mac.
Install Node 22.
Install OpenClaw.
Run it.
If it works, you’re done.
If it doesn’t, you’ve lost an hour.
Keep your API keys local.
Keep your hardware physical.
Keep your monthly costs at zero.
The fancy deployment guides with Docker Compose and load balancers will still be there if you need them later.
But most of you won’t.
What old hardware are you going to resurrect?
Reply and tell me what you’re running OpenClaw on - I’m collecting a list of confirmed working machines from 2012 and earlier.