Matillion VS Meltano

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.

Meltano was founded in 2018 as an open source project within GitLab to support their data and analytics team. It’s a Python framework built on the Singer protocol. The Singer framework was originally created by the founders of Stitch, but their contribution slowly declined following the acquisition of Stitch by Talend (which in turn was later acquired by Qlik).

Meltano is focused on configuration-based ELT using YAML and the CLI.

• Open source ELT: Meltano is the main successor to Stitch if you’re looking for a Singer-based framework.
• Configuration-driven: If you are looking for a configure-driven approach to ELT, Meltano may be a great option for you.
• Connectivity: Meltano and Airbyte collectively have the most connectors, which makes sense given their open source history with Singer. Meltano supports Singer and has an SDK wrapper for Airbyte, giving it 600+ open source connectors in total. Open source connectors have their limits, so it’s important to test out carefully based on your needs.

• Not low-code: If you’re looking for a more graphical, low-code approach to integration, Meltano is not a good choice.
• Latency: Meltano is batch-only. It does not support streaming. While you can reduce polling intervals down to seconds, there is no staging area. The extract and load intervals need to be the same. Meltano is best suited for supporting historical analytics for this reason.
• Reliability: Some will say Meltano has less issues when compared to Airybte. But it is open source. Connectors may not be maintained and if you have issues you can only rely on the open source community for support.
• Scalability: There isn’t as much documentation to help with scaling Meltano, and it’s not generally known for scalability, especially if you need low latency. Various benchmarks show that larger batch sizes deliver much better throughput. But it’s still not the level of throughput of Estuary or Fivetran. It’s generally minutes even in batch mode for 100K rows.
• ELT only: Meltano supports open source dbt and can import existing dbt projects. Its support for dbt is considered good. It also has the ability to extract data from dbt cloud. Meltano does not support ETL.
• Deployment options: Meltano is deployed as self-hosted open source. There is no Meltano Cloud, though Arch is offering a broader service with consulting.
• DataOps: Data engineers generally automate using the CLI or the Meltano API. While it is straightforward to automate pipelines, there isn’t much support for schema evolution and automating responses to schema changes.

Meltano is open source. There is no pricing. But it’s not really free. You’ll need to spend more on data engineering resources to stand up, build, and maintain Meltano. If you need scalability, there isn’t a lot of documentation on how to scale. Make sure you evaluate carefully and find some Meltano expertise.

Estuary is a managed data integration platform for CDC, streaming, and batch pipelines. It supports database CDC, SaaS and API ingestion, event streams, files, warehouses, data lakes, operational systems, and AI destinations, with delivery ranging from real-time streaming to scheduled batch intervals.

At the center of Estuary is its runtime, where captured data is written to durable collections and can be independently read by multiple destinations and transformations. This separates source capture from downstream delivery and allows data to be reused for additional destinations, backfills, and reprocessing without repeatedly extracting it from the source.

Estuary offers 200+ fully managed connectors, no-code capture and materialization setup through the web application, and streaming transformations using SQL, Python, and TypeScript. It also supports dbt Cloud, materialization triggers, Agent Skills for AI-assisted pipeline development, and Public, Private, and Bring Your Own Cloud (BYOC) deployment options.

• CDC, streaming, and batch in one platform: Estuary supports log-based CDC, SaaS and API ingestion, event streams, files, and scheduled batch movement for analytical and operational use cases.
• Real-time runtime with durable collections: Estuary's runtime separates captures from materializations through durable collections, allowing data to be reused for multiple destinations, transformations, backfills, and replay without re-extracting it from the source.
• Low-latency delivery: Supported real-time pipelines can deliver data with sub-second latency, while delivery can also be scheduled when lower freshness is sufficient.
• No-code setup with advanced transformation options: Pipelines can be configured through the web application, while SQL, Python, and TypeScript transformations, dbt Cloud, APIs, and flowctl support more advanced workflows.
• Built-in monitoring and AI-assisted operations: Estuary includes logs, latency and usage metrics, pipeline alerts, OpenMetrics integrations, and Agent Skills for AI-assisted pipeline development and troubleshooting.
• Flexible deployment and predictable pricing: Public, Private, and BYOC deployments provide different levels of infrastructure control, while pricing is based on data volume and prorated connector task hours rather than Monthly Active Rows.

• Smaller managed connector catalog than some large ELT platforms: Estuary offers 200+ fully managed connectors, but some larger platforms have broader packaged coverage, particularly for long-tail SaaS and legacy enterprise applications. Custom connector development is available with Enterprise.
• No visual transformation canvas: Pipeline setup is no-code, and fields can be selected or renamed in the UI, but more complex streaming transformations use SQL, Python, or TypeScript rather than a drag-and-drop transformation canvas.
• Advanced workflows have a learning curve: Basic capture and materialization pipelines can be built through the web application, but advanced derivations, schemas, CLI workflows, and GitOps-style deployments require more data engineering familiarity. Some Estuary users on G2 also mention a learning curve for more advanced configurations.

Estuary pricing is based on data volume moved and connector instance usage. Data movement is priced at $0.50 per GB. The first six connector instances are priced at $100 per month each, while additional connector instances are $50 per month each, with usage prorated based on active connector instances.

The permanent free tier includes up to 10 GB of data movement per month and two concurrent connector instances, while the 30-day trial provides access to the full Cloud plan.

Enterprise plans can include volume discounts, Private or BYOC deployments, custom SLAs, private networking, dedicated support, and custom connector development.

Because pricing is based on GB moved plus connector usage rather than row-change metrics such as MAR, costs are relatively predictable from data volume and connector usage.