I own two laptops. A 2020 Intel MacBook Air, 8GB RAM, no unified memory, gifted by my sister. And a Windows machine: Intel i5 11th Gen, integrated graphics, 16GB RAM.
A tweet made the rounds recently arguing that local AI makes no financial sense. Add up the hardware, the power bill, the hours spent fiddling with quantization settings, and you get a number. Compare that number to years of a frontier lab subscription. The subscription wins, easily. The tweet lists three reasons anyone still bothers running models locally: it's fun, it's cool, or you hate the labs.
I build offline tools for a living, from Port Harcourt. None of those three are the real reason. My own two laptops make the actual case better than the math does.
The Mac can't do this. The Dell already did.
The Mac is close to useless for local model work. No Apple Silicon means no unified memory advantage. No fan means it throttles under sustained load. 8GB doesn't fit anything past a tiny quantized model. It's a fine machine for writing and light coding. It is not a machine you run inference on.
The Windows laptop is the one that's actually done real work. I built StacksNG, an offline AI coding assistant for the African developer stack (Paystack, Flutterwave, Monnify, Termii), entirely on that Dell, for the Africa Deep Tech Challenge 2026. No discrete GPU. Just Ollama, a 7B coding model, and a RAG pipeline running on integrated graphics. It works because I built it for the hardware constraints instead of around them.
That's the split nobody in the "just pay for the subscription" argument accounts for. The machine you already have decides a lot of what local AI costs you. Sometimes it's free, because you own hardware that can already do it. Sometimes it's a wall.
Why I'm renting a GPU before I buy anything
I'm looking at upgrading the Mac, likely to an M4 Pro or a Mac mini M4 with 24GB or more of unified memory, enough to run a 27B-class model comfortably. I'm not buying yet. I'm renting GPU time first.
I don't know exactly what I need until I've actually run something heavier. An RTX 4090 instance on RunPod or Vast.ai runs $0.35-0.55/hr. A few hours of testing costs less than a plate of jollof rice and tells me more about real RAM and throughput needs than any spec sheet. Whatever hardware I buy will be based on that data, not a guess.
Power in Port Harcourt is not something you build a plan around and forget. A local setup that assumes 24/7 uptime is a bet on infrastructure that doesn't always hold. And that's before you get to the part I wrote about separately: an API call from here is a physical trip across submarine cable to a data center that isn't yours, and the same prompt can come back instant one day and sluggish the next depending on load you can't see from Port Harcourt. Renting for the experimentation phase means I'm not sinking money into hardware before I know it's the right call.
If money were no object, an M5 Mac Studio Ultra would fix basically everything in this post. I could kill for one. But it's a wish list, not a plan. Renting is what you do while it stays one.
The honest middle ground
Cloud models aren't wrong. Frontier intelligence at scale is genuinely hard to replicate locally. Keep frontier models for tasks that actually need frontier reasoning. Push high-volume, low-stakes, or offline-required work to whatever you can run locally, on hardware you already have or hardware you've actually tested against your real workload.
The question was never local or cloud. It's which tasks actually need the thing you're paying a premium for, and which ones don't. For a lot of the world building software, that answer depends on things a hardware price comparison never touches: what infrastructure you can actually count on, and what happens to your work when the connection or the power doesn't.
Top comments (4)
The thing is, you rent cloud, but you still need your interface. A laptop running an IDE, using a cloud model, still uses power. The real question is the delta, how much do you save per hour, on average, over a month, vs running local inference. But in all honesty, the conversation goes out the window when you consider Qoder's Lite model is pretty damn impressive and at $20 a month for a sub, you get 2000 credits (for eg. qwen, minimax, kimi, etc.) and access to Lite, for free... And I've pushed millions of LOC through it, I dont even wanna know how many tokens it ran through, all I know is it was likely over 30m+, especially cuz I ran multi-agents and have each agent spawn sub-agents, across 2 PCs and 2 laptops at once... At any given time, you'll see atleast 16+ agents running at once... You cant get that in hardware for $20 a month, nor can you find that anywhere else on cloud?
You're right about the delta. My laptop still draws power, even with cloud inference. I didn't run that math in the piece.
Qoder's price is impressive. $20 a month for that much throughput beats anything I could build locally.
My real point was different. It's about the days the network or the power fails, not the price per hour. Cloud wins on cost almost every time. It doesn't help when the connection drops mid-task. That's the gap local fills for me.
There's also the model choice itself. Some local models skip the usual guardrails. No cloud subscription gives you that, no matter the price.
give qoder's a try, it's pretty solid for stepping over guardrails, I mean I had it apply for jobs for me, using resume helper to generate the CV, it browsed the web to find jobs and while it blocked the actual submission on my behalf on principle, it's confirmation and non-blocking, so dunno bout your exact use cases, but for me, I found that anything that blocked it can be overridden.
True on the power cut, but how long does a laptop's battery last you running local inference? Accounting for battery life degradation, the total downtime is closer, especially when you compare vs having a fallback network, like a LTE router?
Fair question on battery. Sustained local inference drains a laptop fast, maybe an hour or two on battery, not a full day. Degradation makes that worse over time.
An LTE router as backup is real infrastructure though, not free. Data costs money here, and coverage still drops sometimes. It's a fallback, not a guarantee.
So the honest comparison isn't local vs cloud. It's which failure mode you'd rather plan around. I'd still rather own the failure mode than depend on someone else's uptime.