LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore
LiveStore is a next-generation state management framework based on reactive SQLite and git-inspired syncing (via event-sourcing). - LiveStore
Johannes Schickling on Twitter / X
After 4 years of work, I'm incredibly excited to introduce LiveStore, the next-gen data layer I'm building for Overtone.It's based on reactive SQLite and has a built-in sync engine. Give it a try - would love your feedback! https://t.co/DB0cEXY9MD— Johannes Schickling (@schickling) May 27, 2025
LiveStore: SQLite-based data layer for local-first apps
Introducing: LiveStore - the client-centric, local-first data layer for high performance applications.
PowerSync: Backend DB - SQLite sync engine | For Postgres, MongoDB, MySQL, SQL Server
Automatically sync your backend database with in-app SQLite and avoid the complexities of using APIs to move app state over the network.
Persistent Storage Options
This API provides database persistence via localStorage/sessionStorage and, in compatible browsers, the Origin-Private FileSystem.
SQLSync
SQLSync is a collaborative offline-first wrapper around SQLite. It is designed to synchronize web application state between users, devices, and the edge.
RedwoodSDK: A simple framework for humans
Server-first React, running on the Cloudflare platform. Simple to build. Easy to maintain.
Observable Notebooks: Fast data exploration and prototyping
Quickly explore and analyze data, build prototype data visualizations, and collaborate with your team in real-time with live JavaScript notebooks.
Litestream
Litestream is an open-source, real-time streaming replication tool that lets you safely run SQLite applications on a single node.
Jazz - The database that syncs.
Jazz is a local-first relational database. It runs across your frontend, backend and our global storage cloud. Sync partial tables, durable streams and files, fast. Feels like simple reactive state.
Experimental live content collections
Live content collections are a new type of content collection that fetch their data at runtime rather than build time. This allows you to access frequently updated data from CMSs, APIs, databases, or other sources using a unified API, without needing to rebuild your site when the data changes.
Honker
Durable queues, streams, pub/sub, and time-trigger scheduling on SQLite. One file, zero servers.
Introducing Tap: Repository Synchronization Made Simple | Bluesky
Just about every app built on AT needs data from a repository at some point. For many use cases – feed generators, labelers, bots – streaming live data through a Relay or Jetstream works well. But some applications need to go beyond what Jetstream was designed for, like tracking specific subsets of a repo, automatically backfilling a database when adding new repos to monitor, or even mirroring the entire Atmosphere.
candystore - Rust
A fast (blazingly, of course), persistent, in-process key-value store that relies on a novel sharding algorithm. Since Candy does not rely on log-structured merge (LSM) trees or B-Trees, no journal/WAL is needed and IOs go directly to file.
neodb-social/neodb
🧩 a self-hosted server tracking what you read/watch/listen/play, powering a global distributed community federating via ActivityPub and ATProto.