Language Runtime Support Policy

# Language Runtime Support Policy

Catalyst serverless entities are built on Java, Node.js, or Python and their runtimes rely on the runtime of the specific versions of the programming environments. Catalyst implements a phased reduction in its support of a language's runtime, and therefore provides you with plenty of time to plan, implement, and test upgrades in your serverless entities.

Catalyst will begin implementing an end of support for a language version as soon as an end-of-life announcement is made for it by the community. It is always advisable to build and maintain your Catalyst serverless entities in the latest stable release of a programming environment. This ensures that high security and stability are retained in your Catalyst application performance. You must make appropriate changes in your function libraries and code to make them compatible with the version you upgrade them to.

Note: Catalyst's language runtime support policy currently applies to the Java, Node.js, and Python programming environments. This policy is applicable to Catalyst serverless entities, including Functions, AppSail, and Slate.

Catalyst will end support for a runtime in four phases as explained in this document.

### Phase 1: Deprecation Announcement

The deprecation announcement marks the start of the end of support of a language version. Catalyst will announce the deprecation of a runtime six months before the official end-of-life of the runtime.

For example, if the official end-of-life of the runtime as announced by the community is on April 1, 2022, then we will make the deprecation announcement on October 1, 2021.

The deprecation announcement will contain the details of the official retirement of the version and Catalyst's end of support for it. This provides you enough time to plan and prepare to upgrade your serverless entities to the latest stable version.

### Phase 2: Deprecation Period

The deprecation period of Catalyst's support for a language version begins right after the deprecation announcement is made. The deprecation period of a runtime in Catalyst will last for one year. For example, if the deprecation announcement was made on October 1, 2021, the deprecation period will last until October 1, 2022.

You will be able to create and update serverless entities in the deprecation period, and work with your existing Catalyst serverless entities of that version unhindered. However, you must use this period to upgrade all your serverless entities in your Catalyst applications to the latest stable version of the programming environment.

### Phase 3: Retirement Period

The retirement period of a deprecated runtime begins right after the one year of the deprecated period. The retirement period will last for three months. For example, if the deprecation period ends on October 1, 2022, the retirement period lasts until January 1, 2023.

You will not be able to create new serverless entities targeting the deprecated runtime of a language in the retirement period. You can still continue to run and make updates to the existing serverless entities of the deprecated version in your Catalyst applications.

We strongly recommend you to make sure all your serverless entities are fully updated and functional in the latest runtime during this period.

### Phase 4: End of support

The end of support for a deprecated runtime begins right after the three months of the retirement period. For example, if the retirement period ends on January 1, 2023, Catalyst will end its support for the runtime from then on.

You will no longer be able to create or update serverless entities of the deprecated version after it reaches the end of support phase. We also do not guarantee serverless entity invocations or application stability, if you continue to maintain deprecated runtimes in your application.

Catalyst will not apply the latest security patches and updates of a language runtime to a deprecated runtime. The serverless entities of a deprecated build may or may not continue to execute. However, we provide you the convenience of upgrading the version of the serverless entities alone at any time, after the end of support is reached.

Note: Catalyst retains the ability to make changes to the deprecation or retirement policies of a language runtime at any time, based on exceptions in rare cases. In case we decide to implement any changes to a prior announcement, we will communicate all the necessary details pertaining to these changes. These changes might include, but are not limited to, changes in the end-of-life as announced by a language community, or runtimes that reach their end of life but will continue to be supported on the platform until further notice.

You can refer to the Functions Implementation help page to learn about updating an existing serverless entity from the remote console.

### Language Version Support Policies and Timeline

You can always keep a track of a language release status, and their current or active versions from their official websites:

Java: Oracle Java SE Support Roadmap

Node.js: Node.js Releases document

Python: Python Developer's Guide — Version Status

### Java Runtime Deprecations

Catalyst currently supports Java versions 8, 11, 17, 21, and 25. You can upgrade your existing functions to the latest supported version from the remote console. You can also select the latest runtime when you create Java functions, or initialize them from the CLI.

There are no active Java runtime deprecations at this time. Catalyst will follow the same phased deprecation policy outlined in this document when a Java runtime version approaches its end of life. Please refer to the Oracle Java SE Support Roadmap to stay updated on the support status of each Java version.

### Node.js Runtime Deprecations

Catalyst has implemented a phased end of support for older versions of Node.js. The versions below are listed in descending order.

* Node.js v18: The deprecation phase of Node.js v18 began on September 11, 2025, coinciding with the community's official end-of-life announcement. Following the deprecation period of one year until September 11, 2026, Node.js v18 will enter the retirement period on September 11, 2026, and Catalyst will end its support for the runtime on December 11, 2026.
* Node.js v16: The deprecation phase of Node.js v16 began on April 30, 2025. Following the deprecation period of one year until April 30, 2026, Node.js v16 will enter the retirement period on April 30, 2026, and Catalyst will end its support for the runtime on July 30, 2026.
* Node.js v14: The deprecation phase of Node.js v14 began on April 30, 2025. Following the deprecation period of one year until April 30, 2026, Node.js v14 will enter the retirement period on April 30, 2026, and Catalyst will end its support for the runtime on July 30, 2026.
* Node.js v12: End of support completed. The deprecation phase of Node.js v12 began in April 2022. Following the deprecation period of one year until April 30, 2023, Node.js v12 was retired on July 31, 2023. Catalyst ended its support for the runtime on July 31, 2023.
* Node.js v10: End of support completed. The deprecation phase of Node.js v10 began in April 2021. Following an extended deprecation period until October 31, 2022, Node.js v10 was retired on January 31, 2023. Catalyst ended its support for the runtime on January 31, 2023.

Please ensure you upgrade the serverless entities in your Catalyst projects to the latest stable version of Node.js.

Note: Catalyst now provides support for Node.js v20, v22, and v24. You can upgrade your existing functions to the latest supported version from the remote console. You can also select the latest runtime when you create Node.js functions, or initialize them from the CLI.

### Python Runtime Deprecations

Catalyst currently supports Python versions 3.10, 3.11, 3.12, and 3.13. You can upgrade your existing functions to the latest supported version from the remote console. You can also select the latest runtime when you create Python functions, or initialize them from the CLI.

* Python 3.9: The deprecation phase of Python 3.9 began on June 1, 2026. Following the deprecation period of one year until June 1, 2027, Python 3.9 will enter the retirement period on June 1, 2027, and Catalyst will end its support for the runtime on September 1, 2027.

Please ensure you upgrade the serverless entities in your Catalyst projects to a supported version of Python (3.10 or later).

Note: Catalyst currently supports Python 3.10, Python 3.11, Python 3.12, and Python 3.13. You can upgrade your existing functions to the latest supported version from the remote console. You can also select the latest runtime when you create Python functions, or initialize them from the CLI.

Catalyst serverless entities are built on Java, Node.js, or Python and their runtimes rely on the runtime of the specific versions of the programming environments. Catalyst implements a phased reduction in its support of a language’s runtime, and therefore provides you with plenty of time to plan, implement, and test upgrades in your serverless entities.

Note: Catalyst's language runtime support policy currently applies to the Java, Node.js, and Python programming environments. This policy is applicable to Catalyst serverless entities, including Functions, AppSail, and Slate.

Catalyst will end support for a runtime in four phases as explained in this document.

Phase 1: Deprecation Announcement

The deprecation announcement marks the start of the end of support of a language version. Catalyst will announce the deprecation of a runtime six months before the official end-of-life of the runtime.

For example, if the official end-of-life of the runtime as announced by the community is on April 1, 2022, then we will make the deprecation announcement on October 1, 2021.

The deprecation announcement will contain the details of the official retirement of the version and Catalyst’s end of support for it. This provides you enough time to plan and prepare to upgrade your serverless entities to the latest stable version.

Phase 2: Deprecation Period

The deprecation period of Catalyst’s support for a language version begins right after the deprecation announcement is made. The deprecation period of a runtime in Catalyst will last for one year. For example, if the deprecation announcement was made on October 1, 2021, the deprecation period will last until October 1, 2022.

You will be able to create and update serverless entities in the deprecation period, and work with your existing Catalyst serverless entities of that version unhindered. However, you must use this period to upgrade all your serverless entities in your Catalyst applications to the latest stable version of the programming environment.

Phase 3: Retirement Period

The retirement period of a deprecated runtime begins right after the one year of the deprecated period. The retirement period will last for three months. For example, if the deprecation period ends on October 1, 2022, the retirement period lasts until January 1, 2023.

You will not be able to create new serverless entities targeting the deprecated runtime of a language in the retirement period. You can still continue to run and make updates to the existing serverless entities of the deprecated version in your Catalyst applications.

We strongly recommend you to make sure all your serverless entities are fully updated and functional in the latest runtime during this period.

Phase 4: End of support

You will no longer be able to create or update serverless entities of the deprecated version after it reaches the end of support phase. We also do not guarantee serverless entity invocations or application stability, if you continue to maintain deprecated runtimes in your application.

Note: Catalyst retains the ability to make changes to the deprecation or retirement policies of a language runtime at any time, based on exceptions in rare cases. In case we decide to implement any changes to a prior announcement, we will communicate all the necessary details pertaining to these changes. These changes might include, but are not limited to, changes in the end-of-life as announced by a language community, or runtimes that reach their end of life but will continue to be supported on the platform until further notice.

You can refer to the Functions Implementation help page to learn about updating an existing serverless entity from the remote console.

Language Version Support Policies and Timeline

You can always keep a track of a language release status, and their current or active versions from their official websites:

Java: Oracle Java SE Support Roadmap

Node.js: Node.js Releases document

Python: Python Developer’s Guide — Version Status

Java Runtime Deprecations

Node.js Runtime Deprecations

Catalyst has implemented a phased end of support for older versions of Node.js. The versions below are listed in descending order.

Node.js v18: The deprecation phase of Node.js v18 began on September 11, 2025, coinciding with the community’s official end-of-life announcement. Following the deprecation period of one year until September 11, 2026, Node.js v18 will enter the retirement period on September 11, 2026, and Catalyst will end its support for the runtime on December 11, 2026.
Node.js v16: The deprecation phase of Node.js v16 began on April 30, 2025. Following the deprecation period of one year until April 30, 2026, Node.js v16 will enter the retirement period on April 30, 2026, and Catalyst will end its support for the runtime on July 30, 2026.
Node.js v14: The deprecation phase of Node.js v14 began on April 30, 2025. Following the deprecation period of one year until April 30, 2026, Node.js v14 will enter the retirement period on April 30, 2026, and Catalyst will end its support for the runtime on July 30, 2026.
Node.js v12: End of support completed. The deprecation phase of Node.js v12 began in April 2022. Following the deprecation period of one year until April 30, 2023, Node.js v12 was retired on July 31, 2023. Catalyst ended its support for the runtime on July 31, 2023.
Node.js v10: End of support completed. The deprecation phase of Node.js v10 began in April 2021. Following an extended deprecation period until October 31, 2022, Node.js v10 was retired on January 31, 2023. Catalyst ended its support for the runtime on January 31, 2023.

Please ensure you upgrade the serverless entities in your Catalyst projects to the latest stable version of Node.js.

Note: Catalyst now provides support for Node.js v20, v22, and v24. You can upgrade your existing functions to the latest supported version from the remote console. You can also select the latest runtime when you create Node.js functions, or initialize them from the CLI.

Python Runtime Deprecations

Python 3.9: The deprecation phase of Python 3.9 began on June 1, 2026. Following the deprecation period of one year until June 1, 2027, Python 3.9 will enter the retirement period on June 1, 2027, and Catalyst will end its support for the runtime on September 1, 2027.

Please ensure you upgrade the serverless entities in your Catalyst projects to a supported version of Python (3.10 or later).

Note: Catalyst currently supports Python 3.10, Python 3.11, Python 3.12, and Python 3.13. You can upgrade your existing functions to the latest supported version from the remote console. You can also select the latest runtime when you create Python functions, or initialize them from the CLI.

Last Updated 2026-06-05 13:37:37 +0530 IST

Yes

Thank you for your feedback!

Send your feedback to us

Skip

Submit