1. The data haven and the orbit above it

Neal Stephenson’s Cryptonomicon spends a lot of time on the idea that data wants a physical home, and that the location of that home matters for law, latency, and trust. A server in the right jurisdiction can be worth more than a faster server in the wrong one. The keeper platform is a data haven with an even more literal claim to being outside normal boundaries.

Entry 179 estimated what the second platform’s attachments could earn. This entry asks why a customer would pay those prices. The answer is usually not the hardware. It is what the hardware removes from the customer’s own balance sheet.

2. Earth observation: buying decisions, not pixels

A customer buying imagery is not buying megapixels. They are buying a decision: plant here, insure this, move that, report now. The keeper platform’s value is persistence and rapid tasking. If a customer can get a fresh image of a specific place within hours instead of days, they can act sooner.

What they pay for is not the camera. It is the reduced latency between an event and their response to it.

3. Compute and storage: buying jurisdiction and resilience

Orbital compute is strange because the physics is worse than on Earth. The latency to ground is higher, the environment is harsher, and the hardware is harder to fix. Customers do not buy it for performance. They buy it for properties that are hard to replicate on the ground: jurisdictional separation, physical resilience, and the ability to operate without relying on a single country’s infrastructure.

This is the “above cloud” idea again. The customer is buying a place where their data lives under different rules.

4. Additive manufacturing: buying schedule insurance

A satellite operator with a broken bracket or a missing spacer faces a choice: launch a replacement part in six months, or do without. An orbital printer that can produce the part in days is not cheaper than the ground alternative. It is insurance against schedule slip.

The customer pays for the option to avoid a six-month delay. The actual parts printed may be few, but each one is valuable because the alternative is a stranded mission.

5. Servicing: buying asset life extension

A geostationary satellite that runs out of fuel or loses a thruster is not broken in the usual sense. It is still generating revenue, but its operational life is ending. A servicing mission that refuels it or repairs the fault can extend that life by years.

The customer pays for extra years of revenue from an asset they already own. The price is high because the asset is high, but so is the return.

6. Hosted payloads: buying risk reduction

The simplest customer is buying risk reduction. Instead of building and launching their own satellite, they rent a slot on a platform that already exists. They trade control for speed and capital efficiency.

This is the most familiar market. The keeper platform competes with other hosted payload providers by offering standardized interfaces, rapid integration, and the option to upgrade or move the payload later.

7. The common thread

In every case, the customer is not buying the platform. They are buying an outcome: faster decisions, different jurisdiction, schedule insurance, longer asset life, or lower risk. The platform’s job is to make those outcomes reliable enough that the price feels obvious.

What this changes

  • Customers buy outcomes, not hardware.
  • Earth observation sells timeliness; compute sells jurisdiction and resilience; manufacturing sells schedule insurance; servicing sells asset life; hosted slots sell risk reduction.
  • Pricing should be framed in terms of the customer’s avoided cost or gained revenue, not the platform’s cost.
  • The next leisure entry can ask which customer segments are most likely to buy first.