① Publishers · Software AG
Adabas and Natural run some of the most durable application estates in enterprise computing, and some of the most expensive per unit of capacity. This guide covers how Software AG licenses its mainframe portfolio, how its renewal and audit behavior has evolved under new ownership, and where the buyer leverage sits. Facing a deadline now? Get expert help.
The estate: what you probably run.
If Software AG is on your mainframe, the center of gravity is almost always Adabas, the high performance database, and Natural, the 4GL application language built around it. Around that core sit EntireX for integration, Entire Net-Work for distributed Adabas access, Com-plete as the transaction processing environment, Adabas Replication for real time data movement, and tooling such as Natural Engineer. Estates dating from the 1980s and 1990s commonly carry all of it, whether or not all of it still runs.
The corporate picture changed substantially in recent years. Silver Lake took majority control of Software AG in 2023, the integration business (webMethods and StreamSets) was sold to IBM in a transaction completed in July 2024, and in January 2025 the remaining company announced Adabas & Natural and ARIS would operate as standalone businesses under the Software GmbH holding company. For mainframe buyers the practical consequence is a publisher whose remaining revenue base is concentrated on your estate, which typically sharpens renewal behavior.
Software AG mainframe products are typically licensed against machine or LPAR capacity, expressed in MSU or MIPS tiers depending on contract vintage. Older agreements are commonly perpetual licenses with annual maintenance; newer paper and renewals increasingly move toward subscription style terms. Because the estate has usually been in place for decades, most customers hold a stack of amendments, side letters, and acquired entity agreements rather than one clean contract, and the effective terms are whatever that stack adds up to.
Two structural features matter most at the negotiation table. First, capacity tiers mean a hardware upgrade can raise your Software AG bill even when Adabas workload is flat, the same MIPS creep pattern seen across the industry. Second, the contracted capacity in old paper frequently bears no resemblance to current consumption, and the gap between contractual and consumed capacity typically favors the vendor until a buyer forces a reconciliation.
With the portfolio narrowed to Adabas & Natural and ARIS, renewal pressure on the installed base is the revenue strategy. Patterns commonly observed: multi year renewals proposed with uplifts attached, capacity true ups raised at renewal time based on hardware changes, and migration risk used as a pricing argument in both directions, the vendor pointing at your switching costs, the buyer needing a credible answer.
Audit exposure concentrates in legacy contracts. Decades old agreements often contain capacity definitions, named entity clauses, and usage restrictions written for a different datacenter, and commonly observed audit themes include capacity measured on the wrong boundary (machine vs LPAR), acquired or divested entities using licenses that never transferred, and DR arrangements never papered. If a notice has landed, start with our guide to Adabas and Natural audit defense.
Software AG renewals reward preparation unusually well because the installed base is sticky and both sides know it. The leverage is rarely a bluffed migration; it is the documented option.
Where the money moves
Scope control, independent recalculation of capacity findings, and settlement on your terms. The service →
The 18 month program that resets the baseline before the quote arrives. The service →
Buyer side execution when the number on the table has to move. The service →
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →