# Starship Secondary at San Francisco: deployment

Canonical ID: `cf041edf-032a-4b2a-b91d-0d8cb42e79e9`

Secondary product deployment at Starship Technologies operational region.

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

_Last updated: 2026-06-08_

- **Slug:** starship-technologies-secondary-deployment
- **Status:** operational
- **Model:** [Starship Secondary](/models/starship-technologies-secondary.md) (id: `a3a42591-5168-4337-8a05-55fad62ed0e4`)
- **Company:** [Starship Technologies](/companies/starship-technologies.md) (id: `05630ae8-f210-43e1-91d7-218bbefbfa45`)
- **Location:** [San Francisco](/locations/california/sf-bay-area/san-francisco.md) (id: `0d5aa2e8-c47a-41e2-b0b9-ccfbf395e193`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the Starship Secondary deployment at San Francisco?

Starship Secondary, built by Starship Technologies, is recorded as a deployment at San Francisco on the DEPLOY registry. Starship Technologies operates the deployment directly.

### Who operates Starship Secondary at San Francisco?

Starship Technologies, the manufacturer of Starship 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 Starship Secondary deployment at San Francisco?

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/cf041edf-032a-4b2a-b91d-0d8cb42e79e9 · feeds: GET /v1/feeds?deploymentId=cf041edf-032a-4b2a-b91d-0d8cb42e79e9 · canonical URL: /deployments/starship-technologies-secondary-deployment_