Local-first Software Movement

Software Design Philosophy/Architecture Movement L Applications & Practices

Basic Information

  • Name: Local-first Software
  • Origin Paper: "Local-first software: You own your data, in spite of the cloud" (2019)
  • Proposed by: Ink & Switch Research Lab (Martin Kleppmann et al.)
  • Type: Software Design Philosophy/Architecture Movement
  • Core Technology: CRDTs (Conflict-free Replicated Data Types)
  • Status: Entered mainstream adoption in 2026

Concept Description

Local-first software is a set of software design principles that allow users to enjoy the convenience of cloud applications (cross-device access, real-time collaboration) while maintaining full ownership of their data. The core idea is: the data copy on the user's local device is the primary copy, and the server is only a secondary copy. Even if the server disappears, users still retain complete data and functionality.

Core Principles (Defined by Ink & Switch)

  1. Instant Response: Operations are executed locally without waiting for network round-trips
  2. Multi-device Sync: Data automatically syncs across all user devices
  3. Offline Availability: Functions normally without an internet connection
  4. Real-time Collaboration: Multiple users can edit the same document simultaneously
  5. Data Durability: Data is stored locally and won't be lost if the service shuts down
  6. Security & Privacy: End-to-end encryption, servers cannot read user data
  7. User Control: Users have full control over their data

Comparison with Traditional Architectures

Traditional Desktop Software

  • Pros: Offline availability, data stored locally
  • Cons: No collaboration, no cross-device synchronization

Cloud/SaaS Software

  • Pros: Cross-device, real-time collaboration
  • Cons: Network dependency, data stored on someone else's server, data loss if service shuts down

Local-first Software

  • Combines the best of both: Local storage + cross-device sync + real-time collaboration + offline availability
  • Automatically resolves data conflicts across multiple devices/users via CRDTs

Core Technologies

  • CRDTs: Conflict-free Replicated Data Types, automatically merge concurrent modifications
  • Automerge: JSON-like CRDT library (JavaScript/Rust)
  • Yjs: High-performance CRDT library focused on text collaboration editing
  • SQLite: Client-side embedded database
  • IndexedDB/OPFS: Browser-side storage
  • WebRTC/WebSocket: P2P or server-assisted data synchronization

Ecosystem Development in 2026

  • The first Local-First Conference was successfully held
  • Multiple production-ready local-first frameworks emerged (Jazz, Triplit, Evolu, etc.)
  • Expo (React Native framework) officially released local-first architecture guidelines
  • Developer community interest in local-first architecture continues to grow
  • "Why I'm Betting on Local-First Architecture in 2026" became a popular technical article

Representative Projects

  • Automerge: CRDT reference implementation
  • Yjs: Fastest CRDT implementation
  • ElectricSQL: Local-first database synchronization
  • PowerSync: Backend database → SQLite synchronization
  • Jazz: Local-first development framework
  • Triplit: Full-stack local-first database (acquired by Supabase in 2025)
  • Evolu: Local-first framework
  • Replicache: Client-side synchronization framework

Relationship with OpenClaw

The local-first architecture aligns perfectly with OpenClaw's design philosophy—data is primarily stored locally on the user's device, with the server acting as a secondary support. OpenClaw can adopt the local-first architecture to manage user conversation history, configurations, and data, ensuring continued functionality even when the network is disconnected.

Sources

External References

Learn more from these authoritative sources: