LzLabs featured in Sunday Times “Cloud for Business” report

Modernising the legacy application landscape should not necessarily involve complete replacement. In fact, many aspects of an organisation’s technology architecture are there for good reason and remain critical to core processes. On the other hand, parts of an IT infrastructure might not be as adaptable to current demands and shifting business objectives. Rather than looking […]
On the road again! Meeting clients to help them unleash the potential of their legacy applications.

Together, we will exchange ideas about application modernisation from a holistic perspective. Because organisations that want to reduce their dependency on the mainframe look for solutions, not just software or consultancy. They look for end-to-end guidance and advice along the transformation journey. We will be joined by fascinating speakers who will share with us their […]
Funkschau: Mainframe Modernisation

Funkschau: “Let’s take a look at the practice – what can you report here?” Thilo Rockmann, LzLabs: “LzLabs helped the Italian bank BPER to reduce its dependency on the mainframe. Here, LzLabs Software Defined Mainframe® (SDM) is utilised in two different ways. On the one hand, applications are migrated to SDM and, on the other […]
Forbes: Italian Bank BPER Moves Mainframe Core Banking Apps To Linux

IT Administrator: Mainframe goes Software

The Stack: Mainframe to Linux – still a howling headache of a job?

InfoWorld: The future of COBOL is now

Telecom Ramblings: Industry Spotlight – Software-Defined Mainframes with LzLabs’ Mark Cresswell

IT Finanzmagazin: Software Defined Mainframe – Eine inkrementelle Mainframe-Migration mittels Re-Hosting

IT-Daily.net: Mainframe reloaded – Modernisierung und Generationenwechsel meistern
DataCenter Insider: Young Professionals und die Mainframes

TechRadar Pro: The legacy mainframe crisis – Why COBOL is not the issue

Why are so many organizations – including the state governments of New Jersey, Kansas, Connecticut and Colorado – experiencing such issues with legacy applications written in COBOL? I argue that the problem is not with COBOL itself, but with the arcane mainframe environment the programmers must inhabit to maintain the programs. Read the full article