# Laevo Secondary at Utrecht: deployment

Canonical ID: `db54cd13-7ebe-41d6-b79c-4cd0667deb3c`

Secondary product deployment at Laevo operational region.

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

_Last updated: 2026-06-08_

- **Slug:** laevo-secondary-deployment
- **Status:** operational
- **Model:** [Laevo Secondary](/models/laevo-secondary.md) (id: `214f08da-d310-4cef-92d3-9c147faaadf2`)
- **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://rover.report

## Common questions

### What is the Laevo Secondary deployment at Utrecht?

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

### Who operates Laevo Secondary at Utrecht?

Laevo, the manufacturer of Laevo 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 Laevo Secondary 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/db54cd13-7ebe-41d6-b79c-4cd0667deb3c · feeds: GET /v1/feeds?deploymentId=db54cd13-7ebe-41d6-b79c-4cd0667deb3c · canonical URL: /deployments/laevo-secondary-deployment_