What people build on it.

Five shapes the same pipeline takes, each with the sinks that fit.

Webhooks for your database

A row changes, an HTTP request fires. No trigger functions, no cron polling a updated_at column, no outbox table to drain.

Cache invalidation

The second-hardest problem in computer science, solved by reading the write-ahead log: every committed change reaches the cache in order, and a delete removes the key.

Search index sync

Rows in, documents out, within about a second — no nightly re-index, no dual writes from the application, no indexing pipeline to run.

Event-driven services

Every committed change becomes a message on the bus you already run, keyed by row. Services subscribe instead of calling each other.

Audit log and archive

An append-only record of what changed, when, and what it changed from — written to object storage you control.