Company · Nexus One

A true machine,
driven by OUPI.

A device the size of a book, placed in your home and connected to the OUPI cloud. It runs code for real, indexes your datasets on-site, works for hours on end, and controls your devices — webcam, printer, smart home, sensors, actuators.

Nexus One USB USB ETH HDMI GPIO HOLDS IN ONE HAND related to the OUPI cloud
a pocket PC that truly runs
Join the pilot program. See the business offer.

Also available in cloud version, without hardware · Initial deployments on selection

Why a machine

An agent who thinks is good.
An agent who has hands is something else.

A conversation does not connect a webcam, does not run for six hours on four hundred gigabytes, and does not turn on a light. It needs a machine of its own — and that is exactly what Nexus One is.

01

Execution sandbox

The code runs on a real machine, isolated from the rest of your system, with real resources and real permissions.

02

Local documentary research

Your corpora are indexed on the device. The documents go nowhere, and the querying does not depend on the bandwidth.

03

Long tasks

Hours of processing on large volumes, without session limits or interruptions after a few minutes.

04

Physical objects

Webcam, printer, home automation, sensors, arms: what is connected can be controlled, and what is controlled is part of a mission.

The principle

The cloud decides,
the machine acts.

Nexus One is not an isolated intelligence: it constantly works with the OUPI cloud, which orchestrates missions, mediates models, and keeps track. The box, on the other hand, provides what the cloud will never have — ports, dedicated resources, and the right to access your devices.

The two together create an agent that reasons like in your browser, but acts in your workshop.

o Nexus One · physical execution6 PERIPHERALSNEXUS ONEOUPI cloudORCHESTRATE AND SUPERVISEpermanent liaisonwebcamprinterhome automationsensorseffectorsstorageUSB · ETHERNET · SERIAL · GPIO · LOCAL NETWORKThe cloud decides, the machine acts on the real world.
a real machine, connected to real things
Governance

The agent proposes,
the signature provides.

An agent makes a mistake. Ours does too. That’s why the action power of the device is not determined by intelligence: it is defined by a policy cryptographically signed by the hardware owner.

Two layers that do not overlap. The Driver decides what to do — smart, fallible layer. The policy defines what is possible — deterministic layer, inviolable without your key. It's stronger than an administrator account: the perimeter is a signature, not a setting that gets forgotten.

o Governance · signed policyEd25519SMART BED — FALLIBLEThe driver decides what to do.CAN BE MISTAKENDETERMINISTIC LAYER — SIGNED BY THE OWNERThe policy defines what is possible.authorizedauthorizedrefusedauthorizedThe gesture is carried out — or it is abruptly halted.NEXUS IS NOT ROOT · THE SCOPE IS A SIGNATURE, NOT A SETTING
the agent proposes, the signature disposes
The anchor

Nothing is irreversible.
without a point of return.

Before each sensitive action, the unit freezes its state — including the physical position of its effectors, chopped and persisted. If the action fails or you refuse it, it rewinds back to that moment.

It is the most distinctive mechanism of the product, and the most reassuring when the machine interacts with real things.

o Anchor · return pointSAFE REELING1frozen stateanchor placed2the arm movesexecution3the take failserror detected4return to a frozen staterewindingTHE PHYSICAL STATE IS CHOPPED AND PERSISTEDNo irreversible action without a point of no return.THE ARM POSITION IS FIXED BY THE ANCHOR — THE STAMPING IS MECHANICAL
one can always return to the previous state
Three regimes

Of the atomic gesture
to the delegated mission.

According to the task, the device operates at three levels: discrete command controlled from the cloud, reactive behavior that loops locally when the round trip would be too slow, and delegated reasoning where it carries out a long mission within the framework you have signed.

A temporary cut does not break anything: the mission continues locally and resynchronizes when the link is restored.

o Execution regimes3 LEVELS1Discreet orderthe cloud commands, the device executestake a photogo to this position2Bounded reactive skilla perception → action loop, without feedbackavoid the obstacleFollow the play.3Local reasoningthe casing decides alone within the signed frameworklong mission hodiagnostic on ifNETWORK DEPENDENCE ↓AUTONOMY ↑
three ways to execute, from atomic gesture to autonomous mission
Nexus OS Cloud

The same system,
without equipment.

Nexus OS also exists as a cloud instance: created in a few minutes, sized according to the task, billed by the hour. It joins the same fleet as the devices, is managed with the same tools, and adheres to the same policies.

That's where we look for power when a dataset grows: we scale up, we add nodes, and the mission doesn't change one bit. Develop on the instance, deploy on the box — or run both.

o Nexus OS Cloud · sizingON REQUESTS2 vCPU · 4 GBM4 vCPU · 8 GBL8 vCPU · 16 GBXL16 vCPU · 32 GBSHORT TASKBIG DATANeed more? We’re adding knots to the fleet.+ AS MUCH AS THE MISSION REQUIRESTHE SAME FLEET, THE SAME MISSIONS — ONLY THE SIZE CHANGES
we're increasing power without changing tools

Three ways to do it

Only one is designed.
to act.

Conversation assistantHomemade mini-serverNexus One
Execute code on a real machine.Restrained sandboxYesYes, governed.
Tasks of several hoursNoAccording to the setupNatives
On-site indexed corpusNoTo writeUnderstood
Control of connected devicesNoTo writeUnderstood
Governed scope of actionWithout subjectSystem settingsSigned policy
Rewind on physical actionWithout subjectTo writeNative anchor
Supervision and traceabilityPartialTo writeFleet console
Power surgeWithout subjectNew machineInstances on demand
CommissioningImmediateSeveral weeksGuided pairing

Where it helps

Four plots of land
where a cat is not enough.

Home automation and premises

Lighting, openings, thermal, cameras, printers. The agent sees the state of the premises and acts on it, with the safeguard of the policy regarding what they are allowed to order.

Large documentary corpus

Hundreds of gigabytes indexed on-site, queryable without uploading and without waiting. The data stays with you.

Long treatments

Mass conversion, series analysis, calculations that take all night. The mission lasts and reports at the end.

Robotics and instruments

Straps, sensors, measurement benches. The perception-action loop occurs on the spot, the anchor makes each gesture reversible.

What the program includes

What is provided,
and what is subsequently billed.

Understood

  • The case, for you
  • Preinstalled and hardened Nexus OS
  • Guided pairing to your OUPI space
  • Policy profiles ready to sign
  • Fleet console and telemetry
  • Managed remote updates

Charged based on usage

  • The credits consumed by the missions.
  • The hours of cloud instance, if you create them
  • The OUPI seats of your users

The zero balance suspends, it never destroys: the disk is preserved.

What you do not pay

  • No hardware subscription.
  • No license per connected device.
  • No integration development to write.

Questions

What is being asked of us
before signing.

Does the box need internet?
Yes. Nexus One works in conjunction with the OUPI cloud, which orchestrates missions, arbitrates models, and keeps track. What remains local is the execution: the code, the document index, the working files, and the control of the devices. A temporary disconnection does not interrupt an ongoing mission — it continues and resynchronizes upon the return of the connection.
What is the difference with the cloud sandbox?
The cloud sandbox runs isolated code, with no access to the outside world and for short durations. The box provides three things it cannot offer: truly connected peripherals, dedicated resources for long processing, and a document index that resides on your network.
Who decides what the machine is allowed to do?
You. The scope of action is defined by a policy signed with your key. The intelligence suggests actions, the policy authorizes or blocks them, without human intervention each time. Ready-to-use profiles exist — laboratory, regulated, home automation — and can be assigned in one move.
What happens if the agent makes a mistake regarding a physical action?
An anchor is set before the action: the state, including the position of the effectors, is frozen and shredded. In case of failure or refusal, the box rewinds to that state. This is what makes a physical action reversible.
Do my documents leave the site?
Your document repository is indexed locally and not uploaded. What goes up to the cloud is what the mission needs to bring up: relevant excerpts, execution logs, deliverables. The rest remains unchanged.
What do we do when more power is needed?
We create a Nexus OS instance in the cloud, to the desired size, and we add as many nodes as the mission requires. The fleet is mixed: hardware and instances coexist, with the same tools and the same policies. The mission does not change one bit depending on where it runs.
Can we start without equipment?
Yes. Nexus OS in the cloud version runs the same system and allows for mission preparation. Only physical devices require a box.
Which devices can be connected?
What connects via USB, serial, local network, or through extension pins: cameras, printers, readers, home automation controllers, sensors, arms. The support for the pilot program covers the connection of specific equipment.

Let's talk about your land.

The pilot program is by selection, with support for implementation. Tell us what you are looking to do — that is the best starting point.

Join the pilot program. Our research work