# Skydio Secondary at San Mateo: deployment

Canonical ID: `b55f03d2-4a72-4f35-b23f-a9537eaa994b`

Secondary product deployment at Skydio (Inspection) operational region.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** skydio-inspection-secondary-deployment
- **Status:** operational
- **Model:** [Skydio Secondary](/models/skydio-inspection-secondary.md) (id: `5a018bd0-beb7-4e3e-83e5-284cdf3c71e0`)
- **Company:** [Skydio (Inspection)](/companies/skydio-inspection.md) (id: `8dd6b067-5de5-46b5-aac5-03baba8b3938`)
- **Location:** [San Mateo](/locations/san-mateo.md) (id: `0ff2111c-1f07-4028-9a6c-b077ef7d3c73`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the Skydio Secondary deployment at San Mateo?

Skydio Secondary, built by Skydio (Inspection), is recorded as a deployment at San Mateo on the DEPLOY registry. Skydio (Inspection) operates the deployment directly.

### Who operates Skydio Secondary at San Mateo?

Skydio (Inspection), the manufacturer of Skydio Secondary, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the Skydio Secondary deployment at San Mateo?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/b55f03d2-4a72-4f35-b23f-a9537eaa994b · feeds: GET /v1/feeds?deploymentId=b55f03d2-4a72-4f35-b23f-a9537eaa994b · canonical URL: /deployments/skydio-inspection-secondary-deployment_