DEV Community

Cover image for The Private Sovereign AI IDE — Why I built Atlarix differently
Amariah Kamau
Amariah Kamau

Posted on

The Private Sovereign AI IDE — Why I built Atlarix differently

There's an assumption baked into every major AI coding tool right now.

That you have a $20/month subscription to an American AI company. That you have a fast, stable connection. That the models worth using are the ones coming out of San Francisco.

I'm building software from Nairobi. That assumption doesn't hold.

So I built Atlarix differently — and after a year of building, v5.1.0 is the version that finally says out loud what it was always trying to be: The Private Sovereign AI IDE.

What that actually means

Sovereign doesn't mean offline-only or anti-cloud. It means you decide.

You decide which model runs your code.

You decide what context gets sent.

You decide whether your keys live on your machine or in a provider's system.

Atlarix is built around three ideas that most AI coding tools don't share:

1. Blueprint — your codebase as a living graph

Instead of sending files per query, Atlarix parses your codebase into a persistent node/edge graph stored locally in SQLite. That graph becomes the AI's long-term memory. It doesn't reset between sessions. It understands your architecture the way a colleague would — not by re-reading everything each time, but because it already knows.

2. Any model — genuinely

Cloud providers via BYOK. Local models via Ollama and LM Studio. And now Compass — three built-in model tiers (Fast, Balanced, Thinking) that work the moment you open the app. No API key. No configuration. Just open and build.

3. The tool carries the intelligence

This is the core thesis. Atlarix feeds the model exactly what it needs, when it needs it, scoped by your .atlarixignore and Blueprint context tiers. A lighter model with good context beats a frontier model flying blind. That's not a consolation prize — that's the architecture.

Work modes that mean something

  • Ask — read-only. No code changes, no terminal. Research, explore, understand.
  • Plan — map out what needs to happen before anything gets written.
  • Build — full tools, explicit approval queue before execution.
  • Debug — focused on what's broken and why.
  • Review — read your code the way a reviewer would.

Each mode binds to a Blueprint context tier. The AI isn't just switching personality — it's switching what it knows and what it's allowed to do.

Why sovereignty matters right now

AI coding tools are becoming infrastructure. The question of which model runs your code, who sees your prompts, and whether you can switch providers without rebuilding your workflow — these are not small questions.

Atlarix's answer: your architecture, your model, your sovereignty.

v5.1.0 is live. Free to start. Native desktop — Mac, Windows, Linux.

👉 atlarix.dev

I built this from Nairobi. If you try it, tell me honestly what's missing. That feedback is worth more than any press right now.

Top comments (0)