Comparison
Fivetran merged with dbt Labs in June 2026, so extraction and transformation now come from one vendor. Etlworks goes further still — CDC, API integration, EDI, and on-prem deployment, at fixed pricing instead of per-row MAR.
The verdict
Feature breakdown
| Capability | Etlworks | Fivetran |
|---|---|---|
| Pricing & commercial | ||
| Starting price (monthly) | $300 | $1,000+ |
| Pricing model | Fixed per tier | Consumption-based (per-row) |
| Cost transparency | High — flat rate | Low — varies with data volume |
| Vendor lock-in | Monthly or annual, no contract | Annual, no contract |
| Ownership | Independent, founder-run | Fivetran + dbt Labs — merged June 2026 |
| Integration scope | ||
| Sources | 260+ | 700+ |
| Destinations | Warehouses, databases, SaaS, NoSQL, files, APIs, queues, IoT, email | Data warehouses, data lakes |
| ETL capabilities | ETL, ELT, Reverse ETL, wildcard processing | ELT, limited ETL |
| API management | Full | |
| EDI processing | X12, EDIFACT, HL7, FHIR | |
| On-prem deployment | ||
| Embeddable | ||
| Transformations | ||
| Visual mapping | drag-and-drop designer with live preview | column selection and renaming only |
| Scripting languages | SQL, JavaScript, Python, XSLT, shell | SQL and dbt |
| Nested and hierarchical data | JSON, XML, Avro, Parquet — read, write, normalize, flatten by dragging | Partial — passes JSON through, unpacking happens downstream |
| Warehouse pushdown (ELT) | transform before load or in the warehouse, same engine | dbt models in-house since the merger |
| Reusable logic | macros, templates, and 3,900+ prebuilt flow templates | dbt packages |
| Lookups and enrichment | Lookup Builder for cross-source lookups | |
| Data validation | validation rules with per-step error handling | dbt tests |
| Orchestration & workflow | ||
| Scheduling | Cron expressions and fixed intervals, with per-schedule parameters | Sync frequency per connector |
| Event-driven triggers | HTTP listeners and webhooks, message queues, file and email events | |
| Continuous execution | looping schedules for CDC and queue consumers | Partial — continuous sync on higher tiers |
| Visual workflow builder | Composer canvas, 200+ flow types | connector configuration, not a canvas |
| Nested workflows | nested flows with conditional and looped steps | Partial — dbt project dependencies since the merger |
| Run external tools | shell and SSH scripts, CLI, JavaScript, Python, SQL, HTTP calls | |
| Parallel execution | overlapping schedules run as independent, separately cancellable instances | Partial — connectors sync independently |
| Retries and error handling | per-step exception handling with notifications | automatic retry on sync failure |
| Run monitoring | per-schedule status, run history, automatic Flow Findings reports | sync logs and alerts |
| CDC & Streaming | ||
| CDC engine | Debezium-compatible, built-in (no Kafka required) | Native managed CDC |
| Database CDC sources | MySQL, Postgres, SQL Server, Oracle, MongoDB, DB2, others | MySQL, Postgres, SQL Server, Oracle, MongoDB, DB2, others |
| Streaming queues | Kafka, EventHubs, Kinesis, SQS, PubSub, ActiveMQ, RabbitMQ | Kafka |
| IoT brokers | MQTT brokers | |
| Real-time replication | Log-based CDC, full, incremental | Log-based CDC, full, incremental |
| Change tracking modes | Log-based, trigger-based, timestamp/high-watermark | Log-based |
| Developer experience | ||
| REST API | full API for flows, connections, schedules, and runs | |
| CLI | full CLI with built-in SQL | Partial — limited or community CLI |
| MCP server | built-in — connect Cursor, Claude, or ChatGPT to your instance | |
| Client libraries | Python, Bash, and PowerShell clients | Partial — community SDKs |
| Version control | built-in — automatic history, diff, and revert on every artifact | Partial — change history, no diff or revert |
| Embeddable / white-label | ||
| Compliance & security | ||
| SOC 2 Type 2 | audited; report under NDA, SOC 3 public | |
| HIPAA | supported with a BAA | Partial — higher tiers only |
| GDPR / DPA | compliant, DPA available | |
| SSO and MFA | SAML SSO, optional 2FA, JWT stateless auth | Partial — enterprise tier |
| Role and artifact-level access | six roles plus tag-based scoping of flows, connections, and schedules | Partial — role-based, no artifact-level scoping |
| Encryption and data handling | TLS in transit, encrypted at rest, customer-managed PGP, SSH tunnels, IP allowlisting; rows are not persisted by default | encrypted in transit and at rest |
| Audit logging | admin actions logged, access logs monitored | Partial — enterprise tier |
| Security testing | monthly vulnerability and penetration scans, static analysis blocking every build, periodic third-party audits | vendor-managed, details on request |
| Gen AI | ||
| AI agent | Built-in agent (Simba) — builds and edits flows from chat | Partial — MCP-based agents for connector creation (developer-focused) |
| Agent capabilities | Reads metadata, reads/samples data, writes JS & SQL, schedules, deploys, monitors | Generate connectors from API docs, debug sync failures |
| Natural-language flow building | ‘Vibe-build’ — create flows by describing what you want | Partial — primarily for connector authoring |
| AI-driven mapping | Auto-suggests source-to-destination mappings | |
| Built-in analytics | Agent runs analysis on flow data and pipeline behavior | |
| Chat across product | Same agent context on every screen | |
| CLI for agent | Full CLI access for run/deploy/monitor/manage | Partial — via MCP infrastructure |
| Trains on customer data | Never | Not by default |