Inlock
PDF

Four-eyes control for AI agents that move money and records.

Routine actions go through. Risky ones wait for a named person to sign off. Dangerous ones are blocked. Every decision lands in a tamper-evident log built for AI Act Art. 12 and 14.

01
Problem

Companies are handing AI agents the keys. Nobody checks what they do with them.

  1. Agents act now. They move money, change records and send email — not just chat.
  2. Guardrails check words. Every cloud filters what an agent says; none decides what it may do.
  3. One bad call is enough. A deleted database or an emptied account can't be undone.
02
Solution

A checkpoint between every agent and every system it touches.

YOUR AGENTS YOUR SYSTEMS Mistral Bielik Claude GPT your own Database Cloud storage Email Slack / webhook Gov registries Inlock Policy engine allow · hold · deny Audit trail every decision, hash-chained every tool call only allowed calls
YOUR FLEET Mistral · Bielik Claude · GPT · your own Inlock tiered classifier WHERE IT LANDS 🗄️ Database · ☁️ Cloud storage ✉️ Email · 💬 Slack / webhook 🏛️ Gov registries

Nothing irreversible without sign-off

Risky calls wait for a named person to approve or deny.

No feed to babysit

Routine calls clear in milliseconds. People only see the exceptions.

A record auditors trust

Every decision, and who made it, in a tamper-evident log.

03
Why now · Market

Agents got hands in 2025. The rules land in 2027.

2025

MCP goes mainstream

OpenAI, Google and Microsoft adopted one open standard for agents to call real tools.

June 2026

Europe starts buying European

The EU Cloud and AI Development Act, and Poland's sovereignty test for public tech purchases.

2 December 2027

High-risk AI Act rules apply

Human oversight (Art. 14) and automatic logs (Art. 12) become mandatory. Fines reach €15M or 3% of turnover.

100 customers is €7.5M a year. 4,200 EU firms already run agents.

SAM
€320Mthe ~4,200 in the EU already putting agents to work; we sell to those whose agents can write
SOM
€7.5MARR from 100 customers in five years

Start with EU insurers, banks and claims firms of 200–3,000 staff that run at least two agents touching a system of record.

SAM: Eurostat, 55,000 EU firms with 250+ staff (2024), 55% of them using AI (2025); Capgemini (2025), 14% of large firms deploying agents, global sample; × €75K, the Growth tier. SOM is our assumption.

04
Product

One engine. Three views of every agent action.

Prove

Show who approved what

Auditors read a hash-chained record and export it. They can't approve anything.

Operate

See what agents do across the org

A manager panel, cost and usage by agent and model, and an org chart that decides who sees which agents. Agents and teams, not individual people.

Build · free on-ramp

Gate agents while they work

Every tool call is checked through the SDK, the MCP gateway or the Claude Code hook. A CI check does the same for pull requests.

Sample data, real components. Connect once, pick from seven gates, approve only what is held. Live demo on request.

05
Business model

One annual fee per company, from €30K a year.

Not metered: a product that ends surprise AI bills shouldn't send one of its own.

Community
€0

Open-core engine, self-hosted

Contract

Paid upfront or quarterly

Annual contracts, so revenue is predictable from the first design partner.

Target

€50K–€120K a customer

Blended annual contract value: design partners start at €30K and move to Growth at renewal. 6–8 of them reach €400K–€600K ARR within a year of general availability.

Expansion

Grows with the fleet

More agents and more teams under the same sign-off, not usage creep. Paid tiers add compliance reporting, the evidence export and support.

06
Go-to-market

Engineers adopt it free. Risk and audit sign it off.

1

Land

€0

An engineer self-hosts the open-core engine on their own agents.

Build
2

Sign

€30K

The CISO or internal audit signs a paid pilot, not a full procurement cycle.

Prove
3

Expand

~€75K

Managers put more teams and agents under the same sign-off.

Operate
The buyer

Head of Engineering at a 200–3,000-person EU insurer, bank or claims firm

Just told to give an agent write access. The CISO or Head of Internal Audit signs, from a security or compliance budget.

“Who approved this payment, and can you prove it?”

First 6–8 design partners are regulated firms, insurance first. Banks and the public sector follow as EU rules start favouring EU vendors.

07
Competition

Others block or ask. We pick what needs a person, and prove who signed.

Governs actionsPicks the risky calls itselfWho signs offTamper-evident recordUnder EU law
Filter wordsBedrock · Azure Content Safety · Model Armor · Lakerawords only————
Block actionsWitnessAI · Operant AI✓✓——US
Zenity✓✓——Israel
Veto✓✓——self-host
Invariant (Snyk) · Lasso✓by hand——self-host
Ask a personHumanLayer✓by handa reviewer—US
Auth0 for AI Agents✓by handthe user—US
Permit.io · Frontegg AgentLink✓by handa reviewer—Israel
Inlock✓✓✓ named person✓ hash-chained✓ EU

Vendors' own material, Sept–Oct 2026; — means not stated. HumanLayer, Permit.io and Frontegg log decisions but don't call the log tamper-evident. Auth0 asks the agent's own user, not a second person.

Security tools stop attacks. We run the sign-off. Snyk or a platform can sit alongside us: a fleet mixes vendors, and an auditor wants one independent record.

08
Why we win

Hard for a US platform to copy, and hard to build over a weekend.

Four-eyes control, built in

The engine picks the risky calls, a named person signs them off, and the record verifies itself. Security tools are built to stop attacks, not to run the sign-off.

EU jurisdiction, by design

The plan: an EU entity, EU hosting and EU inference, so the whole stack sits out of CLOUD Act reach. A US vendor can't match it without a new legal entity.

Open-core: judge it yourself

Buyers can read and run the engine before they pay. A regulated buyer's security review starts from code, not a sales deck.

Sized for the mid-market

WitnessAI starts at 1,000 users. A 300-person insurer running forty agents is too small to buy it.

09
Traction

Pre-revenue, not pre-product. It runs end to end today.

<1 ms
to decide most calls, without calling a model
18/18
test scenarios passed on 7 mock MCP servers the engine had never seen
2
live external agents governed: a Mistral connector, a Bielik claims agent
4
ways in: SDK, MCP gateway, Claude Code hook, CI check
Pipeline

US interest first, EU sales next

Alight and Travelers will try the sandbox. No EU prospect or signed deal yet: this round buys the first design partners. Next: ten calls with EU insurers and banks. Which agent can write to a system of record, who signs it off today, and does any tool they own cover it?

What a reviewer sees: a payout and a bank-detail change wait for a person, a DROP TABLE is blocked, the rest go through in under a millisecond.

10
Team

A founder who has been the buyer, built for the regulation, and shipped the mechanism.

RB

Roman Belfer, Founder

Poland, EU

The buyer

Director of Engineering at Travelers, a Fortune 500 company and the 6th-largest US P&C insurer. Led its modernisation and security programmes.

The regulation

CTO at EyreACT, an EU AI Act governance platform, building compliance tooling before the rules made it urgent.

The mechanism

Piloted AI-guardrailed CI/CD checks at Travelers that caught AI-written code breaking business logic.

The team this round builds: four people by month 6
First close · €400K · months 0–3Founding engineer: approvals in Slack and Teams, the evidence export, transaction limits
Second close · €550K · months 3–6Platform & security engineer: EU hosting, durable audit storage, uptime, audit readiness
Full round · €700K · by month 6Solutions engineer: connects the first customers’ agents and runs onboarding while the founder sells
11
The ask

Raising a pre-seed round from EU capital.

€700K

First close at €400K funds the founder and a founding engineer. A second close at €550K adds a platform and security engineer. The full €700K adds a solutions engineer, the audit and paid pilots.

Months 0–3Ten EU buyer calls, then the EU entity, first engineer, open-core launch
Months 3–6Slack and Teams approvals, Art. 12/14 evidence export and per-agent transaction limits ship; general availability on EU hosting
Months 6–126–8 paid design partners; third-party audit
Months 12–18€400K–€600K ARR and a seed round, before the December 2027 deadline
55% engineering
15% EU entity, hosting, compliance
20% pilots and go-to-market
10% buffer

ContactRoman Belfer · linkedin.com/in/roman-belfer