What is Spegling? In plain words.

Start with the problem it solves.

AI assistants are getting good at real work: drafting replies, summarising meetings, updating records, writing documents. Useful enough that people start to rely on them.

Then one Tuesday: a record has changed and nobody knows what changed it or why. An AI-written summary confidently states something that turns out to be wrong. A colleague asks "who approved this?" and there is no answer.

The AI was helpful right up until the moment you needed to trust it. And there was no record of anything it did.

That moment is why many organisations that would like to use AI cannot. Not because the AI is bad at the work, but because nothing about the setup can answer for the work afterwards. Spegling exists for exactly that gap.

What Spegling does, in three plain things.

A record of everything

Every action the AI takes, and the reason for it, is written down in a record that cannot be quietly changed. Think of a flight recorder. If you ever need to know what happened and who approved it, it is all there, in order, with timestamps.

A second opinion that is not itself

Before the AI's work is accepted, a separate, independent AI from a different company checks it, like a second doctor reading the same scan. It cannot approve its own homework, because it never wrote the homework. And before anything risky or hard to undo, the system stops and asks you first.

Rules that are rules

What the AI may touch, what it may spend, and what needs a human signature are set as fixed rules, not as another AI's judgment call. It keeps what you have confirmed separate from things it just read somewhere, so a rumor never gets treated as a decision.

The promise, in one sentence: AI you can hand real work to, because everything it does is recorded, independently checked, and stays inside the rules you set.

If you are reading this for an organisation

The record is the compliance answer. When oversight, an auditor, or a citizen asks what the AI did and on whose authority, the answer is a report you can produce, not a reconstruction from memory.
It runs in the EU. The AI models in the standard setup are hosted on European infrastructure, under European jurisdiction. Nothing in the default depends on a US cloud AI service.
Your systems connect once, to one place. Email and calendar connect to Spegling, not to each AI tool separately. The AI asks through a controlled gate and never holds the passwords. Access can be revoked in one place, and every access is on the record.
Your people stop falling behind. In regulated work, the ones avoiding AI are not unwilling, they are forbidden, because nothing so far could answer for the work. Spegling turns "not allowed" into "allowed, with receipts": they finally get to build the skill, and every use leaves a record that speaks for them.
People and roles are kept apart. A person acting in two roles gets two separate scopes. What one role may see, another may not. The separation is enforced by the system, not by policy documents.

None of this requires your organisation to stop using the AI it already knows. Spegling sits underneath the AI as the layer that remembers, checks, and answers for it.

What to do next

Spegling is currently in a private phase: access is by invitation while the first users shape it. If any of the above sounds like your problem, write a short note about what you would want it to do. A person reads it and a person answers.

Write to Hannu Read the product page About the company

Built by Varjosoft in Helsinki. This page deliberately avoids technical vocabulary; the product page has the full detail, and the integration docs have the technical setup.