A Declaration of Independence
Every Fourth of July celebrates an independence most of us have quietly traded back, one subscription at a time. The cloud that holds your files, your photos, your mail, and now your AI is not a service you own; it is a landlord who rents you access to your own life. This is the account of moving all of it into my own house, need by need, what it actually cost, and why the technology sold as the ultimate instrument of control turned out to be the shortest road back to independence. You do not need permission to leave.
The men who signed the Declaration were not asking for better terms. That is the part we forget. They were not petitioning for a fairer tax or a lighter hand, they were saying the relationship itself was illegitimate, that a people can govern itself, and that the burden of proof had flipped. Independence is not a discount. It is a change in who decides.
Two hundred and fifty years on, the empire is softer and the tax is a recurring charge you stopped reading years ago. It comes disguised as convenience, which is the only form of control a free person accepts without a fight. Your photos, your mail, your documents, your calendar, the whole record of a life, all of it sits on machines you will never see, inside accounts a single unappealable email can close. It never felt like dependency, because a dependency that announced itself would never have found a taker. It felt like relief, like one less thing to carry. That was the bargain, and for a long time it was an honest one.
Then AI arrived, and it is the same trade taken to its conclusion. The most capable tool most people have ever touched, metered by the word, running on hardware you will never see, trained on the exhaust of everything you and everyone else ever typed, and available only as long as the account stays open and the terms stay bearable. It is sold, correctly, as the most empowering thing to happen to ordinary work in a generation. It is also, in the same motion, the most complete dependency ever offered to a consumer, because it does not just hold your files, it holds your ability to think through them. Both of those are true. The whole argument of this piece is that which one you get is not a property of the technology. It is a property of who owns the machine it runs on.
It is worth saying this plainly in the year we are having it, when the word king has come back into the American mouth and the corporate overlord is only its economic form. The new sovereigns rule the way the old ones never could, not by owning the land but by owning the tools you think with, and the deepest joke of the arrangement is that those same tools will help you leave it if you simply point them the other way. The model built to keep you inside someone else's walls will, if you ask it, help you raise your own. That is the whole maneuver, and it is not storming a palace. It is using the master's instruments to stop needing the palace at all, with software already sitting on a drive you own tonight. So that is the question this piece is really asking. In a moment when we are once again talking about kings and the men who would be them, why would we not use the most powerful tools ever handed to us to build our independence from the world they built to hold it?
The soft empire
The people building the cloud are not villains, they are landlords, and the distinction matters because landlords are rational. The business is not selling you software, it is selling you the recurring inability to leave, and everything about the product is shaped to that end. Your data goes in easily and comes out badly. The formats are open enough to import and just proprietary enough to trap. The price is low while you are deciding and adjusts once you cannot. I have written about where that money actually goes, the way the infrastructure spend is really a wealth transfer dressed as a utility bill, and about the specific and enormous waste of the metering model itself, the tens of millions burned on malformed requests that a check on your own machine would have caught for free.
The AI version is only sharper. A model you rent can be retrained, re-priced, deprecated, aligned away from the thing you used it for, or simply switched off, and you will find out the way you find out about any landlord's decision, after it is made. The original sin was letting the most important tool of the decade arrive as a service instead of a possession. Every serious capability you build on top of a rented model is a structure you are erecting on land you do not own, and the rent is not fixed.
The other read
Here is the part the landlords would prefer you not dwell on. The exact same technology, run on a machine that sits in your house, is the most liberating thing to happen to self-reliance since the personal computer, and for the same reason the personal computer was: it collapses the amount of institution you need standing between you and a capability.
Self-hosting was always possible and almost always impractical. The tools existed, the hardware got cheap, and still almost nobody did it, because the work of standing it all up and keeping it alive was a second job you had to actually be good at. That is the thing that changed, and it changed underneath everyone's notice while they were arguing about chatbots. The model that the landlords rent you by the word is the same kind of model you can run locally to carry the exact overhead that used to make self-hosting a second job. It writes the deploy script, reads the log, remembers the flag, drafts the config, and explains the error, which is precisely the labor that stood between a normal competent person and running their own infrastructure. I have made this argument for organizations, the lean coordinator in the cloud and the heavy repetitive work on hardware you already own, and the argument for a household is the same argument with a smaller electricity bill. AI is the thing that finally makes independence maintainable by one person. The tool built to be the ultimate dependency is also the tool that dissolves every other dependency, if you are willing to point it that way.
So I pointed it that way. What follows is not a theory. It is an inventory.
What independence actually costs
I will be honest about the price before I sell you the thing, because the whole point is that there is no free lunch, only a better landlord, which is you.
The physical footprint is smaller than people expect, and less exotic. Two of the three machines are literally my old gaming PCs, retired from games and given a second life, ordinary multi-core desktops with a modest amount of RAM, the kind of thing a lot of people already have going quietly obsolete in a closet. The only purpose-built box is the workhorse, which holds the bulk of the storage and carries everything heavy, the local models, the media, the big services. And the graphics card doing all of that acceleration is itself a hand-me-down, an old GTX 980 from a decade ago, which is the detail worth dwelling on: every bit of acceleration in this house, the language models, the image generation, the streamed desktops, runs on that one aging desktop gaming card. You do not need a data-center GPU for any of this. You need the kind that is probably already sitting in a machine in your closet. One of the repurposed gaming rigs is a deliberately modest little machine that faces the public internet, chosen to be low-power and boring because the thing on the edge should be the thing you care least about losing. Its only job is to be the front door, the reverse proxy, with nothing sensitive living on it. The home automation used to sit on that edge box, and I have since moved it inward, off the public-facing machine entirely, because the last system that should be reachable from the open internet is the one that controls your lights and your locks. The other repurposed rig has a single job, identity, certificates, and mail, the trust anchor for everything else. There is a small pleasure in all of this that the cloud quietly took from us, which is that these machines have names. The one I am writing this on, my personal desktop, is the Millennial, which, for the record, I am. The old edge box is Boomer, fittingly the oldest and lightest of the three; the trust anchor and the workhorse were meant to round out the joke as GenX and GenZ, though if I am honest the naming outran me and at least one of them still answers to whatever the installer called it. Remember when we got to name our own servers fun things, back before every machine you touched became an anonymous instance ID in a rack you would never see? Owning the hardware hands that back too, along with everything more serious. And there is one small rented server in a datacenter that exists for a single reason I will come back to, because it is the one honest exception to the whole philosophy.
The cost is not the hardware, it is the discipline. Everything is defined as code, so that the system is a thing I can rebuild rather than a thing I have configured and must now fear. Certificates come from my own internal authority. Names resolve through my own split-horizon DNS. Deploys run through a pipeline, not through me typing on a Tuesday. And yes, occasionally something falls over at three in the morning and I add a restart policy at three in the morning, which is exactly the kind of labor the landlord was absorbing for you and charging you for. That is the real answer to what it takes. It takes accepting that you are now the operator, and using the machine to make being the operator survivable for one person.
And the sacrifice, the thing you actually give up in exchange, is close to nothing. That is the claim I most want to be held to. At the layer where you live, opening an app and doing a thing, there is no downgrade. The replacements are not sad approximations of the products you left. In several cases they are better, and in a few cases they do things the hosted product will not let you do at any price. Here is the whole map.
The everyday things you already rent
Start with the boring, load-bearing needs, the ones you would notice within a day of losing them.
Documents. Every receipt, statement, warranty, and contract goes into Paperless-ngx, which scans, OCRs, tags, and makes the whole paper history of a life full-text searchable. It is the filing cabinet you always meant to keep, run by a machine that never gets bored. This is the single service that most convinced my family the project was worth it, because "where is that document" stopped being a question.
Files and sync. Nextcloud is the OneDrive, the Google Drive, the shared family folder, syncing across every device with the same casual reliability. It is worth saying outright that much of this whole section is really just Nextcloud wearing different hats, because it does far more than files straight out of the box: calendar and contacts and notes and Talk for calls and chat, and with Collabora alongside it the office suite too, all through my own server instead of a company's. A surprising amount of the everyday cloud turns out to be one install. The files are on my disk. The link you share expires because I decided it does, not because a plan tier decided it.
Office and editing. Collabora and LibreOffice cover documents and spreadsheets with real fidelity. But for anything genuinely sensitive I reach past them on purpose, to CryptPad, which is end to end encrypted and zero knowledge, meaning the server, my server, cannot read what you are writing on it. This is the choice I want to point at, because it is the whole thesis in miniature. Given the option, I did not pick the tool that merely moved the surveillance in-house. I picked the one where the surveillance is mathematically impossible. Independence is not just changing who holds the key. Sometimes it is making sure there is no key.
Passwords. Vaultwarden holds every credential, the Bitwarden protocol on my own hardware, which is the correct place for the keys to your entire life to live.
The chatbot. Open WebUI is the ChatGPT-shaped window, pointed at models running on the box downstairs. The family uses it the way everyone uses the hosted one, except the conversations do not leave the house, nothing is training on them, and there is no meter running. It is not a compromise version of the experience. It is the same experience with the landlord removed. And for the version of this you can hand to someone who does not want to assemble any of the pieces, there is Project N.O.M.A.D, an offline AI and knowledge server that packages the model, the tools it can call, and a local knowledge base into a single box that still works with the internet unplugged.
There is also, since someone always asks, a Jellyfin server, and behind it an *arr stack. What that stack does is left as an exercise for the reader.
The things you didn't know you could hold
Then there are the needs you assumed structurally required a corporation, the ones where the surprise is that they can sit on a shelf at all.
Navigation. This is the one that changes how people think about the whole project, and it is easily the most expensive thing in the house to pull off. Everyone assumes maps are a thing only Google could do, an entire planet's worth of tiles and imagery and routing, and the reason they assume it is that they are half right: to hold the world you have to actually hold the world. Wayfinder is a full maps app, address search, turn-by-turn routing, points of interest, 3D terrain, and it runs against a local geo stack that is, frankly, a monster. The vector tiles for the whole planet, the aerial imagery, the routing graph, the geocoding database, the elevation model, it runs to terabytes on disk, which is the honest price of never asking a datacenter for a single turn. None of that lives on a phone, and it never could. It lives on the workhorse, the box with the disks and the GPU, and every screen in the house is just a browser pointed at it. On top of the data sits the part that makes it feel like a maps app from this decade instead of a static atlas: a local AI stack, speech-to-text so you can ask it where to go out loud, a language model that understands the asking, and text-to-speech that reads the route back, all of it running on hardware I own and none of it phoning home. It is a maps app you can talk to, that talks back, and that answers to me instead of to an advertiser. You do not need Google to hold the world. You need a big enough disk and the will to fill it.
Learning. Kolibri is a self-hosted education platform, a genuine library of courses and materials that lives at home and works whether or not the wider network does. Kiwix sits next to it holding offline copies of the reference web, and here too the scale is the point. The full text of Wikipedia, the programming Q&A archives, the how-to and medical and survival libraries, packed down and sitting on my disk, is hundreds of gigabytes of the knowledge that used to require a live connection to somebody else's servers and now requires nothing but electricity. And this is where the separate pieces quietly become one thing: the map data, this whole knowledge base, and every document I have ever scanned are all reachable through the same local chatbot from earlier. Open WebUI is not just a model in a box, it answers out of my own corpus, the planet and the encyclopedia and my own paperwork, so the assistant knows my world rather than the internet's, and it learned none of it by watching me.
Making things. BambuBuddy runs the 3D printers and Manyfold is the library of models to feed them, so the design-to-object loop is entirely inside the house.
Comms that survive the grid. This is where independence stops being a metaphor. Meshtastic is long-range mesh radio that needs no cell tower and no internet, a text network that keeps working when the infrastructure everyone else depends on does not. Alongside it I run OpenTAKServer, the open-source TAK server, for shared situational awareness across those devices. Most of the stack is about not depending on a company. This part is about not depending on the grid.
The odds and ends. The small daily utilities that you currently hand to random websites, the PDF tools, the format converters, the diagramming, the inventory of what you own, all self-hosted, all private, all yours.
The plumbing you have to own
Underneath the things you use are the things that make using them safe, and this is where the real engineering lives.
Accounting. This one is a nice-to-have rather than a necessity, and honestly mostly for the business owners among us. If you run a company, the books can sit on a proper self-hosted stack instead of a subscription that raises its price the year you can least afford it, ERPNext as the system of record with the supporting ledger tools and the tax automation around it. For everyone else it is happily overkill, but if your financial history has to live somewhere, there is a real case for that somewhere not being a rental.
Identity. One login, Authentik, single sign-on across everything, so the family has one identity I control rather than forty accounts a dozen companies control.
Secrets. Every password, key, and token the system needs lives in OpenBao and is injected into a service at deploy time, never written into a file, never committed to a repository, never sitting in plaintext waiting to leak. The rule is absolute and it is the difference between self-hosting and self-owning.
Your own git, and a clever use for the cloud you left. I run Forgejo, my own git host, as the source of truth for all of this code. And then I do the thing I like best in the whole design: I push a mirror of it to GitHub. Not as the home. As a backup. The cloud I spent this entire essay leaving becomes a dumb, free, geographically separate copy of my repositories, holding a replica in case my house burns down, while owning nothing and controlling nothing. That is the correct relationship to have with a hyperscaler. Let it be the off-site drive. Do not let it be the landlord.
The network itself. AdGuard filters ads and trackers for every device in the house at the DNS level, which means the surveillance most people accept as the price of a free web simply does not arrive.
The home. Home Assistant runs the lights, the sensors, the locks, the routines, entirely locally, and Music Assistant handles audio through the house, none of it phoning home, none of it dependent on a cloud that can sunset a device you paid for.
The desktops. This is quietly one of my favorite things in the whole house. For the times you need a real computer and are not sitting at one, I stream full Linux desktops out of the server and into a browser tab, built on Selkies, which pushes a live GPU-accelerated desktop over WebRTC with barely any latency. Any screen becomes a workstation without a workstation being there: a Chromebook, a tablet, a decade-old laptop, the television, each of them borrowing the horsepower of the box downstairs. On top of it I built my own front end, a hub where each person spins up their own desktop, stops it, restarts it, and installs real applications into it from a menu, Blender and Krita and FreeCAD and the slicers for the 3D printers, the heavy creative software that has no business running on a tablet, running on a tablet. The part that still gets me is how little it costs to do. A desktop is only alive while someone is actually in it, they auto-stop when they go idle, and the streaming itself is so light that one modest machine hands out full workstations to the entire house on roughly the power of a light bulb.
Analytics, and a choice worth explaining. I run OpenPanel for the analytics I actually need, and I want to say why it is not PostHog, because the reasoning is the reasoning behind the whole project. PostHog is capable, but it is heavy, and it is on the well-worn path of the open-core product that is free until the day it is steering you toward the paid tier. I wanted the lean, genuinely free-standing option, the one whose incentives are not quietly pointed at a future invoice. Choosing your tools by where their incentives point, not just by their feature list, is most of what independence turns out to be in practice.
Holding it all together are four rules, and they are the actual constitution of the thing. Free and open source first, with exactly one exception I will name in a moment. Everything as code, so the system is reproducible and not merely running. Every build works fully offline, from a local registry and local package mirrors, so no outside company's uptime is load-bearing for mine. And secrets never touch the repository. That is the whole discipline. It fits in four sentences and it is the difference between a hobby and a home.
The one exception
I promised to come back to the little rented server in the datacenter, and here it is, because it is the seam where this whole philosophy meets a wall it cannot argue with. The wall is email. You can run a mail server at home, and I do, but you cannot make the rest of the internet accept mail from a residential address. Residential IP ranges are permanently distrusted, most consumer ISPs block the outbound mail port on purpose, and a message from an unknown address at home lands in spam if it lands at all. Deliverability is not a technical problem you can out-engineer from your living room. It is a reputation problem, and reputation is granted by everyone else.
So the mail server itself, Mailcow, lives at home, where the mailboxes and the data are, and a tiny rented VPS with a clean, reputable datacenter address sits out on the internet as its relay, the face the world sees and trusts. The two are joined by an encrypted tunnel, and the VPS holds nothing, no mailboxes, no archives, no key that matters. It is a dumb, reputable pipe and nothing more. If it vanished tomorrow I would lose the ability to send for an afternoon, not a single message already received. It is the one place the outside world's rules force me to keep a foothold outside the house, and pretending otherwise would be a lie. Independence is not purity. It is knowing exactly where your one dependency is, why it has to be there, and how little it is allowed to hold.
The glue
I would be lying if I called any of this turnkey. The dirty secret of self-hosting is that the products are the easy part, and the system is held together by dozens of small, unglamorous, custom tools that nobody ships and everybody needs. The thing that injects the secret at the right moment. The thing that bootstraps the certificate authority. The thing that waits for a service to come healthy before declaring a deploy successful. The thing that dispatches a bulk job to the local model instead of an expensive one. The thing that audits the whole repository to make sure no key ever slipped into it. Each is fifty lines. Together they are the actual labor, and they are invisible, because when they work you never see them and when they fail you see nothing else.
This is exactly the work AI is good for, and exactly the work worth keeping. I have argued that a skill is a wish and a script is a guarantee, that the deterministic tools a model helps you build are assets you should keep instead of regenerating, and this whole layer of glue is that argument made physical. The first piece of it is already out in the open, Rote, the small library that keeps the solved things solved. More of the glue is worth sanitizing and releasing, and I intend to, because the tools that make one household independent are the tools that make the next one's job smaller.
I will also be honest that the system is mid-migration. It used to be orchestrated by Nomad, and I am retiring Nomad in favor of plain per-stack compose and a real deploy pipeline, but its fingerprints are everywhere still, the internal proxy that routes the friendly names, the naming scheme, the app tiles on the desktops. Independence is not a state you arrive at. It is a direction you keep walking, and there is always a piece you have not broken off yet.
Keeping it alive
A system you cannot rebuild is not independence, it is a hostage situation with extra steps, so the backup story is not an afterthought, it is the point. Because everything is code, recovery starts as a clone and a command, and unchanged configuration redeploys to a no-op. Because every container image is saved locally and mirrored into my own registry, a rebuild from bare metal needs zero external downloads, which is what "offline-capable" has to mean if it means anything. Application data is dumped in each tool's native format and copied between machines. Secrets are re-materialized from the vault on recovery, never from a backup file, because a backup of a secret is just a leak with a delay.
And the off-site copy, the last line of defense, is that reverse mirror to GitHub I described, the elegance of which I will not pretend I am not proud of. The empire keeps a copy of the rebellion's papers, for free, and gets no say in anything. The same trick scales to the heavy stuff. The very largest binary stores, the things too big for a git remote, get compressed into a single image and encrypted so thoroughly that what leaves the house is indistinguishable from noise, then parked in Google Drive and OneDrive. Google and Microsoft, the two landlords this whole essay is about leaving, are now helping hold my backups, and there is nothing they can do with them, because all they have is ciphertext. The cloud makes a fine dumb vault precisely when it cannot read what it is holding. The honest part is that this is a waypoint, not the destination. The destination is not a hyperscaler at all, it is a trust partner, or a handful of them, a small federation of people in the same position who simply store each other's encrypted images, so the last copy lives on hardware owned by someone who owes you the same favor and nothing more. Independence is not the same as isolation. Sometimes it is just choosing who you depend on, and on what terms.
The declouder
There is one problem left with everything I have described, and it is the only one that actually matters: I can do this, and most people cannot, and a liberation available only to people who can hand-build a datacenter is not a liberation, it is a hobby. The barrier is not the hardware anymore and it is not the software, both are cheap or free. The barrier is the standing-it-up, the exact labor the model is now good enough to carry.
So I am building the thing that carries it. It is a command-line tool called declouder, and it is open source, and it does the unglamorous work of starting. It scans your network and takes an honest inventory of the compute you already have, the old laptop, the spare desktop, the little server you bought and forgot. It asks you, by need and not by jargon, what you actually want, maps and mail and photos and documents and a private chatbot. Then it does the honest part that almost nothing else will: it weighs what you asked for against what you actually have, and tells you plainly which of it your current hardware can serve right now and which will have to wait. For the things that must wait, it tells you exactly what you would need to add, so many more cores, so much more disk, a GPU, or just one more old machine. It writes the infrastructure-as-code for everything that fits today, placeholders instead of secrets, and records the rest instead of pretending it does not exist. Add a box later and run it again, and the deferred pieces fold themselves in. It is a plan that grows with you, not a promise that your spare laptop is secretly a datacenter. It is deliberately a scaffold, not a magic button, because the whole ethos is that you should end up owning and understanding the thing, not renting a new black box that happens to sit in your house. It exists so that the first step, the one that stops almost everyone, is a command instead of a cliff. You can find it here.
Who owns the machine
The tool that looks like the ultimate instrument of control is also the ultimate instrument of independence, and the only variable that decides which one you are holding is who owns the machine it runs on. That is the entire finding. The cloud is not evil and the model is not a trap, they are landlords, and the alternative to a landlord is not homelessness, it is a home. The technology that could finish making you dependent is, in the same year, the technology that could let you finally stop being. On the day the country celebrates declaring that a people can govern itself, in a season when kings and their corporate heirs are back in the conversation, it is worth remembering that the same sentence scales all the way down to a person, a house, and a machine you own. The tools they built to rule you are the tools you can use to leave, and they are on your hard drive already. You do not need better terms. You do not need permission. You can just leave.
William Dunn is the founder of Quasarke, a software development consultancy, and has spent a decade building company architectures. Rote and declouder are open source under the MIT license.