# Under Flagship at Baltimore: deployment

Canonical ID: `0843045a-0fc9-4ec1-a18d-48eb17bee57b`

Aggregate deployment at Under Armour headquarters.

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

_Last updated: 2026-06-08_

- **Slug:** under-armour-hq-deployment
- **Status:** operational
- **Model:** [Under Flagship](/models/under-armour-flagship.md) (id: `5ea9d506-1dbf-4419-a6cd-e352d99533a8`)
- **Company:** [Under Armour](/companies/under-armour.md) (id: `5ffb024f-1e11-4fb7-8e67-eb584875a94a`)
- **Location:** [Baltimore](/locations/baltimore.md) (id: `8467a838-ad37-424d-a9a9-6d6bbc62722d`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.underarmour.com/

## Common questions

### What is the Under Flagship deployment at Baltimore?

Under Flagship, built by Under Armour, is recorded as a deployment at Baltimore on the DEPLOY registry. Under Armour operates the deployment directly.

### Who operates Under Flagship at Baltimore?

Under Armour, the manufacturer of Under 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 Under Flagship deployment at Baltimore?

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/0843045a-0fc9-4ec1-a18d-48eb17bee57b · feeds: GET /v1/feeds?deploymentId=0843045a-0fc9-4ec1-a18d-48eb17bee57b · canonical URL: /deployments/under-armour-hq-deployment_