docs · reading path

use the engine.

Maintain a query result in-process with the open engine — read models, caches, derived state. Scale to shared, high-concurrency reads with the commercial live-replica runtime.

the embedded track lands herebuilding the whole app? build a synced app →

Start

What is Rindle?Rindle keeps your queries live with one engine — from a browser tab to a Node server to a synced, local-first app, behind one query language and one correctness contract.
Is Rindle for you?Who Rindle is for, what it replaces, how it compares to hand-rolled stacks, sync frameworks, hosted reactive backends, and warehouse-scale IVM — and the workloads it's wrong for.

The engine

How it worksThe five-step lifecycle every crate shares — build a query, lower it into a graph, add a view, hydrate, push and flush — and why incremental beats recompute.
The change modelTwo change vocabularies: SourceChange goes in, CaughtChange comes out — plus the change sink that delivers them and the replay-equivalence invariant.
Reactive queries in the browserThe dream API — a typed schema, a fluent query builder, and a live materialized view, all running on the IVM engine compiled to wasm, in-process in the browser.
Rust quickstartStand up a live, incrementally-maintained SQLite query with the open engine — register a source, hydrate a view, and watch a write-through push update it by the delta.
Backends & the homesOne engine, one query API, one correctness contract — over wasm in the browser, native SQLite in Node, or a server. The Backend seam that lets one view serve every tier.
Fold the delta stream yourself (Rust)The low-level home — attach a change sink and the open engine hands you the raw delta stream. Maintain your own view from the diffs alone, and prove it equals a fresh query.
Schema & migrationsSQL is the source of truth. Define your tables in SQL, evolve them with additive migrations, and generate the typed schema your query builder needs — with one CLI: rindle migrate, rindle schema gen.

High-concurrency runtime

The live-replica runtimeThe commercial runtime on top of the open engine: open a SQLite file, write ordinary SQL through one writer, and every live query streams back raw deltas — then scale it across readers with a thread pool or the daemon.
Run the daemon (rindled)rindled — the always-on server you run like Postgres: the config, the two network planes, boot-id restart recovery, and the multi-threaded Cluster engine underneath.
Deploying & scaling RindleRindle's one topology, from the colocated pair to a read-scaled fleet: an HCTree write-master, read-only followers, canonical backup, concurrent writes, and follower-affinity placement.
@rindle/cliThe npm-installed Rindle toolchain: the rindle CLI, the supervised local rindled daemon, SQL migrations, generated TypeScript schema, and remote daemon commands.

Rindle Cloud

Cloud quickstartSign up, compose a stack, and provision a managed Rindle app in a few minutes — then point your code at it. The fastest path from zero to a running, durable Rindle backend you don't operate.
Connect your app to Rindle CloudPoint your API server and browser client at a managed Rindle Cloud app using the fleet, control, and write endpoints from the dashboard.
Scale & operate on Rindle CloudWhat the Rindle Cloud dashboard does after provisioning — read the converged topology, resize compute and storage, grow the read fleet, suspend and reactivate, and how usage-based billing works.

Reference

Crates & API mapWhat each crate owns, how they compose, and the API index — the map for navigating between the building blocks.
Supported query shapesThe honest matrix of what builds, pushes, and materializes today — written in the Rust rindle::table builder. The explicit list of what does not work yet.
PerformanceWhy incremental maintenance is sub-microsecond and stays flat as data grows — measured end to end over a real dataset, plus a head-to-head against TanStack DB.