First product
qlaas Site Authority.
The owner console for UK sites where the owner, operator and site host are different parties, which is exactly where a signed Receipt settles who did what.
Fig. 01 — Site AuthoritySimulated
- Request
- HUM-01 → open DOOR 7
- Mandate
- M-0112 · v3
- Verdict
- Step up
- Awaiting
- Co-signer · supervisor
The console
In the console.
01 / 06
Decisions
Allow, step up and deny, with reasons and obligations such as reduced speed near people.
Site-wide, timed from the click to the first refused command.
30 days of logs checked against today's Mandates, producing a divergence report.
A signed, hashes-only bundle mapped to one regime.
A yard tractor buys a charging slot within its spend ceiling.
MCP tools to list assets, request actions and verify Receipts.
Simulated site
The demo depot.
A simulated UK depot with a closed-OEM humanoid governed only at door 7, an autonomous yard tractor, an AMR tote robot, and the depot's doors, docks and chargers.
Gate · door 7
HUM-01 → open DOOR 7 · Step up
Floor plan: docks 1 to 4 along the north wall, door 7 between the warehouse and the yard, chargers A to C on the east wall. HUM-01 waits at door 7 for a step-up decision, then continues once allowed.
Receipts
Verify it yourself.
Every Receipt verifies offline with a dependency-free kit. It proves authorisation, not safety or lawfulness.
Sample Receipt
Simulated
{
"id": "RCPT·C74A-B9E9-169C",
"ts": "2026-09-24T14:02:11Z",
"verdict": "ALLOW",
"mandate": "M-0112 v3",
"request": "HUM-01 → open DOOR 7",
"obligation": "co-signed",
"prev": "3b0d51c7e2a9",
"simulated": true,
"hash": "c74ab9e9169c56d24b8c097fdfdc5e58a13648ce913fa271afbaf4b04cf2aed5"
}
Begin
Find out who really holds the stop.
A Replay audit takes two weeks and reads logs you already have. You keep every Receipt.