REAL-TIME DATA

Turn database changes into live products.

Capture committed PostgreSQL changes, send them to other systems, and update connected users—without losing track of delivery or recovery.

1.1.0-rc.1 publicStreamsCapture changes and recover safely
RC verified · 72-hour stable test pending
1.1.0-rc.1 publicSyncKeep other systems up to date
RC verified · 24-hour stable test pending
1.1.0-rc.1 publicLiveSend permitted updates to users
Package and install checks passed
1.1.0-rc.1 publicControl PlaneMonitor and manage the system
Package dependencies verified
SAFE DELIVERY

Save progress only after the work is safe.

Select a step to see how BlueTusk moves from a committed database change to a recoverable update.

SOURCE OF TRUTH

PostgreSQL commits the transaction

PostgreSQL replication provides changes only after the transaction commits.

No progress is marked complete yet.
EXISTING DATA → LIVE CHANGES

Start live updates without missing anything.

How the initial load works
01

Choose a consistent starting point

Open one consistent view of the data and record where live changes begin.

02

Load the existing data

Stream the current rows to the consumer without loading everything into memory.

03

Save the handover point

Record the exact position where the initial load hands over to live changes.

04

Follow new changes

Continue from the saved position without a gap or an unknown overlap.

SYNC DESTINATIONS

Retries stay safe, even after a crash.

BlueTusk never saves progress before the destination is durable. If the final transaction is sent again during recovery, each connector has a tested way to prevent stale or unsafe work.

DestinationHow it writesHow it recoversProven guarantee
PostgreSQLWrite the full change and checkpoint togetherA retry finds the saved checkpoint and does no duplicate workAtomic state + checkpoint
NATSPublish one durable transaction envelopeDeduplicate its stable ID in JetStream and downstreamDurable publish + stable identity
RedisWrite the full change and checkpoint in one Lua operationA retry cannot pass an equal or newer checkpointAtomic state + checkpoint
OpenSearchBulk-write documents with source versionsReplay the bulk; older versions cannot replace newer stateReplay-safe materialisation
LIVE DELIVERY

Send the right data to the right users.

Live sends an initial result and then only the changes. It checks permissions when needed, recovers missed updates, and slows down safely when clients cannot keep up.

SSEWebSocketsBrowser clientReplayBackpressureShared subscriptions
OPERATIONS AT A GLANCE
Data sourcesIdentity, current position, and delay
Replay storageStored changes, retention, and backups
ConsumersWorkers and their saved progress
Audit historyWho changed what and when
Open operations guide