Estuary

AWS DMS VS Informatica

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

Compare
View all comparisons
AWS DMS logo
Comparison between AWS DMS and Informatica
Informatica 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 AWS DMS vs Informatica 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: AWS DMS vs Informatica vs Estuary

AWS DMS logo
AWS DMS
Informatica logo
Informatica
Estuary logo
Estuary
Database replication (CDC)AWS DMSOracle, SQL Server, MySQL, PostgreSQL, MongoDB, etc. (full load and CDC, but limited to AWS-centric use cases)InformaticaDB2, MySQL, SQL Server, Oracle, Postgres, IBM i and Z/OS sources (PowerExchange)EstuaryMySQL, SQL Server, Postgres, AlloyDB, MariaDB, MongoDB, Firestore, Salesforce, ETL and ELT, realtime and batch
Operational integrationAWS DMS

DMS is not a general-purpose data integration platform. No support for SaaS connectors, event streaming, or cross-cloud delivery.

Informatica
Estuary

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

Data migrationAWS DMS

Mainly built for one-time lift-and-shift database migrations. Lacks real pipeline orchestration or reusability.

Informatica
Estuary

Intelligent schema inference and evolution support.

Support for most relational databases.

Continuous replication reliability.

Stream processingAWS DMS

Not supported. No event streaming or integration with systems like Kafka or Kinesis.

Informatica
Estuary

Real-time ETL in Typescript and SQL

Operational analyticsAWS DMS

Only works for CDC into AWS-native targets like Redshift. Limited visibility and control over latency and freshness.

Informatica
Estuary

Integration with real-time analytics tools.

Real-time transformations in Typescript and SQL.

Kafka compatibility.

AI pipelinesAWS DMS

Not supported. DMS cannot deliver to vector databases or support real-time AI/ML pipelines.

Informatica

Pinecone and Databricks Vector Database

Estuary

Pinecone support for real-time data vectorization.

Transformations can call ChatGPT & other AI APIs.

Apache Iceberg SupportAWS DMS

No Iceberg Support

Informatica

Batch-focused, support possible via Data Engineering Integration, but requires complex pipeline design for Iceberg.

Estuary

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

Number of connectorsAWS DMSLimited to 30+ legacy database and message queue endpointsInformatica300+ connectors Estuary200+ high performance connectors built by Estuary
Streaming connectorsAWS DMSNo streaming or pub/sub support. Only proprietary CDC for supported databases.InformaticaCDC, Kafka via PowerExchangeEstuaryCDC, Kafka, Kinesis, Pub/Sub
3rd party connectorsAWS DMS

Not extensible. No community ecosystem or third-party integrations.

Informatica
Estuary

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

Custom SDKAWS DMS

Not supported. No ability to build or extend connectors.

Informatica

Informatica Connector Toolkit

Estuary

SDK for source and destination connector development.

Request a connectorAWS DMS
Informatica
Estuary

Connector requests encouraged. Swift response.

Batch and streamingAWS DMSNot true streaming. Delivers data in small CDC bursts with added latency.InformaticaStreaming to batch, batch to streamingEstuaryBatch and streaming
Delivery guaranteeAWS DMSAt-least-once. Requires manual deduplication at the destination.InformaticaExactly onceEstuaryExactly once (streaming, batch, mixed)
ELT transformsAWS DMS

Limited to basic column renaming, filtering, and casting. No enrichment or joins.

Informatica

dbt, SQL, pushdown optimization

Estuary

dbt Cloud integration

ETL transformsAWS DMS

Not supported at all. Transformations must be handled entirely outside of DMS.

Informatica

PowerCenter

Estuary

Real-time, SQL and Typescript

Load write methodAWS DMSInsert, update, delete; no support for soft deletes or log-based replay.InformaticaSoft and hard deletes, append and update in placeEstuaryAppend only or update in place (soft or hard deletes)
DataOps supportAWS DMS

No versioning, no CI/CD support, no “as code” pipelines. Monitoring limited to CloudWatch metrics.

Informatica

CLI, API

Estuary

API and CLI support for operations.

Declarative definitions for version control and CI/CD pipelines.

Schema inference and driftAWS DMS

Basic mapping with minimal customization. Complex schemas require manual tuning.

Informatica

With limits

Estuary

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

Store and replayAWS DMS

No staging or persistence. If a pipeline fails, the only option is to re-run the full job.

Informatica
Estuary

Can backfill multiple targets and times without requiring new extract.

User-supplied cheap, scalable object storage.

Time travelAWS DMS

Not supported. No access to historical versions or rewind functionality.

Informatica
Estuary

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

SnapshotsAWS DMS

Supports initial full-load only. Not useful for ongoing use cases or fast reloads.

Informatica

N/A

Estuary

Full or incremental

Ease of useAWS DMS

Integrated into AWS, but operations can be resource-intensive.

Informatica

Takes time to learn

Estuary

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

Deployment optionsAWS DMSOnly deployable as a managed AWS service. No hybrid or BYOC support.InformaticaOn premises, private cloud, public cloudEstuaryOpen source, public cloud, private cloud
SupportAWS DMS

Depends on your AWS account tier.

Informatica

Known for good support

Estuary

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

Slack community.

Performance (minimum latency)AWS DMSLatency ranges from seconds to minutes. No sub-second streaming or guarantees.InformaticaSub-secondEstuary< 100 ms (in streaming mode) Supports any batch interval as well and can mix streaming and batch in 1 pipeline.
ReliabilityAWS DMSMedium. Failures are not automatically retried and require manual reconfigurations.InformaticaHighEstuaryHigh
ScalabilityAWS DMSManual scaling only. No autoscaling or elastic provisioning.InformaticaHighEstuaryHigh 5-10x scalability of others in production
SOC2AWS DMS

AWS DMS itself is not SOC 2 certified. It inherits AWS platform compliance but lacks service-specific attestations.

Informatica

SOC 1, SOC 2, and SOC 3 compliance

Estuary

SOC 2 Type II with no exceptions

Data source authenticationAWS DMSHTTPS / SSH / SSLInformaticaOAuth / HTTPS / SSH / SSL / API TokensEstuaryOAuth 2.0 / API Tokens SSH/SSL
EncryptionAWS DMSEncryption at rest, in-motionInformaticaEncryption at rest, in-motionEstuaryEncryption at rest, in-motion
HIPAA complianceAWS DMS

HIPAA compliance is not explicitly guaranteed for AWS DMS. Customers must architect and validate HIPAA-compliant solutions manually using the broader AWS ecosystem.

Informatica
Estuary

HIPAA compliant with no exceptions

Vendor costsAWS DMS

Charged per hour per replication instance, plus log and storage usage. Hard to predict costs for long-running tasks.

Informatica

Opaque pricing based on "Informatica Pricing Units"

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 costsAWS DMS

Frequent engineering involvement to debug replication failures, latency issues, and configuration mismatches.

Informatica

Complex product with a steep learning curve

Estuary

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

Admin costsAWS DMS

Admin effort required for pipeline setup, task recovery, and credential rotation.

Informatica
Estuary

“It just works”

Start streaming your data for free

Build a Pipeline

AWS DMS

Amazon DMS - ETL Tool

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.

Pros

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

Cons

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

AWS DMS Pricing

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.

Informatica

Informatica introductory image

Informatica started as one of the first ETL vendors with Powercenter, in 1993. It then released one of the first cloud integration products, Informatica Cloud, in 2006. Informatica Cloud was originally built based on an older version of Informatica PowerCenter. After PowerCenter started to get replaced by a new Hadoop (Spark)-based framework, Informatica Cloud eventually moved over as well. After being taken private by Permira in 2015 and having a long period as a private company, Informatica became publicly traded again in 2021. In May 2025, Salesforce signed a definitive agreement to acquire Informatica, aiming to enhance its enterprise data and AI capabilities.

Informatica is perhaps the best example of a mature data integration platform. While it was one of the first to make the transition to the cloud and has one of the strongest and broadest data integration feature sets, it is harder to use, more expensive, and not as DataOps-native. But it has great enterprise features and one of the better private cloud architectures.

Pros

  • A comprehensive data management platform: Informatica Intelligent Data Management Cloud is much more than ETL-based data integration. It includes dozens of options including replication, data quality and master data management.
  • Rich data integration functionality: Informatica has developed a rich library of capabilities over the years for data integration. 
  • Great connectors: Over 300 connectors, including proven connectors to high-performance on premises and cloud data warehouses.
  • Performance and scalability: Informatica is built to support large deployments and deliver low latency data pipelines at scale. Informatica has supported serverless compute, pipeline partitioning, push-down optimization, and other features for years.
  • Private cloud: Informatica is one of the few vendors that supports a private data plane deployment managed by a shared SaaS control plane.
  • Now backed by Salesforce: The acquisition by Salesforce positions Informatica to be more tightly integrated with the Salesforce Data Cloud and Einstein AI ecosystem.

Cons

  • Harder to learn: While Informatica Cloud is easier than Powercenter was, it still has a significant learning curve compared to most SaaS ELT services. This makes it more suitable for larger, specialized data integration teams.
  • Doesn’t support DataOps as well: Informatica Cloud was built pre-CI/CD and DataOps. While you can use its CLI and API to automate deployment, it’s not as simple as a more modern platform. Schema evolution is supported, but there are some limitations depending on the source and destination. Versioning and other tasks are harder than some of the more modern ELT tools.
  • Higher vendor costs: Informatica is more expensive than most other ELT and ETL vendors.
  • Salesforce ecosystem lock-in: Now that Informatica is being integrated into Salesforce, platform neutrality may diminish over time, especially for organizations not already using Salesforce products.

Informatica Pricing

Informatica’s consumption-based pricing is complicated and requires a quote. You can read the Informatica Cloud and Product Description Schedule here. Cloud is mostly based on hourly pricing per compute units, with some other pricing like row-based pricing for CDC-based replication. In general, you can expect a higher cost compared to most other vendors. With Salesforce’s acquisition, Informatica pricing may increasingly reflect bundled Salesforce ecosystem offerings and enterprise packaging.

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