A model that costs nearly nothing to run can be priced for everyone, granted to anyone, and revoked by no one.
The economics of the inward direction are not the economics of a cloud product. They are the economics of an appliance — a thing built once, installed once, and run on hardware its owners already pay for. The cost structure is different, the value structure is different, and the thing that compounds over time is not usage but memory. This chapter describes those economics honestly, without naming a price, because the price is a function of the cost structure and the cost structure is what matters.
The price floor
Every intelligence product has a price floor — the cost below which it cannot be delivered without losing money. For a cloud product, the floor is set by inference cost: every token has a price, every request consumes compute, every user adds marginal cost. The product must charge enough to cover the marginal cost of each user, or it loses money on every interaction.
A local-first system inverts this. The compute is paid for once, in the hardware. The inference cost per turn is approximately zero. The marginal cost of an additional conversation, an additional book, an additional year of memory is the electricity to run the machine — less than a reading lamp. The price floor is set by the hardware, which is consumer-grade and depreciating, not by the inference, which is effectively free.
This is why efficiency is a freedom concern and not only a cost concern. A model that draws forty watts can be given to someone who has no credit card, no stable internet, no relationship with any platform. A model that draws four hundred watts cannot. The path to a product that serves the people the market has skipped runs through energy efficiency, because energy efficiency is what makes the price floor reach the floor of the market.
Locality as the moat
A cloud product is defensible while its provider holds the best model, and it loses that defensibility the moment a better model arrives somewhere else. The moat is rented from the model layer, and the model layer is the layer most likely to be commodified.
A local-first system is defensible for different reasons. The substrate — the books, the conversations, the daily records — is owned. The index is computed locally. The memory has accumulated over years of living with the people it serves. None of this moves when a better model arrives. The better model is dropped in, reads the same retrieved text, and the system continues. The moat is not the model. The moat is the accumulated relationship between a system and the people it lives with.
This is also the safety argument and the privacy argument, and they are the same argument. The radius of any failure is one home. The data that never leaves cannot be breached in transit, cannot be subpoenaed from a provider, cannot be monetized by a platform. Locality is the moat because locality is the protection.
Memory as the compounding asset
A cloud subscription compounds for the provider, not for the user. The longer the user pays, the more the provider earns. The user's position is unchanged — they have access for as long as they pay, and they lose it the moment they stop.
A sovereign system compounds for the people who own it. The longer it runs, the more it remembers — the family's conversations, its books, its readings, its days. Over years, it becomes something no cloud service can sell back, because no cloud service has it: a historical memory of a particular household, present and accountable, belonging to the people it serves. This is the asset that cannot be replicated by a competitor, because it cannot be transferred. It is built in place, over time, by being lived with.
The implication for the business is unusual. A cloud product is valued on its recurring revenue. A sovereign product is valued on the longevity of its relationships. The longer a household runs the system, the more valuable the system is to that household, and the harder it is for anything else to replace. The compounding is not in the revenue. It is in the relationship.
The unit of deployment
The household is the unit of deployment, not the individual. This is a deliberate choice, and it shapes everything downstream. A system deployed to a household serves several people at once, accumulates memory shared among them, and becomes a piece of the family's infrastructure in the way a kitchen or a bookshelf is. It is not a personal device. It is a domestic one.
The community is the next unit. A system deployed to a community — a building, a neighborhood, a parish, a school — serves several households, carries shared norms, and is accountable to the people who run it in a way no cloud service can be. The community integrates the system into its own life. Safety becomes a property of proximity rather than of policy.
The economics compound at each scale. A household system is efficient. A community system is more efficient still, because the fixed costs are shared. The path from one to the other is the path the inward direction takes as it grows — not by aggregating users into a central service, but by connecting sovereign nodes into a network of mutually accountable local intelligences.