LICENSEWARE
Contribute

Informatica IPU licensing

From the LICENSEWARE WikiLast edited 9 ReferencesCited

This article is about Informatica Processing Unit (IPU) consumption licensing for Intelligent Data Management Cloud and the CPU-core, Environment and connector rules for on-premises Informatica Software such as PowerCenter. It is not legal advice and does not replace the executed Order.

On This Page

Informatica IPU licensing is how Informatica sells Intelligent Data Management Cloud (IDMC). The customer subscribes to a quantity of Informatica Processing Units (IPUs), and each eligible cloud service draws them down at a published rate against its own scalar, such as Compute Units, Rows Processed, Data Volume or API Calls.[1] On-premises Informatica Software, including PowerCenter, is licensed or subscribed per CPU-core inside an Environment.[1] Both sets of rules are in the Cloud and Product Description Schedule (CPDS). Version 39.2 is effective 11 September 2026, applies to Informatica Pricebook 39.2 and is published under the “Informatica from Salesforce” name. The CPDS in effect when an Order is placed governs that Order. Legacy SKUs may follow an earlier version, and earlier versions are available only on Informatica Network.[1]

Editions

The IDMC IPU model has no editions. Informatica’s pricing FAQ says IPUs “give customers access to all eligible cloud services listed in the Cloud and Product Description Schedule”.[2] Customers choose how IPUs are packaged instead. Intelligent Data Management Cloud - IPU has a monthly entitlement, Intelligent Data Management Cloud - Flex IPU has an annual entitlement, and Unlimited - Intelligent Data Management Cloud - Flex IPU sets no maximum IPU quantity for a single parent Org.[1] The PowerCenter License Management Report records an edition, a deployment level (Development or Production) and an expiration date for each license.[9]

Metrics

Eight catalog rows cover the Informatica units. Each uses Informatica’s name. Definitions are in the rows.

Informatica name Catalog row Unit of measure 
Informatica Processing Unit (IPU) Informatica Processing Unit (IPU) “A unit of capacity that can be used across eligible Cloud Services” (CPDS).[1] The documentation calls it “a unit of credit used to pre-pay” for IDMC scalars.[3] 
Compute Units Compute Units Per hour of processing capacity 
Rows Processed Rows Processed Per thousand or per million rows 
Data Volume Data Volume Per gigabyte 
API Calls API Calls Per thousand or per million calls 
CPU-core CPU-core Execution core or vCPU (on-premises Software) 
Repository Repository PowerCenter metadata repository 
End Point End Point Source or target connection for Tier B-D Connectors 

The IDMC Administrator documentation lists more scalars, including Events Processed, Daily Assets Stored, Connection Definitions, Objects Processed, Organizations and Queries.[4]

IPU rates for selected services

The CPDS matrix gives each service a scalar, a metric and an “IPU Per Metric Unit” rate, often tiered by monthly volume. Selected rates from Version 39.2, effective 2026-09-11:[1]

Service Scalar / metric IPU per metric unit 
Data Integration Compute Units, per hour 0.16 for the first 2,000 hours; 0.025 above 2,000 
Data Integration with Advanced Serverless Compute Units, per hour 0.28 for the first 2,000 hours; 0.10 above 2,000 
Advanced Data Integration Compute Units, per hour 0.19 
Data Quality Compute Units, per hour 0.38 for the first 2,000 hours; 0.152 above 2,000 
Database Ingestion and Replication Data Volume, per GB 0.1 for the first 2TB; 0.08 for 2-10TB; 0.05 for 10-25TB; 0.018 above 25TB 
Database Ingestion and Replication - Change Data Capture Rows Processed, per million 6.5 for the first 15M; 0.55 for 15M-750M; 0.05 above 750M 
API Center API Calls, per million 13.33 
Additional Production Org Org, per Org 6.00 

Counting / floors

IDMC scope. IDMC is subscribed per IPU. IPUs apply only to eligible services in the IDMC matrix, not to cloud services subscribed separately. Consumption is aggregated across all Orgs and Sub-orgs, and the total must not exceed the subscribed quantity. Rule: IDMC subscribed per IPU; eligible services only; aggregated across Orgs, effective 2026-09-11.[1]

Measurement. All scalars and IPU consumption are measured monthly. Apart from natural language queries, a job in one service that uses components of another is charged at the highest applicable rate. Rule: Scalars measured monthly; cross-service jobs at the highest rate, effective 2026-09-11.[1] The rate-card documentation explains that tiered meters charge each tier at its own rate and that the compute unit count resets to zero at the start of each billing period.[5]

Compute Unit minimum. Compute Units are calculated on a minimum of four CPU-cores or Logical CPU-cores. When a Secure Agent runs with hyperthreading, each Hyper-Thread counts as a Logical CPU-core. Rule: Compute Units: minimum of 4 CPU-cores; each Hyper-Thread is a Logical CPU-core, effective 2026-09-11.[1] Worked rate rule: Data Integration: 0.16 IPU per Compute Unit hour (first 2,000), 0.025 above.

No carry-over. Intelligent Data Management Cloud - IPU grants the subscribed IPUs for each monthly period, and “IPUs do not carry over to the next month”. Flex IPU grants them for each annual period, and they do not carry over to the next annual period. Rules: IDMC - IPU: monthly entitlement, no carry-over and Flex IPU: annual entitlement, no carry-over, Order overage fee, effective 2026-09-11.[1] The documentation matches this: the Metering 1.0 model bills monthly and the Flex IPU model bills annually with monthly reporting periods.[6]

Overage. Informatica monitors consumption for overages. If consumption exceeds the subscribed IPUs, the customer must subscribe to additional IPUs for the rest of the Subscription Period. Under Flex IPU, if the customer does not, the overage fee in the Order applies. Rule: IPU overage: subscribe additional IPUs for the rest of the Subscription Period, effective 2026-09-11.[1] Admin users are emailed when consumption crosses 25, 50, 75, 95 and 100% of the IPU balance.[3] Because entitlement expires each period, an effective license position for IDMC compares metered IPUs against the entitlement for each month (or year for Flex IPU), not against a cumulative balance.

CPU-core counting (on-premises Software). Each execution core on a chip counts as one CPU-core, as does each vCPU shown in virtualization software, so a single quad-core chip is four CPU-cores. Cores may be spread across the shared servers of an Environment only if the licensed quantity equals the total cores of those servers, unless use is restricted to a verifiable Partition. Informatica products may not be installed on VPU or GPU technologies. Rule: CPU-core counting: each core and each vCPU counts as one CPU-core, effective 2026-09-11.[1] See Processor and core licensing for how other vendors count cores.

Environment. An Environment is a single domain behind one master gateway node. Moving licensed cores to more servers or Nodes inside an Environment has no license effect. Designating another master gateway node creates a new Environment, and any per-Environment products must then be licensed again for it. Rule: Environment licensing: reallocating cores inside an Environment is free; a new master gateway node creates a new Environment, effective 2026-09-11.[1]

PowerCenter reports. The License Management Report counts logical CPUs as processors x cores x threads. Informatica states that “license compliance is based on the number of physical cores, not threads”. Rule: PowerCenter: compliance on physical cores, not threads. The documentation page is not date-stamped (retrieved 2026-09-26).[7] Original license keys record the edition, deployment type, number of authorized CPUs, options and connectivity.[8] Each license also carries a maximum number of authorized PowerCenter repositories.[9]

Recovery License. Each Production license or subscription includes one recovery Instance on a stand-by server. The recovery Instance must never run concurrently with Production, and hot or active stand-by systems are not covered. Rule: Recovery License: one cold or stand-by recovery Instance per Production license, effective 2026-09-11.[1]

Connectors. Tier B, C and D Connectors are subscribed per End Point, on one of three metrics chosen at purchase: per End Point per consecutive month, unlimited per Data Type, or unlimited per Tier. Connectors of all Tiers are subscription-only. Rule: Connectors Tier B-D subscribed per End Point, per Data Type or per Tier, effective 2026-09-11.[1]

Virtualization & partitioning

The CPDS allows hard Partitions (a fixed set of whole cores dedicated to the server), which must be licensed for at least all the cores in the Partition. It also allows soft Partitions (virtualization), where the virtual machine must never exceed the licensed CPU-cores or other metrics. If the partitioning or virtualization tools are not visible to the Informatica Administration Console, the customer must keep a historical record of the resource limits. Without that record, a CPU-core must be licensed for every deployed vCPU. Every virtual machine or server must be licensed. Rule: Hard and soft Partitions; no record means one CPU-core per vCPU, effective 2026-09-11.[1]

Cloud / BYOL

Customers may deploy on-premises Software on qualified third-party cloud infrastructure, and each vCPU there falls under the soft Partitioning policy. On instance types where one vCPU is one Hyper-Thread, each licensed CPU-core equals two vCPUs. On Microsoft Azure instances licensed by physical core, and on AWS T2 and m3.medium instances, one CPU-core equals one vCPU. Rule: Third-party cloud: 1 licensed CPU-core = 2 vCPUs (hyper-threaded); Azure physical-core and AWS T2/m3.medium 1:1, effective 2026-09-11.[1] IDMC itself is a cloud service metered in IPUs. For IDMC, the cores assigned to a job are one input to the Compute Unit calculation, not a licensed quantity. The public CPDS publishes no conversion from PowerCenter CPU-core licenses to IPUs.[1]

Programs

Out of scope

  • IPU list prices, overage fees and IPU pack sizes. These are Order terms and are not published.
  • MDM SaaS record-based subscriptions (Unconsolidated and Consolidated Records), Data Quality address verification content terms, and FedRAMP packaging. These are in the CPDS but not in these catalog rows.
  • PowerCenter price lists, per-connector PowerExchange prices and earlier CPDS versions. These are available only on Informatica Network.

Catalog rows

References

  1. Cloud and Product Description Schedule (CPDS) Version 39.2Effective September 11, 2026. Definitions; General Notes; IDMC IPU matrix and Product Notes; Overage Protection; Connectivity. Catalog: Cloud and Product Description Schedule (CPDS) Version 39.2Effective 2026-09-11. Retrieved 2026-09-26.
  2. Intelligent Data Management Cloud consumption-based pricinginformatica.com pricing FAQ, not date-stamped. Catalog: Intelligent Data Management Cloud consumption-based pricingRetrieved 2026-09-26.
  3. Informatica processing unit metricsIDMC Administrator, current version, not date-stamped. Catalog: Informatica processing unit metricsRetrieved 2026-09-26.
  4. IPU scalarsIDMC Administrator, current version, not date-stamped. Catalog: IPU scalarsRetrieved 2026-09-26.
  5. Rate cardsIDMC Administrator, current version, not date-stamped. Catalog: Rate cards (IPU)Retrieved 2026-09-26.
  6. IPU billing periodsIDMC Administrator, current version, not date-stamped. Catalog: IPU billing periodsRetrieved 2026-09-26.
  7. CPU Summary (PowerCenter 10.4.0 Administrator Guide)License Management Report, not date-stamped. Catalog: PowerCenter License Management Report: CPU SummaryRetrieved 2026-09-26.
  8. Original Keys (PowerCenter 10.4.0 Administrator Guide)Not date-stamped. Catalog: PowerCenter Original KeysRetrieved 2026-09-26.
  9. Licensing (PowerCenter 10.4.0 Administrator Guide)License Management Report, not date-stamped. Catalog: PowerCenter License Management Report: LicensingRetrieved 2026-09-26.

See also

Esc