# Ottobock Flagship at Duderstadt: deployment

Canonical ID: `7b4132be-e121-499e-b844-8b32aa488c45`

Aggregate deployment at Ottobock headquarters and primary operational region.

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

_Last updated: 2026-06-08_

- **Slug:** ottobock-hq-deployment
- **Status:** operational
- **Model:** [Ottobock Flagship](/models/ottobock-flagship.md) (id: `e0446384-ba32-40a9-98c5-8c584b7e3e26`)
- **Company:** [Ottobock](/companies/ottobock.md) (id: `135e1e83-1345-4fee-b258-e349b065345d`)
- **Location:** [Duderstadt](/locations/duderstadt.md) (id: `5166305e-bb62-4dbc-aebe-4465931d51b8`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.ottobock.com/

## Common questions

### What is the Ottobock Flagship deployment at Duderstadt?

Ottobock Flagship, built by Ottobock, is recorded as a deployment at Duderstadt on the DEPLOY registry. Ottobock operates the deployment directly.

### Who operates Ottobock Flagship at Duderstadt?

Ottobock, the manufacturer of Ottobock Flagship, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the Ottobock Flagship deployment at Duderstadt?

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/7b4132be-e121-499e-b844-8b32aa488c45 · feeds: GET /v1/feeds?deploymentId=7b4132be-e121-499e-b844-8b32aa488c45 · canonical URL: /deployments/ottobock-hq-deployment_