← Writing
July 22, 2026·4 min read

What It Would Take to Run Your Own AI

NVIDIA's DGX Spark puts real inference compute on a desk for the first time. The interesting question isn't the hardware — it's what you'd need to build around it to make it useful.

Every AI feature I've shipped this year has the same dependency: someone else's API, someone else's rate limits, someone else's pricing page. That's fine for most products. It stops being fine the moment your customer cares where their data goes, or your margins start bleeding out on token costs at scale. Neither of those is hypothetical for the people I build for — CNC shops with proprietary cut files, engineering firms with unreleased designs, anyone whose "data" is actually their competitive advantage.

NVIDIA's DGX Spark is the first hardware that makes "just run it yourself" a real option instead of a rack-in-a-closet fantasy. It's a desktop box — not a server room — with a Grace Blackwell chip and roughly 128GB of unified memory, built specifically to run models too large for a consumer GPU without needing a data center behind it. For the first time, a small studio can own enough inference compute to matter, for a few thousand dollars instead of a cloud contract.

Owning the compute is only half the problem, though. A DGX Spark sitting on a desk is a local inference server with no public IP, no redundancy, and no obvious way to serve requests to anything outside the building it's in. That's where it stops being a hardware question and starts being an infrastructure one.

The problem local AI hardware doesn't solve on its own

Cloud AI wins on three things that have nothing to do with model quality: it's reachable from anywhere, it doesn't go down when one machine does, and it doesn't require you to think about networking. Buy a DGX Spark and you've solved cost and data residency — you haven't solved any of that. If the box reboots, your product is down. If you want it to serve a SaaS product with real users, you now need to expose a machine on your home or office network to the internet safely, which is a problem most builders correctly avoid.

This is where I think Cloudflare is the actual missing half of the local-AI story, not the DGX Spark alone. Cloudflare Tunnel solves the "expose a local machine without a public IP or port forwarding" problem cleanly — the DGX Spark never accepts an inbound connection, it dials out. Put Access or Zero Trust in front of that tunnel and you have an authenticated, encrypted path from Cloudflare's edge straight to hardware sitting under a desk. Cache what's cacheable at the edge, route what isn't straight through, and you've turned a single local machine into something that behaves like a real backend without ever renting a server.

Where this actually breaks

I don't think this is a solved pattern yet, and the honest gaps are worth naming. One box has no failover — if it's down, it's down, and Cloudflare routing to it doesn't change that. Model size is still bounded by what fits in 128GB of unified memory, which is generous for a desk but nowhere near a hyperscale cluster running the largest frontier models. And running your own inference infrastructure, even a small one, means you've taken on the operational burden a cloud API was quietly handling for you — updates, monitoring, the 2am "why is it not responding" problem.

The interesting next step is what happens past one box. A few DGX Sparks behind Cloudflare Load Balancing starts to look like a genuinely small distributed inference fleet — one that a solo founder or small studio could actually operate, tuned for exactly the workload it needs to serve instead of general-purpose cloud capacity. That's a fundamentally different economic model than API billing: fixed hardware cost, no per-token ceiling, data that never has to leave the building.

I haven't built this yet. But it's the first time the pieces — real local compute, and edge infrastructure that can safely expose it — have both existed at a price a small studio can actually afford. That combination is worth taking seriously before someone else builds the obvious version of it.