Skip to content

PhyWare Documentation

The operator-owned data plane for physical operations. PhyTrace and connectors acquire data, PhyUDM defines what an event means, and PhyCloud retains and serves it — live, historically, or in storage you control.

Get started with an SDK Read the PhyUDM spec

The platform

  • PhyUDM

    The open, Apache-2.0 event model for drones, robots, vehicles, cameras, sensors and the software systems around them. Implement it without buying anything.

    PhyUDM Docs

  • PhyTrace

    SDKs and connectors that capture source data and normalise it into PhyUDM, with buffering, retry and transport handled for you.

    PhyTrace Docs

  • PhyCloud

    Ingest, stream, index, correlate, govern and replay events across a hot operational store and a long-term PhyUDM lakehouse.

    PhyCloud Docs

  • phyware CLI

    Scriptable, machine-readable access to the platform — with a published command catalog for AI agents.

    CLI Reference

Applications

  • PhySafe

    Safety rules and alerting evaluated against live PhyCloud events and latest-state projections.

    PhySafe Docs

  • PhyComp

    Compliance evaluation, evidence mapping and reporting, with lineage from every finding back to its source events.

    PhyComp Docs

SDK Install Docs
Python SDK pip install phytrace-sdk Python SDK Docs
Rust SDK cargo add phytrace-sdk Rust SDK Docs

Getting Started

  1. Install an SDK — choose Python or Rust based on your platform
  2. Configure an agent — point it at your robot's APIs
  3. Emit PhyUDM events — validated against the open schema before they leave the device
  4. Query, subscribe and replay — through PhyCloud, the CLI, or your own tools