Scale
Thousands of open queries. 1k writes/second. 1 GB of data. 1 vCPU.

A support desk, read as live queries: one zoomable plane, a block of cards per org, and a card
per query — tiles at a distance, real rows and real deltas up close. Customers write in, and
agents watching the inbox, the escalation searches and each team’s load react to what their
own live queries tell them, registering a watch on every ticket they pick up. Behind it are the
tiers a hosted deployment has: one rindled in authority posture holding the data and every
pipeline, and a stateless API server that is the only way in to it.
Running live, with the same page on two hosts in front of one shared backend:
- Vercel: https://rindle-scale-demo.preview.rocicorp.dev/
- Cloudflare: https://rindle-scale-demo.replicache.workers.dev/
Try it locally:
pnpm install
# Builds the server and seeds the data on first run.
# Then open http://127.0.0.1:7801
pnpm --filter @rindle/agent-desk devIts simpler sibling, the same tiers with no agents and a wasm engine in every tab, is
pnpm --filter @rindle/deployed-scale-demo dev on http://127.0.0.1:7800 — it needs
pnpm run build:wasm first, because that board holds its own engine.
Full-Stack Sync
The headline demo from Zero, rewritten using the Rindle adapter.

Try it locally (needs Docker for Postgres; this config still uses a Postgres upstream):
pnpm install
pnpm --filter @rindle/zbugs build:runtime # builds the Rindle binaries
# Starts Postgres, the Rindle gateway + follower, and Vite on :5173
cd apps/zbugs && pnpm dev
# Seed it, using the port `pnpm dev` printed
ZERO_UPSTREAM_DB='postgres://rindle:rindle@127.0.0.1:<port>/app' \
pnpm db-seedClient-Side Live Queries
The core Rindle database is a small library, gzip-compressed. It runs on the web via wasm, in Node natively, and in any Rust program as a crate. It provides a full relational, embedded database with live queries that answer and update in microseconds. Hook it to the Rindle server for a full, opinionated stack, or to your own server however you want.

Try it locally: the demo lives in its own repo, rocicorp/wasm-canvas-demo.
Streaming Queries Against Any Change Source
Put Rindle downstream of your existing database, Kafka stream, whatever. Delete your websockets, webhooks, and API. Agents can directly watch any relational query they want, efficiently. Rindle becomes shared infra within your org that agents use to watch changing data.

Rindle sits downstream of Wikimedia’s live edit firehose. Every browser that opens attaches to the same maintained boards, so N readers cost one pipeline, not N.
Try it locally: the data tier in one terminal, the UI in another.
# Boots a rindled authority with two pinned boards and ingests the live Wikimedia feed
cd apps/wiki-demo && pnpm dev
cd apps/wiki-demo && pnpm dev # the data tier; its browser UI retired with product-page