June 2026 · Essay
Sovereignty is the next default.
For a decade, the bargain was simple: give a company your data, and they'll give you software that feels like magic. We took the deal because the magic was real and the cost was invisible.
AI changes the math. The capability is no longer scarce — a frontier model can be summoned by anyone, for cents. What stays scarce is trust: who actually holds your information, and what they can do with it while you're not looking.
Continue reading →
When the valuable thing was the software, it made sense to rent it. When the valuable thing is your data and your autonomy, renting starts to look like a slow giveaway. Every prompt is a small confession; every uploaded document is a copy you no longer control.
The answer isn't to give up the capability — it's to move the locus of control. Run the intelligence next to your data instead of shipping your data to the intelligence. The hardware is finally fast enough, the models are finally small enough, and the stakes are finally high enough that "local by default" stops being a niche preference and becomes the obvious one.
That's the bet Virohana is built on: sovereignty won't be a feature you pay extra for. It'll be the baseline everyone expects.
June 2026 · Field note
Your books should live on your machine.
Bookkeeping is the perfect test case for sovereign AI. It's tedious enough that you'd love to hand it to a machine — and sensitive enough that you'd hate to hand it to a stranger.
So don't choose. Let the AI do the sorting and drafting, but keep the whole thing on your laptop, signed off by you, posted with your own key.
Continue reading →
Estonia already does the hard part: it gives every company free, official accounting software and a clean way to plug into it. What's missing is the layer that makes it effortless — something that reads a month of messy transactions and turns them into a tidy, reviewable draft in minutes instead of an evening.
The instinct of most tools would be to suck all of that into a cloud dashboard. Ours is the opposite: the numbers stay where they belong, the AI works locally, and the only thing that ever leaves is the entry you explicitly approve. Convenience without surrender. That's the connector we're shipping first.
May 2026 · Essay
One person, many engineers.
A single founder can now run what used to take a team — not by working harder, but by directing a small fleet of AI workers that build, watch, and repair the system around them.
Continue reading →
The trick isn't the model; it's the discipline around it. Deterministic code does the boring, predictable work. A local model handles the judgment that doesn't need a genius. The expensive, frontier reasoning gets summoned only for the problems that genuinely require it. Everything is logged, reversible, and reviewable.
Run that way, "an AI software engineer" or "an AI operations engineer" stops being a slogan and becomes a real, supervised member of the team — one that happens to run on infrastructure you own. That's the same machinery we now build, to order, for others.