In the places where the work really matters, AI stays out. Not because it is bad at the job, but because afterwards nobody can show what it did or who agreed to it, so the answer stays no. I change that two ways: I build it and prove it for your organisation, or you run your own on Spegling.
Done for you · engagements
There is work AI could do and no way to show it is safe, so the answer stays no. I scope it, build it, and hand you evidence you can re-run yourself. Fixed scope, fixed price, from €4,000.
See the engagements →Run it yourself · Spegling
For people already using AI who want a record of it. Spegling remembers across every AI you use, has important work checked by a second AI built by a different company, so it does not share the first one's blind spots, and writes down what happened in a record you own and can take with you.
Open Spegling →Both sit on the same substrate. An engagement ships a governed agent and its ledger starts on day one.
Every field that carries real consequence learned it long ago: when it matters, you keep the record as it happens, because the account written afterward is worth a fraction of the one written in the moment.
The highest-leverage thing to build is not the model. It is the record the model runs on, captured as it happens, because that is the one part you cannot add later.
One AI does the work. A second one, built by a different company so it does not inherit the first one's blind spots, answers a fixed list of yes-or-no questions about it. One verdict per question, no vibe-check. What passes is filed to Memory and sealed onto the Chain with its verdicts, its cost, and the hash of the row before it.
The stop is proportionate: it closes only on what you cannot take back, and lets reversible work run free. The record, though, is complete. Holds included.
Your memory, your review, your record. The speed of AI, without losing track of what it is doing.
Spegling
The place for the AI you already use to build up context with you.
Pour into the Journal for three minutes, or wire your Claude or ChatGPT to it over MCP. Tomorrow's session already knows what today's was about. A reviewer from a different family checks the important work before it files. Open-weight models, EU-hosted, your own encrypted tenant. Models change. Your history does not.
spegl.ingDots
AI that earns the right to answer. A widget for any page with words worth reading: after two minutes of real attention it answers questions grounded in what is actually written. Refuses off-topic. No cookies, no tracking.
Live in the corner of this page. Spend a few minutes reading and it will offer to answer.
patterns-starter
The open bootstrap for your own way of thinking. One Markdown file: fork it tonight, add your first pattern this week. If Spegling stops existing tomorrow, your patterns still work.
Fork on GitHubMemory, decisions, and evidence are owned. Inference, calendars, and email are commodities. That selective sovereignty is what keeps you less capturable as the tools keep changing underneath you.
From finding where AI earns its place to proving it holds: independent evidence, and the boundaries that turn "not allowed" into "allowed, with receipts." Four shapes at a fixed scope and a fixed price, or embedded with your team when the work runs longer than a hand-over. One person either way. Or just a conversation, if you are not sure where to start.
Adopt
Find where AI fits, with a roadmap and the boundaries drawn.
Prove yours
Independent evidence on an AI system you already run.
Build
The AI for one job, built and proven. Not a demo.
Keep it honest
Kept current as the models change underneath you.
Also on the deep-technical track: quantize, serve, prove it. Third-party validation of large-model serving on vLLM: real hardware, reproducible numbers, publishable artifacts.
Hannu Varjoranta. Systems engineer, founder, writer. Two decades of infrastructure, security, and data systems, including Spotify and F-Secure; co-founder of Valo and Cloop; currently founding engineer at Avrea.
Varjosoft is intentionally small, personal, and long-term. The work here is the layer above execution: memory, trust, and the governance of systems that act on our behalf.
The path is a conversation. Spegling access is by invitation: say what you would run through it. Engagements are open: say what the system must do and what it must never get wrong.
Or write directly: hannu@varjosoft.com. A person reads it and a person answers.