Why I defend sovereign infrastructure

For years, I’ve been building systems.

I’ve worked with public cloud, complex infrastructures, modern stacks.
And the more I go forward, the clearer one thing becomes:

Data you don’t control does not belong to you.

The false comfort of the cloud

The cloud simplified many things.
But it also created massive dependency.

We outsource:

• servers
• backups
• keys
• logs

And in the end, we control nothing.

The day your provider changes its rules, its pricing, or its priorities…
you don’t decide anymore.

Sovereignty ≠ isolation

Sovereignty is often misunderstood as isolation.

What I defend is the opposite:

• open source
• open standards
• interoperable protocols

A sovereign system is not a bunker.
It is a portable system.

Why I build this way

When I design infrastructure, I want:

• to understand every layer
• to be able to rebuild it anywhere
• to document critical points
• to remove useless dependencies

Not for control.
For freedom.

This is not political

This is not ideology.
It’s technical pragmatism.

Whoever controls the infrastructure controls the product.

---

Today I’m not chasing ease.
I’m chasing robustness.

Less flashy.
But far more durable.