Aarloven
Live runs today use a simulated firmware and small sample tools, not real firmware · up to 3 live starts a day for the whole site
Agree the checks, run them. Get a signed receipt.
The robot vacuum page shows, with a synthetic example, how a buyer and a robot maker would agree the tests before delivery and both get the same signed receipt, with PASS or FAIL for each agreed test. Here you can run four of its tests on a simulated firmware model: pick the firmware and the floor, and the room runs them and signs the receipt. Real robot firmware tests come next, with design partners.
The two CRM buttons are live runs of our CRM sample case in the room. Run a sample replays a recorded room run of 5 Oct 2026 in this page, with our sample package.
Play the buyer: test a simulated robot vacuum firmware update
In this example, your office robots run firmware 4.2.1 and the robot maker wants to ship 4.3.0. You agreed five tests with them before it goes out; four run here. Pick the firmware and the floor, and the room runs the tests and signs the receipt. Try 4.3.0 on the January floor.
Simulated: the firmware is a model with three settings (lane speed, heading drift, and whether a dark mat is mistaken for a drop, like a stair), not real firmware. The office and its floor are synthetic, the same as on the robot page.
A live run: if the room is off, this press starts it, in about 30 seconds (one of the 3 starts a day shared by all visitors). The tests then take a second or two; the page waits up to 150 seconds for the answer. This tab also runs the same published model and tests, to compare with the room's answer.
Play the buyer: check a vendor's chart tool
A vendor sells you a small tool that turns a table into a bar chart. Type the numbers, pick the points you want checked, and choose the version. The room runs the vendor's tool on your table and sends back each check's result and a signed receipt; this page then shows the chart the checks were run on. Try a negative number with version 2.0.
A live run: if the room is off, this press starts it, in about 30 seconds (one of the 3 starts a day shared by all visitors). The tests then take a second or two; the page waits up to 150 seconds for the answer. Use made-up numbers here. Real deliveries are tested in the design-partner pilot. It is free, runs for six weeks on one real delivery, and you can leave any time. There are three places. This tab also runs the same published tool and tests on your table, to compare with the room's answer.
Where the test runs, and how it is protected
This browser seals your table with the tool and the checks; only the room can open the package, and it deletes its working copy when the run ends. The names and reasons of the checks come back sealed to a key made in this tab.
The room is an AWS Nitro Enclave in Stockholm. An enclave is a sealed compartment inside an AWS server, isolated from its parent EC2 instance. Its attestation, signed by AWS, reports the measurement of the enclave image that is running, which you can compare with the published measurement of our room code; the code itself is public to read. More from AWS
Sample result — not your data · sealed room, Stockholm —
Press a button above: Run the vendor's build or Run a buggy build for a live run, Run a sample for a recorded one.
Can we agree the acceptance tests before delivery? Hi, To make acceptance quicker, we would like to agree with you up front which tests the delivery must pass, and run them with Aarloven. We would both get the same signed PASS or FAIL receipt, test by test. Aarloven is at an early stage and is looking for three design partners. The pilot is free, runs for six weeks on one real delivery, and invites both buyer and vendor: https://aarloven.com/partner You can try a sample run here (a live run can take about 30 seconds to start): https://aarloven.com/try Would you be open to setting this up for our next delivery?Room build, read from the AWS-signed attestation document and checked in this browser: · PCR0
- PCR0 is the fingerprint of the room's code. The PCR0 that counts is the one above, from the AWS-signed document. The "room code" shown in the steps is what the host reported while streaming.
- "The host tried to open it and AWS refused" is reported by the host, outside what AWS signs; the AWS CloudTrail unlock log is where to check it.
- Check a saved receipt offline: github.com/yu-faye/aarloven-room,
node rerun.mjs. The signed daily public log is in the same repository, under public-log.
Run it on your own data, sealed in this browser
Use test data here. Real deliveries are tested in the design-partner pilot. It is free, runs for six weeks on one real delivery, and you can leave any time. There are three places. Change the data below, or paste your own in the same shape. Your browser makes your key and seals the case: your data, the vendor's build and the agreed tests. Only ciphertext leaves this page. The room opens it with a key AWS KMS releases to the room alone, and its details come back sealed to your key.
Build:
Look at the request in your browser's network panel: only the sealed package goes out. Your key stays in this tab.
Technical details, and how to check it yourself
The room's answer
- Status
- Waiting for a run.
Check it yourself
curl -sO https://aarloven.com/samples/espocrm-1-v1.3.sealed.json curl -s https://aarloven.com/v1/receipt -H 'content-type: application/json' --data-binary @espocrm-1-v1.3.sealed.json git clone https://github.com/yu-faye/aarloven-room && node aarloven-room/rerun.mjs v1.3
The second line asks the room, and works while the room is on (press Run above first). The third runs the same published tests on your machine and prints the same checks and fingerprints as the room's receipt. The case is public at /samples/espocrm-1: the agreed points, the data, the tests and both builds.