Deployment
Laevo Flagship at Utrecht
Primary product or system from Laevo. Dutch passive exoskeleton for back support in bending and lifting tasks. No batt...
Laevo Flagship by Laevo · Catalog entry · 1 source · not yet field-verified
Machine-readable surfaces
- Markdown mirror: /deployments/laevo-hq-deployment.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/robots/cfc24031-b2ec-4e61-98b5-940453690bb5
- Data documentation: /data
- Query this programmatically: Deploy MCP
Aggregate deployment at Laevo headquarters and primary operational region.
- Trust tier
- Catalog entry · 1 source · not yet field-verified
- Last updated
- 2026-06-08
- Model
- Laevo Flagship
- Company
- Laevo
- Location
- Utrecht
- Status
- operational
- ID
cfc24031-b2ec-4e61-98b5-940453690bb5
Sources (1)
Methodology: Verified · 1 source (no primary) · last reviewed 2026-06-08
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-06-08
Maturity + lifecycle
Lifecycle: active
Architectural position
Cohort: robot
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Laevo Flagship at Utrecht.Common questions
- What is the Laevo Flagship deployment at Utrecht?
- Laevo Flagship, built by Laevo, is recorded as a deployment at Utrecht on the DEPLOY registry. Laevo operates the deployment directly.
- Who operates Laevo Flagship at Utrecht?
- Laevo, the manufacturer of Laevo Flagship, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.
- Have there been incidents at the Laevo Flagship deployment at Utrecht?
- 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.
Deploy Watch
Track this deployment.
We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.