CenterOS · Robotics Center Request access
Developer preview · Documentation v0.1

Build one auditable robot Cell.

CenterOS gives teams one versioned object model across heterogeneous hardware, teleoperation, synchronized capture, policy runs, evaluation evidence and support.

Early accessConfiguration-specificNo public production package yet

Overview

One control and evidence contract—not one fake robot abstraction.

CenterOS unifies identity, authorization, Session orchestration, clocks, recording, task contracts and evidence. Vendor-specific kinematics, force modes, tactile layouts and safety states remain inside Native Adapters.

Availability: examples below describe the intended early-access interface. They do not claim that unrestricted pip install centeros, autonomous motion, or every listed adapter is publicly available.

Quickstart

From a versioned Cell to a recorded Session.

  1. Request organization-scoped access.API credentials are issued for a named organization, team and allowed environment.
  2. Enroll an Edge Runtime.The Edge host connects vendor SDKs, sensors and the local safety supervisor.
  3. Publish a Cell Manifest.Bind exact Assets, firmware, drivers, calibration and a safety profile.
  4. Run preflight.Resolve capability, authorization, clock, calibration and safety findings.
  5. Create a Session.Teleop, shadow, capture and eval operate inside the same auditable envelope.
Python · interface preview
from centeros import CenterOS

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

report = cell.preflight()
report.require_ready(mode="teleop")

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

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

Object model

The complete physical genealogy.

01

Organization

Tenant boundary for users, teams, API keys, Assets and evidence.

02

Asset

One physical device: serial number, model, firmware, ownership and service history.

03

Cell

A versioned combination of arm, hand, sensors, compute, fixtures and calibration.

04

Environment

The Cell plus scene, task, software, action/observation contract and verifier.

05

Session

Authorization and recording envelope for teleop, shadow, canary or policy execution.

06

Run and Evidence

One execution with commands, observations, results, interventions, cost and findings.

Cell Manifest

Motion authority is configuration-specific.

A catalog listing never grants control. A Manifest must resolve exact hardware and software identity before a Session can request motion.

cell.yaml · illustrative
apiVersion: centeros.roboticscenter.ai/v1alpha1
kind: CellManifest
metadata:
  name: cell_xarm7_wuji_d455
  version: 1.4.0
spec:
  assets:
    arm: {model: xArm7, serial: "SN-REQUIRED", firmware: "PINNED"}
    hand: {model: Wuji, serial: "SN-REQUIRED", firmware: "PINNED"}
    camera: {model: RealSense-D455, serial: "SN-REQUIRED"}
  driverBundle: "centeros-edge/PINNED"
  calibration: "calibration://REQUIRED"
  safetyProfile: "safety://REQUIRED"
  authority: experimental

Placeholder values must be replaced and verified. This example does not authorize physical motion.

Session lifecycle

Plan → preflight → operate → capture → evaluate → support.

Draft→Preflight→Ready→Active→Finalizing→Evidence sealed
ModePurposeTypical authority
SimulationValidate task and interface semantics without physical motion.No hardware authority
TeleopHuman-controlled operation and synchronized demonstrations.Supervised, local safety active
ShadowObserve policy outputs without applying them to actuators.Read-only actuator path
CanaryRestricted physical validation after a release gate.Explicit scope and limits
AutonomousProduction execution after customer-controlled safety approval.Not implied by this preview

Interfaces

Visual Platform, Python SDK, CLI and MCP share one truth layer.

CLI

Operator and CI workflows for login, preflight, Sessions and evidence export.

Read CLI preview →

MCP

Governed AI-agent tools for discovery, planning, replay and approved actions.

Read MCP preview →

Platform

Human interface for organization, Cell, operation, data, eval and support workflows.

Open Platform →

Data and evidence

Every useful conclusion stays bound to physical conditions.

A valid Run can record monotonic timestamps, actuator commands, joint state, poses, RGB/RGB-D, tactile observations, operator events, interventions and verifier output. Evidence references the immutable Cell and Environment versions.

Data ContractRequired modalities, rates, schemas and ownership.
EpisodeSynchronized observations, actions and provenance.
FindingFailure classification, evidence and next action.
Release GateVersion-bound acceptance decision—not a universal score.

Authentication and authorization

Keys belong to organizations—not anonymous machines.

  • Organization and team membership constrain record visibility.
  • API keys carry scopes, expiration and allowed environments.
  • Cell allowlists and Session authority constrain actions.
  • Commands carry identity, sequence, monotonic timestamp, TTL and manifest hash.
  • Cloud services cannot remotely clear a physical emergency stop.
Environment variables · names may change during preview
CENTEROS_API_URL=https://api.example.invalid
CENTEROS_API_KEY=issued_per_organization
CENTEROS_ORG_ID=org_example
CENTEROS_ENVIRONMENT=simulation

Errors and recovery

Failures must tell the operator what is safe to do next.

ClassMeaningExpected response
AUTH_REQUIREDNo valid user or API-key identity.Authenticate; do not retry motion.
AUTHORITY_DENIEDIdentity lacks organization, Cell or action scope.Request access from an administrator.
PREFLIGHT_FAILEDManifest, calibration, clock or safety finding blocks the mode.Resolve findings and rerun preflight.
COMMAND_EXPIREDTTL elapsed or command arrived out of order.Discard; establish a fresh local lease.
EDGE_UNAVAILABLEEdge heartbeat or adapter is unavailable.Enter controlled stop and inspect locally.

Safety boundary

Control access is ours. Functional-safety certification is not.

CenterOS owns

  • Session orchestration and authorization
  • Adapter contracts and command envelopes
  • Recording, provenance and evidence
  • Release gates and support workflows

Native safety layer owns

  • Hardware emergency stop
  • Safety PLC and certified interlocks
  • Real-time torque and motion protection
  • Site-specific risk assessment

Integration maturity

Support language has five explicit levels.

StatusPublic meaning
CatalogKnown product; no CenterOS control claim.
Adapter contractCapability and interface contract defined.
ExperimentalAdapter work exists; not production validated.
Hardware validatedTested on a named model, firmware, driver and configuration.
Certified CellEvidence-backed acceptance applies only to one exact Cell and task scope.

Early access

Bring your exact hardware configuration.

Tell us the arm, hand, camera, tactile sensor, task, site and timeline. We will respond with the current integration status and the safest next step.

Request API keyJoin developer preview