AWS DMS VS Matillion

AWS Database Migration Service (DMS) was introduced as a tool to help migrate legacy databases into AWS. While it supports full-load and CDC replication, DMS is not a modern integration platform. It lacks support for modern SaaS APIs, streaming destinations, and developer-friendly deployment models.

• Available in AWS: Works within AWS without provisioning servers.
• Basic CDC support: Handles incremental replication from supported databases.

• Not real-time: DMS is not a streaming system. Latency varies and is hard to monitor in production.
• No extensibility: No community ecosystem, no custom connectors, no plugin support.
• Operational overhead: Task failures are common and require manual troubleshooting. Configuration and credential management are fragile.
• Rigid delivery options: Cannot deliver to modern analytics stacks or streaming endpoints.
• Expensive at scale: Costs add up with replication instance hours, storage, and logging. Lacks predictability for long-term CDC jobs.

Costs are based on replication instance size and duration (e.g., t3.medium ~$0.036/hr), plus storage and logs. Tasks that run continuously or process high volumes can become costly without offering the capabilities of modern platforms. There is no free tier, and pricing becomes opaque with additional monitoring and retries.

Matillion ETL is an on-premises ETL platform that was founded before the advent of cloud data warehouses, and is still primarily on premises. But its main destinations today are cloud data warehouses such as Snowflake, Amazon Redshift, and Google BigQuery.

Matillion combines many features to extract, transform, and load (ETL) data. More recently Matillion has been adding cloud options as part of the Matillion Data Productivity Cloud. It consists of a Hub for administration and billing, a choice of working with the on-premises Matillion ETL deployed as “private cloud” or Matillion Data Loader, a free cloud batch and CDC replication tool built on Matillion ETL but lacking many of its capabilities including transforms.

As with most of the mature ETL tools, Matillion has a strong set of features, but is harder to learn and use and is more expensive.

Perhaps one of the biggest advantages of Matillion is its ETL and orchestration, especially when compared to various ELT tools.

• Advanced transforms: Matillion ETL supports a variety of transform options, from drag-and-drop to code editors for complex transformations.
• Orchestration: Matillion offers advanced graphical workflow design and orchestration.
• Pushdown optimization: Matillion ETL can push down transformations to the target data warehouse.
• Reverse ETL: Matillion provides the ability to extract data from a source, cleanse it, and insert data back into the source.

• SaaS: Matillion ETL, its flagship product, is on-premises only. It does offer Data Loader, which is built on ETL, as a free cloud service for replication. There is also integration between Matillion ETL and the Matillion Cloud Hub for billing. While you can migrate work in Data Loader to ETL if you choose, it is a migration from the cloud to your own managed environment. 
• Free tier: Matillion Data Loader is free, but it’s limited and doesn’t support transforms. This can make it challenging to fully evaluate the tool before committing to a paid plan.
• Connectors: Matillion has fewer connectors than most (150+ in total). You can invoke external APIs to access other systems, but access to all your sources and destinations can become an issue. Matillion is only used for loading data warehouses. 
• No CDC: Matillion ETL CDC, which was based on Amazon DMS (in turn based on Attunity) has been deprecated. So right now there is no CDC option with Matillion. 
• Schema evolution: Matillion does support adding columns to existing destination tables, deleting a column, and handling data type changes as sources change. But adding a table requires creating a new pipeline and there is no automation for schema evolution.
• dbt integration for SaaS: While Matillion ETL has a connector for dbt, there is no integration between Data Loader and dbt.
• Pricing: Compared to more modern ELT vendors, Matillion is expensive. It starts at $1000/month for 500 credits where each credit is a virtual core-hour similar to an AWS, Azure, or Google virtual core. This is really in the $1000s per month minimum. Data productivity Cloud consumes a credit per running task every 15 minutes, and only consumes when tasks are running. The smallest ETL unit is two cores, which means you consume 2 cores an hour, or nearly 3x the 500 credits every month.

Matillion doesn’t have a pay-as-you-go model. It starts at $1000/month for 500 credits where each credit is a virtual core-hour similar to an AWS, Azure, or Google virtual core. Pricing increases 25% per credit for advanced and 35% for enterprise with higher base commitments.

This is really in the $1000s per month minimum. Data productivity Cloud consumes a credit per running task every 15 minutes, and only consumes when tasks are running. The smallest ETL unit is two cores, which means you consume 2 cores an hour, or nearly 3x the 500 credits every month.

Estuary is the right-time data platform that replaces fragmented data stacks with one dependable system for data movement. Teams use it to move data from databases, SaaS apps, files, and streams into warehouses, lakes, operational stores, and AI systems at the cadence they choose: sub-second streaming, near real-time, or scheduled batch. Founded in 2019, Estuary is built on Gazette, an open-source streaming broker developed by the same founding team that lets Estuary mix CDC, streaming, and batch in a single catalog with exactly-once delivery, deterministic recovery, and targeted backfills.

Unlike traditional ELT tools that focus on batch loads, Estuary stores every event in collections that can be reused for multiple destinations. Captured changes are written once to durable storage and fanned out to any number of targets without reloading the source, which reduces load on primary systems and makes replay easy when schemas change. Estuary runs as a multi-tenant cloud service, private data plane, or BYOC, and ships with 200+ fully-managed native connectors plus support for open-source Airbyte, Meltano, and Stitch connectors.

For AI-native workflows, Estuary ships Agent Skills that work with Claude Code, Cursor, OpenAI Codex, GitHub Copilot, and Gemini CLI, letting developers create captures, materialize into Snowflake, BigQuery, Redshift, or Databricks, and troubleshoot pipelines through natural-language prompts. A separate MCP server handles docs-aware Q&A inside the same assistants.

Customers include Glossier, which cut data costs by 50%; Xometry, which reduced integration costs by 60% with private deployment; Headset, which cut Snowflake ingestion costs by 40% after replacing Airbyte; and Prodege, which built Apache Iceberg pipelines.

• Right-time pipelines from millisecond streaming to scheduled batch. Choose cadence per pipeline so cost and freshness match each workload. Most ELT tools default to 15-minute or hourly intervals.
• One platform for CDC, batch, and streaming. Replaces the typical 3-4 tool stack of Debezium plus Kafka plus Airbyte plus dbt with a single system, reducing tool sprawl and operational overhead.
• Dependable replication built on Gazette. Exactly-once delivery, deterministic recovery, and targeted backfills keep pipelines stable through schema changes and source failures.
• Efficient log-based CDC with collection reuse. Captures inserts, updates, and deletes once, then fans out to any number of destinations without re-reading the source database, reducing load on production systems.
• Predictable usage-based pricing. $0.50 per GB moved plus $100 per connector instance per month for the first 6 instances, then $50 per instance for additional ones. No MAR-based surprises and no per-row charges.
• Agent-native developer experience. Open-source Agent Skills let Claude Code, Cursor, OpenAI Codex, GitHub Copilot, and Gemini CLI build and operate Estuary pipelines from natural language, with an MCP server for docs-aware Q&A in the same tools.

• No graphical transformation UI. Estuary focuses on SQL and TypeScript transformations alongside dbt integration. Teams that need point-and-click visual ETL like Matillion or Informatica PowerCenter will find this a gap, though dbt covers most warehouse-side needs.
• On-premises connectivity is narrower than legacy ETL vendors. For mainframe, SAP ECC on-premises, or other proprietary on-premises systems, vendors like Informatica or Talend may have broader native coverage. Verify legacy on-premises coverage during evaluation.
• Smaller market presence than category incumbents. Fivetran, Informatica (now Salesforce), and Talend (now Qlik) have larger enterprise customer bases and longer procurement track records. Estuary fits teams able to evaluate on technical merit, but buyers requiring a Gartner Magic Quadrant leader may need to factor this in.

Estuary uses a straightforward usage-based pricing model. Data movement is charged at $0.50 per GB sourced or delivered. Connector instances are $100 per month for the first 6 instances, then $50 per month for each additional instance. A Developer tier is free indefinitely up to 10 GB per month and 2 concurrent connector instances, and Cloud-tier customers can request a 30-day free trial.

Use the Estuary pricing calculator to model your specific workload. For larger deployments, Enterprise plans add volume-based discounts, SOC 2 and HIPAA compliance reports, SSO, custom SLA terms, private deployments, and dedicated support.