Contact us
Temenos T24 · Core Banking · Legacy Windows

Keep Temenos T24 running on supported Windows. No core banking rewrite. No compliance gap.

T24 and its TAFC runtime still run the ledger for banks worldwide, and it works. The exposure sits underneath. The Windows Server the platform depends on has fallen out of support, and regulators now expect financial systems to run on supported, patched software. The vendor routes, a TAFC to TAFJ re-platform or a full core transformation, are multi-year programmes carrying real risk to the ledger. Cloudhouse™ offers a third way. We package T24 and its legacy dependencies so the platform runs on modern Windows Server, keeping the core banking system unchanged, with no rewrite and results guaranteed.

Talk to our team See what we have delivered
3,000+
Financial institutions worldwide rely on Temenos, including 41 of the top 50 banks and more than 500 million customers
0
Lines of core banking code changed to keep T24 running on a supported, patched platform
Since 2010
Cloudhouse has kept business-critical Windows applications running safely on modern platforms
The Temenos T24 problem

A core banking platform that works, on infrastructure that no longer meets the standard.

T24 runs the ledger, and most banks would rather not touch it. The risk is not the application. It is the Windows Server and supporting stack beneath it, which have fallen out of support, and the widening gap between that and what regulators and auditors now expect of a financial system.

Support

The platform underneath is out of support

Older T24 and TAFC builds were certified against Windows Server versions that have themselves reached end of support. An unpatched operating system carrying the core ledger is the finding an auditor raises first.

Cost

Re-platform or transform, both heavy

The vendor routes are a TAFC to TAFJ runtime re-platform, or a full core banking transformation onto a current release or the cloud. For a live ledger, either is a multi-year programme carrying material risk, on a timeline the supplier sets.

Compliance

Regulators expect supported software

Under the EU's Digital Operational Resilience Act, in force since January 2025, and operational resilience expectations more broadly, running a critical financial system on unsupported software is a documented ICT risk. Supervisors and auditors treat it as one.

How Cloudhouse solves it

Package T24. Modernise the platform. Keep the ledger untouched.

Cloudhouse containerises the application at the application level. T24, its TAFC runtime and their legacy dependencies are sealed inside a self-contained package and are never installed or registered on the host operating system. The core banking system behaves exactly as it does today, while the unsupported platform is lifted off the estate.

01 / PACKAGE

Contain T24 and its runtime

  • T24, the TAFC runtime and their legacy components packaged together
  • Old Windows libraries, C runtime and database client encapsulated, not installed on the host
  • Application and database tiers handled as one controlled environment
02 / MODERNISE

Run it on current Windows Server

  • The package runs on Windows Server 2022 or 2025
  • The unsupported operating system leaves your estate
  • The host stays patched, supportable and audit-ready
03 / CONTINUE

Business as usual for the bank

  • No core banking rewrite and no code changes
  • No change to the ledger, the interface or daily operations
  • Well-governed delivery through testing and go-live
The Cloudhouse approach

A proven, repeatable pattern, built for critical systems.

Alchemy runs legacy Windows applications on any modern platform with no rewrites. Cloudhouse has kept business-critical applications running safely since 2010, and core banking workloads are among the most demanding we package. The same approach that keeps a finance or line-of-business system live keeps a ledger live too, without the risk of touching the code.

Results guaranteed, or your money back
No core banking rewrite, no runtime migration
Covers T24, the TAFC runtime and the database tier
Governed delivery across testing and go-live
Runs on current Windows Server 2022 or 2025
UK-based engineering and support
Book a 20-minute conversation See case studies
Your options

Re-platform, transform, risk it, or package it.

Every bank facing an unsupported platform under T24 is weighing the same paths. Set side by side, the trade-offs are clear.

TAFC to TAFJ or full transformation Carry on as-is Cloudhouse
Cost and effort Multi-year programme, material change to a live ledger Low now, higher later A fraction of a transformation, delivered in weeks
Risk to the ledger High, the core system changes Rising, the platform is unsupported Low, the core system is unchanged
Support and compliance posture Resolved, eventually Unsupported OS under a regulated system, at risk now Supported OS, legacy risk contained
Who sets the timeline The vendor The next audit or incident You do
Proof in regulated environments

Core banking workloads, packaged and kept live.

Cloudhouse has packaged Temenos T24 across multiple TAFC releases, alongside the wider legacy Windows estate that banks run. Names are withheld, the pattern holds: keep the core system running, take the unsupported platform off the estate, and avoid a forced transformation.

Core banking · Temenos T24

Multiple TAFC releases packaged

T24 packaged across several TAFC builds, including R10 and R12 era runtimes, and moved onto a supported platform without a core banking rewrite.

Financial services · Legacy estate

The systems around the core

Pricing, confirmation and quote tools, and other line-of-business applications that sit around the core ledger, packaged and kept supportable.

One supplier · Any legacy Windows app

Beyond the core

The same approach handles the rest of the bank's legacy Windows estate, from classic ASP and IIS workloads to other end-of-life applications.

Engagements are anonymised. Cloudhouse can arrange a reference conversation with a comparable customer under NDA on request.

Frequently asked questions

Temenos T24 on legacy Windows, answered.

Is Temenos T24 end of support?
No. T24, now part of Temenos Transact, is an actively supported platform. The exposure is usually the Windows Server and infrastructure beneath older T24 and TAFC builds, which have reached end of support, not the application itself.
Can we keep running T24 on TAFC without a core banking upgrade?
Yes. Cloudhouse packages T24 and its TAFC runtime into an isolated container and runs it on a supported operating system. The unsupported Windows layer leaves your estate, the server stays patched, and the ledger runs exactly as it does today.
Does this mean migrating from TAFC to TAFJ?
No. Packaging keeps the existing TAFC runtime as it is. A move from TAFC to the Java-based TAFJ runtime is a separate re-platform you can plan on your own terms, rather than under the pressure of an unsupported operating system.
Can Temenos T24 run on Windows Server 2022 or 2025?
Yes. Once packaged, a T24 environment built for an older Windows Server runs on Windows Server 2022 or 2025 without changing the application. The legacy components are encapsulated inside the container rather than installed on the host.
Does this affect our regulatory or audit position?
Running a core banking system on an unsupported operating system is a documented ICT risk under rules such as the EU's Digital Operational Resilience Act, which has applied since January 2025. Packaging moves the platform onto supported, patched Windows Server, which addresses that specific finding. Your compliance team confirms the wider position.
Does packaging change performance?
No. The application runs inside the package without emulation, so throughput and latency for the ledger are unchanged. Delivery is governed through testing, including performance testing, and results are guaranteed.
Get in touch

Before your next audit or resilience review, let's talk.

Tell us where the pressure is: an unsupported Windows Server under T24, a resilience or DORA finding on the core platform, or a transformation programme you are not ready to commit to. We will show you the approach on your own environment, under NDA, not a generic demo.

  • Running T24 on an unsupported Windows Server? We will show how to keep it supported.
  • Facing a resilience or DORA finding on the core? We will map a way to close it without touching the ledger.
  • Other legacy Windows apps around the core? We handle them the same way, one supplier.
  • Results guaranteed, so you can commit with confidence.
    • Our offices
    Venture X · White City, London
    Response within one working day

Book a conversation

20 minutes. We listen first. No slide deck unless you ask.
Request a conversation →

Temenos, T24, TAFC, TAFJ and Transact are trademarks of the Temenos group, and Microsoft, Windows Server and SQL Server are trademarks of the Microsoft group of companies, all used here for descriptive purposes only. Cloudhouse™ is not affiliated with or endorsed by Temenos or Microsoft.