# R-Storm Flagship at Beijing: deployment

Canonical ID: `856ddc34-efa1-4d84-86cc-39670576f6ae`

Aggregate deployment at R-Storm Technology headquarters.

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

_Last updated: 2026-06-08_

- **Slug:** r-storm-hq-deployment
- **Status:** operational
- **Model:** [R-Storm Flagship](/models/r-storm-flagship.md) (id: `580d6a46-a02d-4cab-af45-5624b43b0bdb`)
- **Company:** [R-Storm Technology](/companies/r-storm.md) (id: `7250ba47-0494-483b-a70e-aa7359809acf`)
- **Location:** [Beijing](/locations/beijing.md) (id: `4dcea30f-1b34-41af-9aa0-f1440e395b68`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.r-storm.com/

## Common questions

### What is the R-Storm Flagship deployment at Beijing?

R-Storm Flagship, built by R-Storm Technology, is recorded as a deployment at Beijing on the DEPLOY registry. R-Storm Technology operates the deployment directly.

### Who operates R-Storm Flagship at Beijing?

R-Storm Technology, the manufacturer of R-Storm 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 R-Storm Flagship deployment at Beijing?

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/856ddc34-efa1-4d84-86cc-39670576f6ae · feeds: GET /v1/feeds?deploymentId=856ddc34-efa1-4d84-86cc-39670576f6ae · canonical URL: /deployments/r-storm-hq-deployment_
