① Journal · Software AG
Adabas and Natural have run as a standalone business under Silver Lake since the start of 2025, and a focused owner of a legacy line tends to optimize it for cash. Here are five recurring Software AG price patterns, and the buyer counter to each.
The product is stable. The ownership, the keys, and the migration question are what move the renewal.
Software AG broke up its estate, and the Adabas and Natural line has run as a standalone business under Silver Lake ownership since the start of 2025, operated through the Software GmbH holding structure. A focused private equity owner of a maintenance heavy legacy line typically runs that line for cash, which shows up at renewal as a firmer posture and less appetite to discount than a diversified vendor would carry. The product itself barely changes; the commercial behavior around it does. That is the first pattern, and it sets the tone for the rest.
Two technical patterns then do the work. Adabas has long used machine specific license keys tied to the processor, so estates that moved workload, consolidated LPARs, or refreshed hardware without rekeying can drift out of strict compliance even while paying maintenance in good faith, and a key mismatch becomes an audit opening or a renewal lever. Alongside that sits the migration question: the vendor knows that moving Adabas and Natural to Db2 for z/OS or off the platform is slow and expensive, and frames the renewal around the cost of leaving. Countering Software AG is about cleaning the key position before notice, and holding a credible migration plan as leverage without committing to execute it. Read this with our Adabas renewal guide and the Software AG publisher hub.
What we commonly observe · the pattern and the buyer counter
| Price pattern | What it looks like | Buyer counter |
|---|---|---|
| Standalone repricing | Firmer renewal posture under a cash focused owner | Negotiate against value extraction, build the alternative early |
| Legacy key mismatch | Machine keys drift after a move, refresh, or consolidation | Reconcile keys to the running config before notice |
| Migration pressure framing | Renewal built around the cost and risk of leaving | Hold a costed migration plan as leverage, not a commitment |
| Capacity MSU growth | Higher capacity raises the licensed baseline | Right size capacity before the baseline is set |
| Annual maintenance uplift | Compounding support increase on a stable product | Cap the annual increase and fix the list reference |
Patterns are what we commonly observe across buyer side engagements, not statements of Software AG policy, and may change. Your contract, key configuration, and consumption govern the real number.
Adabas machine keys drift when workload moves, LPARs consolidate, or hardware refreshes without rekeying, and a mismatch is the easiest opening for an audit or a renewal lever. Reconcile every key against the running configuration before any notice arrives, document the entitlement, and close gaps on your own terms. A clean, documented key position removes the vendor's most convenient pressure point.
Rekey on your schedule, not under an audit notice.
The vendor frames the renewal around the cost of leaving because it knows migration is slow. Turn that around: build a real, costed, sequenced plan to move Adabas and Natural to Db2 for z/OS or off the platform, and hold it as leverage. The credible option moves the renewal number even when staying is the right operational decision. Leverage is the plan you could execute, not the one you announce.
The migration you can run is worth more than the one you threaten.
A cash focused owner leans on annual maintenance uplifts because the product is stable and the customer is captive. A one time concession fades; a hard cap on the annual increase with a fixed list reference governs every year of the term. Lock the structure so the renewal is a known quantity rather than an annual exposure, and the captivity stops being a pricing lever.
Govern every year, not just the signing one.
④ Where the Software AG number is countered
The product is stable. The owner, the keys, the exit are the ones that count. Clean the keys, cost the exit, cap the maintenance.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Adabas and Natural have run standalone under Silver Lake since the start of 2025, through the Software GmbH structure. A focused owner of a legacy line typically runs it for cash, which shows up as firmer renewal posture and less discount appetite. Negotiate against value extraction and build the alternative early. See the Software AG publisher hub.
Adabas uses machine specific keys tied to the processor, so estates that moved workload, consolidated LPARs, or refreshed hardware without rekeying can drift out of compliance while paying maintenance. A key mismatch becomes an audit opening. Reconcile keys to the running config before notice. See Adabas licensing.
The vendor knows moving Adabas and Natural to Db2 for z/OS or off the mainframe is slow and expensive, and frames the renewal around the cost of leaving. Hold a credible, costed migration plan as leverage without committing to execute it. See Adabas vs Db2 for z/OS.
Clean the key position before notice, hold a costed exit plan as leverage, and cap the annual maintenance uplift with a fixed list reference. Our audit defense protects the key position and our license negotiation service sets the caps. See also Adabas renewal negotiation.
Related: Software AG publisher hub · Adabas licensing · Adabas renewal negotiation · IBM price increase patterns · audit defense
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →