1. The machine made of people

John Steinbeck’s The Grapes of Wrath follows people who are treated as parts of a larger machine. The desktop is the opposite: a machine made of people and companies working together. No single organization has every capability needed to build it. The question is how to divide the work.

Entry 204 described how the desktop is assembled on orbit. This entry asks who builds the pieces.

2. The integrating company

Someone has to own the system: define the architecture, manage interfaces, integrate modules, and operate the desktop. This could be a startup, a subsidiary, or a consortium. The integrator does not need to build everything, but it must understand everything well enough to hold the design together.

The integrator is the customer-facing entity. It sells capacity, manages customer relationships, and takes overall responsibility for the platform.

3. Prime contractors for major modules

Large aerospace primes are well suited to build the core bus, power module, and radiator module. They have the clean rooms, test facilities, and heritage to produce high-reliability space hardware. Boeing, Lockheed Martin, Airbus, Thales Alenia Space, Northrop Grumman, and similar companies are natural suppliers.

The trade-off is cost and speed. Primes are reliable but expensive. A startup integrator may need to balance prime-built critical modules with in-house or smaller-supplier subsystems.

4. Smaller suppliers for subsystems

Attitude control, propulsion, batteries, solar cells, communications terminals, and computers can come from specialized suppliers. The space industry has a growing ecosystem of smaller companies that focus on one subsystem. Using them can reduce cost and increase innovation, but it increases integration complexity.

5. Attachment builders

Customer payloads and standard attachments — cameras, printers, compute nodes — may be built by the customers themselves, by the integrator, or by third-party vendors. The desktop’s business model depends on making attachment integration easy enough that many builders can participate.

6. Launch providers

The desktop’s modules need rides to orbit. SpaceX, ULA, Arianespace, Roscosmos, ISRO, and emerging providers are options. A multi-module desktop might use multiple launches from multiple providers to reduce schedule risk.

7. The ecosystem bet

Building the desktop is not a vertical-integration problem. It is an ecosystem orchestration problem. The integrator succeeds by defining clear interfaces, choosing reliable partners, and managing the seams between them.

What this changes

  • The desktop is built by an ecosystem, not a single company.
  • An integrator defines the architecture and owns the customer relationship.
  • Primes build critical modules; specialized suppliers build subsystems; customers and vendors build attachments.
  • The next leisure entry can ask who operates the desktop once it is built.