RxDB

Protocolo de Dados Descentralizado

A local-first, reactive NoSQL database for JavaScript applications. Data lives in a local database in the browser, Node.js, React Native, Electron, Capacitor and other JavaScript runtimes; queries can be subscribed to, so the UI updates when the underlying data changes. RxDB replicates to existing backends (the project lists replication with CouchDB, GraphQL, REST, WebRTC, and several hosted services, among others), has plugins for conflict handling, CRDT-style conflict resolution, encryption, schema validation and migration, and swaps its storage engine to suit the runtime. The core is open source; a set of premium storage and performance plugins is sold under paid licences .

Empresa

Detalhes

Licença Core open source (Apache-2.0); premium plugins (extra storage engines, performance plugins, server adapters) are proprietary and licensed under paid tiers. https://github.com/pubkey/rxdb
Status de Dev 🟢 Ativo
Proprietário Daniel Meyer (trading as RxDB), Stuttgart, Germany; the project's legal notice names him as owner and responsible for the content
Órgão de Governança Daniel Meyer, owner and lead maintainer (sole proprietorship); no external governance body is described
País Germany (Stuttgart, per the legal notice)
Ano de Início 2016
Stack TypeScript/JavaScript; RxJS for observables; pluggable storage layer (localStorage, IndexedDB, OPFS, SQLite, memory, filesystem and others, some premium); replication plugins; runs in browsers, Node.js, Deno, React Native, Capacitor, NativeScript, Flutter and Electron
Financiamento Premium licences: the project's pricing page sells Pro, Pro Plus and Corporate tiers to businesses
Última Investigação 29 de out. de 2026

Capacidades

Armazenamento local-first Portabilidade de dados

Protocolo de Dados Descentralizado Atributos

Origens A reactive database for UI-based real-time applications, later positioned as a local-first database that replicates with existing backends instead of replacing them
Banco de Dados RxDB: this entry is the database. A NoSQL document store layered over a swappable storage engine (localStorage, IndexedDB, OPFS, SQLite, filesystem, memory and others)
Linguagem de Consulta Mango-style selector queries (find with a selector), reactive subscriptions to query results, and field-level observables
Formatos de Dados JSON documents validated against a JSON schema, with attachments; the storage format depends on the chosen engine
Edição Colaborativa em Tempo Real Partial: documents sync in real time across clients through replication, with configurable conflict handling and a CRDT plugin; no character-level text editing is described in the README
Edição de Texto Rico Not stated by the project.
Suporte Móvel Yes: React Native, Capacitor, NativeScript and Flutter are listed supported runtimes
Suporte Web Yes: runs in browsers with localStorage by default and IndexedDB or OPFS storages (some premium)
Aplicativos Nativos Yes: Electron, React Native, Capacitor and Node.js; SQLite storage for native runtimes is a premium plugin
Termos Free for the open-source core (Apache-2.0); paid Pro, Pro Plus and Corporate tiers for premium plugins, advertised from $99 per month billed annually
Fundos Not stated by the project.
Baseado Em RxJS (observables), CouchDB-style replication ideas, and the underlying storage engines; the README does not name a single parent project
Arquitetura P2P Replication to backends and, optionally, WebRTC peer-to-peer replication between clients: the README lists replication as a feature and the project documents a WebRTC replication plugin; there is no discovery layer or overlay network of its own
Rede de Sobreposição None: replication is configured per collection; the WebRTC plugin uses a signalling server the application chooses
Endereçamento por Conteúdo No: documents are keyed by a primary key defined in the schema
Local-First Local-First: the project describes itself as a local-first database; data is read and written locally and replicated when connected
Criptografia de Ponta a Ponta (E2EE) Optional: an encryption plugin encrypts stored fields; whether it provides end-to-end encryption between peers depends on how the application is designed; the Pro tier lists WebCrypto encryption
Biblioteca de CRDTs Yes, as an optional CRDT plugin for conflict-free updates within documents
Tolerância a Falhas Bizantinas No: replication trusts the configured backend and peers
Assinatura N/A: documents are not signed by the library
Permissões Application- and backend-level: no permission model in the local database; access control is enforced by the replication backend
Compatibilidade com a Web Semântica N/A: JSON document store with no RDF layer
Contrato Inteligente N/A: no ledger or contract component
Posição na Pilha de Protocolo Application-layer: a JavaScript library over local storage and replication transports (HTTP, WebSocket, WebRTC)
Incorporação de Ativo / Valor None: no token or value-transfer mechanism
Maturidade / Padronização do Protocolo Mature library (version 17) with a documented replication protocol for its own backends; no standards-body involvement