An AI box installed on your premises, run by Oupi
A real machine,
driven by Oupi.
A pocket PC that really executes.
A book-sized box that sits at your place and connects to the Oupi cloud. It really runs code, indexes your datasets on-site, works for hours on end and controls your devices — webcam, printer, home automation, sensors, actuators.
An agent that thinks is good. An agent that has hands is something else.
A conversation can't plug in a webcam, run for six hours on four hundred gigabytes, or turn on a light. It needs a machine of its own — and that's exactly what Nexus One is.

Analyze this year's statements and print the summary.
The cloud decides, the machine acts.
Nexus One isn't an isolated intelligence: it works continuously with the Oupi cloud, which orchestrates missions, arbitrates between models and keeps a record. The box, for its part, brings what the cloud never will — ports, dedicated resources, and the right to touch your devices.
Together, they make an agent that reasons like it does in your browser, but acts in your workshop.

The agent proposes, the signature decides.
An agent makes mistakes. So does ours. That's why the box's power to act isn't decided by the intelligence: it's defined by a policy cryptographically signed by the hardware's owner.
Two layers that never overlap. The Conductor decides what to do — the intelligent, fallible layer. The policy defines what's possible — the deterministic layer, impossible to tamper with without your key. It's stronger than an administrator account: the perimeter is a signature, not a setting you forget to lock back down.

Nothing irreversible without a way back.
Before every sensitive action, the box freezes its state — including the physical position of its actuators, hashed and persisted. If the action fails or you refuse it, it rewinds to that exact moment.
It's the product's most distinctive mechanism, and the most reassuring when the machine touches real things.

From the atomic action to the delegated mission.
Depending on the task, the device works at three levels: the discrete command driven from the cloud, the reactive behavior that loops locally when a round trip would be too slow, and delegated reasoning, where it runs a long mission itself within the framework you've signed off on.
A temporary outage breaks nothing: the mission carries on locally and resyncs when the connection returns.

The same system, no hardware.
Nexus OS also exists in the Oupi cloud: it's Nexus Cloud, created in a few minutes and sized to the task. In time, every Oupi user will have their own. It joins the same fleet as the devices, is driven with the same tools and obeys the same policies.
That's where you go for more power when a dataset grows: you scale up, add nodes, and the mission doesn't change by a single line. Develop on the instance, deploy on the device, or run both.

Only one is built to act.
| Chat assistant | Makeshift mini-server | Nexus One | |
|---|---|---|---|
| Runs code on a real machine | Restricted sandbox | Yes | Yes, governed |
| Tasks lasting several hours | No | Depends on the setup | Native |
| Corpus indexed on-site | No | To be written | Supported |
| Control of connected devices | No | To be written | Supported |
| Governed scope of action | Not applicable | System settings | Signed policy |
| Rollback on physical actions | Not applicable | To be written | Native anchor |
| Oversight and traceability | Partial | To be written | Fleet console |
| Scaling up | Not applicable | New machine | On-demand instances |
| Time to go live | Immediate | Several weeks | Guided pairing |
Four fields where a chat isn't enough.
Home automation and premises
Lighting, openings, heating and cooling, cameras, printers. The agent sees the state of the premises and acts on it, with the policy as a safeguard on what it's allowed to control.
Large document corpora
Hundreds of gigabytes indexed on-site, searchable without uploading them and without waiting. Your archive stays with you.
Long-running jobs
Bulk conversion, series analysis, calculations that take all night. The mission goes the distance and reports back at the end.
Robotics and instruments
Arms, sensors, test benches. The perception-action loop plays out on-site, and the anchor makes every move reversible.
What's provided with the device.
Supported
- The device is yours
- Nexus OS preinstalled and hardened
- Guided pairing with your Oupi workspace
- Policy profiles ready to sign
- Fleet console and telemetry
- Governed remote updates
What we're asked before you sign.
Does the device need internet?
Yes. Nexus One works in tandem with the Oupi cloud, which orchestrates missions, arbitrates between models and keeps a record. What stays local is execution: the code, the document index, the working files and the control of your devices. A brief outage doesn't interrupt a mission in progress — it carries on and resyncs when the connection returns.
How is it different from the cloud sandbox?
The cloud sandbox runs isolated code, with no access to the outside world and for short durations only. The device brings three things it can't offer: peripherals that are actually plugged in, dedicated resources for long-running jobs, and a document index that lives on your network.
Who decides what the machine is allowed to do?
You do. The scope of action is defined by a policy signed with your key. The intelligence proposes actions, the policy authorizes or blocks them, with no human intervention needed each time. Ready-to-use profiles exist — laboratory, regulated, home automation — and can be assigned in a single step.
What happens if the agent makes a mistake on a physical action?
An anchor is set before the action: the state, including the position of the effectors, is frozen and hashed. If the action fails or is refused, the device rewinds to that state. This is what makes a physical action reversible.
Do my documents leave the site?
Your document collection is indexed locally and is not uploaded. What goes up to the cloud is only what the mission needs to send: relevant excerpts, execution logs, deliverables. Everything else stays put.
What do we do when more power is needed?
We rely on Nexus Cloud, at the size you need, and add as many nodes as the mission requires. The fleet is mixed: devices and instances work side by side, with the same tools and the same policies. The mission doesn't change by a single line, wherever it runs.
Can we get started without hardware?
Yes. Nexus Cloud runs the same system and lets you prepare missions. Only physical peripherals require a device.
Which devices can be plugged in?
Anything that connects via USB, serial, local network or expansion pins: cameras, printers, readers, home automation controllers, sensors, arms. The pilot program's support covers connecting specialized hardware.
Let's talk about your field.
The pilot program is selective, with installation support included. Tell us what you're looking to do — it's the best place to start.