2026-06-24 · 3 MIN READ
Local-first by default
Running everything on hardware I own is not frugality. It is a design choice that changes what I am willing to build.

The default way to run AI is to rent it — pay per token, ship your data to someone else's machine, and watch the meter. I do almost none of it that way. The AI swarm thinks on local models. The image-to-video pipeline renders on local GPUs. The audio generator and the app store live on the same network. None of it is hosted, metered, or routed through someone else's account. That is a deliberate posture, not an accident of being cheap.
The first thing owning the hardware buys is cost that does not scale with use. A swarm that runs on local models has no per-token bill, so leaving a fleet of agents working overnight costs electricity, not a four-figure invoice. A diffusion pipeline on cards I already own costs nothing per render. The meter is the thing that makes cloud experimentation feel expensive, and removing it removes the flinch before every run.
The second thing it buys is privacy as a structural property rather than a promise. Code, prompts, conversations, and generated media never leave the house, so there is no data-handling policy to trust and no third party to breach. The boundary is physical: the data is on a disk I can see.
The third thing — the one I did not predict — is that free iteration changes what gets attempted at all. When putting a build on my phone costs one command through a private store, and trying a model costs no money, the threshold for 'is this worth a shot' collapses. A Balatro for smart glasses is a bad idea by every cloud-cost measure and got built anyway, because the cost to find out was a command instead of a bill. Cheap, owned infrastructure does not just make the work faster. It widens the set of things worth making.
- 01
- 02
- 03Smereski Apps — project page
The private store that makes putting a build on the phone one command.
/projects/smereski-apps
- 04