Personal Infrastructure
For most of computing history, building serious infrastructure for an audience of one was economically irrational. You rented what you needed from platforms and accepted their terms, their ads, their shutdowns. AI collaboration broke that math. Now one person with taste and a thinking partner can build and run the whole stack: the server, the photo archive, the knowledge base, the publishing pipeline.
This thread documents the experiment of doing exactly that — moving a digital life off rented land, one system at a time, and what the work turns out to mean.
The Worldview
- Sacred Infrastructure: A Worldview — The philosophical anchor. Nothing is purely secular; every functional system channels something, and infrastructure built with care is a form of devotion.
- Infrastructure for One — The thesis essay. AI collaboration makes personal tooling economically rational for the first time, and that changes who gets to own their digital life.
The Stack
- A Server Called Mercury — Buying a physical machine and remembering that deployment UX is critical infrastructure. Heroku's ghost watches over everything.
- Self-Hosting Adventures — The ongoing practice: photo storage, databases, services, and the maintenance that turns out to be a hobby instead of a burden.
- This Site Now Runs on Responder — Full circle: the site you're reading, served by the framework I built in 2018.
- A Framework of One's Own — The framework under all of it. Five years frozen, revived in a day of AI collaboration, happily serving a userbase of one.
The Archives
- Sixty Thousand Images and Nowhere to Put Them — The problem statement. A life's photography stranded by dying platforms; a memory without a body.
- Building a Home for Twenty Thousand Photographs — The solution. A self-hosted archive with AI tagging; software built to see my own seeing.
- Obsidian Vaults & Claude Code — A second brain that thinks back. Documentation as survival infrastructure for a mind that can't always trust its own memory.
- Tending the Vault — The truer story: not a second brain, per se, but it can be. Why GTD apps fail the underlying problem, why the tending soothes anyway, and why the soothing is the load-bearing feature.
The pattern across all of it: the platforms were never going to take care of my things, because my things were never the point of the platforms. Building your own infrastructure is slower and lumpier and occasionally on fire, and every part of it belongs to you. For someone whose mind keeps unreliable archives, owning the external ones isn't a hobby. It's a load-bearing wall.
Related Themes
- The "For Humans" Philosophy — The design principle, applied to one's own life.
- Evolution of Ideas — How the open source years led here.
- Spiritual Practice & Technology — Maintenance as devotion.