What does local-first software actually keep local?

Building a personal cultural collection requires clear data boundaries. Curatale keeps its working records on the user's device, while Critterarium separates a hosted public Atlas from browser-local encounters. A remotely hosted service may add account, price, or continuity dependencies; local storage changes that risk profile but does not remove backup responsibility.

Rented servers versus physical ownership

A cloud subscription can create a recurring dependency on an account, provider policy, price, and export path. Local files can remain accessible without that account when the product format and device still work. They are not automatically durable: copies, exports, compatible software, and a recovery plan still matter.

Two distinct products with honest boundaries

CozyMuseum practices explicit boundaries rather than vague privacy slogans. Critterarium pairs a public hosted web atlas with browser-local personal encounters. Curatale is a separate, paid local application engineered for private media archives. They share an aesthetic vision, but maintain strictly isolated data boundaries.

What local-first cannot promise

Local-first does not mean a digital experience is isolated from all network traffic. Web resources, documentation, external references, purchase delivery, or updates may still use the internet. The useful promise must be product-specific: identify which records remain local, which services are hosted, and which recovery responsibility stays with the user.

The decisive question before building an archive

Before committing your memories to any software, ask where the records live, which format can be exported, how backups are made, and what happens when a device or provider fails. A personal museum becomes more controllable when those answers are explicit and the user can keep independent copies.