docs · reading path

build a synced app.

Take the same engine all the way to a synced, local-first app: optimistic writes, live subscriptions, three tiers — browser client, stateless authority, always-up daemon.

ai, ui & cache tracks land herejust the engine? use the engine →

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.

Build a synced app

Synced-app quickstartBuild a synced, local-first app end to end on one page: a SQL schema as the source of truth, generated TypeScript, an optimistic browser store, isomorphic mutators, your API authority, and the rindled daemon (self-hosted or on Rindle Cloud). Every file, every command.
Scaffold with create-rindleGenerate a SQL-first Rindle app on TanStack Start: browser client, API authority, rindled daemon, migrations, generated schema, SSR, and devtools in one template.
The three-tier architectureHow a synced Rindle app is wired — an optimistic browser client, a stateless API authority, and the always-up rindled daemon — plus the two planes and who is trusted with what.
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.
Isomorphic mutatorsOne generator body per write, run on both tiers — the browser drives it synchronously as the optimistic prediction, the API server drives the same body into SQL as the authority. The op vocabulary, reads, the acting principal, and the determinism rules.
The browser clientcreateRindleClient gives the browser its own IVM engine over a local database — reads resolve instantly, writes apply optimistically and rebase, and rejections snap back on their own.
Agents on live dataWire an agent as another subscriber: named diffs in, salience-ranked digests out — the narrator registry over a view's own change channel, netted and per-view, on the same store your UI uses.
Compose the UI with fragmentsLet each component declare the data it renders, then root the whole screen in one live coverage query with useRoot - no request waterfall.
The API serverYour app's authority — a stateless, serverless-shaped tier that authenticates the caller, resolves named queries to ASTs, drives the same isomorphic mutators the browser predicted into SQL, and keeps pinned queries warm for one-shot reads.
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.
Server renderingPreload named Rindle queries during SSR, dehydrate first-paint rows, hydrate the browser store, then hand off to the live wasm client without a flash.
Full app: the issue trackerA real issue tracker on all three tiers — rindled daemon, API server, optimistic React client — with paginated live windows over 5,000 issues and two live rejection paths. One command.
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 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

@rindle/cliThe npm-installed Rindle toolchain: the rindle CLI, the supervised local rindled daemon, SQL migrations, generated TypeScript schema, and remote daemon commands.
The change modelTwo change vocabularies: SourceChange goes in, CaughtChange comes out — plus the change sink that delivers them and the replay-equivalence invariant.
Supported query shapes (TypeScript)The honest matrix of what builds, pushes, and materializes today — written in the @rindle/client TypeScript 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.
DevtoolsInspect a Rindle app in development: mutation timeline, live query inspector, raw delta stream, and the dev-only wiring for @rindle/devtools and @rindle/react-devtools.
TroubleshootingThe rules that keep a Rindle app correct, and the ways an app goes subtly wrong when one is broken — sync that never starts, schema drift, optimistic flicker, silent writes, and auth smells, each with its fix.