The dominant reverse ETL tools — Census, Hightouch, Polytomic — all charge $350-$1,000+/month. QueryFlow is the native Mac alternative for warehouse-to-Salesforce reverse ETL at $299/year flat. Same workflows, dramatically lower price.
Quick answer: QueryFlow is the native macOS reverse ETL tool. It moves data from Snowflake, Redshift, Postgres, or MySQL into Salesforce or Google Sheets via scheduled pipelines running on your Mac. Compared to cloud-managed reverse ETL tools (Census $350/mo, Hightouch $350-1000+/mo, Polytomic per-row), QueryFlow is a flat $25/month with no per-row scaling.
Reverse ETL is the practice of moving curated, transformed data from your data warehouse back into operational tools where business users work — Salesforce, HubSpot, Google Sheets, Slack, Intercom, etc. The 'reverse' part: traditional ETL moves data INTO the warehouse, reverse ETL moves data OUT to where it gets used. The market emerged around 2020 as warehouses became the dominant source of truth for analytics and businesses needed those insights operationalized.
The pricing tiers in the reverse ETL category: Census $350-$1000+/mo, Hightouch $350-$1000+/mo, Polytomic per-row scaling, Fivetran reverse ETL similar. The justification: managed infrastructure, 200+ destination connectors, enterprise compliance (SOC 2), real-time sync, audience management. For larger enterprises, the price makes sense. For smaller teams whose reverse ETL needs are simpler (Salesforce primary destination, daily refresh frequency, modest row volumes), the pricing is wildly disproportionate to value.
Connect a warehouse (Snowflake, Redshift, Postgres, MySQL). Connect Salesforce via OAuth (or Google Sheets, or another database as destination). Build a pipeline: warehouse SQL query as source, Salesforce object as destination, field mapping (AI Map handles the standard cases automatically). Schedule the pipeline on cron, interval, or daily/weekly trigger. The scheduler runs locally via macOS SMAppService. Failed runs appear in the Observatory dashboard.
Daily customer health score sync: Snowflake query computes scores, pushes to Salesforce Account.Health_Score__c field. Weekly target account list: dbt-built table in Snowflake, syncs to Salesforce as account_targets custom object. Hourly conversion event push: Postgres query of recent conversions, writes to Salesforce as Lead status updates. Monthly customer enrichment: Snowflake data joined with third-party enrichment, syncs as Account custom fields. All run as scheduled QueryFlow pipelines.
Census, Hightouch, Polytomic all manage the infrastructure: cloud-hosted, vendor-monitored, vendor-supported. The tradeoffs: higher cost, vendor lock-in, less control over the actual data movement, integration into a Mac-native workflow is awkward. QueryFlow's tradeoffs: lower cost, complete control over pipelines, native Mac experience, but you're responsible for your Mac being on when scheduled jobs need to run.
Dedicated Mac mini as reverse ETL server: $600 hardware, plug in ethernet, leave on 24/7. Many indie/small teams find this dramatically cheaper than Census subscription. Power Schedule on MacBook: wake Mac before scheduled jobs, ensures laptop-based ETL still hits expected times. Hybrid: QueryFlow for less critical reverse ETL, Census for highest-volume tables. Teams cut reverse ETL bills 60-80% this way.
QueryFlow's reverse ETL scope is narrower than dedicated tools. Destinations supported: Salesforce, Google Sheets, plus standard database writeback (Snowflake/Postgres/MySQL/Redshift). Not yet supported: HubSpot, Marketo, Iterable, Braze, Mixpanel, Intercom, Zendesk, etc. (some on the roadmap). For workflows where the primary destination is one of these unsupported tools, current QueryFlow won't work. Vote for connectors at queryflow.featurebase.app/roadmap.
Same Visual ETL pipeline builder, different direction. Forward ETL: source like Postgres production database → destination warehouse like Snowflake. Reverse ETL: source like Snowflake warehouse → destination operational tool like Salesforce. QueryFlow handles both with the same model.
Yes. Your source can be any SQL query against the warehouse — including queries against dbt-built tables, materialized views, or complex JOIN/window-function queries. The result of the query is what gets pushed to the destination.
Yes. Pipelines can be configured to sync only rows changed since the last run, based on a timestamp column or sequence ID. Standard incremental sync patterns supported.
Salesforce's Bulk API v2 is used automatically for large operations. Daily API call limits are respected — the Observatory dashboard tracks API consumption so you can stay under your org's limits.
If it's a database-backed CRM with standard connectivity (Postgres-based, MySQL-based, etc.), yes — write to the underlying database. For SaaS CRMs that only expose an API (HubSpot, Pipedrive, etc.), you'd need a Flow Book that calls the CRM's API directly, or wait for native connector support.
14-day free trial. Build your first reverse ETL pipeline and see how much you've been overpaying.