Estuary

Matillion VS Rivery

Read this detailed 2025 comparison of Matillion vs Rivery. Understand their key differences, core features, and pricing to choose the right platform for your data integration needs.

Compare
View all comparisons
Matillion logo
Comparison between Matillion and Rivery
Rivery logo
Share this article

Table of Contents

Start Building For Free

Introduction

Do you need to load a cloud data warehouse? Synchronize data in real-time across apps or databases? Support real-time analytics? Use generative AI?

This guide is designed to help you compare Matillion vs Rivery across nearly 40 criteria for these use cases and more, and choose the best option for you based on your current and future needs.

Comparison Matrix: Matillion vs Rivery vs Estuary

Matillion logo
Matillion
Rivery logo
Rivery
Estuary logo
Estuary
Database replication (CDC)MatillionDB2 (i series), MySQL, Oracle, Postgres, SQL Server RiveryMongoDB, MySQL, Oracle, Postgres, SQL ServerEstuaryMySQL, SQL Server, Postgres, AlloyDB, MariaDB, MongoDB, Firestore, Salesforce, ETL and ELT, realtime and batch
Operational integrationMatillion

Batch only

Rivery
Estuary

Real-time ETL data flows ready for operational use cases.

Data migrationMatillion

Support for many sources, error handling, scheduling & automation.

Not suitable for migrations requiring continuous data consistency.

Rivery
Estuary

Intelligent schema inference and evolution support.

Support for most relational databases.

Continuous replication reliability.

Stream processingMatillion
Rivery
Estuary

Real-time ETL in Typescript and SQL

Operational analyticsMatillion
Rivery
Estuary

Integration with real-time analytics tools.

Real-time transformations in Typescript and SQL.

Kafka compatibility.

AI pipelinesMatillion
Rivery
Estuary

Pinecone support for real-time data vectorization.

Transformations can call ChatGPT & other AI APIs.

Apache Iceberg SupportMatillion

Batch-only, Iceberg writes via file-based destinations and optional Spark/EMR jobs; not real-time capable.

Rivery

Batch-only, no native support.

Estuary

Native Iceberg support, both streaming and batch, supports REST catalog, versioned schema evolution, and exactly-once guarantees.

Number of connectorsMatillion150+Rivery200+Estuary200+ high performance connectors built by Estuary
Streaming connectorsMatillionVery limited. No Kafka, Kinesis, Pub/Sub. Supports a handful of SQL streaming sources.RiveryCDC onlyEstuaryCDC, Kafka, Kinesis, Pub/Sub
3rd party connectorsMatillion
Rivery
Estuary

Support for 500+ Airbyte, Stitch, and Meltano connectors.

Custom SDKMatillion

Custom connectors (API/JSON only) and Flex (preconfigured)

Rivery

(REST)

Estuary

SDK for source and destination connector development.

Request a connectorMatillion
Rivery
Estuary

Connector requests encouraged. Swift response.

Batch and streamingMatillionMostly batch. Limited streamingRiveryBatch-only destinationsEstuaryBatch and streaming
Delivery guaranteeMatillionExactly onceRiveryExactly onceEstuaryExactly once (streaming, batch, mixed)
ELT transformsMatillion

SQL

Rivery

SQL, Python

Estuary

dbt Cloud integration

ETL transformsMatillion

SQL or visual drag-and-drop interface for transformations.

Rivery

Python (ETL or ELT). SQL runs in target (ELT).

Estuary

Real-time, SQL and Typescript

Load write methodMatillionSoft and hard deletes, append and update in place (with work)RiverySoft and hard deletes, append and update in placeEstuaryAppend only or update in place (soft or hard deletes)
DataOps supportMatillion

Limited, and cloud only

Rivery

CLI, API

Estuary

API and CLI support for operations.

Declarative definitions for version control and CI/CD pipelines.

Schema inference and driftMatillion

Limited. New tables, and fields are not loaded automatically

Rivery

Limited to detection in database sources

Estuary

Real-time schema inference support for all connectors based on source data structures, not just sampling.

Store and replayMatillion
Rivery
Estuary

Can backfill multiple targets and times without requiring new extract.

User-supplied cheap, scalable object storage.

Time travelMatillion
Rivery
Estuary

Can restrict the data materialization process to a specific date range.

SnapshotsMatillion

N/A

Rivery

N/A

Estuary

Full or incremental

Ease of useMatillion

Requires a learning curve

Rivery

Requires a learning curve

Estuary

Low- and no-code pipelines, with the option of detailed streaming transforms.

Deployment optionsMatillionOn premises (ETL), SaaS is different.RiveryPublic cloud only (multi-tenant)EstuaryOpen source, public cloud, private cloud
SupportMatillion

Support beginners well. But steep learning curve

Rivery

Varies based on pricing tier.

Estuary

Fast support, engagement, time to resolution, including fixes.

Slack community.

Performance (minimum latency)MatillionMostly batch. Limited real-time with CDC deprecation.RiveryMinutes (Depending on pricing tier, 60, 15, or 5 minutes minimum)Estuary< 100 ms (in streaming mode) Supports any batch interval as well and can mix streaming and batch in 1 pipeline.
ReliabilityMatillionHighRiveryHighEstuaryHigh
ScalabilityMatillionHigh, with workRiveryMed-HighEstuaryHigh 5-10x scalability of others in production
SOC2Matillion
Rivery
Estuary

SOC 2 Type II with no exceptions

Data source authenticationMatillionOAuth / HTTPS / SSH / SSL / API TokensRiveryOAuth / HTTPS / SSH / SSL / API TokensEstuaryOAuth 2.0 / API Tokens SSH/SSL
EncryptionMatillionEncryption in motion (doesn’t store data)RiveryEncryption at rest, in-motionEstuaryEncryption at rest, in-motion
HIPAA complianceMatillion

HIPAA BAA compliant

Rivery

HIPAA BAA compliant

Estuary

HIPAA compliant with no exceptions

Vendor costsMatillion
Rivery

Low for small volumes (< 20 GB a month)

Estuary

2-5x lower than the others, becomes even lower with higher data volumes. Also lowers cost of destinations by doing in place writes efficiently and supporting scheduling.

Data engineering costsMatillion

Steep learning curve and requires work to implement features like upserts

Rivery

Building pipelines and transformations requires learning.

Estuary

Focus on DevEx, up-to-date docs, and easy-to-use platform.

Admin costsMatillion
Rivery
Estuary

“It just works”

Start streaming your data for free

Build a Pipeline

Matillion

Matillion introductory image

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.

Pros

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.

Cons

  • 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 Pricing

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.

Rivery

Rivery introductory image

Rivery was founded in 2019. Since then it has grown to 100 people and 350+ customers. It’s a multi-tenant public cloud SaaS ELT platform. It has some ETL features, including inline Python transforms and reverse ETL. It supports workflows and can also load multiple destinations.

But Rivery is also similar to batch ELT. There are a few cases where Rivery is real-time at the source, such as with CDC, which is its own implementation. But even in that case it ends up being batch because it extracts to files and uses Kafka for file streaming to destinations which are then loaded in minimum intervals of 60, 15, and 5 minutes for the starter, professional, and enterprise plans.

If you’re looking for some ETL features and are OK with a public cloud-only option, Rivery is an option. It is less expensive than many ETL vendors, and also less expensive than Fivetran. But its pricing is medium-high for an ELT vendor.

Rivery's future offerings, policies, and pricing may be uncertain as they undergo an acquisition with Boomi.

Pros

  • Modern data pipelines: Rivery is the one other modern data pipeline platform in this comparison along with Estuary.
  • Transforms: You have an option of running Python (ETL) or SQL (ELT). You do need to make sure you use destination-specific SQL.
  • Orchestration: Rivery lets you build workflows graphically.
  • Reverse ETL: Rivery also supports reverse ETL.
  • Load options: Rivery supports soft deletes (append only) and several update-in-place options including switch-merge (to merge updates from an existing table and switch), delete-merge (to delete older versions of rows), and a regular merge.
  • Costs: Rivery is lower cost compared to other ETL vendors and Fivetran, though it is still higher than several ELT vendors.

Cons

  • Batch only: While Rivery does extract from its CDC sources in real-time, which is the best approach, it does not support messaging sources or destinations, and only loads destinations in minimum intervals of 60 (Starter), 15 (Professional), or 5 (Enterprise) minutes.
  • Data warehouse focus: While Rivery supports Postgres, Azure SQL, email, cloud storage, and a few other non data warehouse destinations, Rivery’s focus is data warehousing. It doesn’t support the other use cases as well.
  • Public SaaS: Rivery is public cloud only. There is no private cloud or self-hosted option.
  • Limited schema evolution: Rivery had good schema evolution support for its database sources. But the vast majority of its connectors are API-based, and those do not have good schema evolution support.

Rivery Pricing

Rivery charges per credit, which is $0.75 for Starter, $1.25 for Professional, and negotiated for Enterprise. You pay 1 credit per 100MB of moved data from databases, and 1 credit per API call. There is no charge for connectors. If you have low data volumes this will work well. But by the time you’re moving 20GB per month it starts to get more expensive than some others.

Estuary

Estuary introductory image

Estuary is the right time data platform that replaces fragmented data stacks with one dependable system for data movement. Instead of juggling separate tools for CDC, batch ELT, streaming, and app syncs, teams use Estuary 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, near real time, or scheduled.

The company was founded in 2019, built on Gazette, a battle tested streaming storage layer that has powered high volume event workloads for years. That foundation lets Estuary mix CDC, streaming, and batch in a single catalog and gives customers exactly once delivery, deterministic recovery, and targeted backfills across all of their pipelines.

Unlike traditional ELT tools that focus on batch loads into a warehouse, Estuary stores every event in collections that can be reused for multiple destinations and use cases. Once a change is captured, it is written once to durable storage and then fanned out to any number of targets without reloading the source. This reduces load on primary systems, provides consistent history for analytics and AI, and makes it easy to replay or reprocess data when schemas or downstream models change.

Estuary can run as a multi tenant cloud service, as a private data plane inside the customer’s cloud, or in a BYOC model where the customer owns the infrastructure and Estuary manages the control plane. This gives security and compliance teams the control they expect from in house systems with the convenience of a managed platform.

Estuary also has broad packaged and custom connectivity, making it one of the top ETL tools. The platform ships with a growing set of high quality native connectors for databases, warehouses, lakes, queues, SaaS tools, and AI targets. Estuary also supports many open source connectors where needed, so teams can consolidate around one system while still covering niche sources and destinations. Customers consistently highlight predictable pricing, strong reliability, and partner level support as key reasons they choose Estuary instead of Fivetran, Airbyte, or DIY stacks.

Estuary Flow is highly rated on G2, with users highlighting its real-time capabilities and ease of use.

Pros

  • Right time pipelines: Estuary lets you choose the cadence of each pipeline, from sub second streaming to periodic batch, so cost and freshness match the workload.
  • One platform for all data movement: Handles CDC, batch loads, and streaming in one product, which reduces tool sprawl and simplifies operations.
  • Dependable replication: Exactly once delivery, deterministic recovery, and targeted backfills keep pipelines stable even when sources or schemas change.
  • Efficient CDC: Log based CDC captures inserts, updates, and deletes once and reuses them for many destinations, reducing load on operational databases.
  • High scale architecture: Gazette and collections support large, continuous data streams with reliable throughput across multiple targets.
  • Modern transforms: Supports SQL and TypeScript based transformations in motion, and integrates cleanly with dbt for warehouse side ELT.
  • Flexible deployment choices: Available as cloud SaaS, private data plane, or BYOC, giving enterprises strong control over data residency and security.
  • Predictable total cost of ownership: Transparent pricing based on data volume and connector instances avoids MAR based surprises and is easy to forecast.
  • Fast time to value: A guided UI, CLI, and templates help most teams build their first dependable pipelines in hours instead of weeks.
  • Partner level support: Customers report quick connector delivery, responsive troubleshooting, and SLAs that make Estuary feel like an extension of their team.

Cons

  • On premises connectors: Estuary has 200+ native connectors and supports 500+ Airbyte, Meltano, and Stitch open source connectors. But if you need on-premises app or data warehouse connectivity, make sure you have all the connectivity you need.
  • Graphical ETL: Estuary has been more focused on SQL and dbt than graphical transformations. While it does infer data types and convert between sources and targets, there is currently no graphical transformation UI.

Estuary Pricing

Of the various ELT and ETL vendors, Estuary is the lowest total cost option. Estuary only charges $0.50 per GB of data moved from each source or to each target, and $100 per connector per month. Rivery, the next lowest cost option, is the only other vendor that publishes pricing of 1 RPU per 100MB, which is $7.50 to $12.50 per GB depending on the plan you choose. Estuary becomes the lowest cost option by the time you reach the 10s of GB/month. By the time you reach 1TB a month Estuary is 10x lower cost than the rest.

How to choose the best option

For the most part, if you are interested in a cloud option, and the connectivity options exist, you may choose to evaluate Estuary.

Modern data pipeline: Estuary has the broadest support for schema evolution and modern DataOps.

Lowest latency: If low latency matters, Estuary will be the best option, especially at scale.

Highest data engineering productivity: Estuary is among the easiest to use, on par with the best ELT vendors. But it also has delivered up to 5x greater productivity than the alternatives.

Connectivity: If you're more concerned about cloud services, Estuary or another modern ELT vendor may be your best option. If you need more on-premises connectivity, you might consider more traditional ETL vendors.

Lowest cost: Estuary is the clear low-cost winner for medium and larger deployments.

Streaming support: Estuary has a modern approach to CDC that is built for reliability and scale, and great Kafka support as well. It's real-time CDC is arguably the best of all the options here. Some ETL vendors like Informatica and Talend also have real-time CDC. ELT-only vendors only support batch CDC.

Ultimately the best approach for evaluating your options is to identify your future and current needs for connectivity, key data integration features, and performance, scalability, reliability, and security needs, and use this information to a good short-term and long-term solution for you.

Getting started with Estuary

  • Free account

    Getting started with Estuary is simple. Sign up for a free account.

    Sign up
  • Docs

    Make sure you read through the documentation, especially the get started section.

    Learn more
  • Community

    I highly recommend you also join the Slack community. It's the easiest way to get support while you're getting started.

    Join Slack Community
  • Estuary 101

    I highly recommend you also join the Slack community. It's the easiest way to get support while you're getting started.

    Watch

QUESTIONS? FEEL FREE TO CONTACT US ANY TIME!

Contact us