① Journal · Vendor Roadmap
Software AG now runs Adabas & Natural as a standalone business under its 2050+ agenda, a commitment to support these applications for decades. The roadmap, the 2026 release, a stated licensing compliance focus, and modernization tooling, reshapes both what you pay and where the leverage sits. Here is the impact, move by move.
A vendor planning for 2050 plans to keep billing you.
Software AG's mainframe business is now built around Adabas and Natural as a standalone operation, separated from the webMethods and StreamSets assets sold to IBM in 2024 and from ARIS, and run under Silver Lake ownership. Its defining message is the Adabas & Natural 2050+ agenda, a public commitment to protect, modernize, and optimize these applications well into the future. For customers anxious about end of life, that is reassurance. For a buyer thinking about cost, it is also a signal: a vendor positioning for the very long term is a vendor that expects to bill you for decades, and a relationship framed around permanence is one that needs a counterweight to stay priced honestly.
That counterweight is a credible path off the platform, even a partial one, because the Adabas and Natural license only ends at full migration. The roadmap matters because it both raises the stakes and offers the levers. The 2026 release adds a stated licensing compliance focus that tightens measurement, while the modernization tooling Software AG itself is shipping, including Natural for Visual Studio Code, supplies pieces of the very migration path a buyer can use as leverage. Reading the roadmap means reading both at once: where compliance tightens the screws, and where modernization loosens the lock. This builds on our Software AG renewal advisory and our Natural vs COBOL modernization comparison.
Software AG move · license impact · the buyer lever
| Roadmap move | License impact | Buyer lever |
|---|---|---|
| Adabas & Natural 2050+ agenda | Signals permanence; frames the renewal as a decades long relationship | Hold a credible modernization or exit path so permanence does not mean captivity |
| Standalone under Silver Lake | Focused ownership often sharpens commercial and renewal discipline | Expect tighter negotiation; prepare evidence and alternatives accordingly |
| 2026 release, licensing compliance focus | Tighter measurement can turn quiet usage gaps into billable findings | Reconcile licensed against deployed usage before adopting the release |
| Modernization tooling (Natural for VS Code) | Lowers the cost of modernizing, which cuts both ways | Use vendor supplied modernization as a credible, costed exit lever |
| MIPS and MSU capacity licensing on z/OS | Cost scales with mainframe capacity the applications consume | Control and document capacity; it is the metric the renewal is priced on |
The roadmap tightens compliance with one hand and supplies modernization tooling with the other. The buyer uses the second to answer the first.
The license ends at full migration. Until then, the path is the leverage.
The phrase to watch in Software AG's 2026 release is licensing compliance. When a vendor builds compliance enforcement into a product update, it generally means tighter measurement of what you run and easier identification of usage that exceeds entitlement. For an Adabas and Natural estate, where deployment often drifted over decades of organic growth, that turns a previously quiet gap between licensed and deployed usage into a potential billable finding. The defensive move is to know your own deployment precisely before adopting the release, so a compliance focused update finds nothing you have not already reconciled. Walking into a tighter compliance regime with an unmeasured estate is how a routine upgrade becomes an unexpected cost.
The offensive move is the migration path. The vendor's strongest position is that moving off Adabas and Natural is hard, and it is, which is exactly why the 2050+ agenda assumes permanence. But the license only ends at full migration, and a buyer does not need to complete a migration to use it as leverage; a real, costed, partly executed modernization plan that the vendor believes is enough to reframe the renewal from a captive cost into a negotiation. The irony is that Software AG's own modernization tooling, including Natural for Visual Studio Code, supplies pieces of that path. A buyer who pairs a precise compliance position with a credible modernization roadmap holds both halves of the negotiation. Our Entire Net-Work licensing page works the connectivity layer, and our license negotiation service turns the roadmap into a position.
A licensing compliance focus tightens measurement. Reconcile licensed against deployed usage across the Adabas and Natural estate before adopting the release, so a compliance update finds nothing you have not already corrected.
Measure your estate before the vendor measures it.
The license ends only at full migration, but a real, costed, partly executed plan is leverage long before completion. Use the vendor's own modernization tooling to make the path concrete and believable.
A believed migration plan reprices a captive renewal.
Adabas and Natural on z/OS are typically licensed against MIPS or MSU. Document and manage the capacity the applications consume, because that metric is what the renewal is priced on and uncontrolled growth is a silent uplift.
The capacity you do not manage is the bill you do not control.
Focused ownership under Silver Lake often sharpens renewal discipline. Prepare evidence, alternatives, and timing in advance, and do not assume the standalone Adabas and Natural business will negotiate the way the old conglomerate did.
A focused vendor negotiates harder; prepare to match it.
⑤ The discipline that pays
A vendor planning for 2050 plans to bill you for decades. A credible path off the platform is what keeps the relationship honest.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Software AG's stated commitment to protect, modernize, and optimize Adabas and Natural applications well into the future. Since the Silver Lake transaction, Adabas & Natural runs standalone, separate from the webMethods and StreamSets assets sold to IBM in 2024 and from ARIS. The agenda reassures on end of life but also frames the renewal as a decades long relationship that needs a counterweight.
Software AG describes its 2026 release as adding stronger security, licensing compliance, usability, and modernization options across z/OS, Linux, and cloud. The phrase to watch is licensing compliance, which generally means tighter measurement of what you run. Know your deployment precisely before adopting it, so a compliance update finds nothing you have not already reconciled.
In a credible path off Adabas and Natural, even a partial one. The license only ends at full migration, so a real, costed modernization plan the vendor believes reframes a captive renewal. Combine it with precise capacity control, since Adabas and Natural on z/OS are typically licensed on MIPS or MSU. The vendor's own modernization tooling supplies pieces of that path.
Reconcile licensed against deployed usage before the 2026 release, build a credible modernization path using the vendor's own tooling, control the capacity you are billed on, and expect sharper commercial discipline under focused ownership. Hold the compliance position and the migration lever together. See our Software AG renewal advisory.
Related: Software AG renewal advisory · Natural vs COBOL modernization · Entire Net-Work licensing · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →