Last issue was about internal links — connecting the pages you already own so ranking power flows where you want it. This one's a slight detour from the weekly fix, but it's built on the same instinct: own the thing. I want to show you something I built, and the principle behind it that applies to nearly every tool you pay for.

Here's the uncomfortable truth about most software you rent. When you put your numbers, your customers or your content into a typical SaaS tool, the company running it can read all of it. Their analytics see it, their error logs see it, their staff can query it. And the day you stop paying, your data is on their side of a wall. You're not a customer so much as a tenant.

This is exactly why WordPress won, by the way. It's self-hosted. The site sits on infrastructure you control, the database is yours, and no vendor can switch it off or hold your content ransom. That ownership is the whole point — and it's worth applying the same test to every other tool in your stack.

What I built to prove the point

I've been building a product called NomadWealth — a self-hosted personal net-worth cockpit. One private dashboard for your whole financial picture: holdings, property, loans, cash, a FIRE projection, switching live between currencies. It started as a tool for my own finances, and I packaged it into something anyone can buy and run.

The defining rule shaped every decision: as the vendor, I literally cannot see the buyer's data. Each person deploys their own copy to their own Vercel account, connected to their own database. There's no phone-home, no analytics on the actual numbers, no error reports carrying values off the machine. The importer parses your spreadsheet in your own browser — the figures never touch a server of mine. Even the licensing works offline, so activating it doesn't send anything anywhere. [FILL: one personal line on why you built it this way — e.g. "I wanted my own net worth in one place and wasn't willing to hand it to a third-party app to do it."]

The two questions that matter

You don't need to build your own app to benefit from this. You just need to ask two things of any tool before you trust it with something important. One: can I export everything, cleanly, whenever I want? If the answer is no or "sort of", you're locked in. Two: who can see my data? Most tools' honest answer is "us, and anyone we share infrastructure with." A smaller number are built so that answer is "only you." Those are worth paying more for.

I wrote up the full build — the one-click deploy, the offline licensing, the privacy architecture and the decisions behind it — as a case study. If you're curious how a "the vendor can't see your data" product actually works under the hood, that's the place to read it: the NomadWealth case study. And if you want to see the product itself, it lives at nomadwealth.app.

Why I'm telling you this

Partly because it's the most interesting thing I've built this year, and this newsletter is written by the person doing the building. But mostly because the principle is portable: the tools you own beat the tools you rent, and "can I get my data out, and who else can see it?" is the cheapest due-diligence you'll ever do. It's the same reason your site belongs on WordPress and not on someone's closed platform.

If you're sitting on an internal tool or spreadsheet you've outgrown and wondering whether it could become a real, self-hostable product — that's exactly the kind of build I do. Reply and tell me about it.

This issue lives in the archive, organised by topic. And the plugins page shows the repeatable workflows alongside the service work.

How we can work together

Reply and tell me the one tool you'd most hate to lose your data to. I'll tell you whether there's a self-hosted alternative worth a look.