Digital Sovereignty: Why I Built a Custom Blog Over Rented Land

It has been a while since anything went up here — life, and the ordinary professional entropy that eats the time around it. But I kept coming back to one thing: the habit we have all picked up of keeping our writing on rented land. Medium, Dev.to and the rest give you reach, and in exchange you write inside a polished enclosure you do not control. I looked hard at that trade before I started this, and giving up the infrastructure for a Follow button was never going to be acceptable to me.

The one-size problem

Third-party tools are built for the average case, which is a diplomatic way of saying they are rigid. My requirements were not average: real routing for six languages, exact control over typography and accessibility, and none of the third-party script bloat that comes bundled in. Forcing that into a hosted blog usually means a pile of plugins that wreck performance. On a platform you are not an owner, you are a tenant — no say over the infrastructure, the SEO logic, or whatever is logging you while you type.

A living laboratory

I treat this site as a laboratory for the art of integration. In a company, architectural decisions get worn down by legacy weight and committee consensus. Here there is neither. Building on Next.js and React, I can tune server components and hydration and write logic that would be a nightmare to force into a generic blogging tool.

Concretely, here is what owning the stack buys that a hosted platform structurally cannot:

• The search footprint. The server builds the structured data and localized tags itself — an exact record of who wrote what and in which languages, instead of whatever shape the platform imposes.
• Language handling. The server reads the reader's preferences and resolves the locale before anything renders. No Translate widget, no clutter in the URL.
• Interactions. No rented clap counter, no tracking script, no locked comment box — the endpoints for reads and reactions are mine, private and shaped to the site.
• The content is just data. It is fully decoupled from the presentation, so I can add code sandboxes or diagrams, or replace the entire design, without touching a single post.

This is not only somewhere to keep text; it is a proof of concept. If it feels deliberate, that is because every element and every line had to earn its place. It is the difference between describing a system and walking someone through the running thing.

Ownership as logic

This is my path and I am not especially interested in arguing that it is everyone's. But the reasoning is not sentimental. Platforms move on shifting business models and boardroom moods, and anything built on top of them inherits that instability. Owning the data and the presentation is how this stays predictable and independent of someone else's algorithm.

The foundation is laid; now it's time to build.

• Self-Hosting
• Next.js
• Internationalization