Safety record
pi-top safety record
DEPLOY has no incidents on file for pi-top. This rolls up incidents attached directly to pi-top, to its models, and to its deployments (operated or manufactured): the same graph as the company page's safety-record summary, shown here with full sourcing and exposure context.
Machine-readable surfaces
- Markdown mirror: /companies/pi-top/safety-record.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/safety/companies/1afe7bd9-6079-4cc3-9109-fe540196c91d/profile
- Data documentation: /data
- Query this programmatically: Deploy MCP
Incidents
No incidents on record for pi-top. Absence of a recorded incident is not proof of a clean operating history; it reflects what DEPLOY has tracked and verified to date.
Exposure
DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for pi-top. This is a genuine data gap, not a rounding to zero: no incident count above can be turned into a defensible rate without it. NHTSA's SGO dataset itself does not publish exposure denominators, and there is no standardized, regulator-verified nationwide source for AV fleet mileage or ride counts today. Where a company self-publishes a mileage figure, it is not independently audited and is not shown here as DEPLOY-verified data.
Common questions
What is pi-top's safety record?
Is pi-top safer than a human driver?
Does DEPLOY redact or omit crash details for pi-top?
Full company record: pi-top