MENUCLOSE
Every AI action in your company. On the record.
Tallin is the control plane for AI use by humans, apps, and agents. Route your AI through the gateway and every actor gets an owner, a budget, a policy, and an off switch, on an append-only ledger that records every action and proves every dollar.
Sample Ledger
A representative append-only record. Every action, owner, and dollar, on one line.
Not a ledger. A control plane.
Entry 01 — The Problem
The bill is the first time most companies see their AI usage.
Claude Code spread to ~5,000 Uber engineers far faster than forecast; the annual budget was exhausted by April. Uber now caps per-tool spend at $1,500 per engineer per month.
A solo research project ran ~100 agents: 603 billion tokens, 7.6 million requests, a team of three. OpenAI covered the bill deliberately, as research. Most companies will not get theirs forgiven.
Discovered only when a human opened the invoice. An illustrative single-engineer report; the failure pattern is structural: silent recursive spend with no kill switch.
Cost is one exposure. Data is the other.
Cost
Invisible until the bill arrives.
Uber is the proof: a sophisticated, AI-forward enterprise with dashboards and a CTO, and the spend still outran the year’s budget before anyone could react. A 200-person company has less visibility and the same usage-based pricing.
Exposure
Data leaves silently.
The founding precedent of this category: Samsung, April 2023. Three source-code leaks into ChatGPT in roughly twenty days, covering semiconductor source, test sequences, and a meeting transcript, followed by a company-wide ban (The Economist Korea, Mar 2023). Today every employee has ten AI tools, and agents act on their own.
Tallin makes both visible: observed, inferred, enforced, or honestly not covered.
Entry 02 — Coverage
Most tools imply total visibility. Tallin stamps every entry with what it can prove.
- OBSERVED
- Recorded directly from provider telemetry, SSO, or billing exports. Provable, line by line.
- INFERRED
- Deduced from secondary evidence such as expense records and network logs. Reliable, and labeled as indirect.
- ENFORCED
- Actively governed: routed through the Tallin gateway (recorded, capped, and blockable in real time), or held by access restriction, SSO, CASB, or provider admin policy.
- NOT COVERED
- No reliable signal exists. Tallin says so plainly instead of pretending.
Entry 03 — How It Works
Identities in. Models out. Everything on the ledger.
Entry 04 — The Ledger Spec
The record, specified.
- Write model
- Append-only. Entries are never edited and never deleted.
- Capture
- Configurable per policy: metadata only, or full content when you need it. Every entry carries actor, model, and cost.
- Retention
- 13 months, then archive.
- Tenancy
- Single-tenant architecture. Your ledger shares infrastructure with no one.
- Coverage
- Every entry stamped: observed, inferred, enforced, or not covered.
Product facts, stated as ours. Not research claims.
Entry 05 — Pricing
Priced to the size of your AI, not a headcount guess.
Tallin is priced by covered directory users and governed AI actors. Every plan writes to the same append-only ledger and carries the same coverage stamps, so what you pay changes, what you can prove does not.
We will walk you through the number that fits your company on the demo call.
Request access →Entry 06 — Index
Common questions, on the record.
06.1What does Tallin record?+
06.2What can Tallin actually see?+
06.3Does Tallin sit in the request path?+
06.4Can Tallin cap or block spend?+
06.5How long is the ledger retained?+
06.6Is my data shared across customers?+
06.7How is Tallin priced?+
Join the design partner cohort.
Tell us about your AI actors, provider stack, and the runaway spend or policy gaps you need to close. We will help you decide whether Tallin is a fit for the first cohort.