IBM Informix licensing: editions, PVU, sub capacity, and renewal harvest.

Why Informix licensing remains a buyer side question.

Informix is one of the longest running database product lines in the IBM portfolio. Acquired by IBM in 2001 and continually updated since, Informix is widely deployed in retail, logistics, telecommunications, manufacturing, and embedded application environments where its predictable footprint and low operational overhead keep total cost of ownership down. For many Fortune 500 customers Informix is not a strategic database platform on a par with Db2 or Oracle, but a tactical engine that supports specific workloads. That status makes Informix licensing a buyer side question every renewal cycle: is the current edition still the right edition, are the metric counts still correct, and is the Subscription and Support stream still earning its keep.

This article works through the Informix licensing landscape from the buyer side. It explains the editions, the metering options, the embedded use cases, and the harvest moves that recur on renewal. It also explains where Informix interacts with the rest of the IBM portfolio, particularly Cloud Pak for Data, Passport Advantage anniversary mechanics, and the Subscription and Support harvest. For broader portfolio context see the IBM Licensing Complete Guide and the IBM Product Licensing Guide.

We approach this as an independent firm. We are not an IBM Business Partner, reseller, or affiliate. We hold no resell margin on any Informix licence and earn no commission from IBM on any recommendation. Our perspective is the buyer side only.

The Informix editions and where they apply.

Informix is sold in a small number of editions, each tuned to a deployment profile. The buyer side question on every renewal is whether the current edition fits the current workload or whether a quieter, less expensive edition would do the same job without operational compromise.

Informix Innovator C Edition.

A free entry level edition with capacity ceilings. It is widely used by independent software vendors who embed Informix into a packaged application. It is not licensed for production at scale inside a Fortune 500 estate, but it is worth identifying inside the estate because the presence of Innovator C deployments often signals that a higher Informix edition is paying for capacity that is not actually used.

Informix Workgroup Edition.

A mid tier edition with capacity and feature ceilings. Suitable for branch deployments and remote sites where the workload is bounded. Licensed by Limited Use Socket or by PVU under Passport Advantage. The harvest opportunity at Workgroup Edition is to verify that the deployed socket count matches the entitled count, and that no socket is sitting idle since the last hardware refresh.

Informix Advanced Workgroup Edition.

Adds replication, scale out, and high availability features to Workgroup. Common in regional data centres. Licensed by Limited Use Virtual Server or by PVU. The harvest move at this edition is to verify the high availability features in the deployed environment are actually used; many customers paid for Advanced Workgroup years ago and never enabled the high availability features the edition unlocks.

Informix Enterprise Edition.

The full feature edition with no capacity ceiling. Licensed by PVU under Passport Advantage. Enterprise Edition is the typical edition for production OLTP at Fortune 500 scale. The buyer side discipline here is sub capacity. Enterprise Edition is eligible for sub capacity licensing through ILMT, which materially reduces the entitlement requirement on virtualised hosts. See Sub Capacity Explained.

Informix Growth Edition and Choice Edition.

Newer editions positioned at customers running modest Informix footprints who do not need the full Enterprise feature set but want a per server or per user model. The harvest move at Growth and Choice is to verify the count of users and servers against the entitled count and to confirm the edition still fits the workload.

Metering mechanics that matter on Informix.

Informix metering depends on the edition. Per server, per socket, per Limited Use Virtual Server, and per Processor Value Unit are all in play depending on which edition the customer holds. The renewal anchor is always the metric chosen at original purchase, which propagates through every subsequent true up. Changing metric requires a contractual negotiation, which is precisely when the customer should evaluate whether the current metric still fits.

PVU metering is the most common at Fortune 500 scale. Informix Enterprise Edition is sub capacity eligible, which means the customer can pay for only the virtualised capacity the database actually consumes rather than the full physical capacity of the host. Eligibility requires ILMT deployed, the virtualisation environment on the list of eligible virtualisation environments, and quarterly peak retention for two years. ILMT lapse on Informix Enterprise reverts the licence requirement to full capacity, which can be three to ten times the sub capacity figure. See ILMT Guide.

Socket metering is the simplest model: each populated CPU socket on a server running Informix counts as one socket. Socket metering is generally unattractive once the workload grows because socket count is a coarse instrument. The harvest move on socket licensed Informix is usually to migrate the workload to a smaller server with a fewer socket profile, or to convert to PVU metering with sub capacity in place.

Limited Use Virtual Server metering counts each virtual server running Informix below a stated socket and core ceiling. It is useful where Informix is deployed in many small virtualised environments. The harvest move is to verify which of those virtual servers are still active and which can be retired or merged.

Authorized User Single Install.

Informix can also be licensed on an Authorized User Single Install metric for specific use cases, particularly embedded ISV deployments and small application environments. The harvest move is to verify the AUSI count matches the actual user count and that no inflated count was carried forward from a long retired environment.

Embedded Informix and the ISV question.

A material share of Informix deployment is embedded inside packaged ISV applications. The retail point of sale market, several large telecommunications operational support system platforms, and many logistics applications historically shipped with Informix as the embedded database. For the customer running the packaged application, the Informix licence may be part of the application contract, but the licence economics are still visible to the customer in three ways: as a line item on the application invoice, as a Subscription and Support stream on the IBM Passport Advantage anniversary, or as a separately metered allocation if the customer has ever made the Informix instance available to a second application.

The buyer side discipline on embedded Informix is to clearly identify whether the licence sits with the ISV or with the customer. Where the licence sits with the customer, the customer can negotiate the renewal directly with IBM. Where the licence sits with the ISV, the customer has limited direct leverage, but can still apply pressure through the ISV relationship. The error to avoid is paying for an Informix licence twice: once through the application contract and once through a Passport Advantage Subscription and Support line for the same instance.

We have found this duplication on roughly fifteen percent of Informix audits we have defended. The remediation is to retire one of the two streams at the next renewal and to document the active stream in the entitlement inventory.

Informix and Cloud Pak for Data.

IBM has positioned Cloud Pak for Data as the umbrella under which the data and analytics portfolio converges. Db2, Db2 Warehouse, Watsonx.data, Cognos, SPSS, and Informix are all available under Cloud Pak for Data Virtual Processor Core entitlement, with a conversion ratio that varies by product. For Informix the conversion has been less attractive than for Db2 historically, because the Informix workloads at most Fortune 500 customers do not require the full Cloud Pak for Data toolset. See Cloud Pak Strategy and the Cloud Pak expertise page.

The buyer side discipline on a Cloud Pak for Data conversion offer is to model the alternative cost path. If the customer can run the same Informix workload under Passport Advantage with sub capacity in place, and if the customer does not need the other Cloud Pak for Data components, the Passport Advantage path is usually cheaper at three year total cost of ownership. The conversion to Cloud Pak for Data only pays back when the customer is genuinely consolidating multiple data and analytics products onto the platform.

Annual Informix harvest discipline.

Informix licences accumulate over decades. A Fortune 500 customer typically holds Informix entitlement that grew through five or six waves of acquisition, edition change, and metric migration. A disciplined annual harvest typically recovers ten to twenty percent of the Informix Subscription and Support stream without operational disruption.

1. Inventory all Informix entitlement by edition and metric, including embedded ISV deployments where the customer holds the licence directly.
2. Inventory all deployed Informix instances by host, edition, version, and use case.
3. Reconcile entitlement to deployment. Identify excess entitlement on retired or replaced workloads.
4. Confirm sub capacity eligibility on Enterprise Edition workloads through ILMT.
5. Apply the harvest list to the next renewal. Drop S and S on retired entitlement at the next anniversary date.
6. Document the harvest decision in the entitlement inventory. Confirm that no licence retained is required for an active deployment.

This discipline mirrors the harvest discipline applied to other product lines. See IBM Shelfware Recovery for the general method and the harvesting expertise page for the engagement structure.

The harvest is a contractual move, not a deployment move. The customer is not removing Informix from production, only ceasing to pay Subscription and Support on entitlement that is not in active use. The customer retains the perpetual licence on dropped S and S entitlement and can reinstate S and S later if needed, subject to back support and reinstatement fees. See IBM Software Subscription and Support for the reinstatement mechanics.

Informix at renewal.

Informix renewal is anchored to the customer Passport Advantage anniversary date. The harvest decision must be confirmed at least one hundred eighty days before the anniversary. The negotiation conversation should treat Informix as one line item inside the broader Passport Advantage portfolio, not as a separate negotiation. IBM commercial leverage on Informix is modest, because Informix is no longer a strategic growth product for IBM. Buyer side leverage is therefore strong: the customer can credibly threaten to retire Informix in favour of an alternative database, can credibly drop S and S on excess entitlement, and can credibly convert to a smaller edition.

The negotiation moves that typically pay back on Informix are the harvest of excess entitlement, the conversion of socket licensed deployments to PVU with sub capacity, the alignment of the Informix anniversary to the broader Passport Advantage anniversary, and the resistance against any IBM offer to migrate the workload to Cloud Pak for Data unless the customer has independently decided to consolidate on Cloud Pak for Data. See Renewal Strategy and IBM Discount Structures for the broader moves.

Where Informix sits inside a multi year commitment under an Enterprise Licence Agreement, the buyer side discipline is to ensure the Informix component is sized to the harvest position rather than to the IBM proposed level. Many ELAs include Informix at a level that anticipates growth which never materialised. See ELA vs Passport Advantage.

Informix in an IBM audit.

Informix audits are less common than Db2, WebSphere, or middleware audits, but they happen. The audit triggers we observe are usually transitions: a customer who acquires a smaller company with embedded Informix, a customer who migrates an application from one server tier to another, or a customer who retires an Informix workload without notifying IBM. Each of these creates the conditions IBM looks for when selecting audit candidates.

Informix audit defense follows the general audit defense playbook. Intercept the audit at the notification stage, narrow the scope to the actual Informix instances, control the data the customer provides, dispute every inflated assumption, and settle to a commercial number that reflects the buyer side position. See IBM Audit Complete Guide, Settlement Negotiation, and the Audit Defense service page.

The recurring Informix audit dispute is the metric conversion. IBM auditors often propose that a Workgroup or Advanced Workgroup deployment be reclassified as Enterprise because of a feature use claim. The buyer side response is to document the actual feature use, demonstrate that the Workgroup features were never exceeded, and refuse the reclassification. The cost difference can be material.

Informix conclusion and next steps.

Informix is a mature, stable, predictable product line. The cost discipline is straightforward: hold the right edition, apply sub capacity where eligible, harvest excess entitlement at every anniversary, and refuse the Cloud Pak for Data conversion unless the broader portfolio path supports it. Done consistently, this discipline removes ten to twenty percent of the Informix Subscription and Support stream without operational disruption.

If you would like a buyer side advisor to walk your Informix estate, see the License Consulting service page or contact us through the contact page.