# R-Storm Secondary at Beijing: deployment

Canonical ID: `8728963b-1221-4e1d-841c-e8b2d4e76a2b`

Secondary product deployment at R-Storm Technology operational region.

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

_Last updated: 2026-06-08_

- **Slug:** r-storm-secondary-deployment
- **Status:** operational
- **Model:** [R-Storm Secondary](/models/r-storm-secondary.md) (id: `d477abd6-0d9f-4fa5-b79a-cc20009bae9a`)
- **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://rover.report

## Common questions

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

R-Storm Secondary, 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 Secondary at Beijing?

R-Storm Technology, the manufacturer of R-Storm 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 R-Storm Secondary 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/8728963b-1221-4e1d-841c-e8b2d4e76a2b · feeds: GET /v1/feeds?deploymentId=8728963b-1221-4e1d-841c-e8b2d4e76a2b · canonical URL: /deployments/r-storm-secondary-deployment_