qlaas machines, authorised by WorldAuth
Own the fleet. Own the authority.
Driverless vehicles, terminal automation and factory robotics, to be supplied and operated for business. Every consequential action is gated by your Mandate and leaves a signed Receipt.
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: ALLOW, STEP_UP or DENY, with its reasons. Actions involving people, public roads or leaving site step up to a named human.
One request, one answerSimulated AMR-07 → enter Dock 3 · carry 420 kg
- ALLOW
- STEP_UP
- DENY
- ✓ within scope dock/3
- ✓ 420 ≤ 450 kg
- ✓ before expiry
- obligation: reduced speed near people
Receipt.
Every outcome is signed and chained to the one before it, refusals included. Anyone can verify a Receipt offline.
Simulated ReceiptSimulated - Receipt
- RCPT·7F3A-09C2-E1D4
- Time
- Verdict
- ALLOW
- 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 verdict for one second. Every outcome, refusals included, leaves a Receipt. Hashes are computed in your browser.
- ALLOWWithin the Mandate. The action proceeds.
- STEP_UPA named human must co-sign first.
- DENYRefused, with its reason. Still receipted.
Gate · requestSimulated
AMR-07 → enter Dock 3 · carry 420 kg
MANDATE M-0112 v3 · scope dock/1..4 · max_kg 450
Awaiting a verdict.
Receipt ledger
No Receipts yet. Hold a verdict 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, step-up, revoke and the Receipt ledger. Built to run on any vendor's fleet.
- ALLOW · STEP_UP · DENY · 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
Fleet
Planned: managed autonomous fleets with supervision, maintenance and insurance arranged.
- supervised
- maintained
- insured
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 gate them, so authority reaches any manufacturer's machine without its manufacturer's permission. 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
Send 30 days of fleet logs. We run them against today's Mandates and show what would have been denied or stepped up. 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.
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 refused 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, offline, and checks them against today's Mandates. No gateway, no install. We reply within two working days.
- 01Two weeks, read-only
- 02A divergence report you keep
- 03Every Receipt stays yours
Begin
Find out who really holds the stop.
A Replay audit takes two weeks and reads logs you already have. You keep every Receipt.