Open one consistent view of the data and record where live changes begin.
02download
Load the existing data
Stream the current rows to the consumer without loading everything into memory.
03flag
Save the handover point
Record the exact position where the initial load hands over to live changes.
04play_arrow
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
databasePostgreSQLWrite the full change and checkpoint togetherA retry finds the saved checkpoint and does no duplicate workAtomic state + checkpoint
swap_horizNATSPublish one durable transaction envelopeDeduplicate its stable ID in JetStream and downstreamDurable publish + stable identity
memoryRedisWrite the full change and checkpoint in one Lua operationA retry cannot pass an equal or newer checkpointAtomic state + checkpoint
searchOpenSearchBulk-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.
OPERATIONS AT A GLANCEsourceData sourcesIdentity, current position, and delayarchiveReplay storageStored changes, retention, and backupsgroupsConsumersWorkers and their saved progresshistoryAudit historyWho changed what and whenOpen operations guide arrow_forward