// CONDOR RETL
Open-source reverse ETL for customer activation
Condor RETL turns warehouse-shaped rows into destination-facing mutations for audiences, traits, events, and predictive signals.
// HOW IT WORKS
A sync runtime for activation infrastructure
RETL separates source shaping from destination delivery, so warehouse SQL owns the data shape and the runtime handles planning, recovery, and sync execution.
Warehouse-shaped rows
Start with SQL-backed source rows from DuckDB, Snowflake, BigQuery, Databricks, PostgreSQL, or another supported backend.
State and event intent
Declare desired current facts like audience membership and profile attributes, or occurred facts like purchases and lifecycle events.
Destination surfaces
Bind syncs to connector-owned API contracts such as Meta Custom Audiences, Klaviyo profiles, customer match lists, or event surfaces.
Dry-run planning
Inspect destination-facing mutations before irreversible writes, with operator evidence for what will be sent.
Recovery-first runtime
Run durable collect, stage, reconcile, and sync phases with retry-aware ledger state and clear recovery behavior.
Scheduled delivery
Use RETL as the open sync layer for hourly, daily, weekly, or workflow-triggered audience and signal refreshes.
// DEVELOPER DOCS
Docs are live at docs.condorgraph.com
Start with the quickstart, then move into concepts, guides, examples, destination packages, runtime commands, and recovery behavior.
// USE CASES
Use RETL where activation meets engineering
Run it as open-source infrastructure, use it behind Activation Agent, or build destination connectors around its runtime contracts.
Audience membership
Sync customer lists and suppression audiences from warehouse queries to downstream media partners.
Profile attributes
Send traits, lifecycle states, and predictive signals to lifecycle and customer engagement tools.
Event delivery
Move occurred facts like purchases, signups, or campaign events into destination event APIs.
Local development
Use DuckDB and mock/reference destinations to author, test, and inspect sync behavior before partner writes.
Connector development
Build destination connectors around explicit surfaces, receipts, outcomes, and compatibility contracts.
Standalone operation
Run Condor RETL directly as open-source infrastructure, with or without the broader Condor platform.
Build on open sync infrastructure
Schedule a demo and see how Condor RETL fits into the broader Condor activation system.