Loom · early access
An operations engine that builds itself.
Describe your process in plain language. Loom, together with you, authors the workflows, the tools, and the screens, then runs the process with human approval gates and a full record.
What process should Loom run for you?
workflow gets its own identity · spend + invocation grants · every decision in the ledger
If you can’t list what’s running, you can’t audit it.
On Layr8Every Loom workflow holds its own identity, spends nothing it wasn’t granted, and lands every allow and deny in the ledger.
How it runs
Deterministic where it can be. Intelligent where it must be.
The LLM helps author the workflow, and can modify or enhance it at any time. Inside the workflow, LLM steps run only where judgment is needed: scoring a survey response, drafting a message. Everything else is deterministic pipeline, so cost stays flat as volume grows and the same input gives the same result.
An operator describes a process in six verbs. Loom turns them into pipelines, and the operator’s view is a live board: stages, counts, and, on each lane, the access it needs.
Collect
Pull the inputs the process needs from the systems your team already uses.
deterministicCheck against rules
The rules of the deal, the playbook, the policy. Same input, same result.
deterministicAsk me first
A human approval gate wherever a person should decide.
human gateDraft
The LLM step, only where judgment is needed: a message, a score, a summary.
LLMNotify
Tell the right people, where they already are.
deterministicRepeat
On a schedule or on demand. Every run on the record.
deterministicTwo lanes are not like the others. The human gate and the LLM step are where judgment lives; everything around them is pipeline. That split is why cost stays flat and results stay reproducible.
Running today
What operators run on it.
Prequalify subcontractors
Find, survey, score, and qualify trade partners. Exceptions reach a human; the rest runs itself.
Check closing documents
Transaction documents and agreements checked against the rules of the deal before anyone signs.
Review to your playbook
Review pipelines built to a firm’s own playbook, with every decision on the record.
All three run on the same engine. A new domain is configuration, not code. Bring us yours →
Workflow identity
Workflows never hold credentials.
Every workflow has its own identity, a W3C DID it controls. What it may spend and who may call it are two independent, revocable credentials. Every tool it reaches is a message whose grant the platform evaluates; the credential itself stays in the Key Shield.
A grant is a document your security team can read, not a checkbox an application claims to have honored.
The substrate
Everything that differentiates it is the substrate.
In August we deleted Loom’s own authorization machinery. Not refactored. Deleted. A policy an application enforces internally is invisible from outside: remove the code and every call is authorized again, with no error anywhere. The answer now lives in a credential the platform checks.
- Agent and workflow identities are minted and held by the node. The application signs nothing.
- Every tool call is a message whose grant the platform evaluates before it runs.
- Revocation is a platform status list, verifiable from outside the application.
- Allow and deny decisions land in the node’s ledger, not in application logs.
Loom ships inside each customer’s Space: a per-customer isolated deployment with the directory, the grants, and the decision ledger in one place. What’s a Space? →
Sales-led while it earns its stripes.
Development partners in construction and real estate, with workflows live in production. No GA claims, no invented logos. Your engineers can check our work first: the field report.