Exstream on premise versus cloud licensing

Where Exstream runs changes how it is licensed, and changing how it is licensed changes where an audit can overreach. An on premise deployment and a cloud subscription describe the same composition engine, but they sit under different contractual structures, are measured differently, and fail in different ways. Many organisations are mid migration, running both at once, which is precisely the configuration where a finding can double count the same output across two entitlements. Understanding Exstream on premise versus cloud licensing is what keeps a transition from becoming an audit exposure.

This article compares the two models, explains where each inflates a finding, and shows how a buyer reads usage correctly across a hybrid estate. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

How the two models differ

An on premise deployment is typically governed by a perpetual or term license under the OpenText EULA, with volume entitlements and maintenance, and the software runs on infrastructure the buyer controls. A cloud arrangement is typically a subscription with an included volume tier, overage terms, and the software running on vendor managed infrastructure. The contractual structures differ, the measurement points differ, and the records that prove usage differ. A buyer who treats the two as interchangeable will measure the wrong thing in at least one of them. The broader set of structures is set out in customer communications management license models.

Where on premise inflates

On premise findings inflate at the familiar volume points: unit selection, channel multiplication, a peak counting window, and non production runs folded into the production total. Because the buyer controls the infrastructure, the buyer also controls the records, which is an advantage in reconstruction. The volume reconstruction discipline that applies here is set out in reconciling Exstream entitlements before an audit, and the production scope question in Exstream non production and test volume scope.

Where cloud inflates

Cloud findings inflate at the edges of the subscription: how overage above the included tier is measured, whether non production environments are inside or outside the subscription, and how the tier is interpreted at audit. Because the vendor manages the infrastructure, the buyer must be deliberate about obtaining and verifying the usage data the subscription is measured against rather than accepting a vendor reported figure. These questions are examined in Exstream cloud subscription audit considerations. The capacity versus consumption distinction also recurs in cloud arrangements, where provisioned tier can be confused with consumed volume, the subject of Exstream transactional versus capacity metrics.

Reading a hybrid estate correctly

The defensible reading across a hybrid estate accounts for each environment under its own model and prevents the same output from being counted twice:

• Map the estate. Establish which environments are on premise and which are cloud, and over what period each was live.
• Apply the right model to each. Read on premise volume against the EULA entitlement and cloud volume against the subscription tier.
• Deduplicate the transition. Where communications were produced in both during migration, count the output once against the governing entitlement rather than twice.
• Scope non production in each. Remove test and development runs under both models.

This is the same reconstruction discipline described in reducing an Exstream finding with volume evidence, applied across two deployment models at once.

How the four Rs apply across deployments

The method handles a hybrid estate the same way it handles a single one. In the respond stage the firm takes over the single controlled channel inside the seven day notice window so the vendor does not fix a double counted hybrid reading before the position is built. In the reconstruct stage it maps the estate, applies the correct model to each environment, and deduplicates output produced in both during migration. In the rebut stage every instance of cross environment double counting and every misapplied model is challenged. In the resolve stage the settlement reflects the corrected hybrid reading, and the forward agreement, often an OpenPass arrangement, defines the metric and the deployment scope so the next audit cannot reopen the transition. The earlier the estate is mapped, the cleaner the hybrid reading becomes.

A representative outcome

In a recent engagement, an Exstream finding had counted output on a legacy on premise deployment and on the cloud subscription that was replacing it as two independent volumes, so the communications produced in both during a parallel run migration were counted twice. The buyer mapped the estate, established which entitlement governed each environment and period, and showed that the parallel run output was a single body of communications counted against the wrong combination of entitlements. Once the transition was deduplicated and each environment was read under its own model, the volume fell substantially. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, with no figure introduced beyond what the deployment records contained.

On premise versus cloud in one line

Exstream on premise and cloud deployments sit under different contracts, are measured differently, and must each be read under their own model, with any parallel run output counted once rather than twice. Map the estate, apply the right model, deduplicate the transition. To prepare the underlying records, read preparing an Exstream entitlement reconstruction, and to have your own hybrid estate read correctly you can open a case with our team.

For the first week after a notice arrives, read the OpenText seven day notice response white paper.