cr-sqlite

Protocolo de Datos Descentralizado

cr-sqlite is a run-time loadable extension for SQLite (and libSQL) that lets separate copies of a database, each of which has taken independent writes while offline, be merged without conflict. A table is upgraded into a 'conflict-free replicated relation' with one function call; the extension then exposes a virtual table of changes that one peer can read and another can apply, and applies column-level conflict resolution so every replica converges. The project calls this 'like Git, for your data'. It does not include networking: the application moves change sets between devices or a server by whatever means it likes. It is one component of the broader Vulcan project from Vulcan Labs, which also lists a reactive-query engine and a web stack built on SQLite as a collaborative application file format .

Empresa
Enlaces
Visitar Sitio Web Ver esta herramienta en el grafo Sugerir una corrección

Detalles

Licencia Permissive (MIT). https://github.com/vlcn-io/cr-sqlite (C extension with Rust and Python tooling)
Estado de Desarrollo 🟢 Activo
Propietario Vulcan Labs, the home of the vlcn.io site, whose footer names One Law LLC; the repository is owned by the vlcn-io organisation and the account that created the project (GitHub handle tantaman) is still the committer of recent merges
Órgano de Gobierno Vulcan Labs (One Law LLC named in the site footer); no external governance body is described
País Not stated by the project.
Año de Inicio 2022
Stack C extension for SQLite and libSQL, with Rust and Python components, WebAssembly builds for the browser through the vlcn.io tooling, and loadable builds for macOS, Linux, Windows, Android and iOS
Financiamiento Sponsorships: the README and site list company sponsors (including a database company, a hosting provider and an app platform) and individual sponsors
Última Investigación 29 oct 2026

Dominios de Caso de Uso

Evolución de Plataformas y Soberanía Co-creación y Conocimiento

Capacidades

Almacenamiento local-first Edición libre de conflictos Portabilidad de datos

Protocolo de Datos Descentralizado Atributos

Orígenes Local-first and offline-first application development: bring multi-master replication and partition tolerance to SQLite using CRDTs and causally ordered event logs, so application developers need no custom merge code for offline editing, device sync and real-time collaboration
Base de Datos SQLite (and libSQL): cr-sqlite is an extension to an existing SQLite database rather than a database of its own; upgraded tables add clock tables and the crsql_changes virtual table
Lenguaje de Consulta SQL: changes are read and applied with ordinary SELECT and INSERT against the crsql_changes virtual table, and tables are upgraded with a crsql_as_crr function call
Formatos de Datos SQLite database files; change sets as rows of (table, primary key, column id, value, column version, database version, site id, causal length, sequence) returned by crsql_changes
Edición Colaborativa en Vivo Partial: the extension merges independent edits to SQL tables without conflict and supports real-time collaboration when an application sends changes continuously; it has no text-editing algorithm in its core README, but lists sequence CRDTs in its documentation
Edición de Texto Enriquecido Not stated by the project.
Soporte Móvil Yes: loadable extension builds for Android and iOS are produced by the project, with build fixes merged in 2026
Soporte Web Yes: the project's documentation covers use in the browser through WebAssembly and browser persistence
Aplicaciones Nativas Yes: run-time loadable extension for desktop and mobile native applications
Términos Free and open source (MIT)
Fondos Not stated by the project.
Basado En SQLite and libSQL, and CRDT research; the README cites causally ordered event logs and CRDTs as its two approaches to conflict resolution
Arquitectura P2P Transport-agnostic replication: peers or a server exchange change sets read from and written to the crsql_changes virtual table by application code; the documentation describes whole-database and partial sync patterns but the project ships no network layer
Red de Superposición None: no network is defined; replicas sync through whatever transport the application provides
Direccionamiento por Contenido No: rows are identified by table and primary key with per-site identifiers and version counters
Local-First Local-First: each replica is a normal local SQLite database that can be read and written offline and merged later
Cifrado de Extremo a Extremo (E2EE) No: the extension does not encrypt data; encryption is left to the application or storage layer
Biblioteca de CRDTs cr-sqlite: this entry is itself the CRDT layer for SQLite; its documentation describes table, column and sequence CRDTs
Tolerancia a Fallos Bizantinos No: change sets are applied as presented; the README describes no defence against malicious peers
Firma N/A: change rows carry a site identifier but are not signed
Permisos N/A: no access-control model; any peer that can write the change table can apply changes
Compatibilidad con la Web Semántica N/A: relational model with no RDF or linked-data layer
Contrato Inteligente N/A: no ledger or contract component
Posición en la Pila del Protocolo Application-layer: an in-process database extension, independent of the transport
Incorporación de Activos/Valor None: no token or value-transfer mechanism
Madurez del Protocolo / Estandarización Pre-1.0 (v0.16.3) extension; the change-set format is documented in the README but has no formal specification or standards-body involvement