# TurtleBot Secondary at San Francisco: deployment

Canonical ID: `1df1b0ce-893a-4993-b409-d6b243ca1889`

Secondary product deployment at TurtleBot operational region.

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

_Last updated: 2026-06-08_

- **Slug:** turtlebot-secondary-deployment
- **Status:** operational
- **Model:** [TurtleBot Secondary](/models/turtlebot-secondary.md) (id: `34e0a879-cd22-494f-b8d6-42a140d8715b`)
- **Company:** [TurtleBot](/companies/turtlebot.md) (id: `1da6ae1d-33c6-4af8-9200-f086586967f2`)
- **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 TurtleBot Secondary deployment at San Francisco?

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

### Who operates TurtleBot Secondary at San Francisco?

TurtleBot, the manufacturer of TurtleBot 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 TurtleBot 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/1df1b0ce-893a-4993-b409-d6b243ca1889 · feeds: GET /v1/feeds?deploymentId=1df1b0ce-893a-4993-b409-d6b243ca1889 · canonical URL: /deployments/turtlebot-secondary-deployment_