# ByteDance Flagship at Beijing: deployment

Canonical ID: `d1480e19-cfdc-4bdd-b62b-fb13fda50a67`

Aggregate deployment at ByteDance headquarters.

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

_Last updated: 2026-06-08_

- **Slug:** bytedance-hq-deployment
- **Status:** operational
- **Model:** [ByteDance Flagship](/models/bytedance-flagship.md) (id: `c1f9dff2-be07-4cb3-8032-9c34ad6670e4`)
- **Company:** [ByteDance](/companies/bytedance.md) (id: `53730f8f-d7aa-4a30-9b17-5c28de61cccd`)
- **Location:** [Beijing](/locations/beijing.md) (id: `4dcea30f-1b34-41af-9aa0-f1440e395b68`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.bytedance.com/

## Common questions

### What is the ByteDance Flagship deployment at Beijing?

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

### Who operates ByteDance Flagship at Beijing?

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

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/d1480e19-cfdc-4bdd-b62b-fb13fda50a67 · feeds: GET /v1/feeds?deploymentId=d1480e19-cfdc-4bdd-b62b-fb13fda50a67 · canonical URL: /deployments/bytedance-hq-deployment_