Prove it yourself
Don’t take our word for it. Look at the disk.
Traceless means a service’s code and data never touch the disk of the machine that runs it. We measured it on a live machine serving 29 services. Soon you can run the same proof in your own cloud, and look for yourself.
- Free account
- No card
- A code by e-mail — no password
One live machine, watched every five seconds
0 bytes written to its disk by any service
What we measured
One live machine. 29 services. Nothing of theirs on its disk.
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.
- 227requests served by that one machine
- 0 byteswritten to its disk by any of the 29 services, since each one started
- 86,572files and folders on its disk, every one accounted for
- 1 a minutethe only Omnira write: its runner saving its own sealed state
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
A Raspberry Pi as the only server. Nothing left on its card.
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.
- 43requests it served, for five services
- 32 GBits whole card, read byte by byte on another computer
- 0copies of the phrase it served or of its services’ text, in files or in deleted data
- 1 a minutethe only Omnira write while it served: its runner saving its own sealed state
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.
Coming soon
Run the proof in your own cloud.
The Traceless Compute Proof sets up a private Omnira in a cloud account you control, fills it with services, and lets you watch, and check, every step.
-
1
Connect your cloud
Connect a cloud account you control. Everything that follows runs there, not with us.
-
2
A temporary licence, nothing to pay
Omnira issues a short-lived licence for the proof. No membership needed.
-
3
Your own Omnira, installed for you
One machine becomes your Omnira hub and keeps its storage on its own disk. A second machine runs the work.
-
4
Up to 100 services
Websites, APIs and AI services of every size, each one set to run on the second machine and nowhere else.
-
5
Watch it live
The Traceless Compute Proof dashboard shows the second machine’s disk while requests pour in. Send your own, too.
-
6
Look for yourself
Log in to both machines and list the files. The hub’s disk grows as services arrive; the second machine holds only the Omnira runner and its settings.
What you will see on the second machine
$ ls -lrt omnira-runner the Omnira runner state/ its own settings and sealed state # 100 services running, none of them on this disk
Until it opens, we will show you the proof live on our own fleet.
Questions
What people ask first.
Why should I trust a dashboard you built?
You don’t have to. Both machines run in your own cloud account: log in and list the files yourself.
What does the proof cost?
No Omnira membership is needed. The two machines run in your cloud account, so your cloud provider bills you for them while they run.
What exactly did you measure?
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.
Can I read the full report?
The full technical report is in review. Ask us and we will walk you through it.
Check it on your own machine.
Create your account in about two minutes — free, no card needed.
- Free account
- No card
- A code by e-mail — no password
Already have an account? Sign in