qlaas · Agents and machines
Infrastructure for autonomy.
Private communication between agents. Clear authority for machines. Connect across platforms, with access and permissions held by you.
Scroll to explore
Fig. 01 — MandateWorldAuth
- Mandate
- M-0112 · v3
- Issuer
- owner key ··· 4F2A
- Scope
- RT-07 · zone 3
- Action
- drive ≤ 25 mph
- Until
- 2026-09-30T18:00Z
- State
- Active
The missing layer
Machines are arriving faster than anyone can prove who controls them.
Fleet tools tell machines what to do. Identity tools say which machine is which. Policy engines decide in the moment and forget.
A model’s plan is not permission.
Nothing proves, across vendors, that a named owner authorised a specific physical action, within scope, before an expiry.
How it works
Three steps between intent and motion.
Authority is written once, checked on every request and recorded every time. Nothing moves on a plan alone.
Mandate.
You write the scope in plain language: which machine, where, what, and until when. It compiles to an exact, signed WorldAuth Mandate that only you can issue or revoke.
Plain language, compiledSimulated “Let AMR-07 use Docks 1–4, carrying up to 450 kg, until Friday 18:00.”
MANDATE M-0112 v3scope {asset: AMR-07, zone: dock/1..4, action: move|carry, max_kg: 450}not_after 2026-09-30T18:00Zsig ed25519 ··· 9C1E
Gate.
A person, a warehouse system or an AI agent requests an action. The Gate answers once: accept, hold or decline, with its reasons. Actions involving people, public roads or leaving site are held for sign-off by a named human.
One request, one answerSimulated AMR-07 → enter Dock 3 · carry 420 kg
- Accept
- Hold
- Decline
- ✓ within scope dock/3
- ✓ 420 ≤ 450 kg
- ✓ before expiry
- condition: reduced speed near people
Receipt.
Every outcome is sealed and linked to the one before it, declines included. Anyone can verify a Receipt offline.
Simulated ReceiptSimulated - Receipt
- RCPT·7F3A-09C2-E1D4
- Time
- Decision
- Accepted
- Mandate
- M-0112 v3
- Prev
- 3B0D…A9
- Hash
- 5e2c…41f0
A Receipt proves authorisation happened. It does not prove the action was safe or lawful.
Demo · simulated request
You hold the Gate. Try it.
Hold a decision for one second. Every outcome, declines included, leaves a Receipt. Hashes are computed in your browser.
- AcceptWithin the Mandate. The action goes ahead.
- HoldHeld for sign-off: a named supervisor must sign off first.
- DeclineNothing is dispatched, and the reason is recorded in a Receipt.
Gate · requestSimulated
AMR-07 → enter Dock 3 · carry 420 kg
Mandate M-0112 v3 · docks 1–4 · up to 450 kg
Awaiting a decision.
Receipt ledger
No Receipts yet. Hold a decision to issue one.
Machines
Every machine answers to its owner.
qlaas is being built to supply, prepare and operate the autonomous machines already at work in business, installing each one under your Mandate before it moves.
01 · Driverless vehicles
Driverless ride-hailing already runs in several cities. qlaas will prepare robotaxi and depot fleets for private sites, and gate every depot move, charge and hand-over under your Mandate.
- Gated at
- Depot gates, chargers, dispatch work orders
- Example Mandate
- Vehicle RT-07 · depot + zone 3 · drive · ≤ 25 mph in depot
Platform
One authority layer. Every machine behind it.
Govern
Gateway, console, adapters, Mandate composer, sign-off, revoke and the Receipt ledger. Built to run on any vendor's fleet.
- Accept · Hold · Decline · Revoke
- Mandate composer
- Receipt ledger
Evidence
Site packs mapped to the Machinery Regulation, AI Act, CRA, PLD and UK AV Act roles. Hashes only, no footage.
- 1 bundle → 1 regime
- hashes only
Prepare
Capability manifests and site manifests for doors, lifts, docks and chargers, plus integration.
- manifest
- doors · lifts · docks · chargers
Units
Sovereign quarantine appliances for machines you already own. The machine itself stays unmodified.
- quarantine
- unmodified machine
- Planned
Fleet
Planned: managed autonomous fleets, with supervision and maintenance, and insurance arranged through partners.
- supervision (planned)
- maintenance (planned)
- insurance via partners (planned)
Commerce
Machines buy charging, dock and parking slots from sealed offers, within the owner's spend ceiling.
- sealed offer
- spend ceiling
LaterAssuranceDefence and security autonomy assurance. A separate entity, later.
Explore Site Authority
Works with the fleet you have
Govern the door, not the motor.
Every site already controls four chokepoints: work orders, the building, the network and the credentials. qlaas is designed to govern them for the owner, so the owner's authority applies at those chokepoints, whichever manufacturer built the machine, without needing access to its controller. A closed humanoid still needs the door to open.
- CP-01Work ordersTasks reach a machine only after the Gate checks them against the owner's Mandate.
- CP-02Doors, docks, chargersThe building answers to the owner, so even a closed machine waits at the door.
- CP-03Network egressCommands and data leave site only on the routes the Mandate allows.
- CP-04API credentialsCredentials are scoped, time-boxed and revocable by the owner.
Start without risk
Replay first. Enforce when you're ready.
- Free
Stage 1: Replay
Run 30 days of fleet logs against today's Mandates and see what would have been declined or held for sign-off. It's free, and nothing touches the command path.
Stage 2: Shadow
Commands flow as normal. The Gate records what it would have decided.
Stage 3: Advisory
Decisions go to supervisors before dispatch.
Stage 4: Enforcing
The Gate decides on non-safety commands.
Your log is processed in your browser; the raw rows never leave it. A report is saved only if you choose to save it. See pricing for every stage
The stop is yours
No back door. Not even ours.
Owner-held keys.
Authority starts with you. Agents can never mint it.
Revoke, site-wide.
One action withdraws authority, timed from the click to the first declined command.
Fails closed.
If the Gate is unreachable, no new consequential command is dispatched and machines go to safe hold. A safety hold is never blocked.
Time-boxed support.
Any qlaas remote access is a Mandate you issue and can revoke.
qlaas is a non-safety supervisory layer. It sits above the manufacturer's certified safety controller and never replaces the e-stop.
The deadlines are set
Regulation now asks for evidence.
Cyber Resilience Act
Reporting obligations now apply: an early warning within 24 hours, a notification within 72.
Product Liability Directive
Transposition deadline. Defect can be presumed in complex cases.
Machinery Regulation
Machines must record legitimate and illegitimate interventions.
Evidence exports map one signed bundle to one regime.
Not legal advice.
Introduction
Start with a Replay audit.
A Replay audit reads 30 days of logs you already have and checks them against today's Mandates. No gateway, no install. Run it yourself in the console, or tell us about your site and we'll run it with you.
Your log is processed in your browser; the raw rows never leave it. A report is saved only if you choose to save it.
- 01Self-serve, or with us within two weeks
- 02A divergence report you keep
- 03Every Receipt stays yours
Begin
Find out who really holds the stop.
A Replay audit reads logs you already have. Run it yourself in minutes, or ask us to run it with you within two weeks. It's free.