Adabas: a decades old estate on a capacity meter.

Adabas is Software AG's high performance database management system for the mainframe, one of the two products, with the Natural application language, on which the company built its business from the 1970s. It runs core transactional workloads at large enterprises and government bodies, often as the system of record for applications that have run for decades and are deeply embedded in operations. Following Silver Lake's buyout of Software AG, the Adabas and Natural lines were relaunched in early 2025 as a standalone business focused on these mainframe products, after the integration and IoT portfolios were divested. The installed base is large, sticky, and now the commercial center of gravity for its owner.

Adabas is typically licensed on mainframe capacity measured in MSU, with entitlement tied to the machine and the LPARs where the database runs, and enforced through machine specific license keys. That means the contracted capacity, the processor identity, and the LPAR scope are all written into the agreement, and a hardware or configuration change can put the running estate out of step with the licensed scope. Cost tracks the capacity of the environment, not the number of databases, files, or users, so the controlling questions are whether the licensed capacity still matches the estate and whether the legacy contract terms still describe reality.

Confirm your contracted capacity, the keyed machines, and the LPAR scope against the current estate; legacy Adabas agreements drift quietly.

The base driver is the licensed MSU capacity of the environment Adabas runs in. The second driver is the component and option set: Adabas ships with add ons and companion products, replication, networking, utilities, and options enabled beyond the licensed scope extend the bill. The third driver is contract vintage: many Adabas agreements predate current hardware and pricing assumptions, so uplift clauses, indexation, and renewal terms negotiated long ago can compound in ways that no longer reflect the value delivered. Where vendor behavior is described here, treat it as patterns commonly observed, not a guarantee for any single contract.

Adabas exposure concentrates in old paper and capacity drift. Common traps we see at pattern level:

Adabas is sticky, but stickiness is not the same as powerlessness. The five levers that pay:

The headline alternative to Adabas is migration to a relational database such as Db2 for z/OS or an off platform target. It is real, and at large organizations it is also a multi year, high risk, high cost program, because applications written against the Adabas data model and the Natural language are tightly coupled to it. That is precisely why the migration threat works as leverage without being executed: a costed, credible plan changes the renewal conversation, while the practical reality keeps most estates in place. The honest posture is to prepare the alternative seriously so it is usable, and to expect that for most buyers the right outcome is a better Adabas deal, not a migration.