Space Data Centers Database
Search and compare space data center projects and related orbital computing demonstrations, including developers, technical specifications, suppliers, agreements and milestones. Follow each commitment to its original announcement.
Catalog: 95 projects. 13 proposal / study · 33 development · 13 launched · 20 demonstrated · 4 operating · 9 historical · 3 uncertain. These are project classifications, not spacecraft counts or verified commercial capacity.
37 projects classified as launched, demonstrated or operating: 29 reviewed, 8 with review limits or awaiting review. Each project appears in one classification.
Linked view: Loft YAM Orbital Computing Platform.
Columns & coverage · 1 empty columns hidden
1 of 1 projects have values for the selected fields. 1–2 of 2 configuration rows shown. Projects without values are hidden.
— No verified value recorded · N/A Not applicable · TBD Not yet defined · Conflict Unresolved. Configurations remain separate. Hardware ratings and plans do not establish measured performance. Open Details & sources for evidence and coverage notes.
| Project / configuration | Compute hardware | Compute throughput |
|---|---|---|
| Loft YAM Orbital Computing PlatformYAM-9 JPL demonstrationLoft OrbitalProject status: On-orbit computing demonstrated | NVIDIA Jetson AGX Orin for the JPL vision-language-model demonstrationYAM-9 JPL demonstrationReported specificationpreviously verified operator account Comp0: 4 × 2 GHz CPU. Comp1 and Comp2: each 12 × 2 GHz CPU plus GPUYAM-9 JPL demonstrationReported specificationofficial reported specification | GPU1: 248 TOPS. GPU2: 248 TOPSYAM-9 JPL demonstrationReported specificationofficial reported specification |
Compute hardware: NVIDIA Jetson AGX Orin for the JPL vision-language-model demonstration YAM-9 JPL demonstration. Existing accepted October 12 Loft account identifies this processor on YAM-9. Do not apply the description to YAM-6 or the Altair constellation. previously verified operator account. Included with these qualifications. Source observation: 2026-10-28. Supporting source ↗Compute hardware: Comp0: 4 × 2 GHz CPU. Comp1 and Comp2: each 12 × 2 GHz CPU plus GPU YAM-9 JPL demonstration. Table I hardware layout. CPU clock is not arithmetic throughput. Exact CPU core model and RAM are not specified. Existing Jetson AGX Orin identification is retained separately. official reported specification. Included with these qualifications. Source observation: 2026-10-28. Supporting source ↗Compute throughput: GPU1: 248 TOPS. GPU2: 248 TOPS YAM-9 JPL demonstration. Table I reported hardware ratings, arithmetic precision unspecified. Do not sum into measured mission throughput. Engineering models were benchmarked, and only Comp2 provided working GPU acceleration in that test. official reported specification. Included with these qualifications. Source observation: 2026-10-28. Supporting source ↗ | ||
| Loft YAM Orbital Computing PlatformYAM-6 AI hostingLoft OrbitalProject status: On-orbit computing demonstrated | NVIDIA compute on YAM-6YAM-6 AI hostingReported specificationofficial operator hardware identification | — |
Compute hardware: NVIDIA compute on YAM-6 YAM-6 AI hosting. October 12 operator release explicitly identifies NVIDIA GPU on YAM-6. It conflicts with the June anniversary page on the original launch year. Module count and generation remain unspecified. official operator hardware identification. Included with these qualifications. Source observation: 2026-10-27. Supporting source ↗Compute throughput: No supported value is assigned to this configuration. The recorded coverage note applies to another configuration. | ||
Technical specifications retain the source’s original units and evidence status. Hardware counts, compute rates and power are not equivalent; launched hardware does not establish demonstrated performance. Supplier counts include suppliers and hosts only, reflect current filters and cover this directory, not the entire market. “No record” means no disclosure captured; it does not mean the work is unawarded. Latest developments use source dates, not routine review or collection dates.