// AI PRICING OBSERVATORY
Layer 01 of 3 · LicensingThe licensing layer.
Who may use the software, on what grant, measured by what unit. The value metric lives here, and every decision downstream inherits it.
The vendor announces the pricing surface. The licensing decision underneath decides whether it holds. This page collects the licensing moves from the Observatory’s verified ledger: the metric swaps, the credit introductions, the entitlement changes. The dated tables render live from the record; the prose around them is the frame.
01 · The decision
One decision, made before the price exists.
The licensing model pairs a value metric with entitlement rules: the unit that grants access, and the conditions the grant carries. It is the upstream-most of the three decisions in pricing architecture — the three structural decisions (licensing model, packaging model, pricing model) that determine how a software company captures value.
The canonical order runs licensing, then packaging, then pricing, because that is how the decisions compose: the grant defines the unit, packaging bundles the rights the grant defined, and pricing attaches a number to the bundle. The licensing model is foundational and changed rarely. When it does change, everything downstream changes with it, whether or not the vendor meant it to.
That is why this layer’s page exists. Most of the moves below were announced in pricing language, because the pricing surface is the visible part and it captures the naming. The record files each move where the decision actually happened. If you want the same question asked of your own architecture, the Pricing Architecture Assessment reads all three layers in a few minutes, no sales conversation attached.
02 · “We’re moving from seats to usage”
How do software companies move from seats to usage-based pricing?
The industry calls the destination usage-based pricing, and the name bundles two decisions into one. Selecting the usage unit is the licensing half: a new value metric, a new definition of what grants access. Attaching a rate to that unit is the pricing half.
Vendors that treat the move as one decision tend to meet the second one at renewal, when the rate they set encounters the unit they chose. The metric decides how the bill scales, who inside the customer’s organization owns it, and what an overage even means. The rate only decides how steep the line is.
The table below is the dated record of vendors that made the metric change, with the read on what actually moved. It renders live from the Observatory ledger and updates as the record does. Read it with one question: which unit did each vendor move to, and does that unit measure what the customer values or what the vendor spends?
03 · “We’re introducing credits”
How do software companies add credits to their pricing?
A credit introduction is announced as a pricing move: a new way to buy, a pool that draws down. The licensing decision is quieter. The unit that now grants and limits access is the credit, which makes the credit the value metric, whether or not it was chosen as one. What rides on top, prepaid and drawn down and expiring, is the pricing model.
Credits are a surrogate unit: one billing unit standing in for several underlying metrics, with the conversion between them held by the vendor. That is a licensing choice whose consequences the announcement never names, because the unit chosen does not itself correspond to value. The vendor appears to make only a pricing decision while quietly making a licensing one.
This section carries both layers on purpose. The two travel together in every credit move on the record, and that is the teaching; the pricing layer’s page points here rather than holding a second copy, because splitting the record would hide exactly the thing it shows.
04 · “We’re capping usage”
How do software companies cap usage on their plans?
A cap is an entitlement rule. It marks the boundary of the grant: how much use the unit permits before the terms change. Entitlement terms are licensing, which is why a cap announcement, however commercial it sounds, is a licensing move.
It becomes a packaging question in exactly one case: when the cap is the line that separates two editions, so the boundary is doing capability-allocation work rather than grant work. The test to run on any cap, your own or a vendor’s: is this a term of the grant, or the line between two editions? The two answers live in different layers of the architecture and behave differently at renewal.
The Observatory tracks these as governance moves. The dated record for this situation is still filling in; until it reads as a sequence, it lives in the full ledger rather than as a table here.
05 · “We’re passing model costs through”
How do software companies pass through AI model costs to customers?
Cost-plus metering reads as a pricing formula, and the plus is one. The core is a licensing decision that happens first: selecting the origination metric to pass through. Before anything is priced, the vendor has adopted the unit its model supplier meters, tokens or requests or compute-seconds, as its own value metric. That unit was chosen upstream, by a supplier with different economics.
Bring-your-own-key is the same structure with the entitlement held by the customer. The supplier relationship moves across the table; the vendor’s unit question does not go away, it just stops appearing on the invoice.
The question this frame asks: who chose your unit? A vendor that inherits its metric has made the licensing decision by default, and default decisions are the ones that surface at renewal. If the unit you inherited is the one you are about to reprice, that is a working conversation: talk to a pricing expert and describe the situation in your own words.
Pass-through moves, BYOK included, are tracked as their own kind on the Observatory. This record is still filling in; until it reads as a sequence, it lives in the full ledger rather than as a table here. The pricing layer’s page cross-links this section: the treatment on top of the pass-through is real, but it is the second decision, not the first.
06 · The next layer
Licensing decides the unit. Packaging decides what ships around it.
The canonical order runs licensing, then packaging, then pricing: the grant is defined, the grant is bundled, the bundle is priced. The next page collects the moves where the bundle itself moved. And when the question stops being what the market did and becomes what your company should do, that is a conversation, not a page.