Which CenterOS hardware configurations are certified?

This public site does not claim a certified hardware configuration. Hardware validated and Certified Cell statuses require evidence for an exact model, firmware, driver, calibration, Asset and Cell configuration.

Live at Robotics Center · 2026

One runtime.
Many robot bodies.

Q: Is CenterOS hardware agnostic?

CenterOS provides hardware-independent orchestration while preserving hardware-specific adapters, kinematics, limits and safety behavior. Support is configuration-specific.

Q: Can I install CenterOS with pip today?

The Python SDK, CLI and MCP interfaces are currently an early-access developer preview, not an unrestricted public package.

Q: Does CenterOS replace the robot safety controller?

No. CenterOS owns session orchestration, authorization, recording, adapter access and release gates. Vendor controllers, safety PLCs and hardware emergency stops retain real-time functional-safety responsibility.

CenterOS connects arms, hands, cameras and tactile sensors through one versioned Cell Runtime—then turns every operation into synchronized data and auditable evaluation evidence.

Explore the live concept ↓ Launch CenterOS ↗

Native adaptersEdge-first safetyEvidence by default

Illustrative example · Reference configuration

cell-runtime / preview● simulated session

Reference Cell Manifestexample_cell_01 · v1.4

CENTEROSRUNTIME

ARMxArm 7Native adapter

HANDWujiSynergy + tactile

VISIOND455RGB-D · 30 FPS

POLICYRelease v17Shadow mode

clock sync 0.8 ms recording shadow

THE OPERATING PRINCIPLE

Hardware-independent orchestration.
Hardware-specific truth.

CenterOS does not pretend every robot is the same. It unifies sessions, intent, clocks, recording, evidence and release gates while preserving each device’s native kinematics, force control, tactile layout and safety limits.

ONE CELL SESSION

From connection to learning loop.

A single record follows the physical system from configuration through operation, data, evaluation and support.

Illustrative workflow

01 / 05

Compose a versioned Cell

Select exact Assets, firmware, drivers, sensors, calibration and a safety profile. CenterOS creates an immutable Cell Manifest rather than a loose list of brands.

Asset and serial-number genealogy
Capability and adapter contracts
Calibration and safety preflight

PRODUCT EVIDENCE

See the complete Cell loop.

A 30–60 second field recording will show the actual hardware, operator actions and resulting evidence as one continuous run.

Awaiting authorized footage

No simulated or stock video is presented as product evidence.

The published recording will cover xArm, Wuji and camera connection; teleoperation; synchronized replay; CLI/MCP calls; and evaluation evidence output.

Connect
Teleoperate
Replay
Call CLI / MCP
Review evidence

MULTI-VENDOR BY DESIGN

Bring the hardware your task requires.

Support is configuration-specific. A brand or model advances only when the evidence for that exact configuration advances.

Catalog

Known model; no control integration claim.

Adapter contract

Capability and interface contract defined.

Experimental

Adapter work exists; not production validated.

Hardware validated

Tested on the named hardware configuration.

Certified Cell

Evidence applies only to an exact Cell configuration.

UFactory xArm collaborative robot — UFactory xArm

ROBOT ARM

UFactory xArm 5 / 6 / 7

Joint and Cartesian intent, state, workspace constraints and session recording.

Adapter contractIntegration details →

ROBOT ARM

Franka FR3

Research-grade manipulation with native impedance and force capabilities preserved.

Adapter contractIntegration details →

TELEOP SOURCE

Wuji Glove

Glove input tracked separately with its own retargeting profile.

Experimental

REALSENSEProduct image not shown

VISION

Intel RealSense

RGB-D streams, calibration, timestamps and dropped-frame evidence.

Adapter contractIntegration details →

VISION

Stereolabs ZED

Stereo streams, intrinsics, extrinsics, timestamps and dropped-frame evidence.

Adapter contract

ORBBECProduct image not shown

VISION

Orbbec

RGB-D observations and timing metadata under a model-specific contract.

Adapter contract

TASHANProduct image not shown

TACTILE

Tashan

Contact and force sensor family listed for integration discovery.

Catalog

TACTILE

PaXini

Contact, pressure and force sensor family listed for integration discovery.

Catalog

Truth boundary: these labels describe integration maturity, not blanket compatibility or motion authority. “Hardware validated” and “Certified Cell” apply only to a named model, firmware, driver, Asset, calibration and Cell configuration backed by verified evidence. No card above claims either stage. Product photography is shown only for the named product; text-only cards deliberately do not reuse another brand’s image.

ONE SYSTEM · THREE INTERFACES

Use CenterOS where your team works.

Operate through the visual platform, automate from the terminal, or give an AI agent governed access through MCP.

Early-access API preview

The SDK, CLI and MCP examples show the intended developer experience. Public installation and production access are not yet generally available.

quickstart.py

from centeros import CenterOS

os = CenterOS()
cell = os.cells.load("cell_xarm7_wuji_d455")

with cell.session(mode="teleop") as run:
    run.capture(contract="manipulation.v1")
    run.arm.move_cartesian(delta=[0.02, 0, 0])
    run.hand.grasp("precision")

evidence = run.evaluate("pick_place.v2")

Same object model

Platform, SDK, CLI and MCP operate on the same Organization, Cell, Session and Evidence records.

Scoped authority

API keys and agent tools inherit tenant, role, Cell and action permissions.

Auditable by default

Every command carries identity, timestamp, manifest hash, acknowledgement and evidence linkage.

MODEL CONTEXT PROTOCOL

Let agents work with robots—without giving them the keys to everything.

CenterOS exposes governed tools for discovery, planning, simulation, evidence review and approved Session actions. High-risk motion remains behind capability and release gates.

cells.listsessions.plandatasets.inspectruns.replayevals.comparecases.create

Illustrative example · No motion authority

centeros-mcp example tool trace

agent

Find Cells compatible with wrist RGB-D and tactile capture.

tool

cells.list organization=demo capability=capture.rgbd+tactile

2 reference configurations found

xArm 7 + Wuji + D455 experimental

Franka FR3 + BrainCo + ZED Mini adapter contract

agent

Create a simulation-only Session plan for the first Cell.

tool

sessions.plan mode=simulation authority=no_motion

✓ Example draft Session createdNo physical motion authority granted

THE DIFFERENCE IS EVIDENCE

Every run leaves a usable record.

CenterOS answers the question that matters: under which real conditions can this policy complete this task, reliably and economically?

Illustrative example · Synthetic values

EXAMPLE RUN VERDICT

Garment fold · Reference Station A

Not ready to scale

POLICYv17example release

→

ENVIRONMENTv1.4Reference configuration

→

RUNS50illustrative count

→

SUCCESS82%illustrative metric

Example finding: tactile drift after thermal warm-up.

Example finding: glare failures in one camera angle.

Example next action: targeted capture, recalibration, re-evaluate.

This card demonstrates the evidence format. It is not a published benchmark, certification result or claim about a deployed Cell.

DESIGNED FOR REAL SYSTEMS

Cloud orchestration.
Edge execution.
Native safety.

CLOUD

CenterOS Platform

Organization · Cell config · policy release · data contract · evidence · support

low-frequency orchestration

EDGE

Cell Runtime

Safety supervisor · time sync · calibration · recorder · policy runner · local buffer

native adapters

HARDWARE

Vendor SDK + Safety Controller

Arm · hand · camera · tactile · hardware estop · safety PLC

CLEAR BOUNDARIES

Frequently asked questions.

What is available today, what remains in preview, and where functional-safety responsibility stays.

Is CenterOS hardware agnostic?

It provides hardware-independent orchestration, but never erases hardware-specific truth. Native adapters, kinematics, limits, firmware and safety behavior remain configuration-specific.

Can I install CenterOS with pip today?

Not as an unrestricted public package. The Python SDK, CLI and MCP interfaces are in an early-access developer preview; request access for the current supported path.

Does CenterOS replace the robot safety controller?

No. CenterOS handles session orchestration, authorization, records, adapters and release gates. Vendor controllers, safety PLCs and hardware emergency stops retain real-time functional-safety responsibility.

Which configurations are certified?

This public site does not claim a certified configuration. Hardware validated and Certified Cell require verified evidence for the exact model, firmware, driver, calibration, Asset and Cell configuration.

DEVELOPER PREVIEW · LIVE DEMO

Tell us what you want to build.

Share your current hardware and goal. We will use this information only to prepare a relevant CenterOS preview, API access conversation or on-site demo.

No account required.This static form opens your email client. Nothing is sent to a third party or stored by this page.

SEE IT IN PERSON

Build one Cell.
Keep the whole learning loop.

Visit Robotics Center for a live walkthrough of multi-vendor operation, synchronized capture, MCP/CLI workflows and evidence-first evaluation.

Book a CenterOS demo ↗Open the platform →

One runtime.Many robot bodies.

Hardware-independent orchestration.Hardware-specific truth.

From connection to learning loop.

Compose a versioned Cell

See the complete Cell loop.

No simulated or stock video is presented as product evidence.

Bring the hardware your task requires.

UFactory xArm 5 / 6 / 7

Franka FR3

Universal Robots e-Series

AgileX PiPER

Nero

Trossen

OpenArm

Wuji

BrainCo

Linkerbot

Sharpa

MANUS Gloves Pro

Wuji Glove

Intel RealSense

Stereolabs ZED

Orbbec

Tashan

PaXini

Use CenterOS where your team works.

Same object model

Scoped authority

Auditable by default

Let agents work with robots—without giving them the keys to everything.

Every run leaves a usable record.

Garment fold · Reference Station A

Cloud orchestration.Edge execution.Native safety.

CenterOS Platform

Cell Runtime

Vendor SDK + Safety Controller

Frequently asked questions.

Tell us what you want to build.

Build one Cell.Keep the whole learning loop.

One runtime.
Many robot bodies.

Hardware-independent orchestration.
Hardware-specific truth.

Cloud orchestration.
Edge execution.
Native safety.

Build one Cell.
Keep the whole learning loop.