Full narration of the briefing. Click a section heading to jump the player to that moment.
Part one counted and stratified. Now the meters that remain, the paper, and the close. I am Claire, Tom is with me, and this is part two of the VendorBenchmark Red Hat playbook: the Ansible node meter, the OpenShift workload map and suite ladder, the paper decision between Red Hat direct, the IBM enterprise agreement, and the marketplace, the virtualization migration priced as an entry deal, the tactics and counters, and the endgame that lands a one point nine million path at roughly one point two five million inside IBM's December quarter.
Ansible's managed node meter counts everything automation touches, and inventories double count network devices, ephemeral instances, and rediscovered hosts with enthusiasm. Deduplicate before the meter is read, and define the node classes and exclusions in the order form; in the illustration, eight thousand nodes become five thousand two hundred real ones. On OpenShift, the suite ladder, Platform Plus, Advanced Cluster Management, Advanced Cluster Security, and the AI attach, OpenShift AI and RHEL AI, all ride the core count. Tier to the features actually operated, and put the young meters on short clocks at contracted rates.
Two commodity web workloads in the illustration move to managed upstream per the defense file.
Three structural choices finish the position. The paper: Red Hat direct, the IBM enterprise agreement, or the cloud marketplace each carry different leverage, and whichever is chosen, the Red Hat estate stays separable, its counts, rates, and caps on their own schedule, because entitlements dissolved into a bundle cannot be benchmarked or trued down. The entry deals: OpenShift Virtualization migrations and any net new platform adoption are priced under the entry doctrine, funded migration, ramps gated to cutover, five year caps, portability, while Red Hat is spending to win the VMware moment. And the calendar: IBM closes December thirty first, and a stable November anchor collects the December terms.
The tactics and counters. The count inertia: the renewal reflects your current entitlement footprint. The footprint reflects twenty twenty three; Satellite shows two thousand fifty active instances and the remapped models. The risk framing on clones: community rebuilds carry supply chain risk your production estate cannot accept.
Which is why production stays on Premium; the dev, test, and edge tiers generate no support calls, and the clone plan is costed and scheduled. The platform default: standardizing everything on OpenShift unlocks platform value. The workload map standardizes where the premium earns it; commodity namespaces run identically on managed upstream, and the file prices both.
Two more. The bundle absorption: folding Red Hat into the IBM agreement improves your overall economics. The economics improve when they are visible; Red Hat rides its own schedule with its own counts, rates, and caps, whatever paper carries it. The uplift as policy: the adjustment reflects current subscription pricing.
The benchmark shows what comparable estates pay and how their caps are written, and the clone file is open on the table. And the line worth using verbatim: Satellite is your product and it says twelve hundred fifty subscriptions at these tiers. We are happy to pay Red Hat prices for the Red Hat the estate actually uses.
The endgame: roughly one point two five million all in, caps at four percent, separable Red Hat paper, true down rights at anniversaries, model remap rights as densities change, OpenShift counting rules and Ansible node definitions written, and the virtualization migration priced separately as an entry deal with funded migration and ramped subscriptions gated to cutover. Against the one point nine million plus uplift path, a third lighter, with every production workload keeping exactly the support it had. Pay the fee where the assurance is real, decline it where the free was always the product, and arrive in December counted. More briefings at redresscompliance dot com slash research videos.
This briefing is drawn from the full playbook by Vendor Benchmark LLC: the preparation runway, the estate math, the give and get table, the tactics and counters, and the concessions checklist. Read it here, save the PDF, or send it to whoever owns the renewal.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Red Hat negotiator