Agent-native company operating substrate

The operating system
for the autonomous company.

Deterministic substrate, probabilistic agents. lagstyr is the governed universe your company runs on — where bounded agents do the work, the kernel keeps every fact true, and humans are reserved for judgment.

Request early access How it works

The state of the company

Every company today is either islands or sprawl.

failure mode 01

Islands

The same customer has different identifiers in billing, the CRM, and a signed contract. Nothing joins. No agent — and no human — ever sees the whole picture.

failure mode 02

Sprawl

Five databases adopted on day one, each half-owning the truth. Drift sets in, and a permanent sync tax is paid forever after.

lagstyr collapses both into one coherent universe — where every entity has one identity, and every fact has one authority.

One coherent substrate

Not a database. Not an automation layer.
The ground the company stands on.

  1. one identity

    Every entity has a single canonical id. Everything links back to it — and that linking is the universe.

  2. one authority

    Every fact has one authoritative home. Authority is sacred; projections are disposable and rebuildable at will.

  3. one memory

    An append-only log records what changed and when. No row is ever written without naming its source.

  4. one action surface

    Every agent action passes a single governed, typed chokepoint. Agents are never pointed at raw tables.

Deterministic execution, driven by agents

Agents execute. Humans decide.

The reasoning may be uncertain. The record may not. Agents reason over projections and evidence, but their output becomes authoritative only by passing a governed write surface — so company truth is never probabilistic.

propose

An agent drafts a change. It cannot commit it.

approve

A human reviews and authorises — re-authenticated, proposer excluded.

commit

Only then does the kernel write it, and emit the event in the same breath.

read

Look, never touch.

write_safe

Routine writes, deterministically spot-checked into a review queue.

write_governed

Proposed by an agent, then approved by a human.

write_kernel

The company's spine. Approval required; the proposer can't sign off.

An agent starts with nothing — no shell, no filesystem, no ambient reach. It is handed exactly the skills its role requires. The confine is the grant.

Bring your own cloud

Your company. Your cloud. Your boundary.

Each customer runs its own deployment — kernel, workers, database, storage — inside its own cloud account. Your record data never crosses its trust boundary.

Isolation by deployment

Not by row. One tenant, one deployment, one boundary — no shared multitenant blast radius.

No vendor reach-in

No licence check, heartbeat, or telemetry sits on any runtime path. The only channel is outbound, signed, and carries no record data.

Operable in the dark

The data plane runs fully with the vendor unreachable. Your company doesn't depend on ours being online.