“Where is unit 12 right now, what is its battery level, and what is it assigned to?”
Recent events plus latest-state projections, tuned for live maps, subscriptions, geospatial search, alerting and short-window replay.
Trusted autonomy
A verifiable record for every autonomous system
PhyTAU signs robot telemetry in hardware, PhyUDM gives it an open, vendor-neutral shape, and PhyCloud verifies and retains it — one trustworthy data layer that outlives any single vendor.
Robots are becoming autonomous. Proof hasn't kept up.
Robots now work next to people and increasingly act on decisions made by AI. Yet most cannot prove which machine they are, what software they ran, or that their records were not changed — and every vendor stores what they did in a different format.
Know which robot it was, and what it was running
PhyTAU gives every robot a hardware identity and proves which firmware and software it booted — so a record can be tied to a specific, uncompromised machine.
Reconstruct an incident without opening six products
Retrieve the complete history around an incident and replay a synchronised timeline across every source, with data gaps shown rather than silently omitted.
Prove what happened, and who looked
Telemetry signed on the robot, verified on arrival, stored append-only, with an audit trail over every search, export and share.
Change vendors without losing the record
Every robot speaks PhyUDM, the open-source data model, so your history lives in an open format you own — not inside whichever vendor you bought from last year.
Sign, represent, verify — as three separable concerns
Separating where trust is established from how facts are represented and how events are used is what turns a dashboard into an evidence architecture.
- 01
PhyTAU signs at the source
A hardware trust module on the robot captures telemetry from ROS 2, CAN and serial buses and signs it with a TPM-held key. PhyTrace SDKs and connectors bring in every other source.
PhyTAU - 02
PhyUDM represents the facts
The open-source, Apache-2.0 event model covering drones, ground robots, vehicles, cameras, sensors and the software systems around them. Implement it without buying anything.
PhyUDM - 03
PhyCloud verifies and retains
Checks device identity and integrity on ingest, then keeps the record in a hot store for today's operation and an open lakehouse for everything since.
PhyCloud
From trusted data to trusted autonomy
PhyTAU is a hardware trust module for robots. It starts by making every record verifiable, and grows into securing the robot itself and the AI agents that drive it.
PhyTAU
A TPM-based root of trust for commercial fleets: hardware identity, measured
boot and signed telemetry, fitted alongside the robots you already run.
PhyTAU Enterprise
A datacenter-grade root of trust for humanoids, defense and critical
infrastructure — built to attest the whole robot and to let you verify the
agents, models and policies in control before they act.
Events, media and actions are not the same problem
Treating them as one is how platforms end up storing video in event rows and letting a dashboard issue commands. PhyCloud keeps them on separate planes with different controls.
Event plane
Structured PhyUDM facts: identity, location, motion, health, mission and incident state, detections, annotations and provenance. Indexed for subscriptions, correlation and replay.
Media plane
Video, audio and high-volume sensor data stay in governed object storage or your existing VMS. PhyCloud holds a catalog of stream references, time bounds, permissions and hashes — not the bytes.
Action plane
Commands carry materially greater risk than observation, so they are isolated: explicit connector capabilities, step-up authentication, human confirmation and full command audit.
A hot store for right now. A lakehouse for everything since.
You should not have to know which tier holds an event. Query by source, incident, geography or time window and PhyCloud plans the retrieval across both.
“Across last year's missions, where did communication dropouts correlate with carrier coverage?”
Canonical history in open columnar files — for multi-year analysis, AI, compliance and bulk export. Managed by us, owned by you, or both.
Moving an event into long-term storage never breaks the trust model: the original event hash and its verification result stay with it.
Built for robots in the real world
Wherever autonomous machines work alongside people, the questions after an incident are the same: which robot, what software, and what exactly happened.
Make your robots provably trustworthy
We are working with robot OEMs and operators on the first PhyTAU deployments. Tell us about your fleet and what you need to be able to prove.