You Don't Own Your Docs

You wrote your documentation. You maintain it and argue about its wording in pull requests. None of that means you own it.

Ownership of a docs site is a narrow, testable thing: if the company that renders and serves it disappeared tonight, would the site still be online tomorrow morning? For most teams the honest answer is “once we migrate.” That is the definition of renting. You are a tenant who pays in content.

The part you own and the part you don’t

The source is genuinely yours. Your Markdown is in the repo. Your OpenAPI spec is YAML you can read. Stop Renting Your OpenAPI Docs makes the case that the spec was portable the whole time; the same is true of Doxygen comments and go doc strings. The inputs were designed to be moved.

The rendering was not. The build step, the hosting, the URL structure, the search index, the navigation, the theme: those live on the vendor’s side, and they are the part a reader actually touches. You own the screenplay and rent the cinema. When people say “our docs are on GitBook” or “our docs are on Mintlify,” they are naming the half they do not control, which is the half the world sees.

Leaving gets more expensive every day you stay

Most purchases get cheaper to walk away from over time; you depreciate the thing and move on. Documentation does the opposite. Every page you publish, every cross-reference, every deep link someone else has bookmarked raises the cost of moving. The platform that felt free at fifty pages is a hostage negotiation at five hundred.

This is not an accident of the model; it is the model. A hosted docs platform’s retention is your migration cost. The longer you write, the better their numbers and the worse your options.

The morning the terms change

You find out who holds the files on the day incentives diverge. GitBook deprecated the open-source CLI a generation of developers liked and moved everyone onto the hosted platform. Pricing across the category drifts in one direction: the hosted platforms charge a few hundred a month to render what compiles to static HTML, with per-seat and per-site fees stacked on top.

None of this is villainy. It is a subscription company doing the one thing a subscription company must, which is to convert a thing you need into a thing you pay for every month, indefinitely. The point is not that vendors are bad. The point is that you signed up for an arrangement where their best move and your best move eventually stop being the same move, and on that morning the only leverage that matters is whether the build output is in your hands or theirs.

The price is set by the reader who never pays

Here is the part that should bother you most. The buyer of a docs platform is usually a human evaluator with a company card, comparing screenshots in a procurement meeting. The readers are the developer debugging at 2am, the integrator who will never log in, and now an agent grounding its next API call. The people and processes that read your docs the most are the ones the pricing was never aimed at.

So you pay rent, set by the least frequent reader, on the most-read artifact in your product. Documentation Is the Contract Surface argues that docs became the contract surface humans and agents both ground on. If that is true, paying a monthly fee for the right to render your own contract surface is the strangest line item in the stack.

Ownership is an economic argument

This is not about ideology or a love of plain text. It is about risk and cost. Owned docs are a directory of static HTML. You can host them on a five-dollar box, a CDN, an air-gapped server, or nothing at all if you just open the files. They survive the vendor. You can grep them, diff them against the last release, and serve them in 2031 from infrastructure that does not exist yet. The migration cost is zero because there is no migration; the files were always yours.

That is the whole reason Sourcey builds to static HTML and then stops. It is a renderer, not a platform. It reads the source you already own and hands you an artifact you also own, and then it gets out of the way. No account stands between you and the thing you wrote.

You already did the hard part. Owning the output is just declining to pay rent on work you have already done.