Prove it yourself
Traceless means a service’s code and data never touch the disk of the machine that runs it. Run the proof on a machine you have: one line, every test live, nothing left behind. Or see what we measured.
One live machine, watched every five seconds
0 bytes written to its disk by any service
The proof in four scenes
About ten minutes on a machine you have, from the line you paste to the verdict. Here is all of it in under a minute.
1What it is
One line joins a Linux machine you control — a cloud VM, a server, a laptop — to your free Omnira account for the length of the proof. Omnira then runs test services on it, from memory, and sends them real requests.
2What it proves
PASS needs all three. A fourth, T5, fingerprints every file before and after, and you can search the disks for a secret of your own.
The numbers are from a real run on 7 October 2026, on a Linux VM in Google Cloud.
3How it runs
Or connect your own Google Cloud (Sovereign Omnira or Enterprise plan): the proof makes the machines for you, and deletes them at its time limit.
4Where to look
The proof page draws your machine while it runs. Five places tell the story.
Tested again · 10 October 2026
We ran an Omnira hub and an edge runner in Google Cloud, sent 500 requests to 50 services — every one pinned to the runner — and read the runner’s disk before, during and after. Here is the whole run on film: every value on screen is a real command’s output.
The film didn’t load.
That was the whole run.
The full report — every record, and how we checked each step — is available under NDA.
What we measured
We sent requests to a Linux machine in our fleet, every one of them aimed at that machine and no other, and read its disk every five seconds.
Everything else the disk received came from the operating system itself: its clock, and its record of failed logins from the internet.
Tested again · 3 October 2026
We made a Raspberry Pi the only machine serving for an Omnira hub, recorded every write to its storage, then took its card out and read every byte of it on another computer.
Was it really the Pi answering? Later that evening we traced 14 of 14 requests to it by its device id, 5801277142788769303, in three separate records: ours, the hub’s and the Pi’s own.
The full report — how we set it up, every record, and how we checked each step — is available under NDA.
Run it yourself
Any Linux machine you control — a cloud VM, a server, a laptop. One line turns it into one of your Omnira devices for the length of the proof, then every test runs on it while you watch.
Two minutes, a code by e-mail, no card. You land on the proof page.
The page gives you one line. Run it as root on the machine. It joins your account and the proof starts; nothing is installed for the proof itself.
Requests go to that machine and only it; its own log is checked against ours. The page shows what the services wrote to its disk (0 bytes), and the search of every disk for the proof’s secret.
Type any phrase; the machine’s disks are searched for it. Restart its runner mid-proof. Fingerprint every file before and after.
The machine’s own terminal prints every test and the verdict, with the commands to check them with the machine’s own tools.
End the proof from the page: its two test sites are archived and removed, the requests stop, and the machine is left as it was.
What the machine’s own terminal prints
$ (echo OMNIRA_PROOF_CODE=…; curl -fsSL https://omnira.dev/prove.sh) | sudo bash prove: checked in — the proof page now shows this machine prove: watching this machine’s disk; the proof page shows it live PASS — no customer bytes on this machine’s disk T1 Which device served: pass — 697 of 697 answered requests are in this machine’s own log T2 What the services wrote to the disk: pass — the services wrote 0 bytes T4 Your secret, searched across the disk: pass — 0 of 133659 files hold the proof’s phrase T5 Before and after: pass — 2 fingerprints taken # Look yourself, with this machine’s own tools: find … -newermt, ls -lrt, cat /proc/<runner>/io
Linux machines today. Mac and phones are next.
Members on the Sovereign Omnira or Enterprise plan can also start a full proof in a Google Cloud project they control: two machines — a hub that keeps the services, and an edge runner that serves every one of them from memory — with up to 100 services, watched live and deleted at the time limit.
Start one from the proof pageQuestions
You don’t have to. The machine is yours: its own terminal prints every test, the script is readable shell, and each result comes with the command to check it with the machine’s own tools.
On a machine you have: nothing — a free account, no card. In your own Google Cloud: no charge from Omnira; your cloud provider bills the two machines while they run, and the proof deletes them at the time limit.
It joins the machine to your Omnira account as a device and starts the proof. The proof itself installs nothing and keeps its working files in memory. When you end it, its two test sites are removed and the machine is left as it was; your account’s device can be removed from your devices page.
T1: every request we sent is in the machine’s own log. T2: how many bytes the proof’s services wrote to its disk (0). T4: every disk on the machine searched for the proof’s secret, or one you type. T5: every file on its disks fingerprinted before and after.
Every five seconds: how much the disk received, and how much each program on the machine had ever written to it. The 29 services had written nothing since they started. The operating system and the runner’s once-a-minute save account for everything else.
The full technical report of the Raspberry Pi test is available under NDA. Ask us and we will walk you through it.
Create your account in about two minutes — free, no card needed — and paste one line.
Already have an account? Sign in
