# Innophys Secondary at Tokyo: deployment

Canonical ID: `c0152e7f-88e8-4e4a-8966-37643bdec8f4`

Secondary product deployment at Innophys operational region.

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

_Last updated: 2026-06-08_

- **Slug:** innophys-secondary-deployment
- **Status:** operational
- **Model:** [Innophys Secondary](/models/innophys-secondary.md) (id: `208df3af-c3e6-434d-abdf-9bf95f9af322`)
- **Company:** [Innophys](/companies/innophys.md) (id: `ed8f6ab7-46e7-46a9-ae41-cf8ef4df7478`)
- **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 Innophys Secondary deployment at Tokyo?

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

### Who operates Innophys Secondary at Tokyo?

Innophys, the manufacturer of Innophys 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 Innophys 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/c0152e7f-88e8-4e4a-8966-37643bdec8f4 · feeds: GET /v1/feeds?deploymentId=c0152e7f-88e8-4e4a-8966-37643bdec8f4 · canonical URL: /deployments/innophys-secondary-deployment_