2 suppliers
ByteDance
Export controls
No export-control designations were found.
Public sources name Huawei Technologies as a supplier, without a date, and it matches the Entity List.
Suppliers and customers
The suppliers with the most current records are Huawei Technologies and NVIDIA.
All 2 suppliersFacilities
The two largest operating sites by power. Bars show power, pale where the figure is an estimate. Power and accelerator figures are each site’s own; where this company uses or contracts a site rather than holding it, its share is not on record.
All 5 sites
| Facility | Country | Power | Accelerators |
|---|---|---|---|
| Operating capacity, 2 of 5 sites | |||
| Bridge Data Centres MY06 (Sedenak Tech Park) | Malaysia | ~315 MW | |
| VNET Bayin Ulanqab | China | ~252 MW | |
| No power figure shown, 3 of 5 sites | |||
| AirTrunk SGP2 (Loyang) | Singapore | ||
| Volcano Cloud Taihang Computing Centre II (Datong) | China | ||
| TikTok / ByteDance Thailand BOI Data Hosting Infrastructure | Thailand | ||
Tildes mark estimates.
Compute arrangements
ByteDance holds a colocation of 90 MW with Green Mountain, critical IT load.
Updated 9 Sep 2026. Company statement by Green Mountain, attested. Source
Ownership
Chip observations
| Chip class | Quantity | Scope | Evidence |
|---|---|---|---|
| NVIDIA H20 ByteDance | Deployment status unknown · Disputed report · Disputed press report; stock quantity, deployment and regulatory-freeze status unestablished. | Source, 28 Apr 2025 | |
| Huawei AI chips (model unspecified) ByteDance | Planned use · Planned inference use; chip model, quantity and deployment unestablished. | Source, 26 Jul 2025 |
Sums of recorded estimates, by scope. Planned use: Unknown · quantities unavailable for 1 observation. Deployment status unknown: Unknown · quantities unavailable for 1 observation.
1 organisation with publishable observations · 2 chip categories. Source dates: 28 Apr 2025–26 Jul 2025.
Related pages
Sources
6 sources
| Source | Supplies here | Records | Date | Terms |
|---|---|---|---|---|
| Licensed corporate-ownership database | Subsidiary counts | Licensed-only entities counted, never named | ||
| Compute control disclosures | Filings, calls and announcements by either party | 1 disclosure | ||
| Export-control designations | Federal Register-anchored designations | 0 records | 3 Nov 2026 | |
| Supply-chain relationships | SEC disclosures, re-derived company disclosures, licensed supply-chain database | |||
| BIS Entity List cross-reference | Counterparties matched directly to the Entity List, confidence 0.9 or above | |||
| Facility records and their sources | Known facilities, with each site’s estimate flags |
- Licensed corporate-ownership database: https://scrutica.com/methodology#licensed-substrate
- Compute control disclosures: https://scrutica.com/methodology
- Export-control designations: https://scrutica.com/methodology#export-controls
- Supply-chain relationships: https://scrutica.com/methodology#licensed-substrate
- BIS Entity List cross-reference: https://scrutica.com/export-controls
- Facility records and their sources: https://scrutica.com/methodology#facilities
How the figures were made
Subsidiaries. Subsidiary totals of 20 or more are rounded; subsidiaries recorded only in the licensed database are counted, not named.
Suppliers and customers. Records are grouped by counterparty, and counterparties with more current records come first; disclosures that name no counterparty share one entry. A disclosure more than 5 years old is kept as a record of the past, not evidence of a current relationship, and follows the current records with its fiscal year; a relationship whose recorded end date has passed is marked ended with that date and what it rests on, and follows them too. A product or service, a percentage (the supplier’s share of one product line in the customer’s inputs) and a sole-source mark appear only where the record’s cited source states them for the pair: where a record names no product, its source states none or the description on file has not been tied to the cited source, and records that would read the same are printed once with their count. Where one source’s records about a counterparty cite different documents, each names the site it cites. Alternative suppliers may exist outside this corpus.
Names and pale marks. The companies named at the foot of each side lead the live record’s ledger: most current records first, ties in the ledger’s own order. What each supplies or buys is read from its latest dated record. A public counterparty is drawn pale when every record it has is a disclosure more than 5 years old or has ended.
Known facilities. Each facility record states the relationship its source establishes. A site’s power figure counts as operating capacity, is held from it with the reason beside the figure, or is not shown; of the 5 sites whose record names ByteDance, 2 count as operating capacity and 3 show no power figure. A tilde marks a figure the site’s own record marks as estimated.
Compute arrangements. Filings and announcements recording who owns, runs or contracts compute capacity, where this company is one of the parties. Each is graded by its source’s authority, who disclosed it and whether its figure is an estimate.
Identity. Variant identifiers are resolved to one organisation before its data is combined.
| Quantity | Value | Definition |
|---|---|---|
| Suppliers drawn | 2 | 2 in public sources and 0 in licensed data. |
| Supply records in public sources | 2 | 2 with suppliers and 0 with customers. One counterparty can hold several records. |
Identifiers
- LEI
- 54930057HU24VGK3CO92
- Scrutica ID
- org-bytedance
Name forms resolved to this record: ByteDance Ltd., Volcano Cloud, zijie tiaodong youxian gongsi, 字节跳动, 字节跳动有限公司, 火山引擎.