awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
livestorejs avatar

livestorejs/livestore

0
View on GitHub↗
3,475 stars·121 forks·TypeScript·apache-2.0·35 viewslivestore.dev↗

Livestore

Livestore is a reactive state management framework that utilizes a local SQLite database to store and synchronize application data. It provides an event-sourced state store that processes typed events through materializer functions to derive and persist application state.

The framework implements offline-first data synchronization using a push-pull engine and append-only event logs to maintain consistency between clients and servers. It includes a real-time presence system for tracking user activity and shared session status across connected clients.

The system covers a broad capability surface including event-driven state updates, reactive UI data binding, and durable state persistence. It features developer tools for state inspection and time-travel debugging based on immutable audit trails. Data processing and synchronization are offloaded to web workers to prevent blocking the main user interface.

A command-line interface is available for project scaffolding and initial setup.

Features

  • Reactive SQLite Libraries - A reactive state management framework that combines SQLite persistence with reactive data streaming for automatic UI updates.
  • State Materialization - Processes immutable event logs into relational database tables to derive the application state.
  • Local-First Persistence - Uses a relational database on the client side to provide synchronous data reads and offline-first functionality.
  • Persistence & Durability - Saves data to a durable storage layer so it survives browser refreshes and server restarts.
  • Event Stores - Implements a data store that persists sequences of events for state reconstruction via materializer functions.
  • Local-First Databases - Uses a local database as the primary data source to enable synchronous reads and offline-first functionality.
  • Log Materialization - Transforms append-only event logs into a concrete local SQLite database to derive current application state.
  • Offline Data Management - Ensures the application remains fully operational during network outages by maintaining state in a local database.
  • Reactive Data Queries - Binds database queries to UI frameworks using hooks that trigger automatic updates when underlying data changes.
  • SQLite Storage Adapters - Uses a relational SQLite schema to structure and store application state locally or on a server.
  • Local Database Persistence - Stores application data in a local database using the browser file system for persistence across sessions.
  • Background Data Synchronization - Implements mechanisms for updating local data stores from remote sources without interrupting the user interface.
  • Event Sourcing - Manages application state as an immutable sequence of events to ensure data consistency and enable historical debugging.
  • Offline-First Synchronization - Ships a push-pull synchronization engine and event logs to keep local and remote states consistent offline.
  • Append-Only Event Logs - Distributes append-only event logs between clients and servers to ensure deterministic state reconstruction.
  • State-Synchronized Bindings - Binds global state management to frontend libraries using reactive hooks to synchronize the user interface.
  • Event-Driven State Managers - Provides a centralized mechanism to update application state via typed events and materializer functions.
  • Reactive Data Bindings - Binds a local SQLite database to frontend frameworks to automatically update the UI when data changes.
  • Reactive State Managers - Includes a built-in reactivity system that tracks data changes to automatically synchronize and update UI components.
  • Reactive UI Updates - Triggers automatic UI updates when underlying data changes using a type-safe schema for events and queries.
  • Main Thread Offloading - Moves computationally expensive state management and data processing tasks from the main UI thread to background web workers.
  • Offline-First Web Apps - Provides a framework for building applications that function without internet by prioritizing local storage and synchronization.
  • Real-time Collaboration - Enables real-time synchronization of application data across multiple users and devices for shared interactive experiences.
  • State Inspection Interfaces - Provides visual tools for tracking and displaying real-time state changes and data flow within the application.
  • Data Schema Definitions - Specifies database table structures and event types that translate events into permanent state changes.
  • Offline-First Persistence - Stores events locally to remain functional without connectivity and synchronizes pending changes once online.
  • Time-Travel Debuggers - Provides a developer interface to inspect event logs and reconstruct state transitions for time-travel debugging.
  • Type-Safe Event Contracts - Enforces a type-safe contract for events and queries to ensure unidirectional data flow.
  • Event Logs - Maintains an immutable log of every event to enable historical state reconstruction and analysis.
  • Push-Pull State Distribution - Implements a push-pull synchronization engine to distribute immutable events across clients and servers.
  • Optimistic Offline Queues - Maintains a local queue of pending changes during network outages with automatic synchronization once connectivity is restored.
  • Presence Tracking - Tracks and shares the online status and activity of users within shared sessions.
  • WebSocket State Synchronization - Propagates data events between multiple clients in real-time using a WebSocket backend for shared state consistency.
  • State Management - State management framework based on reactive SQLite.

Star history

Star history chart for livestorejs/livestoreStar history chart for livestorejs/livestore

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Projects sharing features with Livestore

These projects share indexed features with Livestore. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • pubkey/rxdbpubkey avatar

    pubkey/rxdb

    23,048View on GitHub↗

    This project is a reactive, offline-first NoSQL database engine designed for JavaScript applications. It provides a robust framework for managing application state by synchronizing data across browsers, mobile devices, and server-side runtimes. By treating local storage as the primary source of truth, it enables applications to remain functional without network connectivity, automatically reconciling changes with remote backends once a connection is restored. The database distinguishes itself through a modular architecture that supports cross-environment synchronization and high-performance d

    TypeScriptangularbrowser-databasecouchdb
    View on GitHub↗23,048
  • day8/re-frameday8 avatar

    day8/re-frame

    5,532View on GitHub↗

    re-frame is a functional framework for building single-page applications in ClojureScript. It provides a centralized, immutable database that serves as the single source of truth for the entire application state, enforcing a strict unidirectional data flow where events trigger state transitions and subsequent view updates. The framework distinguishes itself through a reactive signal graph and an interceptor-based middleware pipeline. By treating application logic as a sequence of data-driven events and declarative side effects, it decouples business logic from the view layer. This architectur

    Clojureclojurescriptre-framereact
    View on GitHub↗5,532
  • garden-co/jazzgarden-co avatar

    garden-co/jazz

    2,537View on GitHub↗

    Jazz is a local-first relational database and synchronization framework designed for offline-capable applications. It functions as a reactive state management system that treats database records as the primary source of truth, automatically updating user interfaces in real time as underlying data changes. The project distinguishes itself through a collaborative data synchronization model that utilizes row-level versioning to track branching edit histories. It implements a security engine based on identity-claim row security, which enforces granular permissions on individual records, and suppo

    TypeScriptcrdtcrdtsdatabase
    View on GitHub↗2,537
  • nozbe/watermelondbNozbe avatar

    Nozbe/WatermelonDB

    11,722View on GitHub↗

    WatermelonDB is an offline-first data synchronization engine and reactive database library designed for mobile and web applications. It provides a persistent storage layer backed by SQLite, enabling applications to maintain full functionality and data consistency while operating without an internet connection. The framework distinguishes itself through a reactive data binding system that automatically updates user interface components whenever underlying database records change. It utilizes schema-driven model mapping to generate type-safe interfaces and employs lazy object materialization to

    JavaScriptdatabasehacktoberfestpersistence
    View on GitHub↗11,722
Compare all 30 related projects→

Frequently asked questions

What does livestorejs/livestore do?

Livestore is a reactive state management framework that utilizes a local SQLite database to store and synchronize application data. It provides an event-sourced state store that processes typed events through materializer functions to derive and persist application state.

What are the main features of livestorejs/livestore?

The main features of livestorejs/livestore are: Reactive SQLite Libraries, State Materialization, Local-First Persistence, Persistence & Durability, Event Stores, Local-First Databases, Log Materialization, Offline Data Management.

Which projects share features with livestorejs/livestore?

Projects with overlapping indexed features include: pubkey/rxdb — This project is a reactive, offline-first NoSQL database engine designed for JavaScript applications. It provides a… day8/re-frame — re-frame is a functional framework for building single-page applications in ClojureScript. It provides a centralized,… garden-co/jazz — Jazz is a local-first relational database and synchronization framework designed for offline-capable applications. It… nozbe/watermelondb — WatermelonDB is an offline-first data synchronization engine and reactive database library designed for mobile and web… hoodiehq/hoodie — Hoodie is a data synchronization framework and offline-first JavaScript backend designed to keep client-side data… vlcn-io/cr-sqlite — cr-sqlite is a multi-master database replication system that uses conflict-free replicated data types to ensure…