OxOnOS · the operating system inside the Ox1 · Oxford, England
OxOnOS is the part of an Ox1 that took the years. It runs the AI on the machine in front of you, keeps your knowledge on it, and tells you — every time you look — where your thinking actually happened. What it sits on is our business.
This is the whole operating system. Not the highlights, not a tour of the good bits — the entire list of places an owner can be. Everything an Ox1 does, it does from one of these.
Home
The first thing the machine says — and it only says it after the checks have actually run. Ten of them passed. One needs an internet service this computer does not use, and rather than quietly counting that as a pass, the screen says so in the second line.
Two readings on this machine are marked Not checked. That is not a fault. It is the rule the whole operating system is built on, showing its working.
OxOnGPT
Ask it anything, in words. The answer is composed on this computer and nothing you type leaves the box. Conversations are kept here, named, and deleted by you — there is no copy of them anywhere else, including with us.
Open it on the machine’s own screen, or from any browser on your network. Nothing to install on the laptop; it is already on the network you are standing in.
AI
Everyday for the day’s work. Reasoning for the question that deserves a longer think. Coding for software. You pick a kind of thinking, not a filename — and switching is a click, because it is all on the machine already.
A model’s name is available to anybody who opens Technical details (for engineers). Nobody else has to see one. The reading to look at on this screen is the last tile: requests sent out, 0. Counted, not promised.
Kits
A Kit is a set of abilities added to the box. You hand it a job the way you would hand it to a person — read the three supplier quotes and tell me which to accept, with the reason — and it works here and leaves you the files and the argument.
Read the middle reading: where it thinks. On this machine, that Kit’s last job went out to a service on the owner’s own account, and the screen says so in as many words. An operating system that only tells you the flattering half is not reporting, it is marketing.
Apps
Opened without leaving OxOnOS, and — this is the part that matters — the apps are not allowed to ask the box for anything. No key, no account, no knowledge that an API exists. Which is why one of them answered a forest owner’s question on his own land, on a day with no signal at all.
And look at the greyed card. The box probed each app before offering it, one did not answer, and the screen says so: nothing was changed — this is what the box found when it looked.
Files
Nominate a folder and the machine can answer questions out of it. Text, Markdown, and PDFs with real text in them. A scanned PDF it cannot read is listed as skipped rather than quietly dropped — because a document you think was read and was not is worse than one you know was missed.
Nothing is uploaded anywhere. The file goes into a folder on this computer, and the screen says so on the panel you drop it into.
Activity
Newest first, and every line has one of three authors: you, your AI, or the system. You can read just one of them.
Including the unflattering lines. “A routine check found the AI engine slow to respond. It recovered on its own.” Nobody has to be told that. A machine that only logs its good days is not keeping a record, it is keeping up appearances.
Help
Not a help site, not a PDF for a product family — the addresses on it are this box’s addresses, and you can print it from the machine it describes.
One sentence on it is the acceptance test for the whole product, written where the owner can hold us to it: “If you are ever handed a command to type, that is a fault in this product and not something you did wrong.”
System
What the computer is called, who it belongs to, who may use it, what it may reach, and four ways back: restart, repair the AI, reset, factory reset. If it cannot start properly it is built to show a page that says what failed and what to do — a page designed to work when nothing else does.
The third row under Privacy is the one this entire page is named after, and you can read it in the picture.
Every picture above is a render of the build these machines are running, taken through the operating system’s own harness rather than drawn for this page. Figures we have not agreed to publish — speeds, timings, temperatures — were taken out rather than guessed at, which is why two readings on the Home screen say Not checked.
Underneath is plumbing, and plumbing is swappable. What you are buying is the layer above it — the one that decides what your machine knows, what it will do for you, and what it refuses to let out. Anybody can screw a graphics card into a case.
OxOnOS asks for a capability and never for a particular AI engine. The engine of the day is an implementation detail, and on the day a better one exists you do not buy a new computer — which is the opposite of how this industry has been selling to you.
An application asks for a kind of thinking, never for a filename. So the model is the disposable part and your knowledge is the part you keep. Today that is the wrong way round everywhere else, and it is what holds you where you are.
The machine is bound to you, by you, with a code you read off its own screen — and a key you keep in case you lose the device you read it on. There is no account with us. We could not reach your machine if you asked us to.
A graphics card cannot keep a promise.
An operating system can.
Those three words are not ours. They are the heading of a row on the machine’s own System screen, and underneath them the operating system explains itself better than any of this does.
“This is measured, not printed. OxOnOS derives this from where your AI actually ran and whether any request left the machine — every single time you look.”
OxOnOS · System › Privacy
Every computer you own has a settings page that asserts something about your privacy. This one derives it. The difference sounds like pedantry until the day the assertion is wrong and nothing on the machine is in a position to notice.
Verified
“Your AI answered from this computer. No data left the machine during the last request.”
Allowed
“OxOnOS itself is allowed to reach the internet, so it can use services you have connected — like a television subscription.”
0
Not a setting, and not a promise. A number, derived from what actually left the machine, and recomputed the moment you open the screen.
The thing most people get wrong about it
Pull the network lead out of the back and your AI carries on — that is the machine, and it is the demonstration we are proudest of. But OxOnOS is allowed out, because a television subscription, an update you asked for, and the time of day all live out there.
So the claim is not that nothing ever leaves. Anybody can make that claim and almost nobody can keep it. The claim is that the machine counts what left, shows you the number, and derives it from what happened rather than from a box somebody ticked. When the honest answer is can reach out, the screen says can reach out — in amber, on the Home screen, where the owner will see it without going looking.
It answers instantly because it asked a server, and the server told it. That is the only way a machine can know — which means every one of those reassuring “you’re up to date” ticks is a thing your computer phoned somebody to find out, on a schedule you did not set.
This one has not phoned anybody. So watch what it does with the question.
There is one sentence this operating system is not allowed to print, anywhere, ever: “up to date”. It does not ask the internet, and a computer of yours that answered an hour ago told you only what it said it was running. Neither is grounds for the claim, so the claim is not made. That rule is in the repository, not in a style guide.
The screens above are the shape. This is the part you would actually be doing on a Tuesday.
Not routed here, not cached here — composed on this machine, out of a model that is sitting on this machine’s graphics card. On the day your network is down, that is the difference between a quiet morning and no morning.
Your contracts, your notes, the three supplier quotes. The documents do not go anywhere to be read; the reading happens where they already are. And the machine lists what it could not read, which is the half everybody else leaves out.
This is the one to look at. Asked to draft from four of its own documents, the machine came back in one pass and said there were seventeen statements in its own draft it could not stand behind — each one marked in the document, each one explained at the foot of it. We did not teach it modesty. We taught it to say which parts it is guessing, because that is the whole difference between a tool you can use at work and a tool that is confidently wrong in front of a client.
Working software, written by your own machine, running on your own machine, for the one job nobody sells software for. A forest owner wanted to know whether to fell this year or wait twelve months. He now has a screen that answers it with his own prices.
The apps on the box are forbidden from asking the box for anything — no key, no token, no knowledge that an interface exists. It reads like a restriction. It is the reason an app answered its owner on a farm track on a day with no reception at all, and it is enforced in the product rather than promised in a document.
Add a machine and the fleet grows. That is the whole mechanism. Every Ox1 is a complete computer on its own; two or twenty of them introduce each other by hand, on your own network, with a code a person reads off one screen and types into another. No directory of your machines exists anywhere. Not here, not with anybody.
We left that picture exactly as the machine drew it. One computer answered. The other was never asked — this one does not know where it is at the moment, so it did not guess, and the card says so in those words. Look at what it refuses to tell you about that machine: not checked — nothing here knows what it holds. Not “nothing”, and not a stale number from last week. A diagram with three green links would have been easy to arrange and would have taught you nothing at all about this operating system.
There is nothing to sign up to. A person joins this computer by typing a six-character code shown on its own screen, once per device, and the code lasts ten minutes. Then the machine hands them a key to keep, in case they lose the thing they typed it on.
No accounts. No passwords.
A code, and a key you keep.
These are not from a brochure. They are in the repository, they are dated, and they are what gets cited when a decision about a feature has to go one way or the other. We are putting them on a public page because a rule you will not show anybody is not a rule, it is a preference.
Rule 06 is the one you can see from here. It is why two readings on the Home screen say Not checked instead of going green, why the Fleet screen leaves a machine amber rather than guessing, and why this operating system will not tell you it is up to date. On most equipment, a check that never ran is shown in green.
OxOnOS and the Ox1 were designed together. Nothing in it is adapted, ported, or wrapped around somebody else’s idea of a computer — which is what native means, and it is why you switch an Ox1 on rather than set one up.
An aluminium tower with a handle, built to order in Oxford, bought once and owned outright. The operating system is the part that took the years. The box is what we put it in, and the two were drawn at the same desk.
You do not put OxOnOS on an Ox1 any more than you put the engine in a car at the dealership. It is switched on, not set up — and that is the difference between an appliance and a computer somebody has to look after.
It was never written for one piece of hardware. If you build your own machines and you want an operating system that keeps the intelligence on them, we would like to hear from you. That is a conversation, not a waiting list.
Nobody is counted.
Not by the licence, and not by us.