A governed AI layer

All AI usage in one governed point.

Todenta is AI governance: who uses AI, what is allowed, what data may leave the building, and what it costs — and every call leaves a record.

What every request passes through

  • ✓ Who is using it — user and application identified
  • ✓ What is allowed — usage limits and models
  • ✓ What may leave — sensitive data is filtered out
  • ✓ What it cost — costs visible, the budget holds
  • ✓ Audit trail — a record for every call
Why this exists

When AI usage spreads out, no one can see the whole picture.

Every team signs up with its own account and talks to AI services directly. No one knows what data went out, what it cost, or who did it — until something goes wrong.

01

What went out

Sensitive data can end up with an outside service, because no one inspects the content along the way.

02

What it cost

Costs scatter across dozens of accounts. The budget is overrun unnoticed, and the bill arrives late.

03

Who did it, and when

No trail, no accountability. When something needs to be investigated, no one can show what happened.

Simply passing calls through is not a solution — many do that for free. The value of Todenta is in the decisions: what was let through, what was not, and why.

How it works

Four checks that every request passes through.

All AI traffic goes through the same gate. Nothing slips past, and nothing leaves without being checked first.

1

Who is using it

Every request can be traced to a user and an application. No anonymous usage, no shared accounts.

2

What is allowed

Each user and application has its own limits: which models may be used and how much. Prohibited usage stops before it goes anywhere.

3

What may leave the building

Sensitive data — personal data, contact details, account numbers — is filtered out before the content moves on. The filtering shows up in the log; it is not hidden.

4

What it cost

Costs are visible in real time by user and by application. The monthly and daily budget is a hard limit — when it is reached, usage stops.

Cache

The same question, the same answer — without sending the data out again.

If the same question has been asked before, the answer is already in-house. Then no new request is sent anywhere — and each such time is one time the data did not leave at all.

◇

Nothing is sent

A hit means the answer was already found — no new call, no new transfer out.

◇

Savings

The same answer, no new bill. The more often the same question is asked, the less it costs.

◇

A per-application choice

Each application can decide for itself whether storage is used.

◆

Personal data is never stored

If a question or answer contains personal data, it is not kept in memory — regardless of the settings.

◆

Isolation is structural

One tenant's answer can never be visible to another.

◆

Deletion leaves a record

When a stored answer is deleted, the deletion is logged — it is evidence, not a promise.

A hit is stronger than filtering: with filtering the data still travels, just modified; with a hit it does not leave at all. A change to the rules also invalidates old stored answers, so that an old answer does not live on under the new rules.

Audit trail

Every call leaves a permanent record.

Todenta does not just store that something happened. It stores what happened, by whom, and on what grounds — and in such a way that a later change is detected.

▣

What the trail tells you

  • Who made the request — user and application
  • What was requested and for which model
  • What was filtered out before departure
  • What it cost and how long it took
  • Whether the request was allowed through or blocked
▣

Why it stands up to scrutiny

  • Entries cannot be changed afterwards — they are written permanently
  • Changes are detected — if an entry is tampered with, it is noticed and reported
  • Verifiable at any time, by an outside party too
  • Blocked requests are recorded too — what did not get through matters as much

The trail is tamper-evident, not tamper-proof. It is only trustworthy once it is taken outside the application — and that distinction is stated plainly, not hidden.

EU rules

Built to EU requirements — not bolted on afterwards.

Todenta answers the same questions that the GDPR and the EU AI Act require: what was allowed to leave, what was logged, and what was deleted. The answer is evidence, not a claim.

◇

Data minimisation GDPR

Only what is necessary is allowed to move on. Sensitive data is filtered out, and what does not need to be sent is not sent — caching reduces outgoing data even further.

◇

Right to be forgotten GDPR

When data is deleted, the deletion is logged. The right to erasure is evidence, not a promise — for stored answers too.

◇

Traceability AI ACT

The use of AI must be traceable. Todenta records who, what, when and on what grounds — including blocked requests.

◇

Oversight and limits AI ACT

System usage must be known and bounded. Usage is identified and limited, and every blocked request stays visible.

Todenta provides the evidence the rules require — it is not legal advice, and it does not automatically make a company compliant. It makes compliance demonstrable.

For whom

For the people who answer for AI.

When the auditors ask, when the board asks, when a regulator asks — someone has to answer. Todenta is built for the two roles that carry that weight.

▤

For compliance

You are asked to prove what left the building, what was logged, and what was deleted. Todenta produces that as a record — not as a promise you have to defend alone.

  • A tamper-evident trail you can hand to an auditor
  • Every blocked and filtered request stays visible
  • A register of AI systems with their risk classification
  • A one-click export package for an inspection
▤

For management

AI spreads across teams faster than anyone can follow. Todenta gives you one view: who uses it, what it costs, and whether it stays within the rules — before the bill or the incident arrives.

  • Costs and budget in one view, by team and by application
  • Spending stops at the limit — it does not notice afterwards
  • A monthly report you can take to the board
  • Regulatory deadlines tracked, not remembered

For developers, Todenta is one shared route: model changes need no code, and every credential shows who and which application called.

Proof

This is not a mock-up. It runs.

These figures come from live Todenta operation — read from the database, not written by hand.

194 706

model calls recorded

5 716

calls blocked by policy

11 621

calls with sensitive data filtered

$341

total cost, visible to the cent

Over two years of operation, every one of those calls left a record: who, what, when, at what cost — and on what grounds it was let through or stopped. That is the evidence.

Let's roll it out

Applications are routed through Todenta and otherwise keep working the same way. Usage is logged, passes through the checks, and can be managed from one place.

  • We reply within one business day.
  • No-commitment assessment — we first check whether there is a need.
  • Your message goes directly to Lennoware Oy, not a subcontractor.

Your message goes straight to info@lennoware.com. We use it only to reply.

What you get right away

  • Visibility into all AI usage — who, what, when
  • Costs and budget in one view
  • Filtering of sensitive data before it leaves
  • Response caching: the same question does not go out twice
  • A trail that stands up to scrutiny — and the evidence the EU requires

How to proceed

Rollout is agreed case by case. We start with a review, not with a commitment.

info@lennoware.com
+358 44 744 8620

Todenta is a product of Lennoware Oy.

The model is not the bottleneck. Data and logic are.

That is why the value is not in passing calls through but in what is let through — and what remains as evidence of it.