① Journal · Contract traps
Adabas and Natural now run as a standalone business under Silver Lake ownership, and legacy estates carry contract terms written decades ago. The recurring patterns below cost money at renewal and audit, and every one is more negotiable before signing than after.
The expensive clauses in a Software AG agreement are rarely hidden. They sit in legacy capacity definitions, audit rights, and renewal escalators that nobody negotiates, which is the same thing as agreeing to them.
Most Software AG mainframe spend runs through the Adabas database and the Natural development environment, long lived estates that often predate the current owner. Following the 2024 carve up, Adabas and Natural launched as a standalone business in January 2025 under Software GmbH, held by Silver Lake. These products are commonly licensed on mainframe capacity (MIPS or MSU) with contract terms and audit clauses that can be old enough to surprise the buyer who signed them. The traps below sit across that legacy paper. None is exotic. What they share is that the cost lands at a renewal or an audit, when the leverage to fix them has passed to the vendor. Read them as patterns commonly observed, not as claims about any single agreement, which always governs its own terms.
| Trap | What it costs you | Neutralize it by |
|---|---|---|
| Legacy capacity definition | MIPS or MSU read against the full box, not the LPARs running Adabas | Pin the metric to the partitions that actually run the product |
| Stale audit clause | Old agreements grant broad audit rights with no cure window | Renegotiate scope, frequency, and a cure period at renewal |
| Ownership transition drift | Terms reinterpreted as the estate moves to standalone ownership | Confirm the governing paper and freeze surviving rights |
| Natural seat creep | Developer or runtime seats billed on entitlement, not active use | Reconcile seats to live use and document the basis |
| Capacity growth uplift | Renewal repriced on grown capacity with no negotiated cap | Cap the escalator and fix rates for the term where possible |
| Migration and exit friction | No documented exit or data extraction right on a locked in estate | Negotiate exit, extraction, and transition rights up front |
| Support reinstatement penalty | Lapsed support repriced with back maintenance to rejoin | Negotiate reinstatement terms and a grace window up front |
Software AG estate composition (Adabas and Natural standalone under Software GmbH and Silver Lake since January 2025) and the capacity and audit patterns described reflect practices commonly observed across these legacy renewals as of 2026. This is not legal advice; your specific agreement, deployment data, and counsel govern.
Two of these deserve the most attention. The stale audit clause is the quietest exposure: many Adabas and Natural agreements were signed long ago and grant broad measurement rights without the cure window or dispute path a modern buyer would insist on. Use the renewal to modernize the audit clause, not just the price. The second is migration and exit friction, the structural risk of a deeply embedded estate with no documented way out. Even if you intend to stay, negotiating exit, extraction, and transition rights restores the credible walk away that anchors every other term. For the renewal playbook see Software AG renewal uplifts: the response playbook, and the product detail at Natural licensing.
Software AG renewal or audit notice under 18 months out? We mobilize within 48 hours to read the agreement before you sign or pay. Start with the Software AG renewal response playbook.
Every issue of the journal, plus renewal benchmarks we do not publish on the site. No vendor sharing, ever.
More from the journal: IBM contract traps to avoid, Rocket Software contract traps to avoid, and the audit clause you signed and forgot. Guide: estimating switching costs. Product: Natural licensing. Hub: Software AG mainframe licensing.