# teamLab Secondary at Tokyo: deployment

Canonical ID: `83f19023-4302-4b58-8279-d4c2df7cb231`

Secondary product deployment at teamLab operational region.

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

_Last updated: 2026-06-08_

- **Slug:** team-lab-secondary-deployment
- **Status:** operational
- **Model:** [teamLab Secondary](/models/team-lab-secondary.md) (id: `97ef99eb-d270-4465-8f8e-cc3400252e11`)
- **Company:** [teamLab](/companies/team-lab.md) (id: `23579f85-f7f7-49a9-87a3-e9fb17f924cc`)
- **Location:** [Tokyo](/locations/tokyo.md) (id: `555c248e-62e6-4f2c-8c30-412c3231d1b7`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the teamLab Secondary deployment at Tokyo?

teamLab Secondary, built by teamLab, is recorded as a deployment at Tokyo on the DEPLOY registry. teamLab operates the deployment directly.

### Who operates teamLab Secondary at Tokyo?

teamLab, the manufacturer of teamLab 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 teamLab Secondary deployment at Tokyo?

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/83f19023-4302-4b58-8279-d4c2df7cb231 · feeds: GET /v1/feeds?deploymentId=83f19023-4302-4b58-8279-d4c2df7cb231 · canonical URL: /deployments/team-lab-secondary-deployment_