Sovereign

There’s a quiet war happening in tech right now.

On one side, there’s the corporate machine:

subscription-only tools, vendor lock-in, opaque AI pipelines, and dashboards designed to look “clean” while hiding all the internals that actually matter.

On the other side, you have something I care about deeply: technical sovereignty.

Owning what you run.

Knowing where it runs.

And being able to fix things without begging a helpdesk ticket to be escalated to Tier 2.

After being suspended without warning, my account on X was restored.

Lesson stays the same: if you rely only on centralized platforms, you are always one click away from being erased.

Account from 2006. Almost 1200 followers. GONE.

No clear reason. just “violated authenticity rules.”

Didn’t insult anyone. Didn’t spread fake news. Just posted.

They threatened to block any new account I create.

See how dumb it is to rely on centralized platforms?

Building My Own Sovereign RAG for Secure Code Analysis

Lately, I’ve been taking a closer look at some code analysis tools that claim to detect security vulnerabilities in software projects. The idea itself is solid. I got one of these tools recommended to me and decided to dig deeper to see what’s really behind these solutions.

Pretty quickly I noticed a pattern: these platforms are far from cheap. Some offer limited free plans, but we all know how this game works. When something that good is offered for “free”, the real price usually comes from somewhere else — data collection, vendor lock-in, black-box models processing your code in someone else’s cloud. And since I’ve been deeply studying AI lately, especially Retrieval-Augmented Generation (RAG), the question came naturally: why not build my own pipeline, fully local, sovereign, using open-source tools, running on my own machine, and depending on no one?