# Materialise Flagship at Leuven: deployment

Canonical ID: `5b9e5054-cb68-4c54-a307-bcdc284c0066`

Aggregate deployment at Materialise headquarters.

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

_Last updated: 2026-06-08_

- **Slug:** materialise-hq-deployment
- **Status:** operational
- **Model:** [Materialise Flagship](/models/materialise-flagship.md) (id: `be5ea88f-375d-44a3-b5f4-a64f6784c948`)
- **Company:** [Materialise](/companies/materialise.md) (id: `e508f0c6-c75e-4df6-9422-95e2cde5c2bc`)
- **Location:** [Leuven](/locations/leuven.md) (id: `77f2c842-6782-4ba3-8978-27e1d7cff49d`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the Materialise Flagship deployment at Leuven?

Materialise Flagship, built by Materialise, is recorded as a deployment at Leuven on the DEPLOY registry. Materialise operates the deployment directly.

### Who operates Materialise Flagship at Leuven?

Materialise, the manufacturer of Materialise 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 Materialise Flagship deployment at Leuven?

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/5b9e5054-cb68-4c54-a307-bcdc284c0066 · feeds: GET /v1/feeds?deploymentId=5b9e5054-cb68-4c54-a307-bcdc284c0066 · canonical URL: /deployments/materialise-hq-deployment_