One box, two jobs, and they fight.
Your writing wants its model resident and instant. Your pictures want the whole card for a minute at a time. Put both on one machine and one of them waits.
OX1 · Oxford, England · Built to order
A computer with the AI built in, running its own operating system. One machine answers a room of eight. Bought once, outright, with no subscription ever, and nothing leaves the building.
A practice, a studio, a firm of fifty, a lab. You took the work to a hosted AI. Six things followed.
Yours to wire together, and every request leaves the building.
Private, and a second job.
Easy, metered, and processed somewhere you have not seen.
Finished, private, bought once.
Two of these four depend on somebody else's computer. Act 03 shows you what that means.
None of that is a software problem.
It is a location problem.
Plug it in and ask it something. It reads, drafts, answers and writes code — all of it on the processor inside this case, built to ship with the models already on the disk. Nothing to sign up for, nothing to subscribe to, and no command line at any point.
The object
Take a point on the machine. The graphics and the storage are yours to specify. The rest is the same on every Ox1 we build.
Six points marked. Tab to them, or hover.Six points marked. Touch one.




If your data ever needs to leave the building,
that is what the handle is for.
What one box carries
Eight people asking at the same time, on the same box. Not eight licences — eight colleagues on the office network, each with their own work, and one invoice that was paid once.
The operating system
Nine plain screens. You pick a tier in words, not model names, and the machine gets on with it.
What makes it OxOnOS
Anybody can screw a graphics card into a case. OxOnOS is the part that took the years — and it is the part that decides what your machine knows, what it will do for you, and what it refuses to let out.
Point every AI you use at this box and your canon stays on it — your files, your decisions, your project state, the accumulated context that is the thing you would actually miss. Today that lives inside somebody’s product and it is what holds you there. Put it here and you can close the account: the model is what you swap, and the knowledge is what you own.
The cloud model is sometimes better. Fine — use it. When a job genuinely needs one, OxOnOS assembles the smallest package that job requires, sends only that, checks the answer here, and folds the useful part back into your own knowledge. We do not argue that the frontier is worse. We arrange that it does not get to keep anything.
Mark something private and it does not leave, whatever you ask for afterwards. The part that works out what a model needs to see is the same part that decides what is allowed out — one gate, not a setting you can forget to tick. Only what you allowed ever leaves, and the machine writes down exactly what did.
It is the only thing in the chain that can see what one model actually did to your work against what another one did. Not a benchmark, not a review site, not a vendor’s own chart — your jobs, on your material. So it can tell you to stop paying for something, and there is nothing in it for us when it does.
Not a preference — the acceptance test. If a person has to open a command line to own this machine, we have failed the brief we wrote for ourselves. And a bad update cannot take the box with it: it keeps the version that worked, and you go back to it from the screen in front of you.
On the machine today
The five claims above are the shape of the operating system, and the column beside each one tells you honestly how far along it is. This is the other half of that answer: what is already in the machine, read off real hardware rather than written for a web page.
The third one 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 difference between a tool you can use at work and a tool that is confidently wrong in front of a client.
A demonstration. Both machines are answering the same question.
“Which invoices in this folder are still unpaid?”
“Which invoices in this folder are still unpaid?”
Reconnecting…
Everything that stopped
was running on somebody else's computer.
This is what you are buying.
The whole machine, opened from the side. Three of the six points are yours to specify. Act 04 puts a price on them.
Two things leave this box.
Heat, out of the back. The answer, to you.
The Ox1 is a node, not a limit. Add a box when the work grows, and the work spreads across them. No rack. No cluster. No licence. Nothing in the middle, and nobody counting. More than one Ox1 is an Intelligence Fleet.
Your writing wants its model resident and instant. Your pictures want the whole card for a minute at a time. Put both on one machine and one of them waits.
Give each job its own machine and the argument disappears. You carry on asking questions while the other one works. Two unlike jobs on two machines is simply a truer description of the work — and the third unlike job gets the third box.
An Ox1 is complete on its own and complete in a fleet. There is no minimum, no maximum, no edition that unlocks the next one. You buy the next box when the work asks for it, and not before.
Hand the fleet a job and it goes to the machine with room for it. Each box keeps its own intelligence, its own documents and its own answer. The task travels. Your knowledge never does.
No controller, no console, no licence server, no register of anybody’s machines — here or anywhere. A box that wants to work with another box asks the person who owns them both.
Every other answer to growth is somebody else’s arrangement getting larger. This one is yours getting larger. A fleet is boxes you own, on floors you control, introduced by you, divisible between your own jobs, and extendable on a Tuesday afternoon with a purchase order and a mains socket.
Built to order
In Oxford · one at a time · to your specification
More than that on any line — more disk, more memory, a second card built to order — tell us what the work is and we will build to it. These are made one at a time. And when the work outgrows a machine, you add another one. There is no bigger one to sell you.
There are cheaper computers. There is nothing else that arrives with the intelligence already in it, and nothing else that lets you stop paying.
Then: nothing. No subscriptions, ever.
You buy the machine and that is the last invoice. No plan, no seat, no tier, no renewal. The AI runs on your own computer, on OxOnOS — our own AI operating system, built for this machine and included with it.
So it does not add a bill, it removes one — the work happens here now, and what you were paying somebody else for, you stop paying.
Nobody should pay £29.99 a month for something they used £4 of. That is the whole business model you are being asked to leave.
Your arithmetic, with your own number
Whatever that number is, it bought you nothing you still own.
We work out what the machine needs to do, and what it needs to be. You are not buying anything in that conversation.
OX1 is the centre of Oxford, and the machine is designed and supported from inside it. The company is British and the people in it answer the phone. A product that promises to keep your data in one place should be made by people who can be found in one place.
What’s coming · your own boxes first, then everybody’s
It begins with your own two machines, introduced to each other by you. It ends somewhere larger: owners who opt in lend the hours they are not using, earn credit, and spend it the day one box is not enough. Nothing ever joins anything unless its owner says so, and your own work always goes first.
There is no register of your machines anywhere, and there will not be one. A box that wants to work with another box asks the person who owns them both. That is the whole mechanism, and it is the reason we can build a network without becoming the thing the network exists to avoid.
The machines are built in OX1,
one at a time, to the specification
you give us.
Tell us what the work is. We will tell you what the machine needs to be, what it would cost, and when it could be on your desk. No commitment, and no newsletter — nobody here has time to write one.
Investors and partners: choose the last option and we will reply ourselves.
A page selling privacy ought to be able to show you its own.
Did it send anything to another company?
Not checkedDid it set a cookie?
Not checkedIs anything else on this device watching you read it?A web page cannot see past its own tab, so this one will not pretend to. On an Ox1 you own every layer, and every layer can be checked.
Could not checkThree answers, never two. The Ox1 reports its own health the same way — working, failed, or could not check — and a light that never ran its check is never shown green. On most equipment it would be.