Rocket Aldon: priced on people, not on capacity.

Rocket Aldon is a family of application lifecycle management and software change management products that govern how application code moves from development through test to production. It covers source control, change request management, build and deployment orchestration, and release governance across mainframe, IBM i, and distributed environments. Rocket Software acquired the Aldon line and folded it into its broader DevOps tooling, where it sits alongside the company's other mainframe and multiplatform development products. It is a development time tool: it manages the people and the process, not a production workload, and that single fact shapes its entire licensing story.

Because Aldon is a change management tool rather than a runtime, it is typically licensed on user or developer based metrics and on the number of managed environments, editions, or instances, not on the MSU capacity of the LPAR it runs on. The controlling questions are therefore how many people genuinely use it and how many application environments it governs, not how much processor capacity the platform carries. Confirm the exact metric in your own schedule, because user definitions vary, named user, authorized user, and concurrent user each count differently, and the difference between them is a real number at renewal.

Confirm whether your user metric is named, authorized, or concurrent before renewal; each counts differently and the gap is negotiable.

The primary driver is the user count, however your contract defines a user. The second driver is the number of managed environments and instances, since each governed application footprint commonly carries its own entitlement. The third is edition and module breadth: Aldon spans several capabilities, and components licensed for platforms or applications no longer in active development quietly extend the footprint. None of these track mainframe capacity, so a hardware refresh that raises your MSU does not by itself raise Aldon cost, which is unusual for mainframe spend and worth confirming rather than assuming.

Aldon exposure comes from people and environments, not capacity. Common traps we see at pattern level:

Because the metric is people and environments, the levers are about reconciliation and portfolio context. The five that pay:

Aldon's nearest functional rivals are Compuware (BMC) ISPW and Broadcom (CA) Endevor in the mainframe change management space, with native and open tooling increasingly relevant in modernization programs. Switching a source and change management system is real work, because it carries embedded process, history, and team habit, so a migration is rarely justified by licensing cost alone. The more reliable value of the alternative is leverage: a credible, scoped evaluation of a competing change manager disciplines the renewal, particularly when it can ride on a modernization program that is happening anyway. The usual win is a better deal on what you already run, not a disruptive replacement.