# KONE Secondary at Espoo: deployment

Canonical ID: `828dd3bd-707c-4f02-9b55-e01cc37727e5`

Secondary product deployment at KONE operational region.

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

_Last updated: 2026-06-08_

- **Slug:** kone-secondary-deployment
- **Status:** operational
- **Model:** [KONE Secondary](/models/kone-secondary.md) (id: `afddb668-bf51-401c-9a3e-d95b2efbfb85`)
- **Company:** [KONE](/companies/kone.md) (id: `84e3318b-6c27-469c-9e3b-2f0288cb5117`)
- **Location:** [Espoo](/locations/espoo.md) (id: `a4f8e962-7b9c-4cf3-bdcf-d818a857c80a`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the KONE Secondary deployment at Espoo?

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

### Who operates KONE Secondary at Espoo?

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

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/828dd3bd-707c-4f02-9b55-e01cc37727e5 · feeds: GET /v1/feeds?deploymentId=828dd3bd-707c-4f02-9b55-e01cc37727e5 · canonical URL: /deployments/kone-secondary-deployment_