# WORX Secondary at Suzhou: deployment

Canonical ID: `6456721e-f3fb-4d39-b29d-8ba7e3e90ce1`

Secondary product deployment at WORX Landroid operational region.

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

_Last updated: 2026-06-08_

- **Slug:** worx-landroid-secondary-deployment
- **Status:** operational
- **Model:** [WORX Secondary](/models/worx-landroid-secondary.md) (id: `7d74abeb-d4b7-4bb7-a78e-4923e54aec08`)
- **Company:** [WORX Landroid](/companies/worx-landroid.md) (id: `460e0f3c-b979-4669-9968-65031762803f`)
- **Location:** [Suzhou](/locations/suzhou.md) (id: `7319aef8-bd1f-415c-864a-2060e3fdac39`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the WORX Secondary deployment at Suzhou?

WORX Secondary, built by WORX Landroid, is recorded as a deployment at Suzhou on the DEPLOY registry. WORX Landroid operates the deployment directly.

### Who operates WORX Secondary at Suzhou?

WORX Landroid, the manufacturer of WORX 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 WORX Secondary deployment at Suzhou?

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/6456721e-f3fb-4d39-b29d-8ba7e3e90ce1 · feeds: GET /v1/feeds?deploymentId=6456721e-f3fb-4d39-b29d-8ba7e3e90ce1 · canonical URL: /deployments/worx-landroid-secondary-deployment_