With two people, architecture is labour allocation.

A service can be technically small and operationally large. Deployment, support, credentials, billing and incident response all continue after the feature ships. None of that work disappears because the interface has one button.

Local is a boundary, not a slogan#

Several projects on our bench are designed around local operation. Life OS uses Tauri, SolidJS and SurrealDB. Bookey Reader was built as an offline mobile reader. Local execution can reduce the systems we operate on somebody else’s behalf.

It does not remove maintenance. Operating-system changes still happen. Packaging still breaks. Documentation can become false. A local tool transfers some operational responsibility to its owner, so the run notes have to say what that responsibility is.

The pass is still a model#

Bench shows a yearly pass because one pool of maintenance time is simpler than six disconnected update promises. The prices on this catalogue are visibly marked illustrative. There is no checkout and no claim that the tools are ready to license today.

That distinction matters. A pricing table is not evidence of a business. It is a test of whether the offer can be explained without hiding costs.

What the money would buy#

Maintenance. Packaging. Reproduction of failures. Direct support only on the support tier. It would not buy managed hosting, model API usage or a guarantee that security software finds every vulnerability.

The useful constraint is not that two people move faster. It is that two people cannot conceal the cost of a promise for long. We document fewer promises and keep their limits beside them.