# Laevo Flagship at Utrecht: deployment

Canonical ID: `cfc24031-b2ec-4e61-98b5-940453690bb5`

Aggregate deployment at Laevo headquarters and primary operational region.

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

_Last updated: 2026-06-08_

- **Slug:** laevo-hq-deployment
- **Status:** operational
- **Model:** [Laevo Flagship](/models/laevo-flagship.md) (id: `464a4842-792a-42d9-a765-730d40147d4d`)
- **Company:** [Laevo](/companies/laevo.md) (id: `f02dda90-5406-47df-8b26-8c7a6e29b6b0`)
- **Location:** [Utrecht](/locations/utrecht.md) (id: `3842fe5b-15cf-4a71-833f-37757930ad4c`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.laevo.com/

## 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.


_API: GET /v1/robots/cfc24031-b2ec-4e61-98b5-940453690bb5 · feeds: GET /v1/feeds?deploymentId=cfc24031-b2ec-4e61-98b5-940453690bb5 · canonical URL: /deployments/laevo-hq-deployment_