Informatica Pricing: IPU Cost, AWS Marketplace List Prices and What IDMC Really Costs

Informatica publishes no dollar figures on its own pricing pages, but its AWS Marketplace listing for the Intelligent Data Management Cloud does. A 12-month contract for one bundle of 120 Informatica Processing Units per month is listed at $131,760.00, which works out to $91.50 per IPU per month. That is the only public US list price Informatica posts anywhere, and it is the number to negotiate against.

Every article about Informatica pricing you will find says the same thing: it is consumption-based, it runs on IPUs, and you have to call sales. That is true and it is useless. This one is built from the one listing Informatica is contractually obliged to put a real, transactable price on, read from the live page on 26 August 2026, plus what Informatica itself documents about how IPUs are consumed. Where the listing stops and the guessing starts, we say so.

Informatica pricing: the published list prices

Read from the public AWS Marketplace product page for Informatica Intelligent Data Management Cloud on 26 August 2026. The 12-month figure is the amount the listing renders by default; the 24 and 36 month amounts come from the pricing data embedded in the same listing, all three against the identical single dimension of 120 IPU per month. US list price for a standard contract, excluding private offers, reseller margin and negotiated discounts.

The multi-year terms carry no discount at all

This is the finding worth sitting with. $263,520.00 is exactly two times $131,760.00. $395,280.00 is exactly three times it. Not approximately, not within a rounding error. The listed rate for committing to Informatica for three years is identical to the rate for committing for one.

That is unusual. Enterprise software normally pays you to commit early, and a two or three year term is where a buyer expects to find ten to thirty percent. On this listing there is nothing. The practical read is not that Informatica refuses to discount, it is that the discount does not live in the Marketplace listing, so signing a longer public-list term buys you no price advantage whatsoever. If you want multi-year value, it has to come out of a private offer or a direct contract, and you should ask for it explicitly rather than assume the term length earned it.

What is an Informatica Processing Unit (IPU)?

An IPU is a prepaid credit you spend across Informatica cloud services rather than a license for any one of them. You commit to a monthly balance, then draw it down according to what you actually run. Informatica describes the mechanic on its own pricing page: IPU consumption is "calculated per scaler, based on the scaler's usage including Secure Agent, CDI-e, Data Mass Ingestion volume and more."

The word doing the work there is "scaler". Each service has its own scaler, its own meter, and its own conversion rate into IPUs. Data integration bills against one thing, mass ingestion bills against volume, the Secure Agent bills against runtime. So two companies committing to the same 120 IPU per month can consume it at wildly different speeds depending on which services they lean on. The flexibility is real: you can shift units between services as your needs change without renegotiating. The cost of that flexibility is that you cannot forecast spend from the unit count alone.

This is the same structure IBM uses for watsonx.data integration, where we found a published rate of $26.50 per Resource Unit, and the same one Snowflake uses with credits. The pattern across all three is worth naming: the vendor publishes the meter, and keeps the price of the meter private. Informatica is the rare case where a Marketplace listing accidentally makes the second half public too.

Is $131,760 a year what I will actually pay?

No, and treating it as a quote would be a mistake in both directions.

It is a floor in the sense that it is a real, transactable, publicly posted price for a defined quantity, which is more than any comparison article can say. It is not a floor in the sense of being the cheapest way to buy. Large enterprise deals go through private offers, which are negotiated per customer and never published, and those routinely land below public list. Informatica also sells through resellers and directly, each with its own commercial terms.

What the number genuinely gives you is calibration. If you are quoted $400,000 a year for a workload a 120 IPU bundle would comfortably cover, you now have a public figure to point at and a specific question to ask: what is the per IPU rate in this quote, and how does it compare to $91.50? Vendors answer that question very differently when you already know the public answer.

What drives the bill up

Three things, in roughly this order.

Volume-metered services. Anything billing on data volume rather than runtime scales with your business rather than your engineering choices. Mass ingestion is the usual culprit. A pipeline that was cheap at ten million rows is not cheap at a billion, and nothing in your architecture changed.

Always-on compute. The Secure Agent meters on runtime. Long-running or idle agents accrue units whether or not useful work happened, which is the consumption-pricing equivalent of leaving a warehouse running.

Service sprawl. IPUs being spendable across the platform is the selling point and also the trap. Because enabling another service does not require another purchase order, it does not feel like a spending decision, and the drawdown accelerates quietly. Informatica does provide a consumption dashboard with threshold alerts, and configuring those on day one rather than after the first overage is the single highest-value thing a new customer can do.

Informatica pricing versus the alternatives

The honest comparison is not tool against tool, it is commitment model against commitment model.

All figures are vendor-published US list prices read from AWS Marketplace listings or public cloud catalog APIs between 20 and 26 August 2026. None of these vendors publishes a price on its own pricing page.

Two patterns fall out of that table. First, the entry points cluster between roughly $60,000 and $170,000 a year, which is a useful sanity band for anyone being quoted wildly outside it. Second, and more importantly, most of these listings sell an undefined unit. Alation sells units it never defines. Immuta sells Units described only as a metric based on user count and data store type. Informatica is actually the better-behaved one here: an IPU is at least documented as a consumption credit with a named metering mechanism, even if the conversion rates are not public.

If your evaluation is really about cataloging and governance rather than integration, the same published-prices-only treatment is in our Alation vs Collibra pricing comparison and our data governance tools roundup. And if the actual job is pulling a handful of SaaS APIs and databases into your warehouse on a schedule, rather than running an enterprise integration program, a focused data integration platform covers that at a small fraction of a 120 IPU commitment. Not every team that buys IDMC needed IDMC.

Do I need Informatica at all?

Informatica earns its price in a specific shape of company: many source systems, several of them old, real regulatory exposure, a central data team that owns integration for the whole business, and a genuine need for MDM or data quality alongside the pipelines. In that shape, the breadth is the point and assembling the equivalent from six vendors costs more in coordination than it saves in license.

It is oversized when your sources are a dozen SaaS APIs and a Postgres database, when transformation already happens in dbt inside the warehouse, and when what you actually needed was visibility rather than another movement layer. That last case is common enough to name. Teams frequently buy a heavyweight platform because nobody could answer where a number came from or what a change would break, which is a lineage problem wearing an integration problem's clothes.

If that is the real question, you do not need to move any data to answer it. Datatrail connects to your warehouse read-only, parses query history and dbt artifacts into column-level lineage, and computes downstream impact before a change ships. The price is on the pricing page, in dollars, without a scoping call. For the wider field, see our data lineage tools comparison.

How we sourced these numbers

Every figure here was read from a primary source on 26 August 2026: the AWS Marketplace listing for Informatica Intelligent Data Management Cloud for the contract prices, and Informatica's own cloud integration pricing page for the IPU consumption description, which contains no dollar figures. The comparison table draws on Marketplace listings and public cloud catalog APIs for each vendor named, checked between 20 and 26 August 2026.

Nothing here is an estimate, a range, or a number carried over from another article. Where the listing does not say something, such as the IPU conversion rate for any individual service or what a private offer would look like, we say we do not know rather than fill the gap. Prices change, and a list price is a starting coordinate rather than a quote.