PhyWare
Talk to us

Open source · Apache-2.0

PhyUDM One open language for every robot

Every robot vendor ships its own telemetry format. PhyUDM gives them all one shape — so a record from any machine in your fleet can be searched, compared and verified the same way.

View on GitHub Read the specification
Why it matters

Your data, in a format you own

PhyUDM is the format PhyTAU signs and PhyCloud stores. Because it is open, the value of your record never depends on any single vendor — including us.

No lock-in

Your operational history is stored in an open, documented format. Switch robot vendors, analytics tools or cloud providers and the record comes with you.

Verifiable by anyone

Auditors, insurers and regulators can inspect the specification and validate records against it themselves, without relying on PhyWare.

Built to evolve

Domain modules and registered vendor extensions add detail without breaking existing integrations. Changes go through a public review process.
Coverage

Not every source is a robot

The common envelope describes humanoids, drones, vehicles, fixed sensors and software systems without pretending they are all the same thing.

  • Ground robot
  • Humanoid
  • Drone / UAV
  • Fleet vehicle
  • Fixed camera
  • Mobile camera
  • Environmental or acoustic sensor
  • Industrial controller
  • Operations software
  • Video management system
  • Edge gateway

Built for investigations

Every event can carry incident_id, mission_id, case_id and correlation_id; site, zone and geospatial geometry; detections, alerts, assignments and annotations; data classification, retention and legal-hold state; media references; source clock quality; and full lineage, including signed provenance from PhyTAU. That is what lets a timeline across five vendors' machines line up.

Open source

Everything you need to adopt it

  • The PhyUDM specification and JSON Schemas
  • Event and source taxonomies
  • Versioning rules and a vendor-extension registry
  • A conformance suite with canonical fixtures
  • Validators, generators and command-line tools
  • Client SDK contracts and connector interfaces
  • A lightweight local event store for development
  • An independent provenance verifier
PhyUDM on GitHub

Standardise your fleet's data

Adopt PhyUDM on your own, or let PhyWare run verified ingest, storage and evidence for you with PhyCloud.

Talk to us Explore the docs