This section provides clear definitions of key terms to help you navigate and understand stack-related concepts.

• Accelerator automation

  Helm charts and automation scripts are distributed to clients, enabling them to deploy our software faster and easier.

• AMR (Annual Maintenance Release)

  Temenos builds, deploys, and commits software daily, which it accumulates and publishes as part of its regular release cycle. Updates are committed to the monthly build, which combines to form the Annual Maintenance Release (AMR) published in April of each year.

• Certification

  A certification tests specific software combinations through system setup and basic manual testing. The results are published, with notes and recommendations, in a certification document.

• Preferred

  We prefer clients to use the stacks we promote through our stack tables. From R23 onwards, we’ve arranged stacks in tiers, to indicate both shared features, and the level of testing and support infrastructure we offer.

• Recommended

  These are the stacks we recommend to clients. They’re tested every month, which means we’ve built up considerable expertise in their implementation. Runbooks, certifications and benchmarking reports form part of a rich support infrastructure for clients.

• Reference Architecture

  A reference architecture is a diagram that outlines the network components, software, and hardware requirements for deploying Temenos products in a specific stack. Updated annually as part of the AMR (Annual Maintenance Release), it provides a standardized framework to ensure consistent and efficient deployments.

• Runbooks

  Stack runbooks provide clear, step-by-step instructions, configuring, and deploying stacks. Runbooks ensure a smooth deployments experience for supported Temenos products or solutions within a specific target environment.

• Supported

  Supported means that these stacks are maintained for end-of-life issues only. For example, where an app server is no longer supported by the vendor.

• Technical Approval

  A Technical Approval is a more detailed form of certification, using documented tests to validate a specific software combination. This includes running COB (Close-of-Business), injecting online transactions with a specific mix, running COB again, and navigating Transact UI using popular web browsers.

• Technical Guides

  Technical Guides provide in-depth information about a particular software component, including installation and configuration procedures.

• Testing

  Testing includes the tests we carry out on every software build, as part of our CI / CD pipelines. It may also include formal certification or technical approval processes, where the stack undergoes a series of documented tests, from environment setup to COB and transaction testing (where applicable).