Local-first architecture prioritises the ability of a system to remain useful when connectivity is limited, when external control planes are unavailable, or when data must not leave a defined boundary.

In East Africa these conditions are not theoretical. They appear in branch operations, field work, industrial environments and public-sector systems that cannot assume constant high-quality connectivity to global regions.

Local-first does not mean anti-cloud. It means designing the boundary between local capability and remote capability deliberately.

Key properties we look for:

- Core transactions can complete offline or under degraded connectivity.
- Synchronisation is explicit and conflict-aware.
- Cryptographic and access-control roots are under operator control.
- Observability still works when the wide-area network is down.

Fox Height explores these patterns both in commercial Azure deployments and in the longer-horizon Continuum research programme.